The status does not change until you run a CA-1 maintenance job. It is not "real time".
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Uriel Carrasquilla > Sent: Thursday, March 29, 2012 10:10 AM > To: [email protected] > Subject: Re: catalogued datasets in tapes and expiration dates > > Forgot to mention, yes, I am using CA-1. > I ran a GENER to copy to output file on our VTL (UNIT=V3590) > with a LABEL=EXPDT=99000 with a DISP to CATLG if successful. > It ran OK and put the dataset (no stacking) into VOL=SER=682436. > Then, via ISPF TMS, I checked the volume and it shows the > expiration date with the CATALOG description. > Then, I went to ISPF 3.2 and uncatalogued the dataset. > TMS still has the same information with the expiration date > set to CATALOG. > I was expecting to see "SCRATCH" instead. > is this normal? > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on > behalf of Jonathan Goossen [[email protected]] > Sent: Thursday, March 29, 2012 10:23 AM > To: [email protected] > Subject: Re: catalogued datasets in tapes and expiration dates > > The answer likely varies by the TMS in use. > > CA-1 will keep the tape until every dataset on it is expired. > This can be > confusing as the volume record is also the first file on the > tape. CA-1 > will adjust its expiration to be equal the highest on the tape. If you > manually expire the first file (volume record) then the > entire tape will > scratch regardless of the expiration of the rest of the > files. That is one > reason that I am very carful about changing the expiration of volume > records. > > In CA-1 there is an expiration called CATALOG. It will expire the file > when it is no longer cataloged. If a cataloged tape file has a Julian > expiration, then uncataloging the file will not affect > expiration. But > scratching the tape will uncatalog the file. > > Thank you and have a Terrific day! > > Jonathan Goossen, DTM > ACT Mainframe Storage Group > Personal: 651-361-4541 > Department Support Line: 651-361-5555 > For help with communication and leadership skills checkout Woodwinds > Toastmasters > > IBM Mainframe Discussion List <[email protected]> wrote on > 03/29/2012 > 08:51:19 AM: > > > From: Uriel Carrasquilla <[email protected]> > > To: [email protected] > > Date: 03/29/2012 08:52 AM > > Subject: Re: catalogued datasets in tapes and expiration dates > > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > Let's say I have a tape with multiple datasets inside. > > Some datasets may be catalogued, some may not. > > I can understand the once not catalogued when they expire they no > > longer hold the tape from going to the scratch pool. > > But what about those cases when the catalogued datasets hit their > > expiration date? what happens? > > am I also correct in assuming that the entire tape with all the > > stacked datasets is being held until the last dataset in it expires? > > Please share your thoughts. > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > This e-mail message and all attachments transmitted with it may > contain legally privileged and/or confidential information intended > solely for the use of the addressee(s). If the reader of this > message is not the intended recipient, you are hereby notified that > any reading, dissemination, distribution, copying, forwarding or > other use of this message or its attachments is strictly > prohibited. If you have received this message in error, please > notify the sender immediately and delete this message and all > copies and backups thereof. Thank you. > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
