What causes the wrong GDG to be used on a restart or rerun when multiple jobs can create the same GDG dataset
Article ID: 112442
What causes the wrong GDG version to be used on a restart or rerun when multiple jobs can create the same +1 GDG dataset?
Release: Component: 11
During 'P' processing, CA 11 resolves what generation of the GDG will be used base on the information from the OS catalog. This information is stored in the CMT for any anticipated restarts. Multiple jobs can write to a GDG and create +1 versions of the same GDG dataset . If an abended job is not restarted before it can create the GDG number stored in the CMT, it is possible for another job to create that same GDG dataset. Use the BYPGDG=VER option to avoid this issue. BYPGDG=VER will verify if there is a difference in the GDG information stored in the CMT and information for the current catalog value for the GDG. If there is a difference then message U11-115 will be issued indicating so. You would decide at that time if you want to use the GDG information stored in the CMT or the current catalog value for the GDG dataset by specifying BYPGDG=NO or BYPGDG=CAT respectively for your rerun. As always, please contact CA Technologies support for CA Workload Automation Restart Option for z/OS Schedulers if you have further questions.