INDEXSTYLE=DOC special report breaking

Previous topic - Next topic

lfbeach

I have a user who wants me to break their 'DOC' style report,  when I come to a record of X'404B4B4B'.   Each document will start with this record.  I set up my application with 'TRIGGER1=*,01,X'404B4B',(TYPE=GROUP)' and I don't have BREAK=YES on anything.    I thought this would automatically cause the report to break on this trigger?  What am I doing wrong?  How can I accomplish what they want?  Why is it lumping documents together, not recognizing the x'404B4B' as the beginning of a new document?  Here is my indexer info...
FILEFORMAT=RECORD,133
CCTYPE=A
CONVERT=NO
INDEXSTARTBY=0
FORMDEF=0088
PAGEDEF=T184
INDEXSTYLE=DOC
INDXEXIT=ODS9XMPD
TRC=NO
CPGID=500
CC=YES
TRIGGER1=*,01,X'404B4B',(TYPE=GROUP)
TRIGGER2=*,14,X'C2D3E4C540C3D9D6E2E2',(TYPE=FLOAT)/*BLUE CROSS*/
TRIGGER3=*,61,X'C3D3C1C9D440D5D67A',(TYPE=FLOAT)/* CLAIM NO: */
TRIGGER4=*,45,X'E2E4C27A',(TYPE=FLOAT)/* SUB: */
TRIGGER5=*,23,X'5C5C5C5C5C5C5C',(TYPE=FLOAT)/* ******* */
FIELD1=0,71,013,(TRIGGER=3,BASE=0)
FIELD2=0,50,009,(TRIGGER=4,BASE=0)
FIELD3=0,02,007,(TRIGGER=5,BASE=0)
FIELD4=0,02,008,(TRIGGER=2,BASE=0)
INDEX1='CLAIM_NUMBER',FIELD1,(TYPE=GROUP, BREAK=NO)/* CLAIM_NUMBER */
INDEX2='SUB_ID',FIELD2,(TYPE=GROUP, BREAK=NO)/* SUB_ID */
INDEX3='NO_DATA',FIELD3,(TYPE=GROUP, BREAK=NO)/* NO_DATA */
INDEX4='POSTING_DATE',FIELD4,(TYPE=GROUP, BREAK=NO)/* POSTING_DATE */
Lori Frazier Beach
Developer-CMOD Admin
Document Management Systems

Greg Ira

TRIGGER1 doesn't automatically cause a document break.  You'll still need to set one of your indexes to BREAK=YES

lfbeach

Is there a BREAK=EVERY or something .... that would be nice.  I need it to break either at every start of document or every end of document.  We have x'404B' that starts the document and hex'405C5C' that ends the document.
Lori Frazier Beach
Developer-CMOD Admin
Document Management Systems

Greg Ira

Nothing like BREAK=EVERY that I'm aware of.  Since you want to break on every page I have to assume there is something you're already indexing on (claim #?) or something you could index on that, when set to break=yes, would accomplish what you want to do.

lfbeach

Unfortunately they don't want to break on claim number.  They want each 'document' to break....even if the same claim number is back to back.   I may open an enhancement request for 'BREAK=EVERY'.
Thanks for your response.
Lori Frazier Beach
Developer-CMOD Admin
Document Management Systems

Justin Derrick

Is there a document type parameter that you can break on?  I've had to do this for multi-part documents/forms in the past. 

-JD.
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Webinars:  https://CMOD.Training/
IBM CMOD Professional Services: https://CMOD.cloud

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

Nolan

If I understand correctly you want to put in a 2 condition break.We often use the BREAKYES=OR to accomplish this.  There must me something on the document that is different between the two which would allow you to accomplish this.  You can use triggers fields that are not required for indexing only finding the break points.
J.

#zOS #AIX #Windows #Multiplatforms
#DB2 #TSM #ODF #zODF #ODWEK
#CapacityPlanning #AFP #ReportDistribution
#Finance #ICN

ewirtz

Hi Lori,
if you write an input exit you can toggle between two different characters at the beginning of the page. So you have a break condition that works for instance between ' ' and '.'. You only have to find a place for this character on the report which can be accepted by the customer.
Example:
line
'Report xxxxxxx '
is changed to
'Report xxxxxxx .'
and back to
'Report xxxxxxx '
.
.

Regards

Egon

J9CMOD

Based on what we have found with our application definitions:  You have carriage control as A (Ansi), and are starting in column 1 for your trigger.  Make sure your trigger is really in line one (counting carriage control column).  As somebody else noted, you will want the BREAKYES=OR to be able to break on either trigger, and you will want to add a second trigger with your second character set that you want to break on.  If that is truly only an "end of page" for you, you don't need the second trigger as long as the first one always appears at the top of your desired new page.
Hope this helps with your situation.

lfbeach

thank you very much for helpful info.  Lori
Lori Frazier Beach
Developer-CMOD Admin
Document Management Systems