TMSCLEAN leaving orphan catalog entries when catalog hardcoded expiration exist
Article ID: 273979
Updated On:
Products
Issue/Introduction
If the expiration date of a file is updated in the future in the catalog, then TMSCLEAN failing to uncatalogue the dataset after scratching the tape in TMC. Is there any way that TMSCLEAN can forcefully cleanup the catalog entry ?
------------------------------------------------------------------------------------------------------------------------------------
VOLSER FILE DATA SET NAME CREATE LAST USE BASE CA 1 SPEC. UNCATALOG F1 F2 F3 F4 TOTAL
SEQ DATE DATE VOLSER KEYWD HNDLE INDICATOR ERRORS
------------------------------------------------------------------------------------------------------------------------------------
VVVVV 1 TEST.DATA 2023/229 2023/229 VVVVVV UE=28 45 C0 00 00
Environment
Release : 14.0
Resolution
If a file could not be un-cataloged and reports a UE=28 error condition (indicating the catalog entry has a future expiration date applied to it), use the same EARLOUT DD statement created by TMSCLEAN as input to Earl report TMECLN1X. This will then generate IDCAMS statements that can be used to un-catalog these entries. This is introduced by applying the LU13400.
Feedback
