IBM Support

II02521: RENAMING 'LOAD MODULES' OF IPDT (1ST THREE CHAR OF LOAD MODULE). WILL RENAMING EFFECT APAR SUBMISSION?

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • PROBLEM:      'INSTALLING TWO VERSIONS OF IPDT FOR CONCURRENT
    USE' (PP. 128) AND 'GENERATING MORE THAN ONE IPDT
                  SYSTEM' (PP. 27) OF IPDT INSTALLATION GUIDE
                  SH1253711.
    ANALYSIS:     RENAMING 'LOAD MODULES' OF IPDT. IF THE LOAD
                  MODULE NAMES ARE CHANGED, THERE IS NO PROBLEM
                  BECAUSE IPDT/PP MAINTENANCE DELIVERS ONLY PANELS,
                  MACROS AND TEXT MODULES. DURING SMP PTF INSTALL-
                  ATION, THE SHIPPED PARTS (PANELS, MACROS AND TEXT
                  MODULES) ARE REPLACED AND AFTERWARDS LINKED
                  ACCORDING TO THE LINK MEMBER WHICH WAS USED AT
                  IPDT INSTALLATION TIME. THE LOAD MODULES WILL GET
                  SAME NAME AS AT IPDT INSTALLATION TIME.
    NOTE:         ON A  FILURE, THE LOAD LIST WILL YIELD THE
                  DISPLACEMENT INTO THE LOAD MODULE AND TO
                  THE FAILING MODULE WITHIN THE LOAD MODULE
                  WHICH WILL BE DESIGNATED BY THE STANDARD
                  DXB___ NAMING CONVENTIONS: REGARDLESS OF THE
                  IPDT LOAD MODULE RUNNING WITHIN THE SYSTEM.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • COMMON PROBLEMS RENAMING IPDT LOAD MODULES.
    

APAR Information

  • APAR number

    II02521

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1986-06-09

  • Closed date

    1986-06-09

  • Last modified date

    1986-06-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Publications Referenced
SH1253711    

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
13 December 2020