Product Verification › Renaming the SVTS and SVTSAS PROCs

Renaming the SVTS and SVTSAS PROCs

In an environment where multiple CA Vtape Subsystems will be active on the same LPAR, having multiple PROCs with unique names may make it easier for the operations and technical support personnel to monitor and manage CA Vtape. To support this environment the SVTS and SVTSAS PROCs can be renamed.

There are two cautions that must be observed when renaming these PROCS:

• The PROCs cannot be renamed to a CA Vtape subsystem name (SVTn where n = 1-8).

  This could cause the tasks to be started under the MASTER subsystem instead of JES resulting in JCL errors or other problems.

• If the SVTSAS PROC is renamed, the SubaddressSpaceName attribute in the Startup Options Section of the VTPARMS parmlib member must be changed to the new name.

When renaming and creating multiple sets of PROCs, a pattern like SVTS1 and SVTS1AS, SVTS2 and SVTS2AS, and so on, allows for easy identification of the CA Vtape Subsystem and its address spaces. In these PROCs the SVTS parameter would be set to their corresponding subsystem name (SVTS=SVT1, SVTS=SVT2, and so on).

If you set the TASKLIB attribute to AUTOMATIC or to a loadlib data set name, the STEPLIB DD in the SVTSAS PROC can be commented out. With the STEPLIB DD commented out, there is no need to have multiple copies of the SVTSAS PROC for different CA Vtape Subsystems. You can start an SVT1 Subsystem, and SVT2 Subsystem, and so on and they can all use the same SVTSAS PROC.

The presence of the last digit of the subsystem name in the PROC name would reinforce the need to use the proper console command prefix or SVTS parm value when issuing commands or running reports to investigating a particular subsystem. When investigating the SVTS2 and SVTS2AS tasks, it would logically follow that console commands should be issued with a command prefix of SVT2 and utility jobs should use a parm of SVTS=SVT2.

When starting or stopping the renamed PROCs, S/P SVTSn, where n is the last digit of the appropriate subsystem number would suffice. When restarting a Virtual Tape Controller address space or the Backstore Engine, the command prefix would control the restart. SVT1 R CU=1 would restart SVTS1AS.SVT1V1, the Virtual Control Unit address space one for the SVT1 Subsystem. SVT2 R B would restart SVTS2AS.SVT2PT, the Backstore Engine address space for the SVT2 Subsystem.