Preparing to use Configuration Manager

Edit online

Review prerequisites and other considerations before you start using Configuration Manager.

This section provides information about the following items, which are prerequisites or should be considered before using Configuration Manager:

Location of SMP/E installation target libraries

You need to know where your target libraries are installed:

  • On MVS™: The high-level qualifiers of the SMP/E target libraries, such as TKANMOD.
  • On z/OS® UNIX® System Services:
    • For products that require it, such as OMEGAMON AI for CICS and OMEGAMON AI for JVM, the path of the SMP/E target directory that is defined in the SMP/E installation jobs by DDDEF entry TKANJAR. The default directory path is /usr/lpp/kan/bin/IBM.
    • For OMEGAMON® Data Provider, the path of the SMP/E target directory that is defined in the SMP/E installation jobs by DDDEF entry TKAYHFS. The default directory path is /usr/lpp/omdp.

A typical best practice is to make a copy of the original SMP/E-managed locations and refer to the copies. This enables you to manage when to introduce changes in the original SMP/E-managed locations into your environment.

Naming your runtime environment

When you define your runtime environment, it is recommended to use a naming convention that will not interfere with your system libraries. Consider meaningful names that will easily distinguish and isolate your OMEGAMON runtime environments on your system.

Configuration Manager uses the values of RTE_NAME and RTE_PLIB_HILEV to set the name of the runtime environment and runtime environment definition library. It is recommended that the combined length of these parameters does not exceed 28 characters. For more information, see Creating your first, minimal runtime environment.

Access privileges for TSO user ID

The TSO user ID that you plan to use to run Configuration Manager jobs (for example, your own user ID) must have the following access privileges:

  • Read access to the target libraries
  • Read access to the z/OS UNIX directories defined by the TKANJAR and TKAYHFS DDDEF entries, if products using the respective directories are installed
  • Read access to the following z/OS System Authorization Facility (SAF) resources:
    • In the FACILITY class:
      • BPX.FILEATTR.APF
      • BPX.FILEATTR.PROGCTL
    • In the SERVAUTH class (if defined):
      • EZB.STACKACCESS.sysname.tcpname

        where sysname is the value of the MVS &SYSNAME. system symbol and tcpname is the name of the procedure used to start the TCP stack.

You do not need z/OS UNIX superuser privileges to run Configuration Manager.

Authorization for certain Configuration Manager functions

Some Configuration Manager programs and actions require APF authorization or special RACF privileges, as follows:
  • To use actions DISCOVER (for full discovery), PACKAGE, and DEPLOY, you must run program KCIALPHA from an APF-authorized load library. Make sure the necessary APF authorization of the TKANMOD library is made. For more information about APF authorization, see step 7 in Creating your first, minimal runtime environment.
  • The PACKAGE and DEPLOY actions use z/OS DFSMSdss commands to implement remote deployment. You might need authority to run ADRDSSU, which is the program that is invoked when using DFSMSdss. For more information, see the authorization requirements in PACKAGE.

Issues to be aware of before using Configuration Manager

When using Configuration Manager, especially the GENERATE action, make sure the job does not use a Batch Optimization tool. These tools are known to exhaust below-the-line storage and fail the job with ABEND878-10.