Chris, Had a similar (same?) client issue recently. It turns out that adding OPTCD=B (I think it was "B", not at the office right now) to the DD statement will cause the system to ONLY use the volser in the JCL. It eliminates the warning message if it is not the first-volume and prevents the Label Anomaly exit from getting control and supplying the NEXT-Volume as well. This works fine for an assembler program (tested with simple IEBGENER), so not sure if it will work with COBOL.
Russell Witt CA -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Chris Cantrell Sent: Friday, February 5, 2016 2:45 PM To: [email protected] Subject: Detect Tape Volume Switch I have a process which determines the VOLSERs belong to a file and then dynamically allocates each tape individually to determine exactly what data is on each of the individual VOLSERs. Our system programers implemented a change last year which caused z/OS (2.01) to add the missing VOLSERs to the DD when EOV is reached. Therefore eliminating the possibility of just opening a single volume and reading it until EOF is reached. It now 'fixes' my 'error' and forces me to read all of the volumes at once. Is there a way I can detect when EOV is reached and the tape is changed? I want to force the EOV to work like an EOF. Thanks for any help you can provide. Chris. ---------------------------------------------------------------------- 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
