Converting from OS/390 to ACIF Indexer

[johnnoel]

Fellow Members,

Currently, we are loading LineData reports from the mainframe using ARSLOAD (on the mainframe) to load the reports to OnDemand server installed on a Windows Server. The Applications are configured as OS/390 for the INDEXER.

To prevent using ARSLOAD on the mainframe, we want to start using the Automatic Loading (Load Data Service) of the Configurator in Windows. So I create a new version of the application and changed the Indexer to ACIF. In doing so I had to remove the INDEXSTYLE=DOC line from the indexer details. I used a sample data report to view in the Graphical Indexer to ensure the mapping of the Triggers, Indexes and Fields were correct. They were....

When I drop the files in the arsload directory though, the load failed!

arsload: Processing file >M:\arsload\SD.CRDTSM.DOC107YR_WIN.KBD12001-V04.2001.121200.ARD<
 
arsload: 05/05/11 11:25:11 -- Indexing started, 0 bytes to process
0425-415 CC=YES
0425-415 CCTYPE=A
0425-415 CONVERT=NO
0425-415 CPGID=500
0425-415 MCF2REF=CPCS
0425-415 TRC=NO
0425-415 FILEFORMAT=RECORD,133
0425-415 TRIGGER1=*,1,X'F1',(TYPE=GROUP)
0425-415 TRIGGER2=*,2,X'E2C46DD9D7',(TYPE=FLOAT)
0425-415 FIELD1=0,2,6,(TRIGGER=1,BASE=0)
0425-415 FIELD2=0,8,10,(TRIGGER=2,BASE=0)
0425-415 FIELD3=1,7,10,(TRIGGER=1,BASE=0)
0425-415 FIELD4=0,43,18,(TRIGGER=1,BASE=0)
0425-415 FIELD5=0,61,16,(TRIGGER=1,BASE=0)
0425-415 INDEX1=X'C2D9C5C1D26DE2F1',FIELD1,(TYPE=GROUP,BREAK=YES)
0425-415 INDEX2=X'C9D5C4C5E76DF0F1',FIELD2,(TYPE=GROUP,BREAK=NO)
0425-415 INDEX3=X'C9D5C4C5E76DF0F2',FIELD3,(TYPE=GROUP,BREAK=NO)
0425-415 INDEX4=X'C9D5C4C5E76DF0F3',FIELD4,(TYPE=GROUP,BREAK=NO)
0425-415 INDEX5=X'C9D5C4C5E76DF0F4',FIELD5,(TYPE=GROUP,BREAK=NO)
0425-415 DCFPAGENAMES=NO
0425-415 UNIQUEBNGS=YES
0425-415 GROUPMAXPAGES=9999
0425-415 IMAGEOUT=ASIS
0425-415 INDEXOBJ=ALL
0425-415 INDEXSTARTBY=1
0425-415 INSERTIMM=NO
0425-415 RESTYPE=NONE
0425-415 inputdd=M:\arsload\SD.CRDTSM.DOC107YR_WIN.KBD12001-V04.2001.121200.ARD
0425-415 outputdd=NUL
0425-415 indexdd=M:\arsindex\SD.CRDTSM.DOC107YR_WIN.KBD12001-V04.2001.121200.ARD.ind
0425-415 resobjdd=NUL
0425-448 INDEXING WAS REQUESTED, BUT NO GROUP 'TRIGGERn' NOR ANY 'FIELD' BASED ON IT WAS SATISFIED WITHIN THE PAGE RANGE SPECIFIED BY THE INDEXSTARTBY PARAMETER.
0425-441 ACIF AT PK74886 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
arsload: 05/05/11 11:25:12 Indexing failed
arsload: Processing failed for file >M:\arsload\SD.CRDTSM.DOC107YR_WIN.KBD12001-V04.2001.121200.ARD<

I haven't changed anything other than the Indexer, so why doesn't it find the trigger nor fields for the new application?

If I leave the indexer as OS/390 I get this message:

arsload: Processing file >M:\arsload\SD.CRDTSM.DOC107YR.KBD12001-V03.2001.121200.ARD<
 
arsload: 05/05/11 12:07:43 -- Loading started, 0 bytes to process
Loaded 0 rows into the database
arsload: 05/05/11 12:07:43 Loading failed
arsload: Processing failed for file >M:\arsload\SD.CRDTSM.DOC107YR.KBD12001-V03.2001.121200.ARD<

Any ideas what I am missing?

[Greg Ira]

In my experience you usually get those errors when your fileformat is off.  I would double check the input file that you are dropping in.  Maybe an EBCDIC- ASCII conversion issue?

[johnnoel]

