Author Topic: Indexing Entire Dataset as One Report Using Posting Date Only  (Read 3452 times)

Bobby.Campbell

  • Guest
Hi,

I am wanting to store a report in CMOD 8.4.0 for z/OS just using the posting date on the first page of the report as the index. I tried using the top of page as the trigger as this is were the date field is located (It is also located at the top of every page of the report)

I am using the OS/390 Indexer with datatype LINE - Record Format is Fixed with the record length of 133.

This index I used below loads the report but I am not getting the desired results as it loads a report for every page of the file and I just want one large report (max 400 Pages) so the user can search on a posting date then perform FINDS on the data they need to view.

The trigger I am using is located at the top of every page in the dataset.

I am ussing the batchload (ARSSLOAD) method to load the report into CMOD.

Is there a way to accoplish this using the OS/390 Indexer.

CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
FILEFORMAT=RECORD,133
GROUPMAXPAGES=999
TRIGGER1=*,1,X'F1',(TYPE=GROUP)                               /* 1         */
FIELD1=0,124,10,(TRIGGER=1,BASE=0)
INDEX1=X'D7D6E2E3C9D5C76DC4C1E3C54',FIELD1,(TYPE=GROUP,BREAK=NO)   /* POSTING_DATE */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE


Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2230
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Indexing Entire Dataset as One Report Using Posting Date Only
« Reply #1 on: May 23, 2012, 03:19:57 AM »
You'd normally trigger on something that only appears on the first page of a document, like "Page 1 ".  (Notice the space after the 1 to avoid triggering on pages 10-19, 100-199, 1000,1999!)

Are there page numbers on your report?
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

bzander

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Indexing Entire Dataset as One Report Using Posting Date Only
« Reply #2 on: May 23, 2012, 11:16:48 AM »
  We do this all the time.  Try using BREAK=YES  on your index

Greg Ira

  • Full Member
  • ***
  • Posts: 240
    • View Profile
Re: Indexing Entire Dataset as One Report Using Posting Date Only
« Reply #3 on: May 29, 2012, 05:35:17 AM »
  We do this all the time.  Try using BREAK=YES  on your index

This is correct.  We've learned that the OS/390 indexer requires at least one BREAK=YES or else it will break on every TRIGGER1 it finds.  We've been told this is considered working as normal for the OS/390 indexer.

Bobby.Campbell

  • Guest
Re: Indexing Entire Dataset as One Report Using Posting Date Only
« Reply #4 on: June 11, 2012, 11:19:29 AM »
Thank you all for the responses, I actually got the report to store by using an additional index and not adding it to the hit list.
I will try your suggestions on my test system to see if they work more efficient that my method.