Possible S0C1 abend using the Endevor or Quickedit ISPF dialogs

Products

• Endevor

Issue/Introduction

A site Using the Endevor dynamic environments feature, which is enabled by GCFDSN= parameter in the C1DEFLTS table, may be exposed to S0C1 abends in the Endevor or Quickedit ISPF dialogs. The conditions for the abend are:

• Running the dialogs in multiple ISPF split screens
• Starting and stopping the dialogs several times in the different screens

The abend may arise when

• Starting the dialog at a particular screen after other screens have already started/stopped
• Returning to the Endevor options menu using the ISPF RETURN key (usually PF4). This PF key returns to the options menu if option INTERCEPT ISPF RETURN CMD is set to Y in the User Defaults panels of the classic Endevor interface

A S0C4 abend is also possible although it has not been observed.

Cause

The support for dynamic environments calls IBM module IGGCSI00 which is used to retrieve information from the catalog related to a dataset. This is done to determine whether the GCF dataset appears to have been updated in order to refresh the information about the dynamic environments which is stored on it.

This logic has a bug which may eventually cause this module to be prematurely deleted from storage. The S0C1 abend will arise when the module is called again and the storage where it resided has been reused (this is the symptom observed so far). The S0C4 would arise if the affected page of storage has been returned to the system.

Resolution

Apply the fix that corresponds to your Endevor release

• LU17232 for Endevor 18.1
• LU17233 for Endevor 19.0

This problem may be worked around by making module IGGCSI00 resident in MVS common storage. This way, its address will be valid at all times regardless of whether it is deleted. This may be done, for example, via SETPROG command in the MVS console:

/SETPROG,LPA,ADD,MODNAME=IGGCSI00,DSNAME(LNKLST)

If this module is already resident in common storage, this abend will never be seen at your site. You can check as follows:

1. From the ISPF command prompt, enter TSO ISRDDN
2. From the ISRDDN menu, enter command LOAD IGGCSI00
3. If the module is resident in your system, you'll get a response like this one. Note that the address falls within extended common storage
   

   +-------------------------+
   | CSA resident          R |
   | Resident above 16 Meg   |
   | Module address:2B88F000 |
   | Module size:   00000790 |
   | Reentrant               |
   | Serially reusable       |
   | Not loadable only       |
   | AMODE 31                |
   | Authorized library      |
   | Not Authorized program  |
   +-------------------------+

    

4. If the module is NOT resident, you'll get a response like this one. Note the mention of LLA and SYS1.LINKLIB and the address that falls into extended private storage
   

   +-------------------------+
   | Job pack area resident  |
   | Resident above 16 Meg   |
   | Loaded by LLA           |
   | SYS1.LINKLIB            |
   | Module address:1DF00848 |
   | Module size:   00000790 |
   | Reentrant               |
   | Serially reusable       |
   | Not loadable only       |
   | AMODE 31                |
   | Authorized library      |
   | Not Authorized program  |
   +-------------------------+