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
