TOL(ENQF) should be a hint. This is telling DFSMSdss that if it can't get
exclusive ownership it's OK - just go ahead and dump the dataset anyways no
matter why or how it is being updated.
Anything that isn't allocated already will get an exclusive enqueue unless
you specify the SHARE option.
TOL(ENQF) would not help his situation. Since the DSS dump started
first, it will get the ENQ. Then when the job with the PROCLIB
statement started it will still fail.
But the SHARE option on DUMP should solve the problem, changes the
SYSDSN ENQ from exclusive to shared and the PROCLIB job should tolerate
that.
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
