I simplified the requirements somewhat because I was expecting to use
TMSEXPDT.
More details:
We have a lot of systems that have been moved off-platform. About half
over 7 years ago. These systems generated GDG tapes but new gens are not
being created.
There are about 700 volumes. About half are over the 7 year max
retention. The staff that understood the real retention requirements are
gone. So, I was told to:
Any tape file that has not had any new generations built since Jan 1,
2015 are to be considered orphaned.
All orphaned tape files over 7 years old can be scratched.
All orphaned tape files under 7 years old are to be set to a 7 year
retention so they will automatically scratch at that point without any
additional programming effort in the future.
Some files are using multiple tape volumes
Some tapes have multiple files.
Some jobs created multi-file/multi-volume tapes.
To build the control cards using rexx, I have:
A listing of all such orphaned files which has the file name, volume(s),
creation job and creation dates.
A listing of all active files with all volumes used.
A listing of all active volumes with all files listed.
(And, I am good at rexx programming.)
Tony Thigpen
Lizette Koehler wrote on 02/19/2016 08:29 PM:
EMID=0000 are good. That means you will probably not have to update them to
allow them to scratch.
I like the TMSUPDTE process.
//TMSUPDTE EXEC PGM=TMSUPDTE,PARM='NODSN,AUDIT'
//TMSRPT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
VOL 200001,NOCHAIN
REP DSN=HEXZEROS
REP DSN17=HEXZEROS
REP ROBTY=X'89'
You can use DSN matching by changing NODSN to DSN and including DSN= in the
control card. The Utilities manual for CA1 will have good details on this
TMSUPDTE process.
See if this might be just as good for your needs.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Tony Thigpen
Sent: Friday, February 19, 2016 6:22 PM
To: [email protected]
Subject: Re: Question on CA-1
I just found that some of the oldest tapes have EDMID = 0000
Tony Thigpen
Tony Thigpen wrote on 02/19/2016 08:19 PM:
On the few I just checked, EDMID = blanks.
Tony Thigpen
Lizette Koehler wrote on 02/19/2016 08:15 PM:
Where these tapes created by an external data manager? (EDM) In a ca1
display of the tape (I like using the ISPF CA1 function) See if this
field is set
EDMID = HPDM
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List
[mailto:[email protected]] On Behalf Of Tony Thigpen
Sent: Friday, February 19, 2016 6:09 PM
To: [email protected]
Subject: Question on CA-1
It's clean-up time.
I have about 400 old 3380 tapes I need to get out of the tape
library and distroy. These are all over 7 years old for systems that
are long gone. They were originally put into the catalog with
multiple generations, but since no new generations are being
created, they have not been scratching.
I found the following old jcl in a library and wanted to ask if this
is the best way to handle this:
//TMSEXPD EXEC PGM=TMSEXPDT,PARM='TEST'
//TMSRPT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DSN=MPXSS1.UPSTREAM.DAILY.BACKUP1.G0189V00,LABEL=RETPD=2600
.. a bunch more ..
/*
Then, just let the next day scratch process scratch the tapes.
I plan on using REXX to build the SYSIN, including all DSNs (full
GEN
number) found on every tape volume I need to scratch out of the tape
library.
Also, Do I need to run TMSOSCAT after the alters, after the scratch
process, or not at all?
Thoughts?
--
Tony Thigpen
----------------------------------------------------------------------
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
