The SERVERDATA SUMMARY report displays the following information
for each allocate queue:
- TP name
- Local LU name
- User ID
- Profile
- Partner LU name
- Queue token
- Current® servers
- Current allocates
- Total allocates
- Pending Receive Allocates
- Keep time
- Time created
- Time of last receive
- Time of last unregister
In the SERVERDATA SUMMARY report, information about each APPC/MVS
server follows the information for allocate queues. For each server,
the SERVERDATA SUMMARY report displays the following information (listed
by server address space):
- Address space ID
- Whether the server has an outstanding Get_Event call
- Number of events
- Number of allocate queues
The following example of the APPCDATA SERVERDATA SUMMARY report
shows three allocate queues, each of which is being served by the
same server. Information about each allocate queue begins with the
name of the TP associated with the particular allocate queue. In this
example, each of the three allocate queues is associated with a different
TP name (TOM001, TOM002, and TOM003).
Information about the server (address space ID 0041) follows the
information about the allocate queues.
For a description of each field in the APPCDATA SERVERDATA SUMMARY
report (Figure 1), see the section that
follows the example.
Figure 1. Example:
APPCDATA SERVERDATA SUMMARY report Summary Report for SERVERDATA
-----------------------------
ALLOCATE QUEUES
TP name:TOM002
Local LU name:M05AP003
User ID: * Profile: * Partner LU name:M05AP003
Queue token:02D5C97000000002
Current servers: 1 Current allocates: 1
Total allocates: 1 Pending receive allocates: 0
Keep time: 0
Time created: 04/12/1996 19:58:24.914258
Time of last receive: *NONE*
Time of last unregister: *NONE*
TP name: TOM003
Local LU name: M05AP003
User ID: * Profile: * Partner LU name: M05AP003
Queue token: 02D5CA7000000003
Current servers: 1 Current allocates: 1
Total allocates: 1 Pending receive allocates: 0
Keep time: 0
Time created: 04/12/1996 19:58:24.984713
Time of last receive: *NONE*
Time of last unregister: *NONE*
TP name: TOM001
Local LU name: M05AP003
User ID: * Profile: * Partner LU name: M05AP003
Queue token: 02D5C87000000001
Current servers: 1 Current allocates: 1
Total allocates: 1 Pending receive allocates: 0
Keep time: 0
Time created: 04/12/1996 19:58:24.012822
Time of last receive: *NONE*
Time of last unregister: *NONE*
SERVERS
Address space ID (ASID): 0041 Outstanding GET_EVENT: NO
Number of events: 3
Number of allocate queues: 3
Each field in the APPCDATA SERVERDATA SUMMARY report is described
in the section that follows.
- TP Name
- This value is the name of the TP associated with the allocate
queue. An APPC/MVS server specified this TP name when it registered
to serve certain allocate requests entering the system (through the
Register_For_Allocates service). The server also specified the TP's
local LU, and, optionally, the user ID, profile, and partner LU associated
with such allocate requests. If the system cannot determine the TP
name, *UNKNOWN* is displayed.
- Local LU Name
- The local LU name is the name of the LU at which the TP specified
by TP name resides. An APPC/MVS server specified this LU name when
it registered to serve certain allocate requests entering the system
(through the Register_For_Allocates service). The server also specified
the TP name, and, optionally, the user ID, profile, and partner LU
associated with such allocate requests. If the system cannot determine
the local LU name, *UNKNOWN* is displayed.
- User ID
- This value is the user ID associated with the allocate queue.
If a blank value was specified for the user ID when the server registered
for inbound allocate requests, an asterisk (*) is displayed.
- Profile
- This value is the security profile (for example, a RACF® group name) associated with the allocate
queue. If a blank value was specified for the profile when the server
registered for inbound allocate requests, an asterisk (*) is
displayed.
- Partner LU Name
- This value is the name of the LU at which the client TP resides.
The partner LU is the LU through which the allocate request flowed
when it entered the network. The partner LU name might be a network-qualified
LU name; that is, the combined network ID and network LU name
(two 1-8 byte Type A character strings, concatenated by a period: network_ID.network_LU_name).
The partner LU name is network-qualified if the network ID is known;
if not, only the network LU name appears in the report. If a blank
value was specified for the partner LU name when the server registered
for inbound allocate requests, an asterisk (*) is displayed.
- Queue Token
- APPC/MVS creates an allocate queue for each unique combination
of filter attributes specified when the server registered for inbound
allocate requests. When APPC/MVS creates an allocate queue, it returns
an allocate queue token to the server. The allocate queue token uniquely
identifies the allocate queue. The server uses the allocate queue
token to identify a specific allocate queue on subsequent calls to
APPC/MVS allocate queue services.
- Current Servers
- This number is the number of servers that are currently serving
a particular allocate queue. More than one server can serve the same
allocate queue. If multiple servers specify the same set of filter
attributes when registering for inbound allocate requests, the servers
will share the same allocate queue (and allocate queue token). Conversely,
a server can serve more than one allocate queue. If a server specifies
more than one unique set of inbound allocate requests when it registers,
the server will serve each allocate queue that results. For example,
if there is one server on the system, and it is serving two allocate
queues, this report lists one current server for each allocate queue.
- Current Allocates
- APPC/MVS places inbound allocate requests for servers in structures
called allocate queues. Servers can retrieve allocate requests from
the allocate queues (through the Receive_Allocate service). The number
of current allocates in an allocate queue reflects the number of allocate
requests that have not yet been received by a server. There is no
limit on the number of allocate requests an allocate queue can contain.
- Total Allocates
- This number is the total number of inbound allocate requests that
have been added to a particular allocate queue since it was created.
This number reflects the number of allocate requests that currently
reside on the allocate queue, plus the number of allocates that previously
resided on the queue and were subsequently removed by a server (through
the Receive_Allocate service).
- Pending Receive Allocates
- This is the number of pending Receive_Allocate requests that one
or more servers of a specific allocate queue have issued. When a server
attempts to receive an allocate request from an empty allocate queue
(and the server has specified that its Receive_Allocate request is
allowed to wait), the Receive_Allocate request is considered to be
pending until it completes.
- Keep Time
- An APPC/MVS server can optionally specify a “keep time” for any
allocate queue it serves. Keep time is the number of seconds an allocate
queue is maintained by APPC/MVS in the absence of registered servers
for the allocate queue. Specifically, keep time would apply when the
last server of the allocate queue unregisters. When keep time is in
effect, APPC/MVS allows the allocate queue to continue to grow as
new inbound allocate requests for a server enter the system. If a
server does not resume serving the allocate queue within the specified
keep time, APPC/MVS purges the allocate queue. If no keep time has
been specified for an allocate queue, APPC/MVS purges the queue immediately
after the last server of the queue unregisters.
- Time Created
- The date and time when the allocate queue was created. The date
and time are displayed in the format mm⁄dd⁄yyyy hour:minutes:seconds:microseconds.
If the system cannot determine the time at which the allocate queue
was created, *UNKNOWN* is displayed.
- Time of Last Receive
- The date and time when a server most recently received an allocate
request from the allocate queue (through the Receive_Allocate service).
The date and time are displayed in the format mm⁄dd⁄yyyy hour:minutes:seconds:microseconds.
If no allocate requests have been received from the allocate queue, *NONE* is
displayed.
- Time of Last Unregister
- This is the date and time when the last server to serve the allocate
queue unregistered (leaving no servers registered for the queue).
If a keep time was specified for the allocate queue, APPC/MVS maintains
the queue from the time of the last unregister until the keep time
expires, or until another server resumes serving the queue. If no
keep time was specified, this field is not set. The date and time
are displayed in the format mm⁄dd⁄yyyy hour:minutes:seconds:microseconds.
If one or more servers are registered for the allocate queue, *NONE* is
displayed.
- Address Space ID
- Information about a particular APPC/MVS server begins with the
address space ID (ASID), which uniquely identifies the server's address
space. The ASID is displayed as four hexadecimal digits.
- Outstanding Get_Event
- An APPC/MVS server can receive notification of certain events
related to a specific allocate queue for which the server is currently
registered. The server requests notification of such events through
the Set_Allocate_Queue_Notification service. When the specified event
occurs, APPC/MVS places an element that represents the event on a
structure known as an event queue. The server can retrieve events
from its event queue through the Get_Event service. A server can specify
whether to have the Get_Event service wait if there are no elements
on its event queue. When the event occurs, the Get_Event call returns
to the server. An outstanding Get_Event call is one that has not yet
returned to the server.
- Number of Events
- An APPC/MVS server can receive notification of certain events
related to a specific allocate queue for which the server is currently
registered. The server requests notification of such events through
the Set_Allocate_Queue_Notification service. When the specified event
occurs, APPC/MVS places an element that represents the event on a
structure known as an event queue. The server can retrieve events
from its event queue through the Get_Event service. The number of
events reflects the number of event elements currently contained in
the server's event queue. There is no limit on the number of event
elements an event queue can contain.
- Number of Allocate Queues
- APPC/MVS places the inbound allocate requests for which a server
has registered on a structure called an allocate queue. APPC/MVS creates
an allocate queue for each unique combination of filter attributes
specified when the server registered for inbound allocate requests
(through the Register_For_Allocates service). The number of allocate
queues is the number of allocate queues for which a particular server
is currently registered. There is no limit on the number of allocate
queues for which a server can be registered.