Warning: incoming "stupid" question.
Although having worked with CMOD for many years, I have not worked a huge lot with AFP files.
I have currently received an - allegedly - fully composed AFP file, with all its resources inline.
Now, how the eitch do I set up the Indexer information to properly process and index this file?
It seems that no matter what parameters I use, I end up with either APK459S or with APK210S+APK420S.
Which one seems to boil down to whether I use "CONVERT="NO"or YES.
Error message type one - you can see my settings as a part of this:
: ARS4302I Indexing started, 2174218 bytes to process
: APK415I CC=YES
: APK415I CCTYPE=A
: APK415I TRC=YES
: APK415I DCFPAGENAMES=YES
: APK415I UNIQUEBNGS=YES
: APK415I IMAGEOUT=ASIS
: APK415I INDEXOBJ=ALL
: APK415I FORMDEF=DUMMY
: APK415I RESTYPE=ALL
: APK415I INPUTDD=D:\OnDemandDirectories\arsload\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD
: APK415I OUTPUTDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.out
: APK415I INDEXDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.ind
: APK415I RESOBJDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.res
: APK210S DATA IN AN INPUT RECORD OR RESOURCE IS INVALID: A REQUIRED TRIPLET OR SELF-DEFINING PARAMETER WITH ID '85'X WAS MISSING FROM A MFC STRUCTURED FIELD.
: APK420S AN ERROR OCCURRED WHILE ATTEMPTING TO OPEN T1001143 RETURN CODE 28.
: APK412I MODULE APKSRIAX HAS RETURNED WITH RETURN CODE 255.
: APK104S DATA IN AN INPUT RECORD OR RESOURCE IS INVALID: ECF STRUCTURED FIELD IS NOT ALLOWED OR FORMS AN INVALID SEQUENCE.
: APK105I THE ERROR REPORTED ABOVE OCCURRED IN LOGICAL RECORD NUMBER 75, WHOSE SEQUENCE NUMBER IS 75, AND RESOURCE NAME IS F1FAL.
: APK441I ACIF AT IPTR923 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
: ARS4309E Indexing failed
Error message type two:
: ARS4302I Indexing started, 2174218 bytes to process
: APK415I CC=YES
: APK415I CCTYPE=A
: APK415I TRC=YES
: APK415I CONVERT=NO
: APK415I DCFPAGENAMES=YES
: APK415I UNIQUEBNGS=YES
: APK415I IMAGEOUT=ASIS
: APK415I INDEXOBJ=ALL
: APK415I FORMDEF=DUMMY
: APK415I RESTYPE=ALL
: APK415I INPUTDD=D:\OnDemandDirectories\arsload\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD
: APK415I OUTPUTDD=NUL
: APK415I INDEXDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.ind
: APK415I RESOBJDD=NUL
: APK459S INDEX NEEDED FOR THE GROUPNAME WAS NOT FOUND.
: APK441I ACIF AT IPTR923 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
: ARS4309E Indexing failed
: ARS4324E File >D:\OnDemandDirectories\arsload\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD<
So what am I doing wrong here? Or is the file indeed corrupted some way?
The TLE tags part looks OK though:
796 BDT Begin Document ACME_VPAK 0012 D3A8A8
797 BNG Begin Named Page Group G0000001 0010 D3A8AD
798 TLE Tag Logical Element 0019 D3A090
TLE Fully Qualified Name Triplet (02)
TLE 0B Attribute Name
TLE Name = 'KANALVAL'
TLE Attribute Value Triplet (36)
TLE Value = '1'
799 TLE Tag Logical Element 0017 D3A090
TLE Fully Qualified Name Triplet (02)
TLE 0B Attribute Name
TLE Name = 'DIGBREV'
TLE Attribute Value Triplet (36)
TLE Value = ''
800 TLE Tag Logical Element 002F D3A090
TLE Fully Qualified Name Triplet (02)
TLE 0B Attribute Name
TLE Name = 'KALLA'
TLE Attribute Value Triplet (36)
TLE Value = 'B20171214FECDB113113800012'
801 TLE Tag Logical Element 001F D3A090
TLE Fully Qualified Name Triplet (02)
TLE 0B Attribute Name
TLE Name = 'PNR'
TLE Attribute Value Triplet (36)
TLE Value = '197503271234'
802 IMM Invoke Medium Map A4_S_B1 0010 D3ABCC
803 BPG Begin Page P0000001 0010 D3A8AF
804 NOP No Operation 0011 D3EEEE
NOP 'ISISTEST'
...
848 EPG End Page P0000001 0010 D3A9AF
879 ENG End Named Group G0000001 0010 D3A9AD
880 EDT End Document ACME_VPAK 0010 D3A9A8
...(more pages)
Lars - run your input through the arsafpd tool.
If arsafpd isn't happy with the input, then ACIF probably won't be either.
Ed
Hi Ed - arsafpd is VERY happy with the content! :) In fact, the TLE listing in my post is created by arsafpd.
Also, the AFP file looks fine using for example IBM's "AFP Workbench for Windows" (included in odwin client installations).
Found this file, trying it out:
http://www-01.ibm.com/support/docview.wss?uid=swg21688078&aid=1
There is of course this variant of error too. After reading the document above, it seems to imply that the Formdef is not to be found in the file, after all?
9: ARS4302I Indexing started, 2174218 bytes to process
: APK415I CC=NO
: APK415I CCTYPE=A
: APK415I CONVERT=YES
: APK415I TRC=NO
: APK415I CPGID=278
: APK415I DCFPAGENAMES=YES
: APK415I UNIQUEBNGS=YES
: APK415I IMAGEOUT=ASIS
: APK415I FORMDEF=DUMMY
: APK415I RESTYPE=ALL
: APK415I INPUTDD=D:\OnDemandDirectories\arsload\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD
: APK415I OUTPUTDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.out
: APK415I INDEXDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.ind
: APK415I RESOBJDD=E:\arstmp\ACME.VPAK_X.kivratestfil3.kivratest3.20171214.131155.ARD.res
: APK420S AN ERROR OCCURRED WHILE ATTEMPTING TO OPEN DUMMY RETURN CODE 28.
: APK412I MODULE APKSRIAX HAS RETURNED WITH RETURN CODE 255.
: APK532S A FORM DEFINITION WITH A MEMBER NAME (DUMMY) WAS NOT FOUND OR WAS INVALID - RETURN CODE 28.
: APK441I ACIF AT IPTR923 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
1: ARS4309E Indexing failed
RC 28 means "File not found", and it only searches for a File named "DUMMY" if it did not find a valid Formdef inside the AFP file itself.
How can I browse/check the input file to see if it contains an FDEF - do I use a HexEditor and scan for a certain combo? (Which Hex combo in that case?)
Maybe you should remove this line from ACIF:
FORMDEF=DUMMY
... and see how it runs. ;D
-JD.
Thanks JD. Tried your suggestion, as well as FORMDEF=F1FAL, but the error remains.
After carefully examining the output from arsafpd, I think it may be an error in the structure of the AFP file. The "MFC" section looks different in the erring position than it does in another instance of "MFC". So I have sent the file back to its originator for review. Will get back if we find (or confirm) the error.
Okay - specifying a proper FormDef name was a good move, but you probably need to include a USERLIB or FDEFLIB parameter to provide a path to that formdef as well.
-JD.
If FORMDEF is not inline in AFP, copy the formdef and keep inside any dir, and mention the actual formdef name path.
Here is a sample of our AFP loading. We don't do fully resolved so it might not help but they work for us :)
CC=YES
CCTYPE=A
CONVERT=YES
FILEFORMAT=STREAM, (NEWLINE=X'5A')
CPGID=500
MCF2REF=CPCS
DCFPAGENAMES=YES
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INSERTIMM=NO
INDEXOBJ=ALL
FORMDEF=f1blank
FDEFLIB=/load/reports/res/sp_ss
PDEFLIB=/load/reports/res/sp_ss
FONTLIB=/load/reports/res/sp_ss
OVLYLIB=/load/reports/res/sp_ss
/* RESTYPE=FDEF,PSEG,OVLY */
RESTYPE=ALL
USERLIB=/download/reports/res/sp_ss