Unlikely to be your problem, but we actually had the following scenario recently. We use 'STK' virtual tape VSMx. After a system crash of some sort, we got the ubiquitous warning to 'run a tape audit'. We've seen this message for years. Somehow it was overlooked in this case, and no 'audit' was run. We started getting similar errors for mismatching tape labels. Damndest thing. We finally ran the STK tape audit. The problem disappeared totally. Maybe the weirdest thing I ever saw.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Edward Finnell Sent: Wednesday, November 13, 2019 3:30 PM To: [email protected] Subject: (External):Re: DFDSS backup retore Only way to find out is run TAPEMAP on INDD1 VOLSER. In a message dated 11/13/2019 5:11:20 PM Central Standard Time, [email protected] writes: ADR012I (SCH)-DSSU (01), 2019.317 14:11:07 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM: TASK 001 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
