This information describes common situations you may encounter during installation, maintenance, and migration.

Problem:

Unpredictable results such as 0C4 or 0C1 abends upon invocation of ISPF.

Cause:

This problem can occur when internal LINKs and LOADs are used in conjunction with the ISPF ISPLLIB DCB.

Solution:

When using STEPLIB to test new maintenance, releases, or versions of products and an ISPLLIB is allocated, data sets allocated to STEPLIB should also be allocated to ISPLLIB.

Problem:

New levels of code residing in STEPLIB do not appear to be executed. This includes changes to customer applications, new levels of code, and changes made by PTFs, for example.

Cause:

This problem can occur when internal LINKS and LOADs are used in conjunction with the ISPF ISPLLIB DCB.

Solution:

When using STEPLIB to test new maintenance, releases, or versions of products and an ISPLLIB is allocated, data sets allocated to STEPLIB should also be allocated to ISPLLIB.

Problem:

Abends occur when invoking or exiting HELP, KEYS, or ISPPREP.

Cause:

An older level of ISPF exists in LPA or LINKLIB; an ISPLLIB or STEPLIB is used to allocate libraries for the new release of ISPF; and a LIBDEF for ISPLLIB that does not include the new level of ISPF libraries has been issued.

Not all of ISPF is loaded at initialization, for example, ISPTUTOR is linked when HELP is requested. The LIBDEF of ISPLLIB results in the older level of any modules that are not loaded on ISPF entry to be picked up from LPA or LINKLIB due to internal search orders. For more information, refer to the LIBDEF command in z/OS ISPF Services Guide.

Solution:

Include the new level of ISPF in any LIBDEFs issued for ISPLLIB.

Problem:

Abend code 806 for ISPLINK or Abend code 0C1 in user application.

Cause:

During installation, the SMP/E install logic for ISPF deletes the existing ISPLINK load module.

Solution:

Relink-edit ISPLINK to user application.

Problem:

Abends in load modules IGC0009C and IGC0009D.

Cause:

Failure to install ISPF in the same zone as TSO/E will result in the supplied ISPF SVC 93 and SVC 94 exits (ISPSC93, ISPSC94), creating SVC 93 and SVC 94 load modules without the proper link-edit information.

Failure to use the correct version of either IGC0009C or IGC0009D or both.

Solution:

TSO/E, ISPF, and ISPF/PDF must all be installed in the same zone. Verify that the correct versions are copied from a test system to the production system.