GDDM V3R2 Diagnosis
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF | BOOK


Trace explanation

GDDM V3R2 Diagnosis
SC33-0870-01



The contents of the trace explanation vary depending on the trace record type, as follows:

CPNIN, CPNOUT
The trace explanation contains:

  • The request control parameter (RCP) in mnemonic and hexadecimal format. The first byte of the RCP identifies the component being invoked, as follows:
    
    
    
    
     X'00'  AIC  Application Interface Component
     X'04'  TSI  Terminal Services Interface Component
     X'08'  ESI  Environmental Services Interface Component
     X'0C'  FSM  Full Screen Manager
     X'10'  PGR  Presentation Graphics Routines
     X'14'  ICU  Interactive Chart Utility
     X'18'    Image Symbol Editor
     X'1C'  CSI  Common Services Interface Component
     X'20'    Vector Symbol Editor
     X'24'  OPU  Output Print Utility
     X'28'  IMS  IMS Interactive Utility Scheduler
     X'2C'  NMR  Numerical Processing Routines
     X'30'  IMD  GDDM-IMD
     X'38'  GKS  GDDM-GKS
     X'3C'  IMC  Image Manager Component
     X'40'  CDU  Composite Document Print Utility
     X'44'  IVU  GDDM-IVU
    
    

    
    
  • An interpretation of the RCP.
    
    
  • For calls to the Environmental Services Interface (ESI), for storage, program load/delete, or abend processing, an interpretation of the parameters to those services.
    
    

ERFIN, ERFOUT
The trace explanation contains:

  • The associated error message number, severity, and text. The string '(INTERNAL)' is produced for error codes that are purely internal to GDDM.
    
    

SUBIN, SUBOUT, MODIN, MODOUT
The trace explanation contains:

  • The module identification, including the module name.
    
    
  • For SUBOUT or MODOUT, the value of register 15, if it appears to be a return code.

Go to the previous page Go to the next page



Copyright IBM Corporation 1990, 2012