ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP '
ADR109I (R/I)-RI01 (01), 2011.199 21:41:58 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR006I (001)-STEND(01), 2011.199 21:41:58 EXECUTION BEGINS
ADR412E (001)-DTDSC(03), DATA SET HLQ.DATA IN CATALOG CATALOG.PRD.ICFCAT ON VOLUME P3GE9B FAILED SERIALIZATION
ADR412E (001)-DTDSC(03), DATA SET HLQ.PROD.CMDLIB IN CATALOG CATALOG.PRD.ICFCAT ON VOLUME P3GEA2 FAILED SERIALIZATION
ADR801I (001)-DTDSC(01), DATA SET FILTERING IS COMPLETE. 3 OF 5 DATA SETS WERE SELECTED: 2 FAILED SERIALIZATION AND 0 FAILED FOR
OTHER REASONS
ADR454I (001)-DTDSC(01), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED
HLQ.DB2PARMS
HLQ.PROD.CNTL
HLQ.SCHEMA.DATA
ADR006I (001)-STEND(02), 2011.199 21:42:19 EXECUTION ENDS
ADR013I (001)-CLTSK(01), 2011.199 21:42:19 TASK COMPLETED WITH RETURN CODE 0008
ADR012I (SCH)-DSSU (01), 2011.199 21:42:20 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM:
TASK 001
When I looked at ADR412E it says..
Code:
ADR412E (xxx)-mmmmm(yy), DATA SET {dsname | clustername COMPONENT
componentname} [IN CATALOG catname] ON VOLUME volser FAILED
SERIALIZATION
Explanation: An ENQ(EXCLUSIVE), ENQ(SHARE), or dynamic allocation with DISP=OLD or SHR failed after a specified (or defaulted) number of retries. TOL(ENQF) was not specified by the user.
System Action: The data set is not processed. The return code is 8.
Programmer Response: Rerun the job when the data set is not in use by other users. You can increase the WAIT parameters, and if you are not using the COMPRESS command to compress a PDS, you can specify TOL(ENQF).
But I couldnt see, Which user has locked it or was using it.
Any way to find out what user\process holding these datasets?
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
Quote:
Any way to find out what user\process holding these datasets?
Generally, this needs to be done while the job is running or the results may -- or may not -- reflect the actual state of the system that caused the ADR412E message.
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
LOL I feel relieved that I'm in sync with your support group!
IF you have access to console commands, you can issue D GRS,C while the job is running to look for contention -- but if you don't have access to the console commands, this won't help.
Your other option would be to add a DD statement for that specific file with DISP=OLD to prevent it from being used while your job is running. With only three data sets, the overhead would not be onerous -- but if you were backing up 150 data sets, this method would not be practical and TOL(ENQF) becomes your only option.
..
