ARS1390 RETURN CODE IS 9
Loaded 0 rows in database.
Has anyone seen this before?
ARS4339I Application Group >CHN_NIDX_01Y_00_ZH_V03<
ARS4340I Application >FC_CNZH0004<
ARS4341I Storage Set >OAM FIS<
ARS4342I Storage Node >SDCMODP.OAM01<
ARS4312I Loading started, --UNKNOWN-- bytes to process
ARS5481I CC=YES
ARS5481I CCTYPE=Z
ARS5481I CONVERT=NO
ARS5481I CPGID=1208
ARS5481I MCF2REF=CPCS
ARS5481I TRC=NO
ARS5481I FILEFORMAT=RECORD
ARS5481I TRIGGER1=*,49,X'20',(TYPE=GROUP)
ARS5481I FIELD1=0,52,1,(TRIGGER=1,BASE=0)
ARS5481I INDEX1=X'64756D6D79',FIELD1,(TYPE=GROUP,BREAK=YES)
ARS5481I DCFPAGENAMES=NO
ARS5481I UNIQUEBNGS=YES
ARS5481I IMAGEOUT=ASIS
ARS5481I INDEXOBJ=ALL
ARS5481I INDEXSTARTBY=1
ARS5481I INSERTIMM=NO
ARS5481I RESTYPE=NONE
ARS5476E The OS/390 indexer failed with the specified return code. (Arsl390 return code is 9).
ARS1146I Loaded 0 rows into the database
ARS4311E Loading failed
ARS4318E Processing failed for file >/ford/proj/ars/tmp//34341987.0000016A8D75E401 (DD:INPUT-FCFE.DREG.P87.MIS.CMODM.CNZH0004.D0501)<
Two follow-up questions...
Which version / PTF of CMOD are you at?
Are there any errors in the System Log related to this failed load? (Find this failed load in the system log, then look for suspicious messages within a minute before or after.) Sometimes the errors are logged separately from the load itself.
-JD.
Noting one of my pet peeves, that this message is mixed case: Arsl390 return code is 9
If I uppercase that it's ARSL390.
When hand-copying it often gets changed to ARS1390, which of course defeats searching on that piece of text.
Happens all too frequently. This is not a criticism. I just wish that wasn't mixed case.
Ed
Found this in a PMR from a couple years back:
after cleaning the ODSCRT table the load failures due to invalid
application groups are gone. And so too is the out of memory error.
Ed
In your load job output, looking at this message:
IEF032I STEP/STEP1 /STOP 2019150.1515
CPU: 0 HR 00 MIN 00.13 SEC SRB: 0 HR 00 MIN 00.00 SEC
VIRT: 20K SYS: 260K EXT: 67060K SYS: 14040K
ATB- REAL: 20892K SLOTS: 0K
VIRT- ALLOC: 90M SHRD: 0M
Are the virtual storage numbers unnaturally low compared to successful loads?
Ed
I opened a PMR regarding this, but it seems the issue was on the application. They were also trying to send a report > 2GB.