WORKER MACHINES DON'T HONOR SERVER RUNTIME ENVIRONMENT

book

Article ID: 193477

calendar_today

Updated On:

Products

CA VM:Account

Issue/Introduction

The VMJDASD and DISKACNT service machines do not honor the runtime environment specified in the VMSERVER NAMES file entry for the VMACCT server, they always access the VMACCT server's PRIMARY runtime environment.

 

Cause

VM:Account worker machine VMJDASD and system account retrieval service machine, usually DISKACNT, have previously been configured with a hard coded access to the VMACCT server's 192 (CODE) minidisk, the server's PRIMARY runtime environment. Therefore, when the VMSERVER NAMES file entry for the VMACCT server is changed to access and run from the
ALTERNATE or PREVIOUS runtime environments, the VMJDASD and DISKACNT service machines continue to access and run from the PRIMARY runtime environment.
 

Environment

Release : 1.7

Component : CA VM:Account

Resolution

Apply VM:Account PTF SO13390.

 

NOTE: After this PTF is installed, perform the following one-time procedure to implement all components effected by the PTF:
 
 1) Issue: VMDEPLOY _vmacct_  _environment_
 2) Issue: VMDEPLOY _vmacct_ PUBLIC
 3) Issue: VMDEPLOY _vmacct_ INIT ONLY
 
 The following additional steps must be performed for the DISKACNT service machine:
 
 1) Bring down the DISKACNT service machine.
 2) Save a copy of the current PROFILE EXEC on the DISKACNT 191 minidisk with a different name.
 3) Add the following new PROFILE EXEC on the DISKACNT 191 minidisk:
 
 * * * Top of File * * *
 /*
    PROFILE EXEC to run CA VM:Account Record Retrieval Processing
 */
 
 /* Access the VMANAGER PUBLIC Disk */
 'VMLINK VMANAGER 193 < 193 B/A RR >'
 If rc <> 0 Then
    Do

       say 'Unable to LINK to VMANAGER 193 (PUBLIC) Disk.'
       Exit 99
    End
 
 /* Run the Startup for VM:Account's Record Retrieval */
 'EXEC VMJRET'
 
 Exit
 * * * End of File * * *


 
You may also have to add authorizations for the VMJDASD and DISKACNT service machines to LINK to the VMACCT server's ALTERNATE and PREVIOUS runtime minidisks, and the VMANAGER 1FF and 193 minidisks.
 

Additional Information

Keep in mind that the VMJDASD service machine is autologged when needed to do work, then it logs off. Therefore, after you apply and deploy service, do not update the Runtime Environment Tag for the VMACCT server entry in the VMSERVER NAMES file until you are ready to recycle the VMACCT and DISKACNT servers to help ensure the VM:Account server, VMJDASD service machine, and the DISKACNT service machine are accessing the same VMACCT Runtime Environment.