Author Topic: Trigger1 Using ASCII Carriage Control  (Read 4761 times)

jpdevin

  • Jr. Member
  • **
  • Posts: 18
    • View Profile
Trigger1 Using ASCII Carriage Control
« on: February 13, 2012, 01:46:52 PM »
 Apparently this works for EPCDIC data, but having problem with ASCII carriage control.

 A previous poster reiterated how this would be done for EPCDIC:
Or, why not define your trigger as the carriage control in column 1, such as:
TRIGGER1=*,1,X'F1',(TYPE=GROUP)


Attempting to do the same with ASCII data. But if we have on our application indexing CC=YES, and use the carriage control exit for ASCII, Trigger1 can not be found. Have tried CC=NO.
 And also tried CC=YES, without the exit which causes the typical
0425-346 DATA IN AN INPUT RECORD OR PAGEDEF RESOURCE IS INVALID: A SKIP TO A NONEXISTENT CHANNEL = '0C'X ON RECORD NUMBER = 1
 

02/13/12 11:41:27 -- Indexing started, 126320 bytes to process
CC=YES
CCTYPE=Z
CONVERT=NO
CPGID=850
MCF2REF=CPCS
TRC=NO
FILEFORMAT=STREAM,(NEWLINE=X'0A')
TRIGGER1=*,1,X'0A',(TYPE=GROUP)
TRIGGER2=0,63,X'4143434F554E54',(TYPE=FLOAT)
TRIGGER3=14,57,X'524547554C4152',(TYPE=FLOAT)
FIELD1=0,10,8,(TRIGGER=2,BASE=0)
FIELD2=0,72,10,(TRIGGER=2,BASE=0)
FIELD3=1,26,35,(TRIGGER=2,BASE=0)
FIELD4=16,57,8,(TRIGGER=3,BASE=0)
FIELD5=19,71,10,(TRIGGER=3,BASE=0)
FIELD6=14,57,35,(TRIGGER=3,BASE=0)
INDEX1=X'7264617465',FIELD1,FIELD4,(TYPE=GROUP,BREAK=NO)
INDEX2=X'61636374',FIELD2,FIELD5,(TYPE=GROUP,BREAK=YES)
INDEX3=X'74797065',FIELD3,FIELD6,(TYPE=GROUP,BREAK=NO)
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE
INPEXIT=/usr/lpp/ars/exits/acif/asciinp
inputdd=/download/mvs.BOSISC.BOSISC.BOSISC.12044.114122.ARD
outputdd=/arsacif/acif1/mvs.BOSISC.BOSISC.BOSISC.12044.114122.ARD.out
indexdd=/arsacif/acif1/mvs.BOSISC.BOSISC.BOSISC.12044.114122.ARD.ind
resobjdd=/dev/null
INDEXING WAS REQUESTED, BUT NO GROUP 'TRIGGERn' NOR ANY 'FIELD' BASED ON IT WAS SATISFIED WITHIN THE PAGE RANGE SPECIFIED
ACIF AT PK72203 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.

02/13/12 11:41:27 Indexing failed

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Trigger1 Using ASCII Carriage Control
« Reply #1 on: February 14, 2012, 07:40:26 AM »
A quick look at your indexing parameters shows that you're using the same character for newlines as you're searching for in column 1:

FILEFORMAT=STREAM,(NEWLINE=X'0A')
TRIGGER1=*,1,X'0A',(TYPE=GROUP)


I think you'll want to change the character you're looking for in TRIGGER1.

-JD.
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

jpdevin

  • Jr. Member
  • **
  • Posts: 18
    • View Profile
Re: Trigger1 Using ASCII Carriage Control
« Reply #2 on: February 14, 2012, 01:16:26 PM »
 Also tried 0C, which is what we really want (new page). Just didn't show that in first example posted -
02/13/12 12:45:38 -- Indexing started, 126320 bytes to process
CC=YES
CCTYPE=Z
CONVERT=NO
CPGID=850
MCF2REF=CPCS
TRC=NO
FILEFORMAT=STREAM,(NEWLINE=X'0A')
TRIGGER1=*,1,X'0C',(TYPE=GROUP)
TRIGGER2=0,63,X'4143434F554E54',(TYPE=FLOAT)
TRIGGER3=14,57,X'524547554C4152',(TYPE=FLOAT)
FIELD1=0,10,8,(TRIGGER=2,BASE=0)
FIELD2=0,72,10,(TRIGGER=2,BASE=0)
FIELD3=1,26,35,(TRIGGER=2,BASE=0)
FIELD4=16,57,8,(TRIGGER=3,BASE=0)
FIELD5=19,71,10,(TRIGGER=3,BASE=0)
FIELD6=14,57,35,(TRIGGER=3,BASE=0)
INDEX1=X'7264617465',FIELD1,FIELD4,(TYPE=GROUP,BREAK=NO)
INDEX2=X'61636374',FIELD2,FIELD5,(TYPE=GROUP,BREAK=YES)
INDEX3=X'74797065',FIELD3,FIELD6,(TYPE=GROUP,BREAK=NO)
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=GROUP
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE
INPEXIT=/usr/lpp/ars/exits/acif/asciinp
inputdd=/download/mvs.BOSISC.BOSISC.BOSISC.12044.124535.ARD
outputdd=/arsacif/acif1/mvs.BOSISC.BOSISC.BOSISC.12044.124535.ARD.out
indexdd=/arsacif/acif1/mvs.BOSISC.BOSISC.BOSISC.12044.124535.ARD.ind
resobjdd=/dev/null
INDEXING WAS REQUESTED, BUT NO GROUP 'TRIGGERn' NOR ANY 'FIELD'
ACIF AT PK72203 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
02/13/12 12:45:38 Indexing failed

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Trigger1 Using ASCII Carriage Control
« Reply #3 on: February 16, 2012, 04:39:13 AM »
The only other thing I've seen regularly is that cover pages prevent 'indexstartby' from working properly.  Increase this to 2 or 3 if you have cover pages before your report.

Otherwise, I think I'd need to see some sample data.

-JD.
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

jeffs42885

  • Guest
Re: Trigger1 Using ASCII Carriage Control
« Reply #4 on: June 19, 2014, 08:06:21 AM »
Extremely old post but, I have came across this with ASCII reports using the asciinp exit.

I am sure by now your issue is resolved but try this for future reference:

Original:

TRIGGER1=*,1,X'0A',(TYPE=GROUP)

New:

TRIGGER1=*,*,X'0A',(TYPE=GROUP)