II07312: INFO APAR ON VSE SDAID

APAR status

• Closed as canceled.

Error description

• SDAID is the part of VSE/Advanced Functions used to trace
  specific events in your system and to create trace records
   for those events. It is useful in problem solving for system
   or application programs.
  
   SDAID offers you several different types of traces and a
   choice of output to be recorded for each event. More than one
   trace can be run concurrently, each with a different set of
   output and options.
  
   SDAID can be initialized in different ways:
   1. Prompts through the Attention Routine
   2. Direct Input to the AR or partition
   3. Job Control Procedures
  First two methods are used most commonly.
  
  Once initialized, the tracing can be started or stopped,
  or SDAIDS can be ended, through the Attention Routine command.
  
  SDAID initialization consists of four steps
   1. Invoke SDAIDS
   2. Define the output device
   3. Define the trace type(s)
   4. End SDAID initialization
  
  OUTPUT DEVICE
  SDAIDS requires an output destination for its' trace records
  when you initialize the trace. The output may be directed to
  printer, tape or buffer.
  
  The buffer may be used in wrap-around mode and dumped using
  the AR DUMP command. This feature is most useful for randomly
  occurring problem where only interest in the output is last
  few entries. The buffer also may be dumped to tape or printer
  by SDAIDS either when it is full, or on occurrence of a
  specified event.
  
  A wrap-around buffer with no output device can be dumped using
  the AR DUMP command and formatted using DOSVSDMP. also, if there
  is an SDAID buffer in storage when a S.A. dump is taken,
  INFO-ANALYSIS will format the buffer in the dump analysis.
  
  TYPES OF TRACES
    BRANCH - An event record is made for every branch taken
             within the area specified.
    BUFFER  - Dumps the contents of the SDAID wrap-around buffer
              to the output device when the buffer is full.
    CANCEL - An event record is made when the main task of the
             program within the area specified is cancelled or
             reaches EOJ.
    EXTERNAL - Gives information on the occurrence of different
               types of external interrupts: KEY SIGNAL TIMER
    INSTRUCTION - You can select specific op-codes or all op-codes
                  to trace within the area specified
    IO - Traces i/o interrupts for a particular channel,
         control unit, or device
    MONITORCALL - Provides trace records for specific monitor
                  call class
    PAGING - Records information about page faults
    PGM - Program check trace provides information on the
          occurrence of certain  program check types or all
          program check types (except page fault).
    PGMLOAD - Creates an event record for fetch/load request and
              handled requests.
              SVC1 SVC2 SVC4 SVC5 SVC30 SVC41 are traced.
    REGISTER - Register alteration trace provides an event record
               on instructions which alter the contents of
               specific registers. A pattern may be specified to
               limit tracing to instructions which modify the
               register to that pattern.
    SIO - Gives an event record for every SIO or SIOF instruction
          for a particular channel, control unit, or device.
    STORAGE - Storage alteration trace provides information about
              instructions which alter the contents of a
              predefined storage area. You may specify a pattern.
    SVC - Provides information about supervisor calls for
          specific SVC codes or all SVC codes.
    VTAMBU - Provides an event record each time VTAM uses one
             of the buffers in its' buffer pool.
    VTAMIO - Combines traces for SVC31 SVC35 SIO and IO for
             VTAM devices.
  
  AREA DEFINITION
   Area definition tells SDAID the tasks to be traced. you may
   specify one of followings : partition-id, SUPVR, ALL,
   space-id  (370 mode). All trace types require the area
   definition except for BUFFER, EXTERNAL, IO, SIO, and VTAMBU.
   SIO and IO may specify an area if desired.
  
   The storage definition allows you to specify the storage
   to trace within the task. You may specify an OFFSET from the
   beginning of the partition or the supervisor, or an ADDRESS
   range within the partition, supervisor, or address space.
   You may trace a particular PHASE or range within the phase
   for a partition.
  
  OUTPUT DEFINITION
   SDAIDS records some basic information for each type of
   event traced. You may specify additional output for each
   trace initialized.
  
   OPTIONS
   For each trace, you may specify one or more options:
   1. HALT - stops the system when the event occurs. The PSW
             address portion will be '0000EEEE'.
   2. NOJCL - suppresses tracing of Job Control Phases
   3. TERM - terminates SDAIDS output on occurrence of the event
   4. OCCURRENCE = occ1:occ2   specify the number of associated
                   events to be traced.
  
  INITIALIZING THE TRACE
    PROMPT MODE
    You can enter SDAID commands through the operator console
    and SDAID will prompt you for input.
  
   Required commands for PROMPT mode are :
          SDAID   invokes the sdaid program
          OUTDEV  defines the output device
          TRACE   defines trace events
          READY   ends initialization of sdaids
  
    SDAIDS prompts you for trace type, area, output and options
    for the trace when you enter the TRACE command. The OUTDEV
    command prompts you for information concerning the output
    device.
  
    If you are not sure of what to respond to a prompt, enter
    a question mark (?) and SDAIDS will list the valid responses.
    You can cancel data entered for the current command by
    entering two question marks (??), then retype the command.
  
  DIRECT INPUT
   DIRECT INPUT mode can be entered in two different ways.
   Commands entered through the attention routine (SDAIDS may
   switch from prompt to direct input and back depending on your
   command input) you determine direct input mode by specifying
   one or more keywords ex: OUTDEV P=E. If you leave out all
   possible keywords or use (?) SDAIDS switches to PROMPT mode
   ex: TRACE INSTR=* AR=BG OUPT=?
  
   Or commands entered through Job Control. SDAID is invoked
   by the // EXEC SDAID statement. This may be entered through
   SYSIN (JCL format) or via the CONSOLE.
  
   Initialization of SDAIDS in DIRECT INPUT mode must be ended
   in one of three ways:
   1. The '/*' statement from SYSIN
   2. The READY command from the attention routine
   3. The <ENTER> key from the console
  
  EXAMPLE: // JOB SDAIDS
           // EXEC SDAID
              OUTDEV P=05E | T=180 | BU=35
  * Output is directed to either Printer address 05E, tape
  * address 180, or to SDAID buffer with size defined as 35.
  
              TRACE SIO AR=ALL UNIT=cuu OUTP=(IRB CCB CCWD=32)
              TRACE IO AR=ALL UNIT=cuu OUTP=(IRB CCB CCWD=32)
  * For SIO / IO trace, AR=ALL is recommended always. If
  * running ESA mode, IRB for OUTP must be specified.
  * Note: IRB can not be specified in VSE/ESA 2.1 and
  *       follow-on releases. IRB is already contained in output
  *       if CCW or CCWD=... is specified.
  * Note: CCWD option with TRACE SIO will show the channel
  *       program as it is finally started, e.g. when a CKD->ECKD
  *       conversion by VSE/ESA supervisor has been done, you will
  *       see the ECKD channel program.
  *       CCWD option with TRACE IO will show the original user
  *       channel program.
              READY
            /*
            /&
  
  or   // JOB SDAIDS
       // EXEC SDAID
          OUTDEV P=05E | T=180 | BU=35
          TRACE SSCH AR=ALL CHANNEL=c OUTP=(IRB CCB CCWD=32 TOD)
          TRACE IO AR=ALL CHANNEL=c OUTP=(IRB CCB CCWD=32 TOD)
          READY
       /*
       /&
  
  SSCH or SIO is allowed for ESA mode.
  
  PROCEDURE MODE
    VSE/Advanced Functions comes with a set of predefined JCL
    procedures to initialize SDAID traces when run in a
    partition. These procs reside in IJSYSRS.SYSLIB, and they
    enable you to initialize SDAIDS with one JCL EXEC PROC
    statement. For information, refer to SERVICE AID manual.
  
  STARTING/ENDING THE TRACE
    Once initialization is complete, the SDAID trace can then
    be STARTED, STOPPED, or ENDED through the use of
    ATTENTION ROUTINE COMMANDS.
     STRTSD  -  will start or restart the trace
     STOPSD  -  will stop the trace with restart capability
     ENDSD   -  end the SDAID session completely
    Once initialized, SDAIDS can be started or stopped as many
    times as needed. When the trace is ended, it must be
    reinitialized in order to begin tracing again because all
    SDAID resources are released.
  
  MORE ON OUTPUT
   DEVICES
    When a printer is specified, trace records are written to
    the printer as they are generated. The printer must be a
    real printer, not a power dummy printer, because SDAIDS
    does physical i/o. Besure that no one else is using the
    printer or the trace entries will be intermixed with
    printer output. PSTOP of the printer is recommended.
  
    If the output device is not ready or has an i/o error
    or output is directed to power dummy printer), the system
    will go into a wait state with PSW address '00EEEEEE' and
    a code will be placed in low core x'000000'. Refer to the
    Message and Code manual for information on how to get out
    of this situation.
    If the output device is a tape (with no buffer specified)
    SDAID aquires a 3K buffer and writes the entries to the
    tape when the buffer fills, or when STOPSD or ENDSD in
    entered. Data could be lost if these command are not entered.
  
  THINGS TO THINK ABOUT
  
   SDAIDS trace runs in the V=R area at the end of the
   supervisor for mode=370 or ESA. This area can be increased
   with the SDSIZE parameter of the SYS command at IPL.
   For mode=E and VM, SDAIDS runs in the SYSTEM GETVIS area.
  
   Messages from SDAIDS are in the VSE/SP message manual section
   with a prefix of '4Cxx'
  
   If you receive MSG4C07I GETREAL failed at SDAID
   intialization time, try increasing SDSIZE. Some OEM code
   resides in V=R area (EXPLORE is one of them) which causes
   SDAID not to initialize. Either turn off the OEM package
  or contact them to see if their residence could be moved
  to different part of the system ie., system getvis.
  
  If MSG4C06I is issused when STRTSD command is entered, make
  sure you have entered READY command prior to STRTSD command.
  
  The initialization phases run in the SYSTEM GETVIS area
  and need about 100k. Initialization from the partition needs
  only 16K so that it will run in even the smallest partition.
  
  Storage requirements for the tracing depend on the number
  and types of traces you are doing. See Service Aids manual
  for more info.
  
  Limit your tracing to only what is needed for performance
  reasons. (and amount of output).
  For details refer to paramters
    AREA OFFSET PHASE  JOBNAME OCCURRENCE NOJCL SUP etc.
  
  If you are tracing an area using PHASE, the phase must be
  loaded after SDAIDS is started or it will not know that the
  phase is there.
  The following traces use PER
  BRANCH, INSTRUCTION, REGISTER and STORAGE.
  The PER bit (bit1) in the PSW must be on in order to trace
  the code. This is usually done by the system automatically.
  However some OEM code intercepts the supervisor code and
  reloads the PSW without PER bit on.
  
  Some parts of the supervisor cannot be traced. HARDWARE or
  VM PER may be needed to trace some problems which SDAIDS cannot.
  
  Also SDAID cannot be used until IPL of VSE is completed.
  
  Also SDAID does not work in multi-processor mode (VSE/ESA V2).
  All but the IPL CPU have to be stopped to start an SDAID trace.
  
  PGMLOAD traces only trace SVCs which fetch phases, a BAL
  to another phase in storage is not detected
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

•  cancelling info 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