Re: HSM question
For NON-SMS volumes, autobackup is not controlled by MGMTCLAS (as there is no MGMTCLAS) For autobackup to occur: The NON-SMS volume must be defined with: ADDVOL volser UNIT(unittype) PRIMARY(AUTOBACKUP) To control how many backup versions to keep: SETSYS VERSIONS(limit) On Wed, 11 Sep 2019 at 21:41, Brian Fraser wrote: > If the dsn is non-sms, then it doesn't have a MGMTCLAS. > > Default MGMTCLAS rules do not apply. > > Regards > Brian > > On Wed, Sep 11, 2019, 6:39 PM Gadi Ben-Avi, wrote: > >> Thanks >> In the Management Class there are to more options I would like to set: >> >> How many backup versions of a deleted dataset are kept. >> How long the backup is kept. >> Do these settings have equivalent setting for Non-SMS datasets? >> >> Gadi >> >> -Original Message- >> From: IBM Mainframe Discussion List On Behalf >> Of retired mainframer >> Sent: Wednesday, September 11, 2019 11:12 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: HSM question >> >> Look at the VERSIONS operand of the SETSYS command and the ALTERDS command >> >> > -Original Message- >> > From: IBM Mainframe Discussion List On >> > Behalf Of Gadi Ben-Avi >> > Sent: Wednesday, September 11, 2019 12:15 AM >> > To: IBM-MAIN@LISTSERV.UA.EDU >> > Subject: Re: HSM question >> > >> > OK, >> > So how do I tell HSM to keep more than one backup version? >> > >> > Gadi >> > >> > -Original Message- >> > From: IBM Mainframe Discussion List On >> > Behalf Of Gibney, Dave >> > Sent: Wednesday, September 11, 2019 10:09 AM >> > To: IBM-MAIN@LISTSERV.UA.EDU >> > Subject: Re: HSM question >> > >> > MGMTCLAS won't matter for Non-SMS datasets >> > >> > > -Original Message- >> > > From: IBM Mainframe Discussion List On >> > > Behalf Of Gadi Ben-Avi >> > > Sent: Tuesday, September 10, 2019 11:39 PM >> > > To: IBM-MAIN@LISTSERV.UA.EDU >> > > Subject: HSM question >> > > >> > > Hi, >> > > I wanted to restore a PDS backed up by HSM. >> > > When I looked, I only found one backup version of the PDS. >> > > When I looked through the HSM logs, I found that it was backed up >> > > many times. >> > > >> > > The PDS is on a NON-SMS volume. >> > > The addvol statement for the volume is: >> > > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) >> > > >> > > Sunday is defined as: >> > > DEFINE DUMPCLASS(SUNDAY DAY(6) - >> > >RETPD(27) AUTOREUSE NORESET - >> > >DATASETRESTORE VTOCCOPIES(0)) >> > > >> > > The default management class says to keep 20 versions of backups: >> > > >> > > What am I doing wrong? >> > > I am running z/OS v2.2. >> > > >> > > Thanks >> > > >> > > Gadi >> > > >> > > >> > > >> > > -- For IBM-MAIN subscribe / signoff / archive access instructions, >> > > send email to lists...@listserv.ua.edu with the message: INFO >> > > IBM-MAIN >> > >> > -- >> > For IBM-MAIN subscribe / signoff / archive access instructions, send >> > email >> to >> > lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > >> > Email secured by Check Point >> > >> > -- >> > For IBM-MAIN subscribe / signoff / archive access instructions, send >> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> Email secured by Check Point >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
If the dsn is non-sms, then it doesn't have a MGMTCLAS. Default MGMTCLAS rules do not apply. Regards Brian On Wed, Sep 11, 2019, 6:39 PM Gadi Ben-Avi, wrote: > Thanks > In the Management Class there are to more options I would like to set: > > How many backup versions of a deleted dataset are kept. > How long the backup is kept. > Do these settings have equivalent setting for Non-SMS datasets? > > Gadi > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of retired mainframer > Sent: Wednesday, September 11, 2019 11:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > Look at the VERSIONS operand of the SETSYS command and the ALTERDS command > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Gadi Ben-Avi > > Sent: Wednesday, September 11, 2019 12:15 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: HSM question > > > > OK, > > So how do I tell HSM to keep more than one backup version? > > > > Gadi > > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Gibney, Dave > > Sent: Wednesday, September 11, 2019 10:09 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: HSM question > > > > MGMTCLAS won't matter for Non-SMS datasets > > > > > -Original Message----- > > > From: IBM Mainframe Discussion List On > > > Behalf Of Gadi Ben-Avi > > > Sent: Tuesday, September 10, 2019 11:39 PM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: HSM question > > > > > > Hi, > > > I wanted to restore a PDS backed up by HSM. > > > When I looked, I only found one backup version of the PDS. > > > When I looked through the HSM logs, I found that it was backed up > > > many times. > > > > > > The PDS is on a NON-SMS volume. > > > The addvol statement for the volume is: > > > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) > > > > > > Sunday is defined as: > > > DEFINE DUMPCLASS(SUNDAY DAY(6) - > > >RETPD(27) AUTOREUSE NORESET - > > >DATASETRESTORE VTOCCOPIES(0)) > > > > > > The default management class says to keep 20 versions of backups: > > > > > > What am I doing wrong? > > > I am running z/OS v2.2. > > > > > > Thanks > > > > > > Gadi > > > > > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO > > > IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email > to > > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > Email secured by Check Point > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Email secured by Check Point > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Gadi, Here is a random snapshot from ISMF's Management Class display for the applicable columns: # BACKUPS# BACKUPS RETAIN DAYS RETAIN DAYS (DS EXISTS) (DS DELETED) ONLY BACKUP EXTRA BACKUPS ---(13) (14) ---(15) (16)- 1 01 1 --- --- ------ 7 2 730730 7 2 180NOLIMIT 1 1 180 30 2 15NOLIMIT 1313 NOLIMITNOLIMIT 1313 NOLIMITNOLIMIT 1313 NOLIMITNOLIMIT 13 3 900900 3 3 180180 13 3 900900 1313 900900 1313 900900 --- --- ------ 1313 NOLIMITNOLIMIT 1313 NOLIMITNOLIMIT 1313 NOLIMITNOLIMIT For non-SMS, look up the ADDVOL command in the manual for stuff enforced at the volume level. For dataset backups, code RETPD and/or EXPDT in the JCL; or use GDGs, etc. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gadi Ben-Avi Sent: Wednesday, September 11, 2019 4:39 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question Thanks In the Management Class there are to more options I would like to set: How many backup versions of a deleted dataset are kept. How long the backup is kept. Do these settings have equivalent setting for Non-SMS datasets? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of retired mainframer Sent: Wednesday, September 11, 2019 11:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question Look at the VERSIONS operand of the SETSYS command and the ALTERDS command > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gadi Ben-Avi > Sent: Wednesday, September 11, 2019 12:15 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > OK, > So how do I tell HSM to keep more than one backup version? > > Gadi > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gibney, Dave > Sent: Wednesday, September 11, 2019 10:09 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > MGMTCLAS won't matter for Non-SMS datasets > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Gadi Ben-Avi > > Sent: Tuesday, September 10, 2019 11:39 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: HSM question > > > > Hi, > > I wanted to restore a PDS backed up by HSM. > > When I looked, I only found one backup version of the PDS. > > When I looked through the HSM logs, I found that it was backed up > > many times. > > > > The PDS is on a NON-SMS volume. > > The addvol statement for the volume is: > > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) > > > > Sunday is defined as: > > DEFINE DUMPCLASS(SUNDAY DAY(6) - > >RETPD(27) AUTOREUSE NORESET - > >DATASETRESTORE VTOCCOPIES(0)) > > > > The default management class says to keep 20 versions of backups: > > > > What am I doing wrong? > > I am running z/OS v2.2. > > > > Thanks > > > > Gadi > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Email secured by Check Point > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Thanks In the Management Class there are to more options I would like to set: How many backup versions of a deleted dataset are kept. How long the backup is kept. Do these settings have equivalent setting for Non-SMS datasets? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of retired mainframer Sent: Wednesday, September 11, 2019 11:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question Look at the VERSIONS operand of the SETSYS command and the ALTERDS command > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gadi Ben-Avi > Sent: Wednesday, September 11, 2019 12:15 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > OK, > So how do I tell HSM to keep more than one backup version? > > Gadi > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gibney, Dave > Sent: Wednesday, September 11, 2019 10:09 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > MGMTCLAS won't matter for Non-SMS datasets > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Gadi Ben-Avi > > Sent: Tuesday, September 10, 2019 11:39 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: HSM question > > > > Hi, > > I wanted to restore a PDS backed up by HSM. > > When I looked, I only found one backup version of the PDS. > > When I looked through the HSM logs, I found that it was backed up > > many times. > > > > The PDS is on a NON-SMS volume. > > The addvol statement for the volume is: > > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) > > > > Sunday is defined as: > > DEFINE DUMPCLASS(SUNDAY DAY(6) - > >RETPD(27) AUTOREUSE NORESET - > >DATASETRESTORE VTOCCOPIES(0)) > > > > The default management class says to keep 20 versions of backups: > > > > What am I doing wrong? > > I am running z/OS v2.2. > > > > Thanks > > > > Gadi > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Email secured by Check Point > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Look at the VERSIONS operand of the SETSYS command and the ALTERDS command > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gadi Ben-Avi > Sent: Wednesday, September 11, 2019 12:15 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > OK, > So how do I tell HSM to keep more than one backup version? > > Gadi > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gibney, Dave > Sent: Wednesday, September 11, 2019 10:09 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > MGMTCLAS won't matter for Non-SMS datasets > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Gadi Ben-Avi > > Sent: Tuesday, September 10, 2019 11:39 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: HSM question > > > > Hi, > > I wanted to restore a PDS backed up by HSM. > > When I looked, I only found one backup version of the PDS. > > When I looked through the HSM logs, I found that it was backed up many > > times. > > > > The PDS is on a NON-SMS volume. > > The addvol statement for the volume is: > > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) > > > > Sunday is defined as: > > DEFINE DUMPCLASS(SUNDAY DAY(6) - > >RETPD(27) AUTOREUSE NORESET - > >DATASETRESTORE VTOCCOPIES(0)) > > > > The default management class says to keep 20 versions of backups: > > > > What am I doing wrong? > > I am running z/OS v2.2. > > > > Thanks > > > > Gadi > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Email secured by Check Point > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
OK, So how do I tell HSM to keep more than one backup version? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gibney, Dave Sent: Wednesday, September 11, 2019 10:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question MGMTCLAS won't matter for Non-SMS datasets > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gadi Ben-Avi > Sent: Tuesday, September 10, 2019 11:39 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: HSM question > > Hi, > I wanted to restore a PDS backed up by HSM. > When I looked, I only found one backup version of the PDS. > When I looked through the HSM logs, I found that it was backed up many > times. > > The PDS is on a NON-SMS volume. > The addvol statement for the volume is: > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) > > Sunday is defined as: > DEFINE DUMPCLASS(SUNDAY DAY(6) - >RETPD(27) AUTOREUSE NORESET - >DATASETRESTORE VTOCCOPIES(0)) > > The default management class says to keep 20 versions of backups: > > What am I doing wrong? > I am running z/OS v2.2. > > Thanks > > Gadi > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
MGMTCLAS won't matter for Non-SMS datasets > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Gadi Ben-Avi > Sent: Tuesday, September 10, 2019 11:39 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: HSM question > > Hi, > I wanted to restore a PDS backed up by HSM. > When I looked, I only found one backup version of the PDS. > When I looked through the HSM logs, I found that it was backed up many > times. > > The PDS is on a NON-SMS volume. > The addvol statement for the volume is: > ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) > > Sunday is defined as: > DEFINE DUMPCLASS(SUNDAY DAY(6) - >RETPD(27) AUTOREUSE NORESET - >DATASETRESTORE VTOCCOPIES(0)) > > The default management class says to keep 20 versions of backups: > > What am I doing wrong? > I am running z/OS v2.2. > > Thanks > > Gadi > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HSM question
Hi, I wanted to restore a PDS backed up by HSM. When I looked, I only found one backup version of the PDS. When I looked through the HSM logs, I found that it was backed up many times. The PDS is on a NON-SMS volume. The addvol statement for the volume is: ADDVOL vv UNIT(3390) PRIMARY(AUTODUMP(SUNDAY) AB) Sunday is defined as: DEFINE DUMPCLASS(SUNDAY DAY(6) - RETPD(27) AUTOREUSE NORESET - DATASETRESTORE VTOCCOPIES(0)) The default management class says to keep 20 versions of backups: What am I doing wrong? I am running z/OS v2.2. Thanks Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [External] Re: HSM question - ML2 copy2 tapes that have no copy1
Thank you, Max, for that excellent response. I'm off to the tape mgmt. doc to figure out how to scratch the tapes. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Max Smith Sent: Friday, February 15, 2019 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Rex, There are 2 places HSM records the DUPLEX volser 1 in the MCV record while the Primary volume is still a partial tape and then in the TTOC record. The DUPLEX tape would be displayed in the LIST TTOC output if the Primary volume still existed. If it doesn't show in the LIST TTOC output then HSM does not know anything about the tape. There will be no commands in HSM that will return it to scratch, HSM should have done that when HSM returned the Primary volume to scratch. At this point you should be able to return the volumes to scratch via your Tape Management system. I know there is a way in TMS that you can force the return to scratch of these tapes as I have directed other clients to do this in the past. Max Smith DFSMShsm Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question - ML2 copy2 tapes that have no copy1
Rex, There are 2 places HSM records the DUPLEX volser 1 in the MCV record while the Primary volume is still a partial tape and then in the TTOC record. The DUPLEX tape would be displayed in the LIST TTOC output if the Primary volume still existed. If it doesn't show in the LIST TTOC output then HSM does not know anything about the tape. There will be no commands in HSM that will return it to scratch, HSM should have done that when HSM returned the Primary volume to scratch. At this point you should be able to return the volumes to scratch via your Tape Management system. I know there is a way in TMS that you can force the return to scratch of these tapes as I have directed other clients to do this in the past. Max Smith DFSMShsm Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question - ML2 copy2 tapes that have no copy1
This can be done, however it's been a long long time since I have used HSM duplex tapes. A PMR w/IBM would probably shortcut this process. Glenn Wilcox is very good about responding. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, February 14, 2019 2:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question - ML2 copy2 tapes that have no copy1 I get "entry not defined". Unfortunately that doesn't help, because on my playground I have duplex tapes with their primary ML2 tape still existent, and I get the same "not defined" message. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: Thursday, February 14, 2019 12:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Try HSEND DELVOL(XX) PURGE FORCE(?) I haven't looked up the syntax. Actually, if they are not in the TTOC you can probably just expire them. Not sure if you are using RMM, TMS, or other, but RMM had a quirk, whereby if the tape ever had a permanent error (as defined by having a SWAP associated) the volume would not go scratch until replaced. Don't remember the exact details. Al -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, February 14, 2019 11:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question - ML2 copy2 tapes that have no copy1 Allan, Sorry, this doesn't help. The LIST TTOC is only showing my VTS-based ML2 tapes which have no duplex. BTW, LIST TTOC does show duplex volumes if they exist. :-) These duplex tapes all have old create dates and so I am confident they are orphans. Now, how to get rid of them. I'll try the TAPEREPL process in a test environment to see what happens. Thanks. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: Thursday, February 14, 2019 8:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Most likely a continuation of a prior volume. Without going into a lot of detail, if a dataset spans from 1 volume to another the 1st volume in the sequence "owns it". Duplex volumes are never referenced by DFHSM directly. HSEND LIST TTOC will list all primary voulmes. I expect the duplex volumes will also be shown, but I am not sure. It has been too long since I've duplexed. This *will* show the predecessor and successor volumes. I expect the "offending" volsers to be successor volumes. HSEND LIST TTOC(volser) will give you a list of datasets on the volume. Use this to obtain the "English" name of the datset. At this point there are 2 choices. HDELETE 'DSN' for the dataset that spans volumes. This will automatically delete the duplex volumes. Use the output of the HSEND LIST TTOC to obtain the "owning" primary volume. Recycle the "owning" primary volume. The "offending" duplex volumes will be deleted as part of the recycle process. HSEND RECYCLE EXECUTE VOLUME(owning volser) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Wednesday, February 13, 2019 4:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 copy2 tapes that have no copy1 Hello list, I have a few HSM ML2 duplex tapes that no longer have their corresponding migrate tapes that I can't seem to get rid of. If I try to do DELVOL, I get an error saying they're not defined migrate volumes. What we're doing is migrating our HSM ML2 environment into a VTS (replicated) and eliminating the duplex tapes. I have these 4 duplex tapes from 2015 and 2017 that I can't get rid of. I think HSM still knows about these tapes and if I try to scratch them in the TMS, it says they're owned by an external data manager (ie HSM). Any thoughts on how to cleanly get rid of these tapes? I've looked at TAPEREPL but don't know if that would be a solution or not. TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send
Re: HSM question - ML2 copy2 tapes that have no copy1
I get "entry not defined". Unfortunately that doesn't help, because on my playground I have duplex tapes with their primary ML2 tape still existent, and I get the same "not defined" message. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: Thursday, February 14, 2019 12:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Try HSEND DELVOL(XX) PURGE FORCE(?) I haven't looked up the syntax. Actually, if they are not in the TTOC you can probably just expire them. Not sure if you are using RMM, TMS, or other, but RMM had a quirk, whereby if the tape ever had a permanent error (as defined by having a SWAP associated) the volume would not go scratch until replaced. Don't remember the exact details. Al -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, February 14, 2019 11:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question - ML2 copy2 tapes that have no copy1 Allan, Sorry, this doesn't help. The LIST TTOC is only showing my VTS-based ML2 tapes which have no duplex. BTW, LIST TTOC does show duplex volumes if they exist. :-) These duplex tapes all have old create dates and so I am confident they are orphans. Now, how to get rid of them. I'll try the TAPEREPL process in a test environment to see what happens. Thanks. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: Thursday, February 14, 2019 8:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Most likely a continuation of a prior volume. Without going into a lot of detail, if a dataset spans from 1 volume to another the 1st volume in the sequence "owns it". Duplex volumes are never referenced by DFHSM directly. HSEND LIST TTOC will list all primary voulmes. I expect the duplex volumes will also be shown, but I am not sure. It has been too long since I've duplexed. This *will* show the predecessor and successor volumes. I expect the "offending" volsers to be successor volumes. HSEND LIST TTOC(volser) will give you a list of datasets on the volume. Use this to obtain the "English" name of the datset. At this point there are 2 choices. HDELETE 'DSN' for the dataset that spans volumes. This will automatically delete the duplex volumes. Use the output of the HSEND LIST TTOC to obtain the "owning" primary volume. Recycle the "owning" primary volume. The "offending" duplex volumes will be deleted as part of the recycle process. HSEND RECYCLE EXECUTE VOLUME(owning volser) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Wednesday, February 13, 2019 4:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 copy2 tapes that have no copy1 Hello list, I have a few HSM ML2 duplex tapes that no longer have their corresponding migrate tapes that I can't seem to get rid of. If I try to do DELVOL, I get an error saying they're not defined migrate volumes. What we're doing is migrating our HSM ML2 environment into a VTS (replicated) and eliminating the duplex tapes. I have these 4 duplex tapes from 2015 and 2017 that I can't get rid of. I think HSM still knows about these tapes and if I try to scratch them in the TMS, it says they're owned by an external data manager (ie HSM). Any thoughts on how to cleanly get rid of these tapes? I've looked at TAPEREPL but don't know if that would be a solution or not. TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed
Re: HSM question - ML2 copy2 tapes that have no copy1
Try HSEND DELVOL(XX) PURGE FORCE(?) I haven't looked up the syntax. Actually, if they are not in the TTOC you can probably just expire them. Not sure if you are using RMM, TMS, or other, but RMM had a quirk, whereby if the tape ever had a permanent error (as defined by having a SWAP associated) the volume would not go scratch until replaced. Don't remember the exact details. Al -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, February 14, 2019 11:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question - ML2 copy2 tapes that have no copy1 Allan, Sorry, this doesn't help. The LIST TTOC is only showing my VTS-based ML2 tapes which have no duplex. BTW, LIST TTOC does show duplex volumes if they exist. :-) These duplex tapes all have old create dates and so I am confident they are orphans. Now, how to get rid of them. I'll try the TAPEREPL process in a test environment to see what happens. Thanks. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: Thursday, February 14, 2019 8:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Most likely a continuation of a prior volume. Without going into a lot of detail, if a dataset spans from 1 volume to another the 1st volume in the sequence "owns it". Duplex volumes are never referenced by DFHSM directly. HSEND LIST TTOC will list all primary voulmes. I expect the duplex volumes will also be shown, but I am not sure. It has been too long since I've duplexed. This *will* show the predecessor and successor volumes. I expect the "offending" volsers to be successor volumes. HSEND LIST TTOC(volser) will give you a list of datasets on the volume. Use this to obtain the "English" name of the datset. At this point there are 2 choices. HDELETE 'DSN' for the dataset that spans volumes. This will automatically delete the duplex volumes. Use the output of the HSEND LIST TTOC to obtain the "owning" primary volume. Recycle the "owning" primary volume. The "offending" duplex volumes will be deleted as part of the recycle process. HSEND RECYCLE EXECUTE VOLUME(owning volser) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Wednesday, February 13, 2019 4:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 copy2 tapes that have no copy1 Hello list, I have a few HSM ML2 duplex tapes that no longer have their corresponding migrate tapes that I can't seem to get rid of. If I try to do DELVOL, I get an error saying they're not defined migrate volumes. What we're doing is migrating our HSM ML2 environment into a VTS (replicated) and eliminating the duplex tapes. I have these 4 duplex tapes from 2015 and 2017 that I can't get rid of. I think HSM still knows about these tapes and if I try to scratch them in the TMS, it says they're owned by an external data manager (ie HSM). Any thoughts on how to cleanly get rid of these tapes? I've looked at TAPEREPL but don't know if that would be a solution or not. TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL
Re: HSM question - ML2 copy2 tapes that have no copy1
Allan, Sorry, this doesn't help. The LIST TTOC is only showing my VTS-based ML2 tapes which have no duplex. BTW, LIST TTOC does show duplex volumes if they exist. :-) These duplex tapes all have old create dates and so I am confident they are orphans. Now, how to get rid of them. I'll try the TAPEREPL process in a test environment to see what happens. Thanks. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: Thursday, February 14, 2019 8:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: HSM question - ML2 copy2 tapes that have no copy1 Most likely a continuation of a prior volume. Without going into a lot of detail, if a dataset spans from 1 volume to another the 1st volume in the sequence "owns it". Duplex volumes are never referenced by DFHSM directly. HSEND LIST TTOC will list all primary voulmes. I expect the duplex volumes will also be shown, but I am not sure. It has been too long since I've duplexed. This *will* show the predecessor and successor volumes. I expect the "offending" volsers to be successor volumes. HSEND LIST TTOC(volser) will give you a list of datasets on the volume. Use this to obtain the "English" name of the datset. At this point there are 2 choices. HDELETE 'DSN' for the dataset that spans volumes. This will automatically delete the duplex volumes. Use the output of the HSEND LIST TTOC to obtain the "owning" primary volume. Recycle the "owning" primary volume. The "offending" duplex volumes will be deleted as part of the recycle process. HSEND RECYCLE EXECUTE VOLUME(owning volser) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Wednesday, February 13, 2019 4:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 copy2 tapes that have no copy1 Hello list, I have a few HSM ML2 duplex tapes that no longer have their corresponding migrate tapes that I can't seem to get rid of. If I try to do DELVOL, I get an error saying they're not defined migrate volumes. What we're doing is migrating our HSM ML2 environment into a VTS (replicated) and eliminating the duplex tapes. I have these 4 duplex tapes from 2015 and 2017 that I can't get rid of. I think HSM still knows about these tapes and if I try to scratch them in the TMS, it says they're owned by an external data manager (ie HSM). Any thoughts on how to cleanly get rid of these tapes? I've looked at TAPEREPL but don't know if that would be a solution or not. TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or a
Re: HSM question - ML2 copy2 tapes that have no copy1
Most likely a continuation of a prior volume. Without going into a lot of detail, if a dataset spans from 1 volume to another the 1st volume in the sequence "owns it". Duplex volumes are never referenced by DFHSM directly. HSEND LIST TTOC will list all primary voulmes. I expect the duplex volumes will also be shown, but I am not sure. It has been too long since I've duplexed. This *will* show the predecessor and successor volumes. I expect the "offending" volsers to be successor volumes. HSEND LIST TTOC(volser) will give you a list of datasets on the volume. Use this to obtain the "English" name of the datset. At this point there are 2 choices. HDELETE 'DSN' for the dataset that spans volumes. This will automatically delete the duplex volumes. Use the output of the HSEND LIST TTOC to obtain the "owning" primary volume. Recycle the "owning" primary volume. The "offending" duplex volumes will be deleted as part of the recycle process. HSEND RECYCLE EXECUTE VOLUME(owning volser) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Wednesday, February 13, 2019 4:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 copy2 tapes that have no copy1 Hello list, I have a few HSM ML2 duplex tapes that no longer have their corresponding migrate tapes that I can't seem to get rid of. If I try to do DELVOL, I get an error saying they're not defined migrate volumes. What we're doing is migrating our HSM ML2 environment into a VTS (replicated) and eliminating the duplex tapes. I have these 4 duplex tapes from 2015 and 2017 that I can't get rid of. I think HSM still knows about these tapes and if I try to scratch them in the TMS, it says they're owned by an external data manager (ie HSM). Any thoughts on how to cleanly get rid of these tapes? I've looked at TAPEREPL but don't know if that would be a solution or not. TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HSM question - ML2 copy2 tapes that have no copy1
Hello list, I have a few HSM ML2 duplex tapes that no longer have their corresponding migrate tapes that I can't seem to get rid of. If I try to do DELVOL, I get an error saying they're not defined migrate volumes. What we're doing is migrating our HSM ML2 environment into a VTS (replicated) and eliminating the duplex tapes. I have these 4 duplex tapes from 2015 and 2017 that I can't get rid of. I think HSM still knows about these tapes and if I try to scratch them in the TMS, it says they're owned by an external data manager (ie HSM). Any thoughts on how to cleanly get rid of these tapes? I've looked at TAPEREPL but don't know if that would be a solution or not. TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question - ML2 tapes no longer avaialble
IMO, an empty tape has no value. HSM will not even mount attempt to mount it for the recycle. That being said, HDELVOL volser MIGRATION(PURGE) will also work just fine. -Original Message- From: IBM Mainframe Discussion List On Behalf Of retired mainframer Sent: Wednesday, February 13, 2019 9:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question - ML2 tapes no longer avaialble Two recommendations below > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Allan Staller > Sent: Wednesday, February 13, 2019 7:03 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question - ML2 tapes no longer avaialble > > For each affected volser: > > HSEND LIST TTOC(volser) ODS(x) > HDEL 'datasetname' for each indicated dataset. Add the PURGE operand to the HDEL command in case any datasets have long retention. > HSEND RECYCLE ALL EXECUTE PERCENTVALID(0) HDELVOL volser MIGRATION(PURGE) might be safer (will not affect any other empty tapes). > HTH, > > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Tony Thigpen > Sent: Wednesday, February 13, 2019 9:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: HSM question - ML2 tapes no longer avaialble > > Several years ago, the HSM tapes were migrated from 3490 to 3590. > > At that time, two 3490 tapes were unreadable so the systems programmer just skipped > the recycle and went on to the next tape. So, now I have 2 > 3490 tapes still in my CDS and I want to remove them. These tapes were created back > in 2001, so we are just going to write-off the data on the tapes as 'aged-out'. > > What is the proper procedure to eliminate these volumes from HSM? > > -- > Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question - ML2 tapes no longer avaialble
Thanks. Tony Thigpen Allan Staller wrote on 2/13/19 10:02 AM: For each affected volser: HSEND LIST TTOC(volser) ODS(x) HDEL 'datasetname' for each indicated dataset. HSEND RECYCLE ALL EXECUTE PERCENTVALID(0) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tony Thigpen Sent: Wednesday, February 13, 2019 9:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 tapes no longer avaialble Several years ago, the HSM tapes were migrated from 3490 to 3590. At that time, two 3490 tapes were unreadable so the systems programmer just skipped the recycle and went on to the next tape. So, now I have 2 3490 tapes still in my CDS and I want to remove them. These tapes were created back in 2001, so we are just going to write-off the data on the tapes as 'aged-out'. What is the proper procedure to eliminate these volumes from HSM? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question - ML2 tapes no longer avaialble
Two recommendations below > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Allan Staller > Sent: Wednesday, February 13, 2019 7:03 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question - ML2 tapes no longer avaialble > > For each affected volser: > > HSEND LIST TTOC(volser) ODS(x) > HDEL 'datasetname' for each indicated dataset. Add the PURGE operand to the HDEL command in case any datasets have long retention. > HSEND RECYCLE ALL EXECUTE PERCENTVALID(0) HDELVOL volser MIGRATION(PURGE) might be safer (will not affect any other empty tapes). > HTH, > > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Tony Thigpen > Sent: Wednesday, February 13, 2019 9:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: HSM question - ML2 tapes no longer avaialble > > Several years ago, the HSM tapes were migrated from 3490 to 3590. > > At that time, two 3490 tapes were unreadable so the systems programmer just skipped > the recycle and went on to the next tape. So, now I have 2 > 3490 tapes still in my CDS and I want to remove them. These tapes were created back > in 2001, so we are just going to write-off the data on the tapes as 'aged-out'. > > What is the proper procedure to eliminate these volumes from HSM? > > -- > Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question - ML2 tapes no longer avaialble
For each affected volser: HSEND LIST TTOC(volser) ODS(x) HDEL 'datasetname' for each indicated dataset. HSEND RECYCLE ALL EXECUTE PERCENTVALID(0) HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tony Thigpen Sent: Wednesday, February 13, 2019 9:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question - ML2 tapes no longer avaialble Several years ago, the HSM tapes were migrated from 3490 to 3590. At that time, two 3490 tapes were unreadable so the systems programmer just skipped the recycle and went on to the next tape. So, now I have 2 3490 tapes still in my CDS and I want to remove them. These tapes were created back in 2001, so we are just going to write-off the data on the tapes as 'aged-out'. What is the proper procedure to eliminate these volumes from HSM? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HSM question - ML2 tapes no longer avaialble
Several years ago, the HSM tapes were migrated from 3490 to 3590. At that time, two 3490 tapes were unreadable so the systems programmer just skipped the recycle and went on to the next tape. So, now I have 2 3490 tapes still in my CDS and I want to remove them. These tapes were created back in 2001, so we are just going to write-off the data on the tapes as 'aged-out'. What is the proper procedure to eliminate these volumes from HSM? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
You might also review this Technote that explains various reasons and things to look at to see what might be going on. http://www-01.ibm.com/support/docview.wss?uid=isg3T1023379 Max Smith IBM DFSMS HSM Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
PSM should expire eligible datasets, regardless of volume residency levels. Have a look at the bottom few paragraphs here, specifically: "Pass 1 of automatic primary space management <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.arcf000/pass1a.htm?view=kc#pass1a> (non-data-movement function in primary space management) and extent reduction are performed for all volumes in storage groups defined with AM=Y and AM=I (SG1, SG2, and SG3). Pass 2 of automatic primary space management <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.arcf000/pass2a.htm?view=kc#pass2a> (migration) is performed only for those volumes that are above the low threshold after pass 1 and extent reduction have completed." https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.arcf000/stgbmgd.htm Have a look at the HSM log messages being produced for the datasets which you expect to be expired. They should indicate why they are not being expired. On 5 March 2018 at 18:26, Mike Schwab <mike.a.sch...@gmail.com> wrote: > Set one volume to Quiesce,New and migrate the volume. Whatever is > left try to manually migrate and note error. Return to spare if you > don't need the space, or Enable to return to active use. Proceed with > next volume. Or just reduce high threshold so it will process all > volumes, return after cleanup. > > On Mon, Mar 5, 2018 at 10:37 AM, willie bunter > <001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > > I verified the MC and DSORGs. No problem found. No patches either > which would impede the PSM. I remember reading or being told that once the > SM conditions had been met, HSM stops looking at the volume(s). > > > > From: Graham Harris <harris...@gmail.com> > > To: IBM-MAIN@LISTSERV.UA.EDU > > Sent: Friday, March 2, 2018 6:05 PM > > Subject: Re: SMS/HSM QUESTION > > > > Primary space management should normally process all volumes in a storage > > group. And PSM should normally look to reduce utilisation of a volume > down > > to the low threshold (caveat - various PATCHes can alter DFHSM standard > > behaviour). > > Have you checked the messages for space management actions for these > > datasets? > > It could be that they need to be backed-up before being expired, and > > auto-backup may not be running against that SG (as an example of a > > condition that could potentially give rise to what you are seeing). > > Or another possibility is that they cant be backed up, because, for > > example, they may have a null DSORG. If they cant be backed-up, and the > > management class says they must be backed up, then DFHSM will not expire > > them until they are backed up. > > > > The above may not precisely match what you are experiencing, but it may > > perhaps point you in a better direction. > > > > On 1 March 2018 at 16:18, Willie Bunter < > > 001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > > > >> Thanks for the info., however it doesn't answer my question as to which > >> threshold I should modify. > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
Set one volume to Quiesce,New and migrate the volume. Whatever is left try to manually migrate and note error. Return to spare if you don't need the space, or Enable to return to active use. Proceed with next volume. Or just reduce high threshold so it will process all volumes, return after cleanup. On Mon, Mar 5, 2018 at 10:37 AM, willie bunter <001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > I verified the MC and DSORGs. No problem found. No patches either which > would impede the PSM. I remember reading or being told that once the SM > conditions had been met, HSM stops looking at the volume(s). > > From: Graham Harris <harris...@gmail.com> > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Friday, March 2, 2018 6:05 PM > Subject: Re: SMS/HSM QUESTION > > Primary space management should normally process all volumes in a storage > group. And PSM should normally look to reduce utilisation of a volume down > to the low threshold (caveat - various PATCHes can alter DFHSM standard > behaviour). > Have you checked the messages for space management actions for these > datasets? > It could be that they need to be backed-up before being expired, and > auto-backup may not be running against that SG (as an example of a > condition that could potentially give rise to what you are seeing). > Or another possibility is that they cant be backed up, because, for > example, they may have a null DSORG. If they cant be backed-up, and the > management class says they must be backed up, then DFHSM will not expire > them until they are backed up. > > The above may not precisely match what you are experiencing, but it may > perhaps point you in a better direction. > > On 1 March 2018 at 16:18, Willie Bunter < > 001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > >> Thanks for the info., however it doesn't answer my question as to which >> threshold I should modify. >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
I verified the MC and DSORGs. No problem found. No patches either which would impede the PSM. I remember reading or being told that once the SM conditions had been met, HSM stops looking at the volume(s). From: Graham Harris <harris...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, March 2, 2018 6:05 PM Subject: Re: SMS/HSM QUESTION Primary space management should normally process all volumes in a storage group. And PSM should normally look to reduce utilisation of a volume down to the low threshold (caveat - various PATCHes can alter DFHSM standard behaviour). Have you checked the messages for space management actions for these datasets? It could be that they need to be backed-up before being expired, and auto-backup may not be running against that SG (as an example of a condition that could potentially give rise to what you are seeing). Or another possibility is that they cant be backed up, because, for example, they may have a null DSORG. If they cant be backed-up, and the management class says they must be backed up, then DFHSM will not expire them until they are backed up. The above may not precisely match what you are experiencing, but it may perhaps point you in a better direction. On 1 March 2018 at 16:18, Willie Bunter < 001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > Thanks for the info., however it doesn't answer my question as to which > threshold I should modify. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
Primary space management should normally process all volumes in a storage group. And PSM should normally look to reduce utilisation of a volume down to the low threshold (caveat - various PATCHes can alter DFHSM standard behaviour). Have you checked the messages for space management actions for these datasets? It could be that they need to be backed-up before being expired, and auto-backup may not be running against that SG (as an example of a condition that could potentially give rise to what you are seeing). Or another possibility is that they cant be backed up, because, for example, they may have a null DSORG. If they cant be backed-up, and the management class says they must be backed up, then DFHSM will not expire them until they are backed up. The above may not precisely match what you are experiencing, but it may perhaps point you in a better direction. On 1 March 2018 at 16:18, Willie Bunter < 001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > Thanks for the info., however it doesn't answer my question as to which > threshold I should modify. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
Thanks for the info., however it doesn't answer my question as to which threshold I should modify. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS/HSM QUESTION
The Track-managed deals with the first 64K cylinders. The other one deals with the EAV 21 Cylinder managed portion past the first 64K cylinders. On Tue, Feb 27, 2018 at 8:55 AM, willie bunter <001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > Good Day To All, > > I am trouble shooting a problem caused by space abends. I looked at all of > the 54 SMS managed volumes > > (via ISPF 3.4) and I found 2,930 dsns which are allocated on this specific > Storage Group which were created in Dec.2017 and have not been referenced > since their creation. > According to the Management class, the dsns are to be deleted after 2 days of > non reference. Primary and Secondary Space management are run daily on this > Storage Group. Since the threshold requirements are being met, SMS does not > process some of these volumes. I was thinking of lowering the threshold in > order to get SMS to select most of the volumes when Space management is run. > > My question is do I modify the Allocation/migration Threshold or the > Alloc/Migr Threshold Track-Managed. > > Below is threshold settings: > Allocation/migration Threshold : High85 > (1-100) Low . . 1 (0-99) > Alloc/Migr Threshold Track-Managed:High85 > (1-100) Low . . 1 (0-99) > > Thanks in advance for your suggestions. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SMS/HSM QUESTION
Good Day To All, I am trouble shooting a problem caused by space abends. I looked at all of the 54 SMS managed volumes (via ISPF 3.4) and I found 2,930 dsns which are allocated on this specific Storage Group which were created in Dec.2017 and have not been referenced since their creation. According to the Management class, the dsns are to be deleted after 2 days of non reference. Primary and Secondary Space management are run daily on this Storage Group. Since the threshold requirements are being met, SMS does not process some of these volumes. I was thinking of lowering the threshold in order to get SMS to select most of the volumes when Space management is run. My question is do I modify the Allocation/migration Threshold or the Alloc/Migr Threshold Track-Managed. Below is threshold settings: Allocation/migration Threshold : High85 (1-100) Low . . 1 (0-99) Alloc/Migr Threshold Track-Managed:High85 (1-100) Low . . 1 (0-99) Thanks in advance for your suggestions. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Do the del/def. populate it then issue a HMIG Sent from my iPhone Sorry for any grammar problems > On Sep 22, 2017, at 16:28, Lizette Koehler <stars...@mindspring.com> wrote: > > Is there a way for your to create a VSAM dataset with Data and Index component > and then migrate it to see what it looks like? > > That might help answer your questions. > > Lizette > > >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of PINION, RICHARD W. >> Sent: Friday, September 22, 2017 10:06 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: HSM question >> >> When a VSAM data set is migrated is the cluster, index, and data component >> displayed under ISPF 3.4 as migrated? Or is only the cluster name shown? >> FIRST TENNESSEE >> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Is there a way for your to create a VSAM dataset with Data and Index component and then migrate it to see what it looks like? That might help answer your questions. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of PINION, RICHARD W. > Sent: Friday, September 22, 2017 10:06 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: HSM question > > When a VSAM data set is migrated is the cluster, index, and data component > displayed under ISPF 3.4 as migrated? Or is only the cluster name shown? > FIRST TENNESSEE > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
All three should show MIGRAT and all three will still show up as they are all in the catalog. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of PINION, RICHARD W. Sent: Friday, September 22, 2017 1:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question When a VSAM data set is migrated is the cluster, index, and data component displayed under ISPF 3.4 as migrated? Or is only the cluster name shown? FIRST TENNESSEE Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HSM question
When a VSAM data set is migrated is the cluster, index, and data component displayed under ISPF 3.4 as migrated? Or is only the cluster name shown? FIRST TENNESSEE Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Run a list of your assigned tapes. Recycle any that are not marked full. They were created before you got the setting correct. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Tony Thigpen > Sent: Thursday, November 24, 2016 2:39 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > That's what I thought, but it does not seem to be working. So, I figured I was > misreading or doing something wrong. > > Tony Thigpen > > retired mainframer wrote on 11/24/2016 04:42 PM: > > Doesn't SETSYS PARTIALTAPE(BAKCUP(MARKFULL)) do what you want? > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM- > m...@listserv.ua.edu] > > On Behalf Of Tony Thigpen > > Sent: Thursday, November 24, 2016 7:30 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: HSM question > > > > The elapsed time is 10 minutes. > > > > Before we get off-track too much, the end result we are looking for is: > > We want the HSM backup process to *always* use a scratch tape. We > > never want it to ask for an existing tape to append to. > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Tony, When DFHSM does migration and backup by dataset (not an auto-function) it will not MARKFULL the tape. Make sure you users are not doing this. An HBACKUP or a HMIGRATE command should send the result to ML1 DASD unless ML2 is specified on the HMIGRATE command. There are settings in the management class to stop the users issuing these commands. . Richard On Fri, Nov 25, 2016 at 12:39 AM, Tony Thigpen <t...@vse2pdf.com> wrote: > That's what I thought, but it does not seem to be working. So, I figured I > was misreading or doing something wrong. > > Tony Thigpen > > > retired mainframer wrote on 11/24/2016 04:42 PM: > >> Doesn't SETSYS PARTIALTAPE(BAKCUP(MARKFULL)) do what you want? >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Tony Thigpen >> Sent: Thursday, November 24, 2016 7:30 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: HSM question >> >> The elapsed time is 10 minutes. >> >> Before we get off-track too much, the end result we are looking for is: >> We want the HSM backup process to *always* use a scratch tape. We never >> want it to ask for an existing tape to append to. >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> >> > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
That's what I thought, but it does not seem to be working. So, I figured I was misreading or doing something wrong. Tony Thigpen retired mainframer wrote on 11/24/2016 04:42 PM: Doesn't SETSYS PARTIALTAPE(BAKCUP(MARKFULL)) do what you want? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Thursday, November 24, 2016 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question The elapsed time is 10 minutes. Before we get off-track too much, the end result we are looking for is: We want the HSM backup process to *always* use a scratch tape. We never want it to ask for an existing tape to append to. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Doesn't SETSYS PARTIALTAPE(BAKCUP(MARKFULL)) do what you want? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Thursday, November 24, 2016 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HSM question The elapsed time is 10 minutes. Before we get off-track too much, the end result we are looking for is: We want the HSM backup process to *always* use a scratch tape. We never want it to ask for an existing tape to append to. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
The elapsed time is 10 minutes. Before we get off-track too much, the end result we are looking for is: We want the HSM backup process to *always* use a scratch tape. We never want it to ask for an existing tape to append to. We will recycle the tapes to combine them at our convenience. But, as best I can tell, the HSM control parms are already set to not use an existing tape: SETSYS PARTIALTAPE( BACKUP(MARKFULL) - MIGRATION(MARKFULL)) SETSYS SELECTVOLUME( BACKUP(SCRATCH) MIGRATION(SCRATCH) - DUMP(SCRATCH)) Tony Thigpen Elardus Engelbrecht wrote on 11/24/2016 09:09 AM: Tony Thigpen wrote: The remote operator is a human. Tape management system is CA1 Still researching logs. Thanks. I see that output and logs you gave to Lizette. I see you have MOUNT WAIT TIME=010 MINUTE(S), but what are the [elapsed] times for these messages and reply? *IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET *0037 ARC0310A CAN TAPE 015010 BE MOUNTED? REPLY Y OR N R 37,N You said it asked for another mount, is that for this message for which you drove in your car to do that mount? ARC0421I BACKUP VOLUME 015010 IS NOW MARKED FULL Just probing questions, because when I was a HSM admin ages ago, I got many gray hairs about those mounts... It is one of those things for which an autoreply is not going to work always in a 'lights-out 24/7' environment. Good luck! You will need all the help you are deserving. I hope you can get a good solution for this PITA. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Other options: 1) Use Automation tool or MPF to automatically respond Y or N 2) Find out where the tape resides physically. Is it on a desk or next to the tape drives? At some shops I have worked at, we automatically responded N to this message and just let DFHSM pick it up next time and allow it to move on to the next task. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Thursday, November 24, 2016 7:36 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > So I would say your MOUNTWAITTIME of 10mins is too short. The default for HSM > is 15 mins if it is not coded. > > You probably need to do the following > > 1) Change the mount wait time to make it longer. > 2) Review the history of tape mounts in general and see what is going on > when HSM is getting the ARC0310A > 3) Review IBMLINK for OS/390 V2.10 and see if there are any ptfs you have > not installed on DFHSM. > 4) Look at the running STC JCL for DFHSM. See what Parmlib member it is > running with. > What you think is the right dataset(member) might be different in the STC > JCL. > > When working with mount wait times, if HSM is held up too long, it may cause > issues as well. > > See if the mount wait time in the ARCCMDxx member is the same as the Q SETSYS > information. > > See when the last date the ARCCMDxx member was changed. If recent, then it is > possible someone updated it > > > There are tools to help with analyzing tape mount issues. IBM has Volume > Mount Analyzer, as well as the TAPETOOLS. > > If you have other products that can read SMF, then you could use those as > well. > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Elardus Engelbrecht > > Sent: Thursday, November 24, 2016 7:09 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: HSM question > > > > Tony Thigpen wrote: > > > > >The remote operator is a human. > > >Tape management system is CA1 > > >Still researching logs. > > > > Thanks. I see that output and logs you gave to Lizette. > > > > I see you have MOUNT WAIT TIME=010 MINUTE(S), but what are the > > [elapsed] times for these messages and reply? > > > > *IEC501A M > > 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET > > *0037 ARC0310A CAN TAPE 015010 BE MOUNTED? REPLY Y OR N > > R 37,N > > > > You said it asked for another mount, is that for this message for > > which you drove in your car to do that mount? > > > > ARC0421I BACKUP VOLUME 015010 IS NOW MARKED FULL > > > > Just probing questions, because when I was a HSM admin ages ago, I got > > many gray hairs about those mounts... > > > > It is one of those things for which an autoreply is not going to work > > always in a 'lights-out 24/7' environment. > > > > Good luck! You will need all the help you are deserving. I hope you > > can get a good solution for this PITA. > > > > Groete / Greetings > > Elardus Engelbrecht > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
So I would say your MOUNTWAITTIME of 10mins is too short. The default for HSM is 15 mins if it is not coded. You probably need to do the following 1) Change the mount wait time to make it longer. 2) Review the history of tape mounts in general and see what is going on when HSM is getting the ARC0310A 3) Review IBMLINK for OS/390 V2.10 and see if there are any ptfs you have not installed on DFHSM. 4) Look at the running STC JCL for DFHSM. See what Parmlib member it is running with. What you think is the right dataset(member) might be different in the STC JCL. When working with mount wait times, if HSM is held up too long, it may cause issues as well. See if the mount wait time in the ARCCMDxx member is the same as the Q SETSYS information. See when the last date the ARCCMDxx member was changed. If recent, then it is possible someone updated it There are tools to help with analyzing tape mount issues. IBM has Volume Mount Analyzer, as well as the TAPETOOLS. If you have other products that can read SMF, then you could use those as well. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Elardus Engelbrecht > Sent: Thursday, November 24, 2016 7:09 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > Tony Thigpen wrote: > > >The remote operator is a human. > >Tape management system is CA1 > >Still researching logs. > > Thanks. I see that output and logs you gave to Lizette. > > I see you have MOUNT WAIT TIME=010 MINUTE(S), but what are the [elapsed] times > for these messages and reply? > > *IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET > *0037 ARC0310A CAN TAPE 015010 BE MOUNTED? REPLY Y OR N > R 37,N > > You said it asked for another mount, is that for this message for which you > drove in your car to do that mount? > > ARC0421I BACKUP VOLUME 015010 IS NOW MARKED FULL > > Just probing questions, because when I was a HSM admin ages ago, I got many > gray hairs about those mounts... > > It is one of those things for which an autoreply is not going to work always > in a 'lights-out 24/7' environment. > > Good luck! You will need all the help you are deserving. I hope you can get a > good solution for this PITA. > > Groete / Greetings > Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Tony Thigpen wrote: >The remote operator is a human. >Tape management system is CA1 >Still researching logs. Thanks. I see that output and logs you gave to Lizette. I see you have MOUNT WAIT TIME=010 MINUTE(S), but what are the [elapsed] times for these messages and reply? *IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET *0037 ARC0310A CAN TAPE 015010 BE MOUNTED? REPLY Y OR N R 37,N You said it asked for another mount, is that for this message for which you drove in your car to do that mount? ARC0421I BACKUP VOLUME 015010 IS NOW MARKED FULL Just probing questions, because when I was a HSM admin ages ago, I got many gray hairs about those mounts... It is one of those things for which an autoreply is not going to work always in a 'lights-out 24/7' environment. Good luck! You will need all the help you are deserving. I hope you can get a good solution for this PITA. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
So what was your analysis of the ARC0310A message ARC0310A CAN TAPE volser BE MOUNTED ON DEVICE devno? REPLY Y OR N Explanation The wait time as established by the DFSMShsm SETSYS command for open or end-of-volume (EOV) processing of a tape data set has elapsed and open or EOV processing has not returned control to DFSMShsm. If the tape with volume serial number volser is available and can be mounted within the next mount wait time period, reply Y. Otherwise, reply N. If the reply is Y, and the wait time again elapses before open or EOV processing completes, open or EOV fails and the currently running task is detached. System action The current DFSMShsm task waits until a reply is received. If the waiting task holds resources critical for DFSMShsm processing, all of DFSMShsm may eventually be waiting for the reply. If the reply is Y, DFSMShsm resets the time to the user mount wait time and continues to wait for mount completion. If the reply is N, the mount request ends and the DFSMShsm function (migration, recall, backup, recovery, or recycle) ends if the mount was for an input volume or continues using another volume if the mount was for an output volume. If the reply is N and the DFSMShsm function is volume dump or volume restore using DFSMSdss, the mount request ends and the DFSMShsm function ends. Operator response If the tape with volume serial number volser is available and can be mounted within the time allowed, reply Y and mount the specified tape. Otherwise reply N. If the time period is not known, issue the QUERY command with the SETSYS parameter and look at the MOUNT WAIT TIME value displayed in message ARC0147I. Did you check out the Wait time in HSM to see why it was taking longer than normal for the tape mount? >From the DFHSM Storage Admin manual: MOUNTWAITTIME: Specifying the time DFSMShsm waits for a tape mount and open Explanation: MOUNTWAITTIME(minutes) is an optional parameter specifying the time, in minutes, that DFSMShsm waits for the tape volume to be mounted and opened. For minutes, substitute a decimal number from 1 to 120 to represent how long DFSMShsm waits for a tape to be mounted and opened. If the first time period expires, DFSMShsm sends message ARC0310A to the operator asking whether to mount the tape volume. If the operator answers Y to message ARC0310A, DFSMShsm resets the timer to minutes. If the input volume has not been mounted and opened when the second time period expires, DFSMShsm automatically ends the task. If the output volume has not been mounted and opened when the second time period expires, DFSMShsm marks this volume as unavailable and selects another tape volume. If you have not mounted an output tape dump volume when the second time period expires, DFSMShsm automatically ends the dump task. DFSMShsm default: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is 15 minutes. This may be due to a slow response to the mount request. Have you analyzed your tape mount process for DFHSM and see what it is okay sometimes and not okay other times? You may need to specify this parameter to extend how long HSM should wait. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Tony Thigpen > Sent: Thursday, November 24, 2016 6:33 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: HSM question > > Answers: > 1) OS/390 2.10 > > 2) output from Q SETSYS: > > QUERY SETSYS COMMAND STARTING ON HOST=1 > BUDENSITY=*, BUUNIT=TAPE90, BU RECYCLE 609 > (CONT.) PERCENTAGE=033%, MOUNT WAIT TIME=010 MINUTE(S), > (CONT.) TAPESPANSIZE(0100) > SELECTVOLUME=SCRATCH, 610 > (CONT.) TAPEDELETION=SCRATCHTAPE, PARTIALTAPE=MARKFULL, > (CONT.) DISASTERMODE=NO > INPUT TAPE ALLOCATION=NOWAIT, OUTPUT TAPE 611 > (CONT.) ALLOCATION=NOWAIT, RECYCLE TAPE ALLOCATION=NOWAIT, > (CONT.) TAPEFORMAT=SINGLEFILE > TAPE INPUT PROMPT FOR BACKUPTAPES=NO > TAPE INPUT PROMPT FOR DUMPTAPES=NO > TAPE INPUT PROMPT FOR MIGRATIONTAPES=NO > TAPE OUTPUT PROMPT FOR TAPECOPY=NO, DUPLEX 615 > (CONT.) BACKUP TAPES=NO, DUPLEX MIGRATION TAPES=NO > TAPEMIGRATION=ML2TAPE(TAPE(TAPE90)), 616 > (CONT.) MIGDENSITY=*, MIGUNIT=TAPE90, ML2 RECYCLE > (CONT.) PERCENTAGE=033%, TAPEMAXRECALLTASKS=01, ML2 PARTIALS > (CONT.) NOT ASSOCIATED GOAL=010, RECONNECT(NONE) TAPESECURITY=EXPIRATION, > DEFERMOUNT RECYCLEOUTPUT BACKUP=**NONE**, 618 > (CONT.) MIGRATION=**NONE** > MAXRECYCLETASKS=01, RECYCLE INPUT 619 > (CONT.) DEALLOCATION FREQUENCY BACKUP=000 MIGRATION=000 MONITOR STARTUP > NOSPACE NOVOLUME, MCDS(080), 620 > (CONT.) BCDS(080), OCDS(080), JOURNAL(080) JOURNAL=RECOVERY, LOG=YES, > TRACE=NO, 621 > (CONT.) SMFID=0240, DEBUG=NO, EMERG=NO, JES=2, SYS1DUMP=YES, > (CONT.) RACFIND=NO, ERASEONSCRATCH=NO, PDA=ON DAYS=380, ML1DAYS=003, 622 > (CONT.) PRIMARYSPMGMTSTART=
Re: HSM question
Elardus, The remote operator is a human. Tape management system is CA1 Still researching logs. Tony Thigpen Elardus Engelbrecht wrote on 11/23/2016 02:04 AM: Tony Thigpen wrote: Once a week, HSM performs an AUTOBACKUP. Until about 3 months ago, if nobody was at the shop, HSM would ask for an exiting tape, wait 10 minutes, and if no tape was mounted, it would ask "Can tape be mounted?". If our remote operator replied 'N', then HSM would us a scratch tape. About once ever month or so, we would run a recycle job to combine all the tapes. What remote operator? A person or automated task? Discussions with all the 3 others involved in the discussion 3 months ago came back with "I did not change anything 3 months ago." Really? Do you have any tape management system? So, I have come to the conclusion that somebody issued a command to HSM but did not update the config file so it would be handled at the next IPL. Hmmm, yes something *has* changed! What command(s) was issued? What are the results of that change(s)? Can you get RACF / SMF / SYSLOG records of that ? Lizette gave you good questions. I will certainly listen to her! ;-) Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
) from log *TMS009 IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET *IEC501A M 0C01,015010,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET *0037 ARC0310A CAN TAPE 015010 BE MOUNTED? REPLY Y OR N R 37,N IEE600I REPLY TO 0037 IS;N IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=DFSMSHSM, ASID=0027. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=DFSMSHSM, ASID=0027. IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=DFSMSHSM, ASID=0027. ARC0421I BACKUP VOLUME 015010 IS NOW MARKED FULL TMS014 IEF234E K 0C01,015010,PVT,DFSMSHSM,DFSMSHSM IEF234E K 0C01,015010,PVT,DFSMSHSM,DFSMSHSM *TMS009 IEC501A M 0C02,015128,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET *IEC501A M 0C02,015128,SL,COMP,DFSMSHSM,DFSMSHSM,DFHSM.BACKTAPE.DATASET Tony Thigpen Lizette Koehler wrote on 11/22/2016 10:10 PM: So some basic questions 1) What version of z/OS? 2) If you do a F dfhsmtaskname,Q SETSYS does it show the same info as the ARCCMDxx member? 3) What is the specific messages you are seeing during autobackup? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Tuesday, November 22, 2016 4:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HSM question HSM is not my ballgame, but I am tasked with figuring out this puzzle, so bear with me. As for background, the shop attempts to run lights-out 24/7. Once a week, HSM performs an AUTOBACKUP. Until about 3 months ago, if nobody was at the shop, HSM would ask for an exiting tape, wait 10 minutes, and if no tape was mounted, it would ask "Can tape be mounted?". If our remote operator replied 'N', then HSM would us a scratch tape. About once ever month or so, we would run a recycle job to combine all the tapes. About 3 months ago, we had some internal discussions about 'fixing' this so that it would just use scratch tapes without asking for an existing tape. The next thing we knew, the weekly tapes would automatically use a scratch tape. This was good. I assumed that one of the other guys had changed something. Then came the time change and the resulting IPL. Now everything is different. It seems to work the way it did prior to 3 months ago, except for one problem. When the operator replies that the tape can not be mounted, instead of HSM using a scratch tape, it now asks for another HSM tape. After about 4 hours of this last week, I got in my car and went down an mounted the tape. (I am the only one that lives in the same town as the processor.) Discussions with all the 3 others involved in the discussion 3 months ago came back with "I did not change anything 3 months ago." But, the other 2 guys that know HSM also say "We are busy. If you want it different, figure it out and change it." Key items I see in the config file are: SETSYS PARTIALTAPE( BACKUP(MARKFULL) - MIGRATION(MARKFULL)) SETSYS SELECTVOLUME( BACKUP(SCRATCH) MIGRATION(SCRATCH) - DUMP(SCRATCH)) SETSYS RECYCLEPERCENT(33) MAXRECYCLETASKS(1) SETSYS TAPEUTILIZATION( UNITTYPE(3590-1) PERCENTFULL(97)) SETSYS TAPESPANSIZE(100) (And the output of HSEND QUERY SETSYS is the same.) The last update date stamp on the config files was 15/12/22. So, I have come to the conclusion that somebody issued a command to HSM but did not update the config file so it would be handled at the next IPL. Looking for any input. -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
Tony Thigpen wrote: >Once a week, HSM performs an AUTOBACKUP. Until about 3 months ago, if nobody >was at the shop, HSM would ask for an exiting tape, wait 10 minutes, and if no >tape was mounted, it would ask "Can tape be mounted?". If our remote operator >replied 'N', then HSM would us a scratch tape. About once ever month or so, we >would run a recycle job to combine all the tapes. What remote operator? A person or automated task? >Discussions with all the 3 others involved in the discussion 3 months ago came >back with "I did not change anything 3 months ago." Really? Do you have any tape management system? >So, I have come to the conclusion that somebody issued a command to HSM but >did not update the config file so it would be handled at the next IPL. Hmmm, yes something *has* changed! What command(s) was issued? What are the results of that change(s)? Can you get RACF / SMF / SYSLOG records of that ? Lizette gave you good questions. I will certainly listen to her! ;-) Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM question
So some basic questions 1) What version of z/OS? 2) If you do a F dfhsmtaskname,Q SETSYS does it show the same info as the ARCCMDxx member? 3) What is the specific messages you are seeing during autobackup? Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Tony Thigpen > Sent: Tuesday, November 22, 2016 4:03 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: HSM question > > HSM is not my ballgame, but I am tasked with figuring out this puzzle, so bear > with me. As for background, the shop attempts to run lights-out 24/7. > > Once a week, HSM performs an AUTOBACKUP. Until about 3 months ago, if nobody > was at the shop, HSM would ask for an exiting tape, wait 10 minutes, and if no > tape was mounted, it would ask "Can tape be mounted?". If our remote operator > replied 'N', then HSM would us a scratch tape. About once ever month or so, we > would run a recycle job to combine all the tapes. > > About 3 months ago, we had some internal discussions about 'fixing' this so > that it would just use scratch tapes without asking for an existing tape. The > next thing we knew, the weekly tapes would automatically use a scratch tape. > This was good. I assumed that one of the other guys had changed something. > > Then came the time change and the resulting IPL. Now everything is different. > It seems to work the way it did prior to 3 months ago, except for one problem. > When the operator replies that the tape can not be mounted, instead of HSM > using a scratch tape, it now asks for another HSM tape. After about 4 hours of > this last week, I got in my car and went down an mounted the tape. (I am the > only one that lives in the same town as the processor.) > > Discussions with all the 3 others involved in the discussion 3 months ago came > back with "I did not change anything 3 months ago." > > But, the other 2 guys that know HSM also say "We are busy. If you want it > different, figure it out and change it." > > Key items I see in the config file are: > SETSYS >PARTIALTAPE( > BACKUP(MARKFULL) - > MIGRATION(MARKFULL)) > SETSYS >SELECTVOLUME( >BACKUP(SCRATCH) >MIGRATION(SCRATCH) - >DUMP(SCRATCH)) > SETSYS >RECYCLEPERCENT(33) >MAXRECYCLETASKS(1) > SETSYS >TAPEUTILIZATION( > UNITTYPE(3590-1) PERCENTFULL(97)) > SETSYS >TAPESPANSIZE(100) > > (And the output of HSEND QUERY SETSYS is the same.) > > The last update date stamp on the config files was 15/12/22. > > So, I have come to the conclusion that somebody issued a command to HSM but > did not update the config file so it would be handled at the next IPL. > > Looking for any input. > > -- > Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HSM question
HSM is not my ballgame, but I am tasked with figuring out this puzzle, so bear with me. As for background, the shop attempts to run lights-out 24/7. Once a week, HSM performs an AUTOBACKUP. Until about 3 months ago, if nobody was at the shop, HSM would ask for an exiting tape, wait 10 minutes, and if no tape was mounted, it would ask "Can tape be mounted?". If our remote operator replied 'N', then HSM would us a scratch tape. About once ever month or so, we would run a recycle job to combine all the tapes. About 3 months ago, we had some internal discussions about 'fixing' this so that it would just use scratch tapes without asking for an existing tape. The next thing we knew, the weekly tapes would automatically use a scratch tape. This was good. I assumed that one of the other guys had changed something. Then came the time change and the resulting IPL. Now everything is different. It seems to work the way it did prior to 3 months ago, except for one problem. When the operator replies that the tape can not be mounted, instead of HSM using a scratch tape, it now asks for another HSM tape. After about 4 hours of this last week, I got in my car and went down an mounted the tape. (I am the only one that lives in the same town as the processor.) Discussions with all the 3 others involved in the discussion 3 months ago came back with "I did not change anything 3 months ago." But, the other 2 guys that know HSM also say "We are busy. If you want it different, figure it out and change it." Key items I see in the config file are: SETSYS PARTIALTAPE( BACKUP(MARKFULL) - MIGRATION(MARKFULL)) SETSYS SELECTVOLUME( BACKUP(SCRATCH) MIGRATION(SCRATCH) - DUMP(SCRATCH)) SETSYS RECYCLEPERCENT(33) MAXRECYCLETASKS(1) SETSYS TAPEUTILIZATION( UNITTYPE(3590-1) PERCENTFULL(97)) SETSYS TAPESPANSIZE(100) (And the output of HSEND QUERY SETSYS is the same.) The last update date stamp on the config files was 15/12/22. So, I have come to the conclusion that somebody issued a command to HSM but did not update the config file so it would be handled at the next IPL. Looking for any input. -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HSM QUESTION
You are correct. 'PREPARE' only creates an ABR record. No verification or data movement occurs. Glenn Wilcock -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HSM QUESTION
Good Morning Gentle Readers, Just to ensure that I don't cause a problem if I issue the following command the ABARS AGGREGATE is NOT recovered. All it does it adds the ABR record to the BCDS. ARECOVER DSNAME (HIL5.C.C01V0025) XMIT PREPARE. An EXPIREBV was run in error. Thank You. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
