> 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).
|_NONE__ _______________________________________________ _|
|_(__ _ROUTETOTAPE_ __ ____________________ __)_|
|_TAPE________| | _ANY______ |
|_(__|_unittype_|__)_|
But the left paren after NONE is a line below, and right after NONE there is a
straight line through implying that no other parameter is needed. Following
that straight line back up I get the right paren and I am set. I have removed
the command and so now I live with the default. We don't have tapes in any case.
> I don't believe that you have the correct understanding of On Demand
> Migration. (See below)
Figures. This is all new to me, and a lot of information to absorb when I go
through the steps for the first time.
> 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 did that in Munich, then it is my bad. In Munich I didn't know how much
aquaintance I would get with the SETSYS command :-)
> 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.
Thank you so much for that offer, Glenn! For now, I have added the RELASE
MIGRATION command at the end of my parmlib member, and HSM does its
once-per-day migration and cleanup thing, which is all that's needed in our
small ADCD system.
Best regards, Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
