>Does somebody has thought on that..?? i still see option to breakdown step
>into 3 separate steps to make sure STOW open and close data everytime
>and we don't see overlap error..

You can resolve the problem via JCL and leave the program alone. Have the 
output be three or more separate temporary data sets. Tnen follow that step 
with steps to copy the temporary data sets one by one into the original target 
PDS. Use DISP=OLD to ensure no other job/user is writing to the same PDS.

If you can be certain no one else will be updating it, then DISP=SHR will 
suffice. This would be typical, for instance, if the output PDS was allocated 
to 
a long-running task or to multiple tasks, such as a JCL library owned by the 
scheduler using it as read only, or ISPF panel/message/skeleton libraries 
allocated to many TSO users for input.

----------------------------------------------------------------------
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

Reply via email to