CA Mainframe VM Product Manager - 1.2 : Implementing the Directory Reader and System Information Diagnose Code

Follow the steps in this procedure before you install or use any other CA VM product. This is not an optional step, but is required for using any CA VM product.

Any product installed and serviced with CA Mainframe VM Product Manager may use the CA Directory Reader and System Information Diagnose Code to retrieve information from the CP online directory. Some product installation steps use the diagnose. Some product servers fail during the initialization process if the diagnose is not installed. Other products start correctly but could fail during execution if certain features of the product are exploited.

The diagnose code programming is distributed as a TEXT file and is loaded into the VM Control Program during system IPL processing. A different version of this TEXT file is distributed for each release of VM. Only the version for one specific VM release will operate properly on that release. The file name specifies the VM release it runs on as follows:

  • VMNDLK54 - z/VM 5.4.0
  • VMNDLK62 - z/VM 6.2.0
  • VMNDLKxx - z/VM x.x.0

Follow these steps to install the diagnose code:

  1. Follow your site procedures for adding and modifying materials on the CP PARM disk.
  2. Copy the VMNDLKxx TEXT file from VMANAGER 195 to the CP PARM disk.
  3. Add the following statements to the SYSTEM CONFIG file on the CP PARM disk:

    CPXLOAD VMNDLKxx TEXT * NOCONTROL LET TEMPORARY NODELAY
    DEFINE DIAGNOSE 100 ENABLE EPNAME VMNDLKUP,
                        PRIVCLASS E CHECKR15 YES
    DEFINE COMMAND VMNDLK ENABLE EPNAME VMNDLKCP,
                        PRIVCLASS E IBMCLASS E
    
  4. To place the diagnose into effect, issue these commands:

    CPXLOAD VMNDLKxx TEXT * NOCONTROL LET TEMPORARY
    DEFINE DIAGNOSE 100 ENABLE EPNAME VMNDLKUP ...
                    ... PRIVCLASSES E CHECKR15 YES
    DEFINE COMMAND VMNDLK ENABLE EPNAME VMNDLKCP ...
                        PRIVCLASSES E IBMCLASS E 
    

    To test that the diagnose is installed and functioning, run the VMRMDS utility. VMRMDS uses the diagnose to gather minidisk information and will end in error if the diagnose is not installed correctly

    Icon
    Note: For more information, see VMRMDS Utility.
  5. Run the VMRMDS utility again after the next IPL, which picks up the SYSTEM CONFIG changes.
Icon
Note: You may substitute a different Diagnose Code number if number 100 is in use at your installation. Any available User Diagnose code number may be specified. Valid hexadecimal values are numbers which are multiples of four between 100 and 1FC.