1
Other / Re: Unable To Sort Columns
« on: April 11, 2019, 01:35:58 PM »
Thanks Greg. That worked.
Wow, that's a cryptic parameter.
Wow, that's a cryptic parameter.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
Other / Unable To Sort Columns
« on: April 05, 2019, 01:26:12 PM »
This one is pretty basic and should be an easy one.
Somehow, I managed to get every single folder, such that the column headers are grayed out and I can no longer sort. By date, report name, etc.
Looks like a default setting somehow?
Currently at V9, but going to V10 soon and even on that version, can not sort by column header as shown in attached example.
Somehow, I managed to get every single folder, such that the column headers are grayed out and I can no longer sort. By date, report name, etc.
Looks like a default setting somehow?
Currently at V9, but going to V10 soon and even on that version, can not sort by column header as shown in attached example.
3
Report Indexing / Re: APK421S Error Attempting AFP to AIX Archive
« on: April 12, 2017, 01:24:47 PM »
Restarted CMOD and entire AIX server we run on, and initial results are promising in that 2 files that wouldn't work, now do.
Surmising even though the error message is severely lacking in useful information, may have been a buildup of fragemented memory or something, since server had been up for over a year.
Web search of an unrelated AFP message for APK421S came up with one obscure hit for an AFP utility product referencing a memory error.
Surmising even though the error message is severely lacking in useful information, may have been a buildup of fragemented memory or something, since server had been up for over a year.
Web search of an unrelated AFP message for APK421S came up with one obscure hit for an AFP utility product referencing a memory error.
4
Report Indexing / Re: APK421S Error Attempting AFP to AIX Archive
« on: April 12, 2017, 08:14:44 AM »
Initially started with a large AFP file. But now starting to crop up with large text files (large, being 1.5 Gb. But at the same time, 3 Gb index files will work.
Attempted to archive text file that had a problem, manually with does not use ACIF directories, also fails with same error trying to close the file.
So, would have to ask, what file system(s)? And why does the error message not point to something specific?
Using the usual measuring displays, and navigating to local file system directories, don't see anything that sticks out.
Attempted to archive text file that had a problem, manually with does not use ACIF directories, also fails with same error trying to close the file.
So, would have to ask, what file system(s)? And why does the error message not point to something specific?
Using the usual measuring displays, and navigating to local file system directories, don't see anything that sticks out.
5
Report Indexing / Re: APK421S Error Attempting AFP to AIX Archive
« on: April 06, 2017, 07:26:06 AM »
My server team states I was misreading, and production server has much more memory available.
Back to needing to know more specifics on vague error message.
Worked on one system with the same amount of available ACIF space, didn't work on other (production) system.
Back to needing to know more specifics on vague error message.
Worked on one system with the same amount of available ACIF space, didn't work on other (production) system.
6
Report Indexing / Re: APK421S Error Attempting AFP to AIX Archive
« on: April 05, 2017, 10:33:27 AM »
For heck of it, attempted to archive 2GB on our test system, which our ACIF is the same size 20Gb.
But for some strange reason has realmem 8126464. Whereas on Production system Realmem 65011712.
The APF statement file archived and indexed:
Loaded 17603 rows into the database
Document compression type used - OD77. Bytes Stored = >1902230824< Rows = >17603
So thinking maybe the first error message APK421S Return Code 6 possibly is more specific diagnostics than the second message with Return Code 12.
But for some strange reason has realmem 8126464. Whereas on Production system Realmem 65011712.
The APF statement file archived and indexed:
Loaded 17603 rows into the database
Document compression type used - OD77. Bytes Stored = >1902230824< Rows = >17603
So thinking maybe the first error message APK421S Return Code 6 possibly is more specific diagnostics than the second message with Return Code 12.
7
Report Indexing / Re: APK421S Error Attempting AFP to AIX Archive
« on: April 05, 2017, 06:17:32 AM »
Thanks Ed. I know you're more on the mainframe side, so thanks for responding.
ACIF available space is a suspicion, but the CMOD error message is sufficiently vague to not confirm that.
ACIF directory (we have 4 total, but apparently it uses one) is an empty 20 Gb file, which on normal month ends is sufficient (there's a pre-processing step that carves up a larger file into smaller pieces that are consistent from month to month). The input AFP file is 2.6 Gb.
ACIF available space is a suspicion, but the CMOD error message is sufficiently vague to not confirm that.
ACIF directory (we have 4 total, but apparently it uses one) is an empty 20 Gb file, which on normal month ends is sufficient (there's a pre-processing step that carves up a larger file into smaller pieces that are consistent from month to month). The input AFP file is 2.6 Gb.
8
Report Indexing / APK421S Error Attempting AFP to AIX Archive
« on: April 04, 2017, 12:04:33 PM »
Have an AFP "statement" file, which we index. File is small typical days, large on "month end". 2 to 4 Gb.
Actually already breaking the file up into 4 or 5 pieces. And this general size even month end usually works.
Getting the following error, which may somehow be storage related. But the error message is sufficiently generic it doesn't confirm that. ACIF directories are empty, and 20 Gb.
ARS4315I Processing file >/download/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD<
ARS4334I Load Version <9.0.0.1> Operating System <AIX> <6.1> OS Userid <root> Install Location </opt/IBM/ondemand/V9.0/>
ARS4335I Server Version <9.0.0.1> Operating System <AIX> <6.1> Database <DB2> <10.01.0002>
ARS4302I 04/04/17 10:39:47 -- Indexing started, 2730488513 bytes to process
APK415I CC=YES
APK415I CCTYPE=A
APK415I CONVERT=YES
APK415I CPGID=500
APK415I MCF2REF=CF
APK415I TRC=NO
APK415I FILEFORMAT=STREAM
APK415I DCFPAGENAMES=NO
APK415I UNIQUEBNGS=YES
APK415I IMAGEOUT=ASIS
APK415I INDEXOBJ=ALL
APK415I INDEXSTARTBY=1
APK415I INSERTIMM=NO
APK415I FORMDEF=F1A10110
APK415I PAGEDEF=P1PEO301
APK415I USERLIB=/home/resources
APK415I RESTYPE=FDEF
APK415I inputdd=/download/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD
APK415I outputdd=/arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.out
APK415I indexdd=/arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.ind
APK415I resobjdd=/arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.res
APK421S AN ERROR OCCURRED WHILE ATTEMPTING TO CLOSE /arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.out RETURN CODE 6.
APK423S AN ERROR OCCURRED WHILE ATTEMPTING TO WRITE /arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.out RETURN CODE 12.
APK412I MODULE APKSRIAX HAS RETURNED WITH RETURN CODE 12.
APK423S AN ERROR OCCURRED WHILE ATTEMPTING TO WRITE OUTPUTDD RETURN CODE 12.
APK441I ACIF AT IM43P11 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
ARS4309E 04/04/17 10:40:01 Indexing failed
ARS4318E Processing failed for file >/download/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD<
Actually already breaking the file up into 4 or 5 pieces. And this general size even month end usually works.
Getting the following error, which may somehow be storage related. But the error message is sufficiently generic it doesn't confirm that. ACIF directories are empty, and 20 Gb.
ARS4315I Processing file >/download/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD<
ARS4334I Load Version <9.0.0.1> Operating System <AIX> <6.1> OS Userid <root> Install Location </opt/IBM/ondemand/V9.0/>
ARS4335I Server Version <9.0.0.1> Operating System <AIX> <6.1> Database <DB2> <10.01.0002>
ARS4302I 04/04/17 10:39:47 -- Indexing started, 2730488513 bytes to process
APK415I CC=YES
APK415I CCTYPE=A
APK415I CONVERT=YES
APK415I CPGID=500
APK415I MCF2REF=CF
APK415I TRC=NO
APK415I FILEFORMAT=STREAM
APK415I DCFPAGENAMES=NO
APK415I UNIQUEBNGS=YES
APK415I IMAGEOUT=ASIS
APK415I INDEXOBJ=ALL
APK415I INDEXSTARTBY=1
APK415I INSERTIMM=NO
APK415I FORMDEF=F1A10110
APK415I PAGEDEF=P1PEO301
APK415I USERLIB=/home/resources
APK415I RESTYPE=FDEF
APK415I inputdd=/download/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD
APK415I outputdd=/arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.out
APK415I indexdd=/arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.ind
APK415I resobjdd=/arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.res
APK421S AN ERROR OCCURRED WHILE ATTEMPTING TO CLOSE /arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.out RETURN CODE 6.
APK423S AN ERROR OCCURRED WHILE ATTEMPTING TO WRITE /arsacif/acif1/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD.out RETURN CODE 12.
APK412I MODULE APKSRIAX HAS RETURNED WITH RETURN CODE 12.
APK423S AN ERROR OCCURRED WHILE ATTEMPTING TO WRITE OUTPUTDD RETURN CODE 12.
APK441I ACIF AT IM43P11 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
ARS4309E 04/04/17 10:40:01 Indexing failed
ARS4318E Processing failed for file >/download/mvs.COMM_STMTS_ALL3.commckst.commckst.commckst.17094.085927.ARD<
9
Report Indexing / Re: ARSLOAD fine if indexing and archiving correctly. Process hangs if fails
« on: January 10, 2013, 11:42:42 AM »
Upgrade to latest and greatest still in progress. Current/old environment as mentioned in the orginal post: CMOD (V8.3) on AIX.
PMR avenue not available due to release levels. IBM refused to assist. We did diagnose to the point that it was apparent the Level 1/Level 2 support on the phone did not know what to do.
We've been doing workarounds since September when TSM database saturated to 100% unknowingly for 3 system processes not fully working.
1) Clearing Cache via ARSMAINT: we have a scheduled process that was this: /usr/lpp/ars/bin/arsmaint -cms -x 0 -n 0
with the system parameter set to 80% I believe.
Started getting syslog error message 106.
Unlink failed for file arscache/cache1/retr/APE/DOC/nnnnFAAA
Process hangs and must be killed manually.
However, doing arsmaint manually vs specific groups works for the most part
/usr/lpp/ars/bin/arsmaint -cms -g abcde -x 0 -n 0
Summary: cache still there, working somewhat, but compromised
2) ARSLOAD - if it needs to fail only. Do get an 88 msg in syslog, but must manually kill the process in AIX. Only then the bad file gets renamed to xxx.yyy.zzz.FAILED
3) We intermittently lose connectivity to DB2 database.
PMR avenue not available due to release levels. IBM refused to assist. We did diagnose to the point that it was apparent the Level 1/Level 2 support on the phone did not know what to do.
We've been doing workarounds since September when TSM database saturated to 100% unknowingly for 3 system processes not fully working.
1) Clearing Cache via ARSMAINT: we have a scheduled process that was this: /usr/lpp/ars/bin/arsmaint -cms -x 0 -n 0
with the system parameter set to 80% I believe.
Started getting syslog error message 106.
Unlink failed for file arscache/cache1/retr/APE/DOC/nnnnFAAA
Process hangs and must be killed manually.
However, doing arsmaint manually vs specific groups works for the most part
/usr/lpp/ars/bin/arsmaint -cms -g abcde -x 0 -n 0
Summary: cache still there, working somewhat, but compromised
2) ARSLOAD - if it needs to fail only. Do get an 88 msg in syslog, but must manually kill the process in AIX. Only then the bad file gets renamed to xxx.yyy.zzz.FAILED
3) We intermittently lose connectivity to DB2 database.
10
Report Indexing / ARSLOAD fine if indexing and archiving correctly. Process hangs if fails
« on: October 04, 2012, 07:10:43 AM »
We experienced problems on our backleveled CMOD (AIX, DB2, TSM) which we are planning to upgrade soon. This ultimately was due to the TSM database filling up and saturating at 100% utilization. As part of the resolution process, we recycled the production server.
Since that time, as long as ARSLOAD is successful it works normally. However, for the small percentage of files that need to fail, it puts the standard 88 message in the syslog, then the process hangs and must be manually killed.
Only then does it react as it used to, appending the back input file name as .FAILED and continuing onto the next file to load. No obvious syslog error messages.
Not sure if related, but we have another process which is also hanging. If we run ARSMAINT w/o specifying a Application Group, it hangs. We had a scheduled process to reduce it to the standard 80% once nightly. If we run ARSMAINT vs an application group or groups, it works for the most part. Although we seen to have lost link to DB2 occasionally and had to recycle that connection.
It seems that may be due to the dreaded "broken links in cache" issue, which doesn't seem to have a well documented solution.
Since that time, as long as ARSLOAD is successful it works normally. However, for the small percentage of files that need to fail, it puts the standard 88 message in the syslog, then the process hangs and must be manually killed.
Only then does it react as it used to, appending the back input file name as .FAILED and continuing onto the next file to load. No obvious syslog error messages.
Not sure if related, but we have another process which is also hanging. If we run ARSMAINT w/o specifying a Application Group, it hangs. We had a scheduled process to reduce it to the standard 80% once nightly. If we run ARSMAINT vs an application group or groups, it works for the most part. Although we seen to have lost link to DB2 occasionally and had to recycle that connection.
It seems that may be due to the dreaded "broken links in cache" issue, which doesn't seem to have a well documented solution.
11
Report Indexing / Re: Invalid Structured Field Header in .ind file
« on: March 27, 2012, 06:16:28 AM »
Thanks very much for taking the time to reply/suggest. Unfortunately, some of these files are 100's of millions of bytes (importing customer statements from another system). And the error message listed doesn't give any sort of clue where the field being flagged as bad is. Plus the load may or may not work on rerun.
So really at this point, I have no way to diagnose this vague error.
So really at this point, I have no way to diagnose this vague error.
12
Report Indexing / Invalid Structured Field Header in .ind file
« on: March 26, 2012, 07:51:28 AM »
I see that others have reported this issue, under different circumstances.
I have a large amount of data to archive which was converted from another system. This data consists of ASCII text data that is being archived with Indexing parameters (EG: not generically). These are customer statements separated by day. For example, one day may have 15 statements, which are loaded by row breaking on a new account number. Another day may have a few hundred of the same.
Am getting intermittent Invalid Structured Field Header in .ind file. There may be one or two out of a large group. Or with more frequency.
It leaves the .ind files and .out files hanging which must be cleaned up. Have had failures, that then worked on second or third attempt without changing anything. Have other failures that keep getting the error.
Initially, I thought it had to do with an Index field that I'm capturing, DATE; changing formats from a 2 digit year to a 4 digit year, but that doesn't seem like it's the case.
The error message is somewhat non specific on how to diagnose and proceed -
arsload: Processing file >STMT_savaccountstatements_0001.20101227.txt<
arsload: 03/26/12 10:32:34 -- Indexing started, 371798 bytes to process
0425-415 CC=YES
0425-415 CCTYPE=Z
0425-415 CONVERT=NO
0425-415 CPGID=850
0425-415 MCF2REF=CPCS
0425-415 TRC=NO
0425-415 FILEFORMAT=STREAM,(NEWLINE=X'0A')
0425-415 TRIGGER1=*,72,X'504147453A2020202031',(TYPE=GROUP)
0425-415 FIELD1=1,55,15,(TRIGGER=1,BASE=0)
0425-415 FIELD2=1,72,10,(TRIGGER=1,BASE=0)
0425-415 FIELD3=14,23,35,(TRIGGER=1,BASE=0)
0425-415 INDEX1=X'6163634E554D',FIELD1,(TYPE=GROUP,BREAK=YES)
0425-415 INDEX2=X'7264617465',FIELD2,(TYPE=GROUP,BREAK=NO)
0425-415 INDEX3=X'4E614D65',FIELD3,(TYPE=GROUP,BREAK=NO)
0425-415 DCFPAGENAMES=NO
0425-415 UNIQUEBNGS=YES
0425-415 IMAGEOUT=ASIS
0425-415 INDEXOBJ=GROUP
0425-415 INDEXSTARTBY=1
0425-415 INSERTIMM=NO
0425-415 RESTYPE=NONE
0425-415 INPEXIT=/usr/lpp/ars/exits/acif/asciinp
0425-415 inputdd=/nnedwnld/011/Statements/STMT_savaccountstatements_0001.20101227.txt
0425-415 outputdd=./STMT_savaccountstatements_0001.20101227.txt.out
0425-415 indexdd=./STMT_savaccountstatements_0001.20101227.txt.ind
0425-415 resobjdd=/dev/null
0425-440 ACIF AT PK72203 HAS COMPLETED NORMALLY WITH RETURN CODE 0.
arsload: 03/26/12 10:32:34 Indexing completed
arsload: 03/26/12 10:32:34 -- Loading started, 371565 bytes to process
Invalid structured field header in the file ./STMT_savaccountstatements_0001.20101227.txt.ind
Loaded 0 rows into the database
arsload: 03/26/12 10:32:34 Loading failed
arsload: Processing failed for file >STMT_savaccountstatements_0001.20101227.txt<
I have a large amount of data to archive which was converted from another system. This data consists of ASCII text data that is being archived with Indexing parameters (EG: not generically). These are customer statements separated by day. For example, one day may have 15 statements, which are loaded by row breaking on a new account number. Another day may have a few hundred of the same.
Am getting intermittent Invalid Structured Field Header in .ind file. There may be one or two out of a large group. Or with more frequency.
It leaves the .ind files and .out files hanging which must be cleaned up. Have had failures, that then worked on second or third attempt without changing anything. Have other failures that keep getting the error.
Initially, I thought it had to do with an Index field that I'm capturing, DATE; changing formats from a 2 digit year to a 4 digit year, but that doesn't seem like it's the case.
The error message is somewhat non specific on how to diagnose and proceed -
arsload: Processing file >STMT_savaccountstatements_0001.20101227.txt<
arsload: 03/26/12 10:32:34 -- Indexing started, 371798 bytes to process
0425-415 CC=YES
0425-415 CCTYPE=Z
0425-415 CONVERT=NO
0425-415 CPGID=850
0425-415 MCF2REF=CPCS
0425-415 TRC=NO
0425-415 FILEFORMAT=STREAM,(NEWLINE=X'0A')
0425-415 TRIGGER1=*,72,X'504147453A2020202031',(TYPE=GROUP)
0425-415 FIELD1=1,55,15,(TRIGGER=1,BASE=0)
0425-415 FIELD2=1,72,10,(TRIGGER=1,BASE=0)
0425-415 FIELD3=14,23,35,(TRIGGER=1,BASE=0)
0425-415 INDEX1=X'6163634E554D',FIELD1,(TYPE=GROUP,BREAK=YES)
0425-415 INDEX2=X'7264617465',FIELD2,(TYPE=GROUP,BREAK=NO)
0425-415 INDEX3=X'4E614D65',FIELD3,(TYPE=GROUP,BREAK=NO)
0425-415 DCFPAGENAMES=NO
0425-415 UNIQUEBNGS=YES
0425-415 IMAGEOUT=ASIS
0425-415 INDEXOBJ=GROUP
0425-415 INDEXSTARTBY=1
0425-415 INSERTIMM=NO
0425-415 RESTYPE=NONE
0425-415 INPEXIT=/usr/lpp/ars/exits/acif/asciinp
0425-415 inputdd=/nnedwnld/011/Statements/STMT_savaccountstatements_0001.20101227.txt
0425-415 outputdd=./STMT_savaccountstatements_0001.20101227.txt.out
0425-415 indexdd=./STMT_savaccountstatements_0001.20101227.txt.ind
0425-415 resobjdd=/dev/null
0425-440 ACIF AT PK72203 HAS COMPLETED NORMALLY WITH RETURN CODE 0.
arsload: 03/26/12 10:32:34 Indexing completed
arsload: 03/26/12 10:32:34 -- Loading started, 371565 bytes to process
Invalid structured field header in the file ./STMT_savaccountstatements_0001.20101227.txt.ind
Loaded 0 rows into the database
arsload: 03/26/12 10:32:34 Loading failed
arsload: Processing failed for file >STMT_savaccountstatements_0001.20101227.txt<
13
Report Indexing / Set Default Printing Orientation in Application or AG?
« on: March 16, 2012, 08:08:33 AM »
Have some statements archived, which when printed from the thick client, need to alter the orientation setting from Best Fit, to Portrait.
Can this Portrait setting be set somehow as the default for this particular application / report?
I know you can change it once in the client, and then it will retain the setting between attempting to print something. Don't see where you can make this the default for just this one application/ report.
Best Fit prints Landscape with larger letters, which will work also, just not optimun.
Hoping there may be a way to do this easily that I'm overlooking reviewing tabs in AG/APP/FOLDER.
Can this Portrait setting be set somehow as the default for this particular application / report?
I know you can change it once in the client, and then it will retain the setting between attempting to print something. Don't see where you can make this the default for just this one application/ report.
Best Fit prints Landscape with larger letters, which will work also, just not optimun.
Hoping there may be a way to do this easily that I'm overlooking reviewing tabs in AG/APP/FOLDER.
14
Report Indexing / Re: Trigger1 Using ASCII Carriage Control
« 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
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
15
Report Indexing / 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
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
Pages: [1] 2