rmm records the SG and other SMS constructs assigned during allocation. All of the SMS constructs recorded in rmm would normally match those sent outboard to the library. The construct names would match an outboard policy and establish the policies used by the library.
Each time the volume is reused from scratch a new SG name would be assigned. The only time the SG is used by the system is during cartridge re-entry. Since you are using virtual volumes the SG name would never be re-checked by the system. You can, however change the SG name for the volume. You can do so using rmm CV subcommand, and it updates rmm, TCDB and will be sent outboard to library - this way you can alter the outboard policy from the host system. Looks like you have converted from 3494 VTS to TS7700, and the SG names used still reflect the VTS values. That is not a problem. If you look at more recently used virtual volumes you should see the SGGRID value recorded. Going forward you can simply ignore the SG names on older volumes and eventually they will be updated as the volumes cycle through scratch status. Other SMS construct values can be changed, and if you do this for the first file on a virtual volume, bear in mind that rmm will send the new construct names outboard to update the policy for the virtual volume - so be sure to use names that are defined outboard, else the default values would be used. Mike Wood ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
