Validate RTCS system resources

This step describes how to ensure the availability of system resources that are required by RTCS.

1. Ensure the availability of sufficient common area data spaces (CADs):

   1. In member IEASYSxx of SYS1.PARMLIB, review the MAXCAD parameter.

      MAXCAD specifies the maximum number of SCOPE=COMMON data spaces that will be available for the life of the IPL. The RTCS subsystem requires four SCOPE=COMMON data spaces.

      The first time (and only the first time) that you configure any particular z/OS system image to be able to run RTCS, BMC recommends that you add four to the value already specified for MAXCAD in the appropriate IEASYSxx member of Logical PARMLIB. The next time that system image is IPLed, there will be four more CADs available than there were before, which you could consider to have been reserved for use by the RTCS subsystem on that image.

      The goal is to ensure that there is a sufficient number of CADs available on each system image. If the existing value for MAXCAD is already close to the actual number needed on that particular z/OS system image, the MAXCAD value will probably need to be increased. It is possible that sufficient unused CADs are already available to start RTCS. If this is the case, no IPL to increase the number is required. If the RTCS subsystem, however, is not able to complete initialization because of insufficient CADs, an IPL will be required to increase the MAXCAD value.

   2. If an insufficient number of SCOPE=COMMON data spaces are available the first time you start RTCS, increase the value of the MAXCAD parameter and IPL the z/OS system image.
2. Ensure the availability of sufficient system linkage indexes (LXs):

   1. In member IEASYSxx of SYS1.PARMLIB, review the NSYSLX parameter.

      NSYSLX specifies the maximum number of LXs (in addition to LXs in the system functional table) that are to be reserved for system LXs. The RTCS subsystem requires one system LX.

      The first time (and only the first time) that you configure any particular z/OS system image to be able to run RTCS, BMC recommends that you add one to the value already specified for NSYSLX in the appropriate IEASYSxx member of Logical PARMLIB. The next time that system image is IPLed, there will be one more system LX available than there were before, which you could consider to have been reserved for use by the RTCS subsystem on that image.

      The goal is to ensure that there is a sufficient number of system LXs available on each system image. If the existing value for NSYSLX is already close to the actual number needed on that particular z/OS system image, the NSYSLX value will probably need to be increased. It is possible that sufficient unused system LXs are already available to start RTCS. If this is the case, no IPL to increase the number is required. If the RTCS subsystem, however, is not able to complete initialization because of insufficient system LXs, an IPL will be required to increase the NSYSLX value.

   2. If an insufficient number of system LXs available the first time you start RTCS, increase the value of the NSYSLX parameter and IPL the z/OS system image.

Where to go from here

If you need to modify member MDZTTD00 to change the CIs that BMC Discovery for z/OS defines by default, continue with Creating-Configuration-Items-for-unique-address-spaces.

If you want to modify member MDZJVSAM and MDZVSAMF, continue with Options-for-BMC-Impact-Integration-for-z-OS-and-BMC-Impact-Manager.

If no other modifications are needed, perform any other required steps for implementing each specific product you are installing, and then verify that the product works properly by using it as described in the 'Using' section for that product.

For BMC Discovery for z/OS perform the following steps:

1. Start the CAS, PAS and server address space.
2. Confirm that all three address spaces started successfully.
3. Notify the BMC Helix Discovery administrator that discovery of z/OS data is available.