II14544: INFORMATION APAR FOR VTAM TRACES - INTERNAL DATASPACE EXTERNAL BUFFER TSO

APAR status

• Closed as canceled.

Error description

• ****************************************************************
  *                                                              *
  *   Information in this APAR is no longer being updated.       *
  *   Please use the following URL for the most current          *
  *   information:                                               *
  * http://www.ibm.com/support/docview.wss?rs=852&uid=swg21292013*
  *                                                             *
  ****************************************************************
  Information APAR for Enabling VTAM Traces
   ===============================================================
  
   This document includes information on the following VTAM
   traces:
   Section 1 - VTAM trace running internally.
   Section 2 - VTAM trace running internally and to dataspace.
   Section 3 - VTAM trace running externally to GTF.
   Section 4 - VTAM buffer trace.
   Section 5 - TSO / VTAM Traces.
  *********************************************************
  *     SECTION 1    VTAM INTERNAL TRACE                  *
  *********************************************************
  VTAM modify command to start VTAM trace running internally.
  F vtam,TRACE,TYPE=VTAM,MODE=INT,OPT=(xxx,xxx,...),SIZE=yyy
  *vtam is the VTAM procedure name.
  *xxx is needed options such as API,PIU,SMS, etc.
  The trace options to be used are dependent on the type
  of problem the trace is being run for.
  Contact z/OS Comm Server support for needed VTAM trace options.
  Default trace options are API,CIO,MSG,NRM,PIU,PSS,SMS,SSCP.
  *****NOTE*****
  It is recommeded that you routinely run with
  with at least the default trace options with SIZE=999.
  **************
  *yyy is the number of pages to be allocated for the internal
  trace table.The page size is 4K.  Values in the range of
  100 - 999 can be specified.
  
  The VTAM internal trace table is allocated in extended CSA
  storage.
  VTAM modify command to stop VTAM internal trace:
  F vtam,NOTRACE,TYPE=VTAM,MODE=INT,OPT=(xxxx,xxxx,...),END
  *xxx is the VTAM trace options currently running that you want
  to stop or OPTION=ALL can be specified.
  Exception trace entries continue to be recorded in the internal
  trace table.
  
  
  
  
  
  If you do not specify the MODE, tracing is stopped both
  internally and externally.
  
  Note: Although the default options are always active, these
  options do not appear in DISPLAY TRACES output unless you have
  specified them on the MODIFY TRACE command or the
  TRACE,TYPE=VTAM start option.
  *********************************************************
  *     SECTION 2    VTAM INTERNAL & DATASPACE TRACE      *
  **********************************************
  F vtam,TRACE,TYPE=VTAM,
    MODE=INT,OPT=(xxx,xxx,....),SIZE=yyy,DSPSIZE=z
  *vtam is the VTAM procedure name.
  *xxx is needed options such as API,PIU,SMS, etc.
  The trace options to be used are dependent on the type
  of problem the trace is being run for.
  Contact z/OS Comm Server support for needed VTAM trace options.
  Default trace options are API,CIO,MSG,NRM,PIU,PSS,SMS,SSCP.
  *****NOTE*****
  It is recommended that you routinely run with at least the
  default trace options and SIZE=999.
  
  **************
  *yyy is the number of pages to be allocated for the internal
  trace table. The page size is 4K.  Values in the range of
  100 - 999 can be specified.
  
  The VTAM internal trace table is allocated in extended CSA
  storage.
  *z is dataspace size - default DSPSIZE is 0, meaning the data
  space will not be used.  Valid values are 0 through 5, where
  a value of 1 is equal to 10 megabytes, a value of 2 is equal to
  20 megabytes, and so on.
  The VTAM trace dataspace is included in the dump when using F
  net,CSDUMP to obtain a dump of VTAM.  When using the MVS dump
  command, you would need to include DSPNAME=('vtam'.ISTITDS1)
  where 'vtam' is the VTAM procedure name.   ISTITDS1 is the
  name of the VTAM trace dataspace.
  
  VTAM modify command to stop VTAM internal trace:
  F vtam,NOTRACE,TYPE=VTAM,MODE=INT,OPT=(xxxx,xxxx,...),END
  *xxx is the VTAM trace options you are currently running that
  you want to stop or OPTION=ALL can be specified.
  If you do not specify the MODE, tracing is stopped both
  internally and externally.
  Note: Although the default options are always active, these
  options do not appear in DISPLAY TRACES output unless you have
  specified them on the MODIFY TRACE command or the
  TRACE,TYPE=VTAM start option.
  *********************************************************
  *     SECTION 3     VTAM EXTERNAL TRACE TO GTF          *
  *********************************************************
  Start GTF with
     TRACE=USRP
     USR=FE1,END
  *
   To prevent GTF from missing trace events, refer to II03922 for
   USRP and II10072 for the proper coding of GTF parameter BLOK=.
   We recommend BLOK=3M.
   The GTF trace dataset must be sufficiently large to contain all
   the expected events - 500-1000 cylinders.
  *
  Start VTAM trace running externally:
  F vtam,TRACE,TYPE=VTAM,MODE=EXT,OPT=(xxx,xxx,....),BFRNUM=yy
  *vtam is the VTAM procedure name.
  *xxx is needed options such as API,PIU,SMS, etc.
  The trace options to be used are dependent on the type
  of problem the trace is being run for.
  Contact z/OS Comm Server support for needed VTAM trace options.
  *yy specifies the number of 8K external trace buffers the VTAM
  internal trace is to allocate and use for GTF processing.
  Values in the range of 2-50, or 0 can be specified.
  
  If you omit this option, the default value is 2. To ensure that
  enough buffers are available, specify a value that is twice as
  much as the number of CPUs.
  
  If 0 is specified or there is no buffer available for the trace
  record, VTAM sends each trace record to GTF as it is recorded.
  This can incur a significant system overhead, but might be
  necessary if you need individually timestamped records.
  Stop VTAM trace running externally:
  F vtam,NOTRACE,TYPE=VTAM,MODE=EXT,OPT=END
  *
  Stop GTF.
  *
  Most likely a dump of VTAM will also be needed.  F vtam,CSDUMP
  or MVS console dump can be taken.  Support may need to specify
  what dump(s) are needed for the type of problem being traced.
  
  
  *********************************************************
  *     SECTION 4    VTAM BUFFER TRACE                    *
  *********************************************************
  Start GTF with
     TRACE=USRP
     USR=(FEF,FF1),END
  For buffer trace, FEF traces buff vtam entries and FF1 traces
  buff user entries.
  Starting VTAM buffer trace:
  F vtam,TRACE,TYPE=BUF,ID=nodeid
  *where vtam is your VTAM procedure name
  and nodeid is the resource you want to trace.
  Stopping VTAM buffer trace:
  F vtam,NOTRACE,TYPE=BUF,ID=nodeid
  *where vtam is your VTAM procedure name
  and nodeid is the resource you were tracing.
  Buffer trace must be run at the application owning VTAM.
  Buffer trace is recorded to GTF in MVS, Trace file in VSE,
  and TRF files in VM.
  Buffer trace output will include the destination and origin
  network names.
  Indicates INBOUND or OUTBOUND (in respect to the appl/VTAM).
  Two types of buffer trace - BUFF USER and BUFF VTAM.
  AMOUNT=FULL | PARTIAL - (default is PARTIAL.
  BUFF USER:
  GTF USRFD FF1
  Traced when data is moved to / from application buffers.
  Limited to 208 bytes for AMOUNT=PARTIAL.
  BUFF VTAM:
  GTF USRFD FEF
  Traced with TH and RH
  Limited to 179 bytes of RU for AMOUNT=PARTIAL
  Note:  trace only the node(s) that are necessary, so
  the trace output will be limited.  If possible, trace only
  the terminal LU name.
  Buffer trace is also recorded for SSCP traffic - if tracing
  a terminal logon problem for a cross-domain session, buffer
  trace may be needed on the LU-owning VTAM (to see the SSCP-LU
  flows) and on the appl-owning VTAM (to see the APPL-LU flows).
  *********************************************************
  *     SECTION 5    TSO / VTAM TRACE                     *
  *********************************************************
  The following URL contains information on TSO / VTAM Trace:
  http://www-01.ibm.com/support/docview.wss?rs=852&uid=swg21322246
  *********************************************************
  INFORMATION APAR FOR VTAM TRACES.
  VTAM INFO
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• closing cancel
  

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