Update for VM:Spool with regard to worker service machine initialization.

book

Article ID: 192800

calendar_today

Updated On:

Products

CA VM:Spool

Issue/Introduction

VM:Spool worker machines (VMLWORK, VMLBAK01, VMLBAK02, VMLRES01), if configured, have pre-defined PROFILE EXECs that are hard coded to access the VMSPOOL server's 192 (CODE) minidisk, the server's PRIMARY runtime environment. Therefore, when the VMSERVER NAMES file entry for the VMSPOOL server is changed to access and run from the ALTERNATE or PREVIOUS runtime environments, the VMSPOOL worker machines continue to access and run from the PRIMARY runtime environment.

Cause

 

 

Environment

Release : 1.8

Component : CA VM:Spool

Resolution

VM:Spool PTF SO13334


 

Additional Information

After the PTF is installed and deployed, there are additional one-time steps that are required to implement the "fix" that are documented in the PTF UMEMO and the Problem Description for the PTF that are included below:

                         *** DISPLAY SOLUTION ***
 APAR #: SO13334
Product: VML        Release: 1.8         Solution #: 35        Type:
     OS: CMS          Group: VMVSE  GBL SUP 1
  Title: WORKER MACHINES DON'T HONOR SERVER RUNTIME ENVIRONMENT

****************** VERSION 0   EFFECTIVE: JUN 11 2020  11:12 ******************
VM:Spool worker machines (VMLWORK, VMLBAK01, VMLBAK02, VMLRES01), if
configured, have pre-defined PROFILE EXECs that are hard coded to access
the VMSPOOL server's 192 (CODE) minidisk, the server's PRIMARY runtime
environment. Therefore, when the VMSERVER NAMES file entry for the
VMSPOOL server is changed to access and run from the ALTERNATE or
PREVIOUS runtime environments, the VMSPOOL worker machines continue to
access and run from the PRIMARY runtime environment.

NOTE: After this PTF is installed, to put the updated PROFILE EXEC on
each defined VM:Spool worker machine you must run:

  --> VMDEPLOY _vmspool_ INIT ONLY

You may also have to add authorizations for each VM:Spool worker to
LINK to the VMSPOOL server's ALTERNATE and PREVIOUS runtime minidisks,
and the VMANAGER 1FF and 193 minidisks.

Keep in mind that VM:Spool workers are autologed when needed to do work,
then they log off. Therefore, after you apply and deploy service, do
not update the Runtime Environment Tag for the VMSPOOL server entry in
the VMSERVER NAMES file until you are ready to recycle the VMSPOOL
server to help ensure the VM:Spool server and workers are accessing the
same VMSPOOL Runtime Environment.