ASCHDATA DETAIL subcommand output

The ASCHDATA DETAIL report displays information about a specific scheduler class or about all scheduler classes. Figure 1 is an example of the ASCHDATA DETAIL report.

Figure 1. Example: ASCHDATA DETAIL report

      Detail Report for ASCH SCHEDULER
      --------------------------------
      Status of ASCH SCHEDULER: ACTIVE
      ASCH SCHEDULER subsystem name: MSTR
      ASCH SCHEDULER default class: A

       Class: A        Status of class: ACTIVE

        Maximum number of initiators:       10
        Minimum number of initiators:        5
        Expected response time: 00:00:51.000000
        Message limit:       20

       Total number of jobs waiting for execution:        0

       Total number of active initiators:        2

       Address space ID (ASID): '0016'X

       TP start time: 10/14/1996 17:44:44.426817
         TP name: TPMAINP
         Current job ID: A0000006
         Local LU name: M09AP001
         Partner LU name: M09AP001
         User ID from FMH5: IBMUSER

         Address space ID (ASID): '0018'X

         TP start time: 10/14/1996 17:34:41.448941
         TP name: TPMAINP
         Current job ID: A0000003
         Local LU name: M09AP001
         Partner LU name: M09AP001
         User ID from FMH5: IBMUSER

       Total number of active waiting MULTI_TRANS initiators:        2

         Address space ID (ASID): '0017'X
         TP name: TPMAINM

         Address space ID (ASID): '0019'X
         TP name: TPMAINM

       Total number of idle initiators:        1
         Address space ID (ASID): '001A'X

The report for the ASCHDATA DETAIL subcommand duplicates everything in the summary report plus the following:

Job ID
Local LU Name
Partner LU Name
TP Name
User ID from FMH5
Time Job Started Wait
Address Space ID
TP Start Time
Current Job ID

Job ID: The job ID is the identifier of a job processing on the APPC/MVS transaction scheduler queue. Additional information about the job follows the job identifier, such as the local LU name associated with the job, the TP name of the TP that came as an inbound FMH-5 attach request, and the time the job began to wait on the scheduler queue.
Local LU Name: An LU is a system interface to a SNA network. A local LU is an LU on your system through which a local TP communicates. The LUs for partner TPs are called partner LUs. Sessions, which allow program-to-program communication, are established between a local LU and partner LUs.
Partner LU Name: An LU is a system interface to a SNA network. An LU on your system, through which a local TP communicates, is a local LU. The LUs for partner TPs are partner LUs. Sessions, which allow program-to-program communication, are established between a local LU and partner LUs. A partner LU can be on the same system as the local LU or on a remote system. 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.
TP Name: A TP is part of a cooperative application that communicates with another part, which is also a TP. The communication between TPs is started by an allocate callable service that becomes an FMH-5 attach request. When the scheduler receives an FMH-5 attach request, it gives the request a job ID and puts it on a queue for the appropriate class. The names of the TPs that are associated with inbound FMH-5 attach requests are the names that appear in this report.
User ID from FMH5: The user ID from FMH5 is the ID that was passed into MVS/APPC with the allocate request. The ID is associated with the security environment in which the TP will run.
Time Job Started Wait: The time the job started to wait is the time that the job was put on the APPC scheduler queue. The date and time are displayed in the format mm⁄dd⁄yyyy hour:minutes:seconds:microseconds.
Address Space ID: The address space ID is the 4 digit hexadecimal identifier of the address space for an initiator. The identifier is expressed as four hexadecimal digits. At the time of the dump, the initiator could have been active on a particular job or could have completed a job and be idle.
TP Start Time: The TP start time is the time the job started for the TP. The date and time are displayed in the format mm⁄dd⁄yyyy hour:minutes:seconds:microseconds.
Current Job ID: The current job ID is the identifier for a job that was running at the time the dump was taken.