Jeff,  leaving all the concerns alone at the moment ..... Deleting volumes 
should be straightforward. You do need to consider the scratch volumes and 
non-scratch volumes separately.
Scratch volumes should already have been through release processing and any 
cataloged data sets uncataloged. RACF profiles deleted (if any). To delete 
scratch volumes - use the RMM DV volser REMOVE command.
Non-scratch volumes you still have this consideration.  You can cause the 
volumes to go through release processing and allow rmm to uncatalog and cleanup 
RACF. Use the RMM CV volser RELEASE command.  Using the RMM DV volser FORCE may 
not do these tasks for you.
You also have some possible cleanup of the VRSes that are causing these 
non-scratch volumes still to be retained even though they no longer exist.

You can use the SEARCHVOLUME subcommand with CLIST to help build the commands 
needed. It is very powerful, can be run in TSO or batch, or even with the help 
of the dialog.  Also in the dialog, within search results list, you can use the 
SELECT primary command to set the line commands for selected entries in the 
list, then press ENTER to process them.

When you are making changes to volumes and other things defined to rmm, it 
normally creates journal records, and processing also should be creating PDA 
trace records, Either journal or trace data sets can become full when making 
mass changes - as others have mentioned.  In a well-run environment there 
should already be automation to take care of these things.

Deleting volumes should not usually cause space problems in the CDS. Rather it 
should free up space that can be reused. However, depending on how old the 
volumes are, and when the records were last updated, causing a change to a 
record may cause the record to be stored back larger than before .....  Again, 
usually, this extra space can be accommodated by VSAM without needing to split 
CIs/CAs.

Another way to delete volumes, which was added more recently to rmm, is to use 
the REPLACE release action. Probably best for non-scratch volumes, use RMM CV 
volser RELEASE(REPLACE) command then release the volume. Once pending release 
you can use RMM DV volser REPLACE to delete them without going through return 
to scratch process.

Mike Wood

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to