Falling back from IMSRSC repository support for dynamically defined MSC resources

You can fall back from an IMS system that has IMSRSC repository support for dynamically defined MSC resources to an earlier version of IMS.

Procedure

  1. Keep your stage 1 system definition synchronized with dynamic definition of MSC resources.
  2. Issue the DELETE DEFN command for all of the MSC resource types that have resource definitions in the IMSRSC repository for the IMS that is falling back. Issue the DELETE DEFN command with keywords FOR(IMSID(IMS1)) and NAME(*) for each MSC resource type.
    For example, if IMS1 is falling back, to delete all MSC resources, issue the following commands in the following order:
    DELETE DEFN TARGET(REPO) NAME(*) TYPE(TRAN)FOR(IMSID(IMS1))
DELETE DEFN TARGET(REPO) NAME(*) TYPE(LTERM)FOR(IMSID(IMS1))
DELETE DEFN TARGET(REPO) NAME(*) TYPE(MSNAME)FOR(IMSID(IMS1))
DELETE DEFN TARGET(REPO) NAME(*) TYPE(MSLINK)FOR(IMSID(IMS1))
DELETE DEFN TARGET(REPO) NAME(*) TYPE(MSPLINK)FOR(IMSID(IMS1))
  3. Run system generation for stage 1 system definition that includes MSC resources, which are the following:
    • MSPLINK, MSLINK, MSNAME, and NAME macros
    • IMSCTRL macro with MSVID and SYSTEM=(MSVERIFY) parameters specified
    • APPLCTN and TRANSACT macros with the SYSID parameter specified
  4. Restore old copies of MSC user exits.
  5. Restore old copies of automation programs that issue QUERY LTERM, QUERY MSLINK, QUERY MSNAME, and QUERY MSPLINK commands and parse the output.
  6. Remove new MSC parameters from the DFSDFxxx member of the IMS PROCLIB data set.
  7. Cold start IMS at a previous IMS release level.
  8. Complete other pertinent tasks related to falling back to a previous version of IMS.
  9. Confirm that dynamic definition is disabled for MSC resources by issuing the QUERY MEMBER TYPE(IMS) command, and ensuring that the command output does not include DYNMSC in the local attributes.