Recent Posts

Pages: [1] 2 3 ... 10
1
z/OS Server / Re: Too many tables in Appl. group
« Last post by 2ma2 on Today at 05:58:34 AM »
Thank you both.
While fixing the problem, the use of the Segment field seems work now
2
MP Server / Re: Changing retention for historical loads
« Last post by jsquizz on Today at 05:33:30 AM »
If the expiration type is 'Load', then CMOD tells TSM to delete the object when it's eligible for deletion.  If the Expiration Type in the AG config is 'Segment' or 'Document', then the storage manager won't be instructed to delete objects, but will rely on it's own expiration.

-JD.

Excellent, thanks
3
Report Indexing / Re: Indexing issues
« Last post by DDP021 on Today at 05:16:14 AM »
HMMMM...The trigger we are using for doing the actual indexes is TRIGGER2....We look for the word ACCOUNT.  In the indexer we used for the mainframe file, we had this trigger set with a RECORDRANGE only looking in the first 6 lines.  If we left it as is, looking in ANY row in column 2 it would find it down the page certain times...

TRIGGER2=*,2,X'4143434F554E543A',(TYPE=FLOAT)                     /* ACCOUNT:     */

The other Trigger is just for channel 1
TRIGGER1=*,1,X'31',(TYPE=GROUP) 

And the last one is for the POSTING DATE because its only on the first page...The one works as we are getting that date for POSTING DATE and not the ingestion date...

so from this, do you think its the TRIGGER 2 causing the problem even though the index fields are being captured???
4
z/OS Server / Re: Too many tables in Appl. group
« Last post by Greg Ira on Today at 05:12:26 AM »
We've run into this as well and developed our own process to join tables.  One possible quick fix to keep things running until you correct the issue is to force users to use the field you designated as your segment field so your queries don't use all 260 segments.
5
MP Server / Re: Changing retention for historical loads
« Last post by Justin Derrick on Today at 05:10:16 AM »
If the expiration type is 'Load', then CMOD tells TSM to delete the object when it's eligible for deletion.  If the Expiration Type in the AG config is 'Segment' or 'Document', then the storage manager won't be instructed to delete objects, but will rely on it's own expiration.

-JD.
6
z/OS Server / Re: Too many tables in Appl. group
« Last post by Justin Derrick on Today at 05:03:36 AM »
I've run into this before, and I've developed a utility to do all the work for you.  Send me a private message for more info.  You can also tweak the DB2 statement heap size to keep the queries running temporarily -- although this is a temporary patch that will make things worse if you don't fix the root cause of the problem.

Also, you'll want to increase the default table size in the AG config under 'Advanced'.  There's an article on the Wiki about optimizing IBM CMOD Application Group table size:  https://cmod.wiki/index.php?title=Table_Segmentation_in_Content_Manager_OnDemand  Doing this will also likely result in an increase in performance in the future.  (That's the other reason I developed the utility to join tables.)

-JD.
7
Report Indexing / Re: Indexing issues
« Last post by Justin Derrick on Today at 04:56:15 AM »
Sounds like your Trigger is ambiguous -- causing it to index every page.  Usually you look for something that only occurs once per report / document.  Like "Page 1 ". (Note the trailing space, so it doesn't index pages 10, 11, 12 ... 100 - 199, 1000-1999, etc.)

-JD.
8
Report Indexing / Indexing issues
« Last post by DDP021 on Today at 04:17:27 AM »
Hi,  We have an app that wants to start sending a mainframe file directly to our server.  Currently its run though a mainframe job that creates the output and sends it CMOD.  So the file they send us shows carriage control characters (1) at top of every page.  We ran the file through the report wizard to get the indexing values.  When we ingest the file, it APPEARS to be indexing correctly but when you open up each index itself, they contain ALL the pages in the file...I've attached the indexer and also screen shot of the results when we pull up the version.  I also attached a screen shot of the VIEW INFORMATION tab on the Application definition...As indicated, when you click on each of the indexes, they all show the same thing.  The full file itself.  we can't figured out what the issue is.  any ideas??
9
z/OS Server / Too many tables in Appl. group
« Last post by 2ma2 on Today at 02:15:27 AM »
Hi

We suddenly ran into a problem with too many tables for one of the Appl. Groups. After table number 260 the SELECT statements became too long.

So question is: Has anyone expierenced this?
Also: can I concatenate all the 260 tables into one larger table BAA261 - close the table BAA260 and create an new Application group with a larger row number - and then modify the ARSSEG table to use only the new tables -and how.?

Or is there a better way to do this to avoid modifing ARSSEG?
10
z/OS Server / Re: ARSDOC complete document extract/retrieval
« Last post by bfoster@enchoice.com on September 25, 2018, 01:30:36 PM »
Is there a way in 10.1 to use the ARSDOC Get command in a JCL job or is OShell the only way.

Looking for some sample JCL

Bruce
Pages: [1] 2 3 ... 10