Updating the maintenance service level of a new or migrated IMS system

After installing an IMS system, whether it is a new system or a new release for an existing IMS system, you need to bring the service level of the new system to an acceptable level of currency by installing service levels and PTFs, resolving PE PTFs, and conducting a test cycle..

Attention: SYSMODs in APPLY-only status can be regressed by an IMS system definition. See Preventing regression of SYSMODs in APPLY-only status by an IMS system definition for instructions about preventing this.
Note: You can use the /DIAGNOSE SNAP MODULE(modulename) command to determine your current maintenance level for a specific module.

If you are starting with a base implementation service level of an IMS production system, the following actions are recommended:

Procedure

  1. Six months before you plan to implement the IMS system in production, install all available PTFs.
  2. Three months before you plan to implement the IMS system in production, install all PTF fixes for HIPER APARs.
  3. Resolve PEs.
    Evaluate any PE PTFs that are installed in your IMS system to determine if they impact your IMS environment. If they do, either install the fix for the PE PTF, remove the PE PTF, or contact IBM® Software Support for assistance.
  4. A 3-month test cycle is recommended before you implement the IMS system in production

Because IMS maintenance continues to be distributed both during and after the test cycle, incorporate ongoing procedures for maintaining the service levels of your production systems as soon as possible in your new system. For an example of the procedures you can use, see Obtaining and installing maintenance.