The simple "fix" is to code the OPTCD=B parameter in the JCL. With the OPTCD=B coded, then z/OS does not care if volume 3 is open'ed before volume's 1 & 2 and does not care if EOV is reached before EOF. It simply reverts back to the way z/OS operated prior to z/OS 1.13 when the new feature was added to z/OS.
Russell Witt CA 1 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of David Speake Sent: Saturday, February 20, 2016 11:26 PM To: [email protected] Subject: Standard User Tape Labels in COBOL Does anyone use this feature? My create program has a DISPLAY that shows the DECLARATIVES section getting control but the read program dosnt. be Monday before i can get a BLP of the labels so i don't know which is at fault. Hesitate to post the code as it is a true 'proof of concept' kludge and not even decent in that category. A working sample of same would be appreciated. The need for this is CAs fix (twernt broke IMHO)to TMS to keep you from reading a single tape volume of multi volume data set. When it detects EOV but not EOF and there are no more volsers for the file in the TIOT(?) it FIXES things by using a systems exit - LABEL ANOMALY. We have history files running 40+ volume and find this MOST inconvenient. So far Tech Support refuses to FIX it back. So looking for a workaround. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
