Joined: 06 Jun 2008 Posts: 8570 Location: Dubuque, Iowa, USA
BTW, bypassing label processing, OPTCD=B, resolves the issue.
Actually, LABEL=BLP is the DCB subparameter to bypass label processing. What you are doing, from the JCL Reference manual, is:
requests that the end-of-volume (EOV) routine disregard the end-of-file (EOF) recognition for magnetic tape. For an input data set on a standard-labeled (SL or AL) tape, the EOV routine treats EOF labels as EOV labels until the volume serial list is exhausted. This option allows SL or AL tapes to be read out of volume sequence or to be concatenated to another tape with the same data set name using one DD statement. See "Data Sets that Span Libraries" in z/OS MVS JCL User's Guide for a description of allocation processing for multi-volume data sets created in different tape libraries.
Joined: 30 Nov 2013 Posts: 883 Location: The Universe
Nic Clouston wrote:
No idea but...DISP=SHR for tape is "invalid". You cannot share a tape volume - you should use OLD.
You are correct when you say two jobs cannot "share" a tape volume, but what DISP=SHR is saying is another job can "share" the data set name.
Actually, two jobs can "share" a tape volume, but only one job at a time can have a data set open on the volume. For that matter, one job cannot have 2 (or more) data sets open on one volume at a time. In other words, this won't work -
Joined: 29 Jul 2016 Posts: 1 Location: United States
I experienced this same situation, and a new version of CA-1 had been installed that leveraged the IBM Label Anomaly Exit. We had to start using the OPTCD=B for jobs that read individual tapes of a multi-volume group.