Indexer BEFORE
/* Migrated from OD/V2 */
CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
FILEFORMAT=RECORD,133
GROUPMAXPAGES=9999
INDEXOBJ=ALL
INDEXSTYLE=DOC
TRC=NO
TRIGGER1=*,1,X'F1',(TYPE=GROUP)                            /* '1' */
TRIGGER2=*,2,X'E2C46DD9D7',(TYPE=FLOAT)                    /* 'SD_RP' */
FIELD1=0,2,6,(TRIGGER=1,BASE=0)
FIELD2=0,8,10,(TRIGGER=2,BASE=0)
FIELD3=1,7,10,(TRIGGER=1,BASE=0)
FIELD4=0,43,18,(TRIGGER=1,BASE=0)
FIELD5=0,61,16,(TRIGGER=1,BASE=0)
INDEX1='BREAK_S1',FIELD1,(TYPE=GROUP,BREAK=YES)
INDEX2='REPORT_ID',FIELD2,(TYPE=GROUP,BREAK=NO)            /* REPORT_ID */
INDEX3='REPORT_DATE',FIELD3,(TYPE=GROUP,BREAK=NO)          /* REPORT_DATE */
INDEX4='TITLE_1',FIELD4,(TYPE=GROUP,BREAK=NO)              /* TITLE_1 */
INDEX5='TITLE2',FIELD5,(TYPE=GROUP,BREAK=NO)               /* TITLE2 */

Indexer AFTER
CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
MCF2REF=CPCS
TRC=NO
FILEFORMAT=RECORD,133
TRIGGER1=*,1,X'F1',(TYPE=GROUP)                            /* 1        */
TRIGGER2=*,2,X'E2C46DD9D7',(TYPE=FLOAT)                    /* SD_RP    */
FIELD1=0,2,6,(TRIGGER=1,BASE=0)
FIELD2=0,8,10,(TRIGGER=2,BASE=0)
FIELD3=1,7,10,(TRIGGER=1,BASE=0)
FIELD4=0,43,18,(TRIGGER=1,BASE=0)
FIELD5=0,61,16,(TRIGGER=1,BASE=0)
INDEX1=X'C2D9C5C1D26DE2F1',FIELD1,(TYPE=GROUP,BREAK=YES)   /* BREAK_S1 */
INDEX2=X'C9D5C4C5E76DF0F1',FIELD2,(TYPE=GROUP,BREAK=NO)    /* INDEX_01 */
INDEX3=X'C9D5C4C5E76DF0F2',FIELD3,(TYPE=GROUP,BREAK=NO)    /* INDEX_02 */
INDEX4=X'C9D5C4C5E76DF0F3',FIELD4,(TYPE=GROUP,BREAK=NO)    /* INDEX_03 */
INDEX5=X'C9D5C4C5E76DF0F4',FIELD5,(TYPE=GROUP,BREAK=NO)    /* INDEX_04 */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
GROUPMAXPAGES=9999
IMAGEOUT=ASIS
INDEXOBJ=ALL
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE

Maybe it's not finding the Trigger 1. I will continues to play with the parameters. Attached is a screen shot of the Indexer Properties.

[johnnoel]

Header of the input file below.

----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
********************************* Top of Data **********************************
1SD_RP_CRDTSUM                            CARD TRANSACTION SUMMARY - CHASE     
      05/04/2011                              CREATED ON 2011-05-05         


HEX ON BELOW:

----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
 ------------------------------------------------------------------------------
********************************* Top of Data **********************************
                                                                               
                                                                               
 ------------------------------------------------------------------------------
1SD_RP_CRDTSUM                            CARD TRANSACTION SUMMARY - CHASE     
FEC6DD6CDCEEED4444444444444444444444444444CCDC4EDCDECCECDD4EEDDCDE464CCCEC444444
124D97D3943244000000000000000000000000000031940391521339650244419800038125000000
 ------------------------------------------------------------------------------
      05/04/2011                              CREATED ON 2011-05-05             
444444FF6FF6FFFF444444444444444444444444444444CDCCECC4DD4FFFF6FF6FF4444444444444
00000005104120110000000000000000000000000000003951354065020110050050000000000000
 ------------------------------------------------------------------------------

[Ed_Arnold]

I've only glanced at this, but I don't like the fact that PK74886 is PE.

PK92298  PEAPAR of UK41729

Ed

[johnnoel]

I found this link Ed

http://www-01.ibm.com/support/docview.wss?uid=swg1PK74886

What is that really saying to me who is using CMOD 8.4.1.2 on the windows server and ODWEK at 8.4.1.7 ?

[johnnoel]

Further digging reveles this link

http://www-01.ibm.com/support/docview.wss?rs=4036&context=SRCMMVX&uid=swg1PK92298&loc=en_US&cs=utf-8&lang=en

Hmmmmm

[Ed_Arnold]

Hi John - PK74886 is the level of ACIF you're calling right now, hence the message:  ACIF AT PK74886 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.

PK74886 is a problem identifier, which on z/OS maps to PTF (for fix) UK41729.   So that's the service you currently have on the ACIF you're calling.

I know that UK41729 is PE, which means it's a PTF in Error - a defect was found in it after it was released.

The problem identifier for that is PK92298, andthe PTF (or fix) for that problem on z/OS is UK50893.

If you're running ACIF on z/OS, then your support team should install UK50893 for you.

If you're running ACIF on some other software platform, then I'm out of my element.