OnDemand User Group
Support Forums => Report Indexing => Topic started by: DDP021 on November 22, 2023, 04:15:49 AM
-
Hello,
We have a user requesting to setup a true AFP data report to CMOD with NO indexing. Has anyone ever done this before? We believe there is one TLE record called DOC CNTL. I've attached a sample screen shot for reference.
-
Just a followup- We attempted to use the DOC CNTL record off the data as an index and then not map it in the folder. But when attempting to load file, received the below message:
APK462S A TRIGGER PARAMETER WAS SPECIFIED, BUT THE INPUT FILE IS ALREADY INDEXED.
APK441I ACIF AT PH34181 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
! LÓÓ ACS PCSFFUDR2023-11-0611:00:5621CSFFUS40 W/ER
! Lyy N 4
! LÓÓ PK93028
! L¿ö CDSCG1
! LyÝ 00000000 000000001
! Lµ° DOC CNTL NOOP: BB930000001MultSite
! LzÝ 00000000 000000001
! Ly® P
! LyI P
! ¯L¿« f C0H400D0 e T1V10500 d - f C0H20000
! L£¬ S10BMAE1
! Lw® } \
! L£º } \
! LzI P
! L®¬ S10BMAE1 ©
! Lyº P
! ^LÓº L G L © 1 G { L I³ü E + ûSECOND REQUEST G {
! Lzº P
! Lz® P
! Ly® P
! LyI P
! \L¿« f C0H400D0 e T1V10500 d - f C0H40090
! L£¬ S10BMAE1
! Lw® } \
-
Are you receiving a .ind file with the AFP output that you're storing? If you are, you don't need any ACIF indexing parameters, just load it with the Generic indexer.
-JD.
-
Justin,
We receive 2 files, a data file and a resource file. These TRUE AFP files, no text
-
I'm not sure what you mean by 'True' AFP... I know of two types of AFP - Fully Composed AFP, and Mixed Mode AFP.
Can you show the ACIF Parameters you're using, and the full output of your load command?
-JD.
-
My apologies Justin, have been out on vacation. The data would be FULLY COMPOSED. Below is the ACIF Indexer we are atteempting to use. I've also included the error from 88 msg. We are thinking the data is bad??
AFP.MCF2REF=CF
CONVERT=YES
USERLIB=/usr/lpp/ars/reslib/fdeflib:/usr/lpp/ars/reslib/fontlib:/usr/lpp/ars/reslib/overlib:/usr/lpp/ars/reslib/pdeflib:/usr/lpp/ars/reslib/pseglib
INDEXOBJ=ALL
CPGID=500
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=ALL
INDEXSTARTBY=0
INSERTIMM=NO
RESTYPE=ALL
FORMDEF=F1CSFEAS
From 88 msg in CMOD Log
: APK267S EITHER NO ENVIRONMENT GROUP WAS SPECIFIED FOR THE PAGE OR AN ERROR OCCURRED IN THE ENVIRONMENT GROUP.
: APK105I THE ERROR REPORTED ABOVE OCCURRED IN LOGICAL RECORD NUMBER 29, WHOSE SEQUENCE NUMBER IS NOT AVAILABLE, AND RESOURCE NAME IS UNKNOWN.
: APK441I ACIF AT PH34181 HAS COMPLETED ABNORMALLY WITH RETURN CODE 8.
-
I don't see any FIELD/INDEX parameters, which I think is okay because you're using INDEXOBJ=ALL (which you have *twice* by the way)...
But what fields do you have defined in the App Group? Just a date and that Doc Cntl? (Fields shouldn't have spaces either...)
The other issue could be that the index data is stored in a NOP (no-op) instead of a TLE (tagged logical element).
It's been a while since I had to index AFP, but it seems like there's a lot going on here...
-JD.
-
I agree Justin...We've been trying to copy from an existing AFP setup in CMOD that was using TLE Records for Indexing and removing things to get it to just send ONE index to CMOD. At one point we somehow got it to break at each page but when opening each index was blank..Here are the fields we have defined. I have a DOC_CNTL field in App Grp and App. I believe you are right about how the data is being stored. The DOC_CNTL line on the data file has NOOP on it
!..Lµ°.......DOC_CNTL....NOOP: BB930000001MultSite
Is there a way to get this to work as its defined now?
-
Just as a followup, from what you indicated, the DOC CNTL in the data isnt a TLE record. We had attempted to edit the file by adding an _ to it (DOC_CNTL) to match the CMOD field setup with bad results. Apparently manually editing a fullly composed AFP data file isnt good! So now we have removed the DOC_CNTL from App Grp. Only fields we have are POSTING_DATE, PAGE_CNT, LOAD_DATE, REPORT_NAME and DESCRIPTION fields. Awaiting a new clean AFP datafile from requestor to test. (FYI- I did remove the duplication INDEXOBJ=ALL line on the indexer. THANK YOU for catching that!!)
-
Well we received a new datafile from requestor. This file DID actually load. Strange thing it created 5 separate indexes. But when you open any of them, they are blank. The 87 msg also references the DOC CNTL which is IN the datafile but not used anywhere in the CMOD definition. I've attached below the lines from the 87 msg.
The field name 'DOC CNTL' found in the index file does not match any expected fields. The field will be ignored.
OnDemand Load Id = >91767-12-0-1FAA-20231130000000-20231130000000-91768<
Loaded 7 rows into the database
-
we got the file to load using and old OS390 Indexer. its breaking on each record in the file (which are 2 pages each). We cannot understand HOW since we are not specifying any FIELDS in the CMOD setup. Seems to break on its own correctly. IDEALLY we want just one line to show when doing a search and not separate index lines. The data and resource files come from the mainframe.
INDEXSTYLE=AFP
CPGID=500
RESTYPE=FDEF,OVLY
CCTYPE=A
INDEXOBJ=ALL
INDEXSTARTBY=1
CONVERT=YES
CC=YES
FILEFORMAT=RECORD
TRC=NO
MCF2REF=CF