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 [email protected] From: "Staller, Allan" <[email protected]> To: [email protected], Date: 07/03/2013 06:45 AM Subject: Re: Installing HSM or rather: DFHSM woes Sent by: IBM Mainframe Discussion List <[email protected]> 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 Implementation&Customization 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 [email protected] with the message: INFO IBM-MAIN
