SMP/E install of SYSMOD C2D61ME / C2D62ME or C2D63ME fails with multiple GIM23901E and IEW2456E messages

Document ID : KB000055112
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When installing any product that supplies the WebCenter SSL capability, you may encounter these errors during install of SYSMOD C2D61ME, C2D62ME or C2D63ME.

GIM23901E ** LINK-EDIT PROCESSING FOR SYSMOD C2D61ME FAILED FOR MODULE NMCOPYDL IN LMOD NM123 IN THE MELOAD LIBRARY. THE RETURN CODE (08)
EXCEEDED THE ALLOWABLE VALUE

IEW2456E 9207 SYMBOL gsk_environment_close UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.

Solution:

When installing, FMID C2D6xME will fail during the APPLY step with several SMP/E errors. For this example we are looking at C2D61ME:

GIM23901E ** LINK-EDIT PROCESSING FOR SYSMOD C2D61ME FAILED FOR MODULE NMCOPYDL IN LMOD NM123 IN THE MELOAD LIBRARY. THE RETURN CODE (08)
EXCEEDED THE ALLOWABLE VALUE

...and the FMID completes with:

GIM30216I    APPLY PROCESSING FAILED FOR SYSMOD C2D61ME. SYSTEM UTILITY,PROCESSING,FAILED FOR AN ELEMENT IN C2D61ME.
GIM30216I    APPLY PROCESSING FAILED FOR SYSMOD NY710ME. SYSTEM UTILITY PROCESSING FAILED FOR AN ELEMENT IN NY710ME.
GIM37001S ** APPLY PROCESSING STOPPED BECAUSE FUNCTION SYSMOD C2D61ME FAILED.
GIM20501I    APPLY PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 12.

...all further processing fails.

The LMOD from the GIM23901E message shows additional messages in the linkage editor section of the output.

As an example, a search for the failing LMOD of NM123 shows many IEW2456E messages indicating that various gsk? symbols could not be resolved. Excerpts from one such section:

IEW2322I 1220  11    INCLUDE ME1SDL(GSKSSL)                 TYPE=UTIN
IEW2303E 1030 MEMBER GSKSSL OF THE DATA SET SPECIFIED BY ME1SDL COULD NOT BE FOUND.
IEW2322I,1220  26    NAME NM123(R)                          MAX ACCEPTABLE RC=04
IEW2456E 9207 SYMBOL gsk_environment_close UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.

The problem goes back to the way the datasets were allocated.

Please review your I01ALLOC job. By default, we generate these DD's defined as DSNTYPE=LIBRARY (PDS/E):

//SMPLTS DD DSN=hlq.SMP.NMB5.SMPLTS,
//ME0001 DD DSN=hlq.NMB5.MELOAD,
//ME0002 DD DSN=hlq.ME1LOAD,
//ME0003 DD DSN=hlq.ME1SDL,

...along with an additional step at the end for the SSL:

//OGET, EXEC PGM=IKJEFT1B,DYNAMNBR=50
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
OGET +
'/usr/lib/GSKSSL.x' +
'hlq.NMB5.ME1SDL(GSKSSLX)' BINARY
EXEC +
'hlq.NMB5.INSTALL(NMGSKSSL)' +
'hlq.NMB5.ME1SDL GSKSSLX GSKSSL'

So you need to check the I01ALLOC job and see how the datasets were originally created. You have two options:

  1. The recommended one would be to go back and review your I01ALLOC job.
    The JCL must have been altered to create non-PDSE libraries.
    It would be best to

    • delete all libraries from the install process
    • change or regenerate the JCL to contain the necessary PDSE libraries
    • re-run all jobs


  2. Your second option would be to omit the C2D61ME FMID.

At the 11.5 release of NetMaster and 11.0 release of SOLVE:Operations, this FMID is used to populate the MELOAD library which is a PDSE that only contains modules needed for WebCenter SSL. If you are doing this for a higher release of NetMaster, please review the Reference manual for potential changes to the content of the MELOAD or call NetMaster support to verify content.

If you are not using WebCenter, or do use WebCenter but are not interested in using secure sockets, you can do without this library. In that case you can simply remove FMID C2D6xME from your SMP/E jobs.

Please be aware that you would need to change the JCL to omit the FMID for any further service packs that you may apply at a later date.