How to correct IECTMS3 Not Scratch (28) message.
Article ID: 27998
Updated On:
Products
Issue/Introduction
What does the IECTMS3 Not Scratch 28 message mean and how do I correct it?
Environment
All releases of CA 1.
Cause
CA-1 will issue this message when a scratch tape is mounted and the DSN that is currently on the tape doesn't match DSN17 field in the TMC.
Normally this is caused by using a CA-1 controlled tape as a scratch tape and using the EXPDT=98000 (foreign tape), or by using the tape while CA-1 is not active, or the CA1 exit TMSXITA was used to bypass CA1 tape tracking. To avoid problems with this error, the CA1 'failsafe' usermod could be installed to prevent writing to tapes without CA1 active. Also, security could be setup for foreign tape processing to only allow a few people the ability to create foreign tapes.
Resolution
To correct this we recommend that you do a tapemap of the volser to verify if you need to keep the data or if it can be discarded. You can use the CTS tapemap function to print out the header of the tape. If you do not need the data, then update the TMC via TMSUPDTE to set the DSN and DSN17 to HEXZEROS (this will cause CA1 to bypass checking these fields and allowing the tape to be reused as scratch).
TMSUPDTE control statements:
VOL=vvvvvv,NODSN,NOCHAIN
REP DSN=HEXZEROS
REP DSN17=HEXZEROS
If the data of the tape is valid, then the DSN17 field in the TMC Volume record should be corrected (using TMSUPDTE) with the proper info from the tape label.
Note: If a non-specific mount is made for a scratch tape from the tape pool, then it should be marked as SCRATCH in OAM. If a specific mount is made (i.e., specifying a specific volume), then the tape will need to be marked as PRIVATE in OAM.
Feedback
