MVSFORUMS.com

schintala · Posted: Fri Mar 11, 2011 11:03 am Post subject: CA Fastload Utility Error

Hi,
I am trying to load the data into table using CA fastload utility and failed with S000 U0100 abend. Any clue? I see below error message from the utility.

kolusu · Posted: Fri Mar 11, 2011 11:44 am Post subject:

schintala,

If you did a google on the first abend code 'PFL0111E' you would have found that PRODUCT: Unicenter Fast Load RELEASE: R11 SP4 has a PTF named 'UFLE231' which is to solve the error 'PFL0111E STG ACQUISITION FAIL'. So talk your system's programmer and see if the PTF is installed.

Kolusu

schintala · Posted: Fri Mar 11, 2011 12:08 pm Post subject:

Kolusu,
Thank you so much for the reference. Our CA DB2 products has been upgraded from R11SP2 to R14.0 recently. Not all CA Fastload utility jobs gives this error. This error comes from in one job. Not sure this is some thing related to sort phase or anything to do with CA PTF.

22.45.17 JOB37820 WER999A RMDD010 ,LOADRMC , - UNSUCCESSFUL SORT 13E S
22.45.17 JOB37820 WER999A RMDD010 ,LOADRMC , - UNSUCCESSFUL SORT 13E S
22.45.18 JOB37820 IEA995I SYMPTOM DUMP OUTPUT 622
622 USER COMPLETION CODE=0100

kolusu · Posted: Fri Mar 11, 2011 12:39 pm Post subject:

schintala,

Well you are on your own now. The messages indicates you are using SYNCSORT. I'm a DFSORT developer. DFSORT and Syncsort are competitive products. I'm happy to answer questions on DFSORT and DFSORT's ICETOOL, but I don't answer questions on Syncsort.

Kolusu

papadi · Supermod Joined: 20 Oct 2009 Posts: 594 Topics: 1

There is most likely more diagnostic information generated. Suggest you post the complete set of informational/diagnostic information so we can see it all.

Possibly the problem is related to a space issue. . .

Suggest also that you look in the CA documentation for the cause of a User 100 abend. It may be specific rather than general.
_________________
All the best,

di

schintala · Posted: Fri Mar 11, 2011 4:25 pm Post subject:

Thank you all. Just want to update you, this abend due to locks held on the load table by some thread. CA Fastload Utilty trying to stop the table/index space and could not do because it was in use by some other application. But error message showing weird in job output. But it should have completed on restart. Keep watching this job in our batch cycle and post here.

schintala · Posted: Mon Mar 14, 2011 1:49 pm Post subject:

Want to update you, the issue has been resolved and it is due to size of REGION parameter in the job card. In job step we coded as REGION=5M and in step we made it as 0M. Job card region overrides the step region specification and hence this error. We got to change job card region to 0M and went fine then.

papadi · Supermod Joined: 20 Oct 2009 Posts: 594 Topics: 1

Good to hear this is working - thanks for the update.

Hopefully, you confirmed this with CA Support. . . The call is free and may save you a surprise later. . .
_________________
All the best,

di