APAR status
INTRAN
Error description
Whenever a new PTF is put onto the CBIPO database any modules supplied in this PTF are link edited with the attributes contained on the ++MOD statement. If there are no attributes on the ++MOD then the defaults are used (NORENT NOREUS NOREFR). The attributes of this module are then compared to the attributes of the module as it was originally supplied in the FMID. If they are different then they are changed to reflect the attributes of the module as supplied by the FMID. However, if a PTF is put onto the database prior to its owning FMID then the modules will remain linked with whatever attributes were obtained from the PTF or the defaults. This may yield incorrect results, as was found with the following DFSMS mods: IGG0CLEI IGG0CLFY IGG0CLF6 IGG0CLGF IGG0CLKH and IDAIISM1 The defaults NORENT NOREUS and NOREFR were used since the ++MOD MCS did not contain link edit attributes. These modules all should have been liked as reentrant (RENT) however. This problem was discovered in 1994. As a result the CBIPO process has been changed to identify any PTFs that already exist on the database at the time when the owning FMID is put on. If any are found then all the modules supplied by these PTFs will be relinked so that their attributes match those contained in the modules supplied by the owning FMID.
Local fix
If any modules have been delivered by CBIPO that are linkedited incorrectly then the following should be done: 1) Get the RMID value from the MOD entry in the CSI. The DLIB and TARGET zone should contain the same value when the CBIPO install is complete. 2) If the RMID specifies an FMID name then the module was linked incorrectly in the product itself and CBIPO is not at fault. If the RMID contains a PTF name then this PTF needs to be obtained from IBM and reAPPLYed and reACCEPTed.
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II08597
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1995-03-31
Closed date
Last modified date
1995-03-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
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":"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"}}]
Document Information
Modified date:
31 March 1995