Just go ahead and issue the vary commands. You may get a "command flooding in class M2" message if there are enough commands. The resolution to this is do nothing. z/OS will handle the command flooding and you will eventually see a 'command flooding relieved in class M2" message.
You can reduce the number of commands with the "range" version of the command. V xxxx-yyyy,offline Excerpt from my test lpar COMMNDxx member COM='V 8000-80BF,OFFLINE' COM='V 8100-81BF,OFFLINE' COM='V 8200-82BF,OFFLINE' COM='V 8300-83BF,OFFLINE' COM='V 8400-84BF,OFFLINE' COM='V 8500-8503,OFFLINE' COM='V 8505-85BF,OFFLINE' COM='V 8600-8603,OFFLINE' <---- note volume 8604 is left online... COM='V 8605-86BF,OFFLINE' COM='V 8700-8703,OFFLINE' HTH, <snip> My production LPAR and Test LPAR have access to almost 600 volumes. My test LPAR only uses and needs about 24 volumes. Any ideas how, at IPL time for the test LPAR, I can use commands to restrict the LPAR to only these 24 volumes. For sure, I could issue vary off and vary on commands for only those volumes needed or not needed by the test LPAR, but the UCB's are so numerous that there would be dozens of commands. I am just trying to have a smaller list of commands in my COMMNDXX member Any other simpler way to accomplish this task? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
