TLMS - CAT9062E MIXING WORM AND R/W VOLUMES.

Products

• TLMS Tape Management

Issue/Introduction

Once the WORM has been activated on the VTS the following messages occur:


13.11.01 JOB09859 CTS014 IEC502E K 3309,U50218,SL,SOPEARC1,ST2023T2,FDRABR.VG1674D.B122131A
13.11.01 JOB09859 IEC501A M 3309,PRIVAT,SL,COMP,SOPEARC1,ST2023T2,FDRABR.VG1674D.B122131A
13.11.03 JOB09859 IEC705I TAPE ON 3309,U55182,SL,COMP,SOPEARC1,ST2023T2,FDRABR.VG1674D.B122131A,MEDIA2,LOGICAL WORM
13.11.44 JOB09859 IEC205I TAPE1,SOPEARC1,ST2023T2,FILESEQ=1687, COMPLETE VOLUME LIST, 127
127 DSN=FDRABR.VG1674D.B122131A,VOLS=U50218,U55182,TOTALBLOCKS=450009
13.11.44 JOB09859 CAT9040I U55182 ON 3309 REJECTED BY CA TLMS
13.11.44 JOB09859 CAT9062E MIXING WORM AND R/W VOLUMES.
13.11.44 JOB09859 IEC518I SOFTWARE ERRSTAT: INTLABEL 3309,U55182,SL,SOPEARC1,ST2023T2
13.11.45 JOB09859 IEC502E R 3309,U55182,SL,SOPEARC1,ST2023T2
13.11.45 JOB09859 CTS014 IEC502E R 3309,U55182,SL,SOPEARC1,ST2023T2
13.11.45 JOB09859 IEC147I 613-04,IFG0195B,SOPEARC1,ST2023T2,TAPE1,3309,, 134
134 FDRABR.VG16713.B122131A.
134 ..
13.11.45 JOB09859 IEA995I SYMPTOM DUMP OUTPUT 135
135 SYSTEM COMPLETION CODE=613 REASON CODE=00000004
135 TIME=13.11.45 SEQ=55626 CPU=0000 ASID=0219
135 PSW AT TIME OF ERROR 075C1000 80E13718 ILC 2 INTC 0D
135 NO ACTIVE MODULE FOUND
135 NAME=UNKNOWN

 

LU02245 has been applied and the volumes have been updated as it is indicated on the ptf.

 

Environment

Release : 14.0

Component : TLMS Tape Management

Resolution

CAT9062E

MIXING WORM AND R/W VOLUMES.

Reason:

TLMSOPEN: The tape was rejected at END-OF-VOLUME to prevent WORM volumes and R/W volumes from being chained together. This is not permitted because R/W volumes can be scratched and rewritten while WORM volumes cannot be scratched and rewritten.

Action:

Ensure that the volume being mounted is the same type as the previous volume.

 When FILE-1 is first created on the first volume; the decision is made to be a Virtual-WORM or non-worm based on SMS constructs. Once that decision is made, all subsequent files will be the same and all subsequent volumes will be the same. It is not possible to  have file-1 be a Virtual-WORM and file-2 be a non-worm. It is not possible to have file-1 be a non-WORM and try to create file-2 as a Virtual-WORM. That is NOT allowed. Whatever is defined when file-1 is first created will continue for all subsequent volumes and files. So a file cannot be half Virtual-WORM and half non-WORM. All volumes and all files must be the same.