Use the APPCDATA subcommand to generate reports about the Advanced
Program-to-Program Communication (APPC) component of MVS™. This subcommand provides information about
the following topics:
- Status of the APPC component
- Configuration of local logical units (LU)
- Local transaction programs (TPs) and their conversations
- Allocate queues and their associated APPC/MVS server address spaces.
- TP FMH-5 attach requests
- APPC component trace status
See the APPC/MVS component
chapter in
z/OS MVS Diagnosis: Reference for
examples of APPCDATA output.
- Syntax
APPCDATA
--------- Report Type Parameters ---------------------------
[ ALL ]
[ CONFIGURATION ]
[ CONVERSATIONS[(asid|ALL)] ]
[ SERVERDATA ]
[ CTRACE ]
[ FMH5MANAGER ]
[ STATUS ]
--------- Data Selection Parameters ------------------------
[ DETAIL ]
[ EXCEPTION ]
[ SUMMARY ]
-------- SETDEF-Defined Parameters -------------------------
Note: You can override the following SETDEF parameters.
See SETDEF subcommand — set defaults.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dsname)|DATASET(dsname) ]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
- Report type parameters
Use these parameters to select
the type of report. You can specify as many reports as you want.
If you omit these parameters, the default is ALL.
- ALL
- Requests that information for all the APPCDATA options be presented.
- CONFIGURATION
- Requests information about the configuration of local LUs in terms
of their connections to partner LUs. The configuration summary report
displays the following information:
- Local LU name and its status
- Number of partner LUs with which the local LU had sessions
- Number of partner/mode pairs for which sessions were established.
- VTAM® generic resource name
or *NONE*
- Local LU resource manager name and token
- Number of units of recovery (URs)
- Total expressions of interest
The configuration detail report includes information from
the summary report and adds the following information for each partner
LU:
- Partner LU name
- Number of modes that defined session characteristics
- Logon name for each mode.
- URIDs and expressions of interest for each UR
- Diagnostic information
- CONVERSATIONS[(asid|ALL)]
- Requests information for each local TP and its conversations for
either a particular address space, specified as an address space identifier
(ASID), or all address spaces. For this parameter, asid is
a 1- to 4-character hexadecimal value. If no ASID is specified, information
for all address spaces is displayed.
The conversations summary
report displays for each address space the following information:
- A scheduler name
- Local TP name or *UNKNOWN*
- TP_ID
- Local LU name through which the session was established
- Work unit ID
- Number of conversations in which the TP was engaged
The conversations detail report includes information from
the summary report and adds the following information for each conversation:
- Conversation identifier
- Conversation correlator
- Partner TP name or *UNKNOWN*
- Attach user identifier
- Conversation type
- Sync level
- Unit of recovery identifier (URID)
- Logical unit of work identifier (LUWID)
- Resource manager name
- LU name of the partner TP
- Logon mode
- The current state
- Time of day (TOD)
- SERVERDATA
- Requests information about allocate queues and their associated
APPC/MVS server address spaces.
The SERVERDATA
summary report displays the following information about allocate queues
and APPC/MVS server address spaces.
- For each allocate queue:
- Name of the TP whose allocate requests are being queued
- Name of the LU at which the server resides
- Userid that was specified on the allocate request
- Profile of the security group to which the userid belongs
- Name of the LU at which the client TP resides
- Number of servers for the allocate queue
- Number of allocate requests (elements) on the allocate queue
- Total number of allocate requests that have been added to the
allocate queue (includes allocate requests that have been received
from the allocate queue)
- Number of pending calls to the Receive_Allocate service
- Keep time (the amount of time APPC/MVS is to maintain the allocate
queue in the absence of servers)
- Time at which the allocate queue was created
- Time at which an allocate request was last received from the allocate
queue
- Time at which a server last called the Unregister_For_Allocates
service to unregister from the allocate queue.
- For each APPC/MVS server:
- Address space identifier (ASID) of the server address space
- An indication of whether the server has an outstanding call to
the Get_Event service
- Number of events on the server's event queue
- Number of allocate queues for which the server is currently registered.
The SERVERDATA detail report includes information from
the summary report and adds the following information:
- For each APPC/MVS server for a given allocate queue:
- Address space identifier (ASID) of the server address space
- Time at which the server registered for each allocate queue
- Time at which the server last issued the Receive_Allocate service
- Time at which a Receive_Allocate request was last returned to
the server
- Total number of allocate requests returned to the server.
- For each pending Receive_Allocate request for a given allocate
queue:
- The address space identifier (ASID) of the server with the pending
Receive_Allocate request.
- For each inbound allocate request for a given allocate queue:
- Conversation identifier
- Access method conversation identifier
- Conversation type (basic or mapped)
- Conversation correlator
- Logon mode
- Partner LU name
- Sync level (“none” or “confirm”)
- Userid
- Security profile
- Time at which the system placed the request on the allocate queue
- Address of the access method control block (ACB) for the LU at
which the APPC/MVS server resides.
- For each server event for a given server:
- Event (“min” or “max”)
- Event object (the allocate queue token of the allocate queue to
which the event pertains)
- Event qualifier.
- For each allocate queue for a given server:
- Allocate queue token
- Minimum and maximum one-time event threshold
- Minimum and maximum continuous event threshold.
- CTRACE
- Displays the status of component trace for APPC, trace options,
and other trace-related information. The CTRACE summary report displays
the following information:
- Trace status
- Most recently specified trace options
- User IDs, ASIDs, and job names used as filters
The CTRACE detail report includes information from the summary
report and adds the following details:
- Console identifiers of the operator who most recently started
or stopped the trace
- Message-routing command and response token (CART)
- Information about the trace table
- FMH5MANAGER
- Requests information about the transaction program FMH-5 attach
requests that are either waiting to be processed or are currently
being processed.
The summary report displays the number of TP FMH-5
attach requests that are waiting to be processed and the number of
requests currently being processed.
The detail report lists,
for both types of requests, the LU names and the total number of requests
they received. For each LU name, the requests are broken down into
the number of requests originating from a specific partner LU name.
If the request was being processed and dump data is available, the
report displays the data.
- STATUS
- Displays a message about the overall status of the APPC component
at the time of the dump.
Note: The reports generated by the APPCDATA
subcommand contain information for IBM® diagnostic
use. The IBM Support Center
might ask for this information for use in problem determination.
- Data Selection Parameters
Data selection parameters
limit the scope of the data in the report. If no data selection parameter
is selected, the default is to present a summary report for all topics
listed below.
- DETAIL
- Requests detailed information for each of the selected topics.
- EXCEPTION
- Requests a list of exceptional or unusual conditions for each
topic. The list of exceptions contains information for IBM diagnostic use.
- SUMMARY
- Requests summary information for each of the requested topics.
- Return codes
See Standard subcommand return codes for
a description of the return codes produced by the APPCDATA subcommand.