Previous Topic: Renaming the SVTS and SVTSAS PROCsNext Topic: Starting the CA Vtape Subsystem


Customizing the PROCs

To customize the PROC, follow these steps:

  1. Copy the SVTSCE members from the HLQ.CCUUPROC library to the appropriate system PROCLIB.
  2. Follow the comments in the members to customize them.

    At your site, if allocations with UNIT=SYSALLDA are not allowed in IGGPRE00 or Dynamic Allocation exit IEFDB401, you may need to add the following DD statement to the SVTS PROC:

    //SYSIN@  DD UNIT=your.DASD.esoteric,SPACE=(TRK,(1,1))
    
  3. Update the SYSID=&SYSNAME parameter in the SVTS PROC to a unique value if all of the following are true:

    When a Subsystem is started, the operating system name is combined with a comma and the last digit of the subsystem name to create an internal system ID that is used to enqueue or reserve the Global VCAT and Virtual Volumes. If the system name is greater than six characters, it is truncated to six characters.

    For example, when Subsystem SVT1 is started on an LPAR named PRODSYSA, the internal system ID will be "PRODSY,1". If Subsystem SVT1 is then started on PRODSYSB, its internal system ID will also be "PRODSY,1". To prevent resource conflicts and corruption of the Global VCAT, each Subsystem checks for an enqueue with a QNAME of SVTSX and an RNAME of its internal system ID when started. If the enqueue is not detected, the Subsystem issues the enqueue to reserve its internal system ID value. If the Subsystem detects that its internal system ID value is already in use, the Subsystem terminates after issuing an SVTnI0151E error message.

    You can avoid this problem by updating the SYSID=&SYSNAME parameter in the SVTS PROC to a unique value less than six characters. For example, on LPAR PRODSYSA, update the SVTS PROC to use SYSID=SYSA; on LPAR PRODSYSB, update the SVTS PROC to use SYSID=SYSB.

  4. If you are going to execute the sub addresses spaces with a different job name, copy the SVTSCE PROC to a new member in the same PROCLIB after you have customized it. Check the SubaddressSpaceName attribute in the Startup Options Section of the OSPARMS parmlib member to make sure it is set to the name of the new member.