Hi David,
It is likely that the inital update(s) happened with NOCHAIN in use, otherwise a scratch operation should have failed for anything other than vol 1. Have you run an invalid pointers report (rpt 29)? It will identify all of the volumes involved. Sometimes it is easier, depending on how many volumes are involved, to rebuild the broken chains and then scratch the vol 1 rapes, which will then take the chains along with them. I have a rpt29 JCL if you want one. If you go ahead with scratching the individual volumes, VOLSEQ for each tape will need to be set to 0001 and the 1STVOL, NEXTVOL, PREVVOL, and OUTCODE (if any) will need to be cleared out. As others have said, that can be done with TMSUPDTE. I see that there is no EDMID= present for the tape posted. That does simplify things. Anytime there is an EDM involved, it has to get the updates too. Scratch operations involving EDM tapes should be initiated with the EDM. Best Regards, Linda Mooney ----- Original Message ----- From: "David W. O'Brien (NIH/CIT) [C]" <[email protected]> To: [email protected] Sent: Wednesday, September 16, 2009 8:04:32 AM GMT -08:00 US/Canada Pacific Subject: Re: Forcing TMS Tape entry into scratch status John and Jay, Thanks for responding, no EDM is not involved nor do we use 'out of area' codes. Our off-site tapes are written to a remote silo so there is no need for tape movement. Volseq is not equal to 001 and the dataset inquiry follows the tape inquiry. Here is the Inquiry display of one of the tapes: VOLSER = 200041 ACTVOL= SMSMC= BLANKS DSN = NIH.NEUMICS.PPT.MBACKUP.CHECKPT.G0059V00 DSN17= P.WEEKS3.G0048V00 EXPDT = 2009/256 ACCT= HEXZEROS FLAG1 = E0 FLAG2 = 40 FLAG3 = 00 BATCHID= 59 = TMSIONLN FLAG4 = 00 FLAG5 = 00 FLAG6 = 00 HOOKID = FE = EDMID = WMC = 00000 WWID = - - CDATE = 2006/182 CJOB = NEUMMBKP CTIME = 0638 CPGM = IKJEFT1B LDATE = 2006/182 LJOB = NEUMMBKP LTIME = 0724 LPGM = IKJEFT1B CSTEP = MICS CDDNAME= BKUPCKPT CUNIT = 0351 LUNIT = 0351 OUTDATE= ZEROS OUTCODE= SLOT = 0000000 TRERRC = 00000 BTHDATE= 2004/154 VENDOR = BLANKS COUNT = 00011 TWERRC = 00000 DATECLN= ZEROS USECLN = 00000 CLNCNT = 000 TRERRI = 00000 VOLSEQ = 0004 ROBTY = ROBID = 000 TWERRI = 00000 1STVOL = NEXTVOL= PREVVOL= PRERRC = 00000 NUMDSNB= 0000 1STDSNB= 0000000 LSTDSNB= 0000000 PWERRC = 00000 LABEL = SL DEN = 38KC TRTCH = 36X2 PRERRI = 00000 RECFM = FB LRECL = 000200 BLKSIZE= 000200 PWERRI = 00000 AUDATE = 2009/256 AUTIME = 2201 BLKCNT = 0000000000 AUCODE = 00 AUFLAG1= 00 CPUID = 4090 USERID = $WGL VOLPERC= 097 FILPERC= 093 COMPRES= 000 CTLGCNT= 000 I = Inquiry U = Update 09.259 (Note: Only the first 43 bytes of the dataset name is displayed.) VOLUME FILE EXPIRE CREATE CMD DATA SET NAME SERIAL SEQ DATE DATE NIH.NEUMICS.PPT.MBACKUP.CHECKPT.G0059V00 200041 0001 2009/256 2006/182 NIH.NEUMICS.PPT.MBACKUP.CHECKPT.G0059V00 200305 0001 2009/256 2006/182 NIH.NEUMICS.PPT.MBACKUP.CHECKPT.G0059V00 300274 0001 *SCRATCH* 2006/182 NIH.NEUMICS.PPT.MBACKUP.CHECKPT.G0059V00 300491 0001 2009/256 2006/182 NIH.NEUMICS.PPT.MBACKUP.CHECKPT.G0059V00 300573 0001 2009/256 2006/182 300274 was the first volume, now how to scratch the others? Thank You, Dave O'Brien NIH Contractor ________________________________________ From: IBM Mainframe Discussion List [[email protected]] On Behalf Of John Kington [[email protected]] Sent: Wednesday, September 16, 2009 10:38 AM To: [email protected] Subject: Re: Forcing TMS Tape entry into scratch status David, >We are in the process of eliminating old pools of tapes. >The application owner and the tech support for the silos uncataloged the >>datasets and changed the Expdt to the current date expecting the nightly TMS >>functions to flip the scratch bit for each of these tapes. > >I thought I could delete the pool but the tapes must be in scratch status >first. > >Maybe I'm just forgetting something simple but I don't see a utility that will >>force a 'scratch status'. > >Any suggestions? I would check to see if there is an out of area code or the external data manager flag is set. Regards, John ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
