Re: Installing HSM or rather: DFHSM woes
I have to ask. What's harm of defining a couple 1 cylinder (or 2 track) OCDS, BCDS that will remain empty and unused? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of nitz-...@gmx.net Sent: Thursday, July 11, 2013 9:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Installing HSM or rather: DFHSM woes Glenn, Have you tried an HSM Modify command to issue it? The syntax seems correct, so it may be some typographical error in your parmlib. 13193 06:03:58.69 me 0290 F DFHSM,SETSYS TAPEMIGRATION(NONE) 13193 06:03:58.71 STC02475 0090 ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION 13193 06:03:58.71 STC02475 0080 ARC0100I SETSYS COMMAND COMPLETED My WAG is that it works for you because you run with OCDS and BCDS. I don't. :-) As far as I can tell, the code just *assumes* that everybody has those data sets defined (opening them is done way before the parmlib content is checked), when it isn't *mandatory* to have them. All I want to do with this parm is make it clear that I don't want to use TAPEMIGRATION (because we don't have tapes). If there is some other way to achieve that, I am perfectly happy to go that other way (short of defining OCDS/BCDS). The problem (as I saw it) is that there are a lot of parms that are kind of interwoven, and having looked at all the parms for about two weeks, I still wasn't sure which the ultimate *I don't want this* parm is for the things I don't want to run, so I had to basically specify them all the way I want them (as far as that is possible). Barbara -- 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: Installing HSM or rather: DFHSM woes
I have to ask. What's harm of defining a couple 1 cylinder (or 2 track) OCDS, BCDS that will remain empty and unused? 'Business reasons'. I just didn't understand why something that looks to have correct syntax is getting a syntax error. Turns out that it *should* be correct. I will just shrug it off. But I will do my best to help Glenn if he wants to follow up on this. Best regards, Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Hi, I discovered that we modified the syntax in the Storage Admin between v1R12 and V1R13. V1R13 (which I looked at) incorrectly shows the left paren to the immediate right. I looked at the code and saw that the subparameter is not required, so I'll get the syntax corrected back to the way it was. We issued the command, as you have listed, on our test system and it worked fine. Have you tried an HSM Modify command to issue it? The syntax seems correct, so it may be some typographical error in your parmlib. Glenn -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Glenn, Have you tried an HSM Modify command to issue it? The syntax seems correct, so it may be some typographical error in your parmlib. 13193 06:03:58.69 me 0290 F DFHSM,SETSYS TAPEMIGRATION(NONE) 13193 06:03:58.71 STC02475 0090 ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION 13193 06:03:58.71 STC02475 0080 ARC0100I SETSYS COMMAND COMPLETED My WAG is that it works for you because you run with OCDS and BCDS. I don't. :-) As far as I can tell, the code just *assumes* that everybody has those data sets defined (opening them is done way before the parmlib content is checked), when it isn't *mandatory* to have them. All I want to do with this parm is make it clear that I don't want to use TAPEMIGRATION (because we don't have tapes). If there is some other way to achieve that, I am perfectly happy to go that other way (short of defining OCDS/BCDS). The problem (as I saw it) is that there are a lot of parms that are kind of interwoven, and having looked at all the parms for about two weeks, I still wasn't sure which the ultimate *I don't want this* parm is for the things I don't want to run, so I had to basically specify them all the way I want them (as far as that is possible). Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
I believe the one of the earlier suggestions to define the CDS's, even if treated as dummy will greatly reduce your woefulness G. Can anybody tell me why SETSYS TAPEMIGRATION(NONE) gets ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION ? Seems to be either a sequencing error (e.g. migration not defined prior to the SETSYS TAPEMIGRATON command) or a cascading error (e.g. prior command received error, thus making this command invalid). Can't do anything with this without seeing the ARCCMDxx and HSM joblog. HTH, snip I got up the nerve to issue the command this morning (after all, the cycle is still defined to not start by itself). HSM said: ARC0100I RELEASE COMMAND COMPLETED Now I manually migrated one data set. It works! Recall also worked. (I'm happy.) Now I need to get up the nerve to have everything start automatically... Can anybody tell me why SETSYS TAPEMIGRATION(NONE) gets ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION ? /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Hi, Just got back from vacation and saw this thread. SETSYS TAPEMIGRATION(NONE is looking for the next set of subparms. In the syntax diagram, note the left paren after NONE, which means it wants another parameter - ROUTETOTAPE(ANY | unit). I don't believe that you have the correct understanding of On Demand Migration. (See below) Lizette mentioned some SHARE presentations that would be beneficial. There is also another one that I presented recently entitled 'The Wonderful World of SETSYS commands' that would be beneficial. If you would like, I'm more than happy to have a conference call with you to give an overview of these presentations and discuss your questions. Just contact me off-thread. As some of the other appends have mentioned, even though some features are optional, it will make your life alot easier to implement them. (This invitation also applies to any other customer reading this append. The development team's opportunity to interact with customers and learn about your specific environments is invaluable). Glenn Wilcock DFSMShsm Architect wilc...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Hi On 08.07.2013 19:41, Glenn Wilcock wrote: Hi, Just got back from vacation and saw this thread. SETSYS TAPEMIGRATION(NONE is looking for the next set of subparms. In the syntax diagram, note the left paren after NONE, which means it wants another parameter - ROUTETOTAPE(ANY | unit). I don't believe that you have the correct understanding of On Demand Migration. (See below) Lizette mentioned some SHARE presentations that would be beneficial. There is also another one that I presented recently entitled 'The Wonderful World of SETSYS commands' that would be beneficial. If you would like, I'm more than happy to have a conference call with you to give an overview of these presentations and discuss your questions. Just contact me off-thread. As some of the other appends have mentioned, even though some features are optional, it will make your life alot easier to implement them. (This invitation also applies to any other customer reading this append. The development team's opportunity to interact with customers and learn about your specific environments is invaluable). ( I have no DFHSM problem currently), but the offer is great, don't remember to read something like this for a long time. Thank you Glenn Glenn Wilcock DFSMShsm Architect wilc...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Kind regards, / Mit freundlichen Grüßen Miklos Szigetvari Research Development ISIS Papyrus Europe AG Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria T: +43(2236) 27551 333, F: +43(2236)21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our brand new extended Website at www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS Papyrus accepts no responsibility for malicious or inappropriate content. --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Alan, You can issue F DFHSM,RELEASE MIGRATION, but it will most likely be held again immediately when the first migration is attempted. I got up the nerve to issue the command this morning (after all, the cycle is still defined to not start by itself). HSM said: ARC0100I RELEASE COMMAND COMPLETED Now I manually migrated one data set. It works! Recall also worked. (I'm happy.) Now I need to get up the nerve to have everything start automatically... Can anybody tell me why SETSYS TAPEMIGRATION(NONE) gets ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION ? Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Barbara, Is this in the ARCCMDxx member? Or is it being issued as a command? If in the ARCCMDxx can you try doing a F dfhsmtaskname,SETSYS TAPEMIGRATION(NONE) and let us know what happens? If in the ARCCMDxx can you post a few lines above and below the Tapemigration line? DFHSM was not meant to be intuitive. So it takes some digging and reviewing the DFHSM Storage Admin Guide to try and figure out why things are not working. Also, do you have an OCDS present? Or is it dummy? Note: From the STG Admin Guide: If you do not intent to use Tape, do not specify TAPEMIGRATION. If you do, an Offline control dataset is required. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of nitz-...@gmx.net Sent: Wednesday, July 03, 2013 11:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Installing HSM or rather: DFHSM woes Alan, You can issue F DFHSM,RELEASE MIGRATION, but it will most likely be held again immediately when the first migration is attempted. I got up the nerve to issue the command this morning (after all, the cycle is still defined to not start by itself). HSM said: ARC0100I RELEASE COMMAND COMPLETED Now I manually migrated one data set. It works! Recall also worked. (I'm happy.) Now I need to get up the nerve to have everything start automatically... Can anybody tell me why SETSYS TAPEMIGRATION(NONE) gets ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION ? Barbara -- 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: Installing HSM or rather: DFHSM woes
Is this in the ARCCMDxx member? Or is it being issued as a command? Doesn't matter. Doesn't work either way, gets the same error message. If in the ARCCMDxx can you post a few lines above and below the Tapemigration line? SETSYS - OBJECTNAMES(OBJ,OBJECT,LOAD,LOADLIB,LOADMODS,LINKLIB) - SOURCENAMES(ASM,COBOL,FORT,PLI,SOURCE,SRC,SRCLIB,SRCE,CNTL,JCL) SETSYS TAPEMIGRATION(NONE) SETSYS PRIMARYSPMGMTSTART ( ) Also, do you have an OCDS present? Or is it dummy? Dummy, or rather it gets a message that it isn't specified. Note: From the STG Admin Guide: If you do not intent to use Tape, do not specify TAPEMIGRATION. If you do, an Offline control dataset is required. That might be the (non-intuitive) reason. There are no tapes in our environment, and specifying TAPEMIGRATION(NONE) should be valid, since we don't intend to use tapes. In other words, I'd better remove the line (although I am unhappy with the default) since it will not be set to NONE, anyway. And I must have overlooked that line, although I have been over all the HSM books for more than two weeks now... Thanks, Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
There are a couple of Share presentations on DFHSM Best Practises Setting Up DFHSM And so forth. If you like some of them, email me offlist Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of nitz-...@gmx.net Sent: Thursday, July 04, 2013 5:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Installing HSM or rather: DFHSM woes Is this in the ARCCMDxx member? Or is it being issued as a command? Doesn't matter. Doesn't work either way, gets the same error message. If in the ARCCMDxx can you post a few lines above and below the Tapemigration line? SETSYS - OBJECTNAMES(OBJ,OBJECT,LOAD,LOADLIB,LOADMODS,LINKLIB) - SOURCENAMES(ASM,COBOL,FORT,PLI,SOURCE,SRC,SRCLIB,SRCE,CNTL,JCL) SETSYS TAPEMIGRATION(NONE) SETSYS PRIMARYSPMGMTSTART ( ) Also, do you have an OCDS present? Or is it dummy? Dummy, or rather it gets a message that it isn't specified. Note: From the STG Admin Guide: If you do not intent to use Tape, do not specify TAPEMIGRATION. If you do, an Offline control dataset is required. That might be the (non-intuitive) reason. There are no tapes in our environment, and specifying TAPEMIGRATION(NONE) should be valid, since we don't intend to use tapes. In other words, I'd better remove the line (although I am unhappy with the default) since it will not be set to NONE, anyway. And I must have overlooked that line, although I have been over all the HSM books for more than two weeks now... Thanks, Barbara -- 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: Installing HSM or rather: DFHSM woes
I don't know the workings of HSM, but I can offer some advice on dealing with 'optional' files. In general, an application checks for the presence of any file by checking for the DDNAME in the allocation. For a file that's truly optional, absence of the file is 'noted' at start-up so that no component will try to use it. However. DUMMY muddies the water because the DDNAME is truly allocated even though there is no tin can at the other end of the string. A component that wants to use that file may well try to open it. Depending on how the file is accessed, DUMMY can cause OPEN failure. So, in general, if you don't want to use an optional file, then don't code it at all. In addition, an application controlled by a parm file may need some statements tweaked to indicate that the related function is not desired at all. All this notwithstanding, suggestions to include files now that you don't think you need is probably sound advice. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Staller, Allan allan.stal...@kbmg.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 06:45 AM Subject:Re: Installing HSM or rather: DFHSM woes Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU The journal is used to rebuild the xCDS dataset in the event of the xCDS being damaged, I would strongly suggest that you plan for a journal. You will need to manually schedule F DFHSM,BACKVOL CDS to periodically clear the journal since you are not performing functions that would result in the journal being cleared automatically (auto backup performs a BACKVOL CDS as the first step, IIRC). IMO, it will be far simpler in the long run to provide the necessary support datasets, even if minimal, and then *remove* as required. I am almost certain that the ARCPDO* and ARCLOG* datasets can be dispensed with. I guess my main question is: Will I be able to migrate data sets after having gotten ARC860E? You can issue F DFHSM,RELEASE MIGRATION, but it will most likely be held again immediately when the first migration is attempted. HTH, snip Finally I have finished wading through the HSM starter set and customized it the way we want to use it - just migrating to ML1, no ML2, no backup, no recovery, no dumping, no tapes, a really minimal environment. That means I only start DFHSM with an MCDS (OFFCAT, BAKCAT, JOURNAL, ARCLOGX, ARCLOGY, ARCPDOX and ARCPDOY all set to DUMMY). According to the ImplementationCustomization Guide, all of the dummied data sets are optional, even if some of them are 'strongly recommended'. Remainder snipped /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
DUMMY muddies the water because the DDNAME is truly allocated even though there is no tin can at the other end of the string. A component that wants to use that file may well try to open it. Depending on how the file is accessed, DUMMY can cause OPEN failure. Well, not in the case of HSM. During my first start I had deleted the OFFCAT and BAKCAT statements, and that resulted in IEC130I BAKCAT DD STATEMENT MISSING ARC0945I OPEN OF DDNAME=BAKCAT FAILED, VSAM REASON ARC0945I (CONT.) CODE IS X'80' *ARC0134I BACKUP CONTROL DATA SET NOT OPENED, BACKUP ARC0134I (CONT.) WILL NOT BE ENABLED IEC130I OFFCAT DD STATEMENT MISSING ARC0945I OPEN OF DDNAME=OFFCAT FAILED, VSAM REASON ARC0945I (CONT.) CODE IS X'80' At which point I made the dd statements dummy, but I did expect the code to check for DUMMY and then NOT try and open something that just isn't there! In addition, an application controlled by a parm file may need some statements tweaked to indicate that the related function is not desired at all. All this notwithstanding, suggestions to include files now that you don't think you need is probably sound advice. I have set all the parms in ARCCMD so that the functions should not get used at all. At least I think I did. But the ARCCMD member is apparently read *after* the open failures. The reason I don't want to go and define these (for us) unnecessary data sets are the many warnings and caveats that come with where to allocate this stuff. I don't have all that many volumes (after all, this is an ADCD system), and we don't have any automatisms that could take care of cleaning up after something we don't need. And yes, everybody is aware of the risks of loosing a volume, that's why I periodically take the system down and backup everything to an external drive, which includes all system data sets and would include the state of HSM. In case of failure I would go back to a complete set of backups. (The vital data are not supposed to get migrated at all.) As I said, we need HSM to clean up temporary stuff and to test migration functions. ML1 only. Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Installing HSM or rather: DFHSM woes
Again, I don't know HSM. But don't necessarily take whining and gnashing of teeth as 'failure'. HSM is letting you know (loudly) that a DD statement is missing in case you overlooked it. You might actually take heart in *ARC0134I BACKUP CONTROL DATA SET NOT OPENED, BACKUP ARC0134I (CONT.) WILL NOT BE ENABLED as an indication of achieving what you wanted. ;-) OTOH abends on OPEN, as with DUMMY, are not likely to be productive. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: nitz-...@gmx.net nitz-...@gmx.net To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 08:16 AM Subject:Re: Installing HSM or rather: DFHSM woes Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU DUMMY muddies the water because the DDNAME is truly allocated even though there is no tin can at the other end of the string. A component that wants to use that file may well try to open it. Depending on how the file is accessed, DUMMY can cause OPEN failure. Well, not in the case of HSM. During my first start I had deleted the OFFCAT and BAKCAT statements, and that resulted in IEC130I BAKCAT DD STATEMENT MISSING ARC0945I OPEN OF DDNAME=BAKCAT FAILED, VSAM REASON ARC0945I (CONT.) CODE IS X'80' *ARC0134I BACKUP CONTROL DATA SET NOT OPENED, BACKUP ARC0134I (CONT.) WILL NOT BE ENABLED IEC130I OFFCAT DD STATEMENT MISSING ARC0945I OPEN OF DDNAME=OFFCAT FAILED, VSAM REASON ARC0945I (CONT.) CODE IS X'80' At which point I made the dd statements dummy, but I did expect the code to check for DUMMY and then NOT try and open something that just isn't there! In addition, an application controlled by a parm file may need some statements tweaked to indicate that the related function is not desired at all. All this notwithstanding, suggestions to include files now that you don't think you need is probably sound advice. I have set all the parms in ARCCMD so that the functions should not get used at all. At least I think I did. But the ARCCMD member is apparently read *after* the open failures. The reason I don't want to go and define these (for us) unnecessary data sets are the many warnings and caveats that come with where to allocate this stuff. I don't have all that many volumes (after all, this is an ADCD system), and we don't have any automatisms that could take care of cleaning up after something we don't need. And yes, everybody is aware of the risks of loosing a volume, that's why I periodically take the system down and backup everything to an external drive, which includes all system data sets and would include the state of HSM. In case of failure I would go back to a complete set of backups. (The vital data are not supposed to get migrated at all.) As I said, we need HSM to clean up temporary stuff and to test migration functions. ML1 only. Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
