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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
