Software requirements for IMS Administration Foundation

Edit online

Before you install and configure IBM® IMS Administration Foundation for z/OS® for use with the Unified Management Server, make sure that your environment meets the following minimum software requirements.

To use IMS Administration Foundation, one or more of the IMS 15 releases are required. IMS Administration Foundation supports the following IMS releases and configurations:

  • Supported IMS releases:
    • IBM Information Management System 15.2.0 (PID: 5635-A06)
    • IBM Information Management System Database Value Unit Edition 15.2.0 (PID: 5655-DS5)
    • IBM Information Management System Transaction Manager Value Unit Edition 15.2.0 (PID: 5655-TM4)
    • IBM Information Management System 15.3.0 (PID: 5635-A06)
    • IBM Information Management System Database Value Unit Edition 15.3.0 (PID: 5655-DS5)
    • IBM Information Management System Transaction Manager Value Unit Edition 15.3.0 (PID: 5655-TM4)
    • IBM Information Management System 15.4.0 (PID: 5635-A06)
    • IBM Information Management System Database Value Unit Edition 15.4.0 (PID: 5655-DS5)
    • IBM Information Management System Transaction Manager Value Unit Edition 15.4.0 (PID: 5655-TM4)
    • IBM Information Management System 15.5.0 (PID: 5635-A06)
    • IBM Information Management System Database Value Unit Edition 15.5.0 (PID: 5655-DS5)
    • IBM Information Management System Transaction Manager Value Unit Edition 15.5.0 (PID: 5655-TM4)
    • IBM Information Management System 15.6.0 (PID: 5635-A06)
      • UMS 1.2.0.13 or later is required.
    • IBM Information Management System Database Value Unit Edition 15.6.0 (PID: 5655-DS5)
      • UMS 1.2.0.13 or later is required.
    • IBM Information Management System Transaction Manager Value Unit Edition 15.6.0 (PID: 5655-TM4)
      • UMS 1.2.0.13 or later is required.
  • Supported IMS system configuration:
    • DB/DC
    • DBCTL
    • DCCTL
    • FDBR (since UMS 1.2.0.9)
  • An IMS subsystem to be used for IMS Administration Foundation must be configured as a member of an IMSplex.
  • The IMSplex to be used for IMS Administration Foundation must be configured with the following features activated:
    • IMS Common Service Layer (CSL)

      CSL must be activated for all IMSplex systems to be used with IBM Unified Management Server for z/OS.

    • IMS Operations Manager (OM)

      OM must be configured for all IMSplex systems to be used with IBM Unified Management Server for z/OS.

If you want to use the IMS command processor feature for an IMSplex or pages for IMSplex, IMS, and IMS Connect, at least one IMS Connect server instance that is connected to the IMSplex must be configured and the IMS Connect OM Command exit routines HWSCSLO1 and HWSSMPL1 must be specified in the EXIT= parameter of the TCPIP statement for the IMS Connect server. For details, see the sections "IMS Connect support for IMSplex", "IMS Connect OM Command exit routines (HWSCSLO0 and HWSCSLO1)", and "Ping support for IMS Connect" in the IMS Communications and Connections Guide.

If you want to use the Unified Management Server authentication type of MFA_JWT to manage user credentials using Zowe JWT tokens, the IMS Connect maintenance provided by the IMS APAR PH51844 is required. For details, see RACF PassTicket support for commands from IMS Connect to IMS OM in the IMS 15.4 Release Planning Guide.

If you want to use any of the following IMS Administration Foundation features for an IMS data sharing group, you must register an IMS Connect DRDA port when registering the data sharing group in Unified Management Server:
  • IMS SQL processor
  • IMS catalog query dashboard
  • XML or DDL source view for a selected DBD or PSB
  • Instance information for a selected DBD or PSB
For registering an IMS Connect DRDA port, the following IMS components must be activated for the subject data sharing group and IMSplex to which the data sharing group belongs:
  • IMS catalog
  • IMS Connect server instance connected to the IMSplex
  • Open Database Manager (ODBM) server instance

For IMS catalog, both ACBMGMT=ACBLIB and ACBMGMT=CATALOG are supported. A data sharing group that can be registered with the Unified Management Server must share a single IMS catalog. If the data sharing group is composed of IMS subsystems of mixed ACBMGMT types, the IMS catalog must be set up to support ACB management by running the DFS3PU00 utility with the MANAGEDACBS=SETUP control statement specified. For this data sharing group configuration, it is user's responsibility to synchronize the active ACB timestamps and content of the IMS catalog and the ACB timestamps and content of ACBLIBs for the IMS subsystems of ACBMGMT=ACBLIB.

For IMS Connect and ODBM, at least one DRDA port needs to be configured, and at least one ODBM datastore alias for an IMS data sharing group for which the IMS SQL processor and catalog query features are used needs to be defined.

For other conditional requirements, see IMS Administration Foundation and IMS Tools.

Notes:
  • If you are using the IMS Database Manager for an IMS subsystem and want to access the full functionality of IMS Administration Foundation for DBDs, PSBs, and data sharing group dashboards, the IMS subsystem and data sharing group to which the IMS subsystem belongs must have an IMS catalog for managing DBD and PSB instances. Both ACBLIB-managed ACBs and IMS-managed ACBs are supported in IMS 15.5 and earlier IMS 15 releases.
  • The following requirement is removed in UMS 1.2.0.10 or later:
    • IMS subsystems must be configured by enabling Dynamic Resource Definition (DRD) for IMS resource management, using the resource definition dataset (RDDS), IMSRSC repository, or both. If the IMSRSC repository is used, it must be configured to register to the SCI of the IMSplex, which uses the IMS resource definitions managed by that IMSRSC repository.