II04081: DIAGNOSTIC INFORMATION FOR ABEND212 MSGIEC909I

APAR status

• Closed as canceled.

Error description

• INFORMATIONAL ITEM CREATED TO ASSIST CUSTOMERS IN DIAGNOSIS
  OF MSGIEC909I ABEND212.
  

Local fix

• THIS APAR IS PROVIDED TO HELP CUSTOMERS DIAGNOSE SYSTEM
  212 ABENDS.  THE S212 IS ISSUED WHEN A SOFTWARE FAILURE
  OCCURS WHILE THE SVRB FOR IGC018 IS ACTIVE.  THE BLDL/FIND
  ESTAE ROUTINE, IGCT0018, ISSUES THE ABEND.  THE INTENT
  OF THE RECOVERY ROUTINE IS TO CAPTURE BLDL CONTROL BLOCKS
  AND WORK AREAS WHEN A PROGRAM CHECK OCCURS DURING BLDL
  PROCESSING.  THE ERROR IS TYPICALLY NOT IN BLDL, (IGC018)
  BUT IN SOME OTHER SYSTEM SERVICE CALLED BY IGC018.  THE
  RESULTING ABEND CODE IS GENERALLY A SYSTEM 212 BECAUSE
  IGCT0018 IS THE LAST ESTAE TO GET CONTROL.  THE PROBLEM
  IS TO FIND THE ORIGINAL ABEND CODE AND PURSUE THE PROBLEM
  WITH THE PROPER COMPONENT.
    ANY SVC18 ISSUED MAY RESULT IN CALLS TO VSM, EXCP, CSV,
  POST AND VLF.  OTHER FACTORS SHOULD BE KEPT IN MIND, SUCH
  AS THE FACT THAT EXCP CALLS RSM, OR THAT CSV USES CROSS
  MEMORY SERVICES TO ACCESS THE LLA ADDRESS SPACE.  IN
  MORE UNUSUSAL CASES SOFTWARE ERRORS IN A SUBTASKING
  ENVIORNMENT OR IN ASYNCHRONOUS EXIT ROUTINES MAY ULTIMATELY
  RESULT IN SYSTEM 212 ABENDS.
    AS AN EXAMPLE OF A TYPICAL ABEND 212, SUPPOSE BLDL DOES
  AN EXCP TO READ THE DIRECTORY OF A PDS.  THE EXCP PROCESSOR
  WILL INVOKE RSM TO PAGEFIX THE BUFFER AREA THE DIRECTORY
  WILL BE READ INTO.  IF AN ERROR OCCURS DURING THE PAGEFIX
  PROCESS, RSM'S ESTAE WILL ISSUE A SYSTEM 18A ABEND.
  AFTER THE ESTAE COMPLETES, IT PERCOLATES TO EXCP'S ESTAE
  WHICH WILL THEN ISSUE AN ABENDB00.  FINALLY, EXCP'S ESTAE
  WILL PERCOLATE TO IGCT0018 WHO WILL ISSUE THE ABEND212.
  IN THIS CASE THE PROBLEM SHOULD BE PURSUED WITH RSM TO
  DETERMINE THE CAUSE OF THE PAGEFIX FAILURE.
    IN A MULTIPLE ABEND SITUATION SUCH AS IS DESCRIBED ABOVE,
  THERE WILL BE AN RTM2 WORK AREA FOR EACH ABEND.  THE FIRST
  FORMATTED RTM2WA WILL BE FOR THE ORIGINAL ABEND.  IF THE
  ORIGINAL ERROR IS A PROGRAM CHECK, THERE IS GENERALLY
  NO RTM2WA FOR THE 0CX ABEND.  IN THIS CASE THE PROGRAM
  CHECK MIGHT BE FOUND IN THE SYSTEM TRACE TABLE. I.E. A PGM
  TRACE TABLE ENTRY SHORTLY BEFOR THE SVC D FORM IGCT0018.
  THE OLD PSW FROM THE TRACE TABLE ENTRY SHOULD IDENTIFY THE
  FAILING COMPONENT.
    IF THE PROGRAM CHECK OCCURRED DURING EXCP PROCESSING, THE
  REGISTERS AND PSW AT THE TIME OF THE ERROR ARE SAVED IN THE
  XDBA (EXCP DEBUGGING AREA) FORMATTED AFTER THE RTM2 WORK AREAS.
    IN THE EVENT THE ORIGINAL ABEND CANNOT BE DETERMINED BY ANY
  OF THE ABOVE TECHNIQUES, THE ERROR IS USUALLY A PROGRAM CHECK
  WHICH FOR SOME REASON IGCT0018 WAS UNABLE TO CAPTURE THE
  ERROR INFORMATION.  IN THIS CASE WE RECOMMEND SETTING THE
  FOLLOWING SLIP TRAP:
  SLIP SET,ACTION=SVCD,ERRTYP=PROG,JOBNAME=XXXXXXXX,ID=X212,END
    THE DUMP PRODUCED BY THE SLIP TRAP SHOULD THEN BE PURSUED
  WITH THE COMPONENT THAT SUFFERED THE PROGRAM CHECK.
  .
  Additional Keywords:
       how howto
  

Problem summary

Problem conclusion

Temporary fix

Comments

• THIS IS A DUMMY APAR
  

APAR Information

• 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