FMH5MANAGER DETAIL report

The detail report for the FMH-5 manager duplicates everything in the summary report. Also, the report lists, for both active and outstanding FMH-5 requests, the LU names and the total number of requests they received. For each LU name, the requests are then 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.

The topics include:

Figure 1 shows an example of the APPCDATA FMH5MANAGER DETAIL report.

Figure 1. Example: APPCDATA FMH5MANAGER DETAIL report
  Detail Report for FMH-5 MANAGER
  -------------------------------

  FMH-5 requests outstanding

    Local LU name: M04AP001    Total requests for this local LU:     5
     Partner LU name: M04AP001    Number of requests:     5

  FMH-5 requests being processed

    Local LU name: M04AP001    Total requests for this local LU:     6
     Partner LU name: M04AP001    Number of requests:     6
      FMH-5 Request data
       120502FF  0003D000  0007D4E3  D9C1D5E2  | ......}...MTRANS |
       E700                                    | X.               |
      FMH-5 Request data
       120502FF  0003D000  0007D4E3  D9C1D5E2  | ......}...MTRANS |
       E700                                    | X.               |
      FMH-5 Request data
       120502FF  0003D000  0007D4E3  D9C1D5E2  | ......}...MTRANS |
       E700                                    | X.               |
      FMH-5 Request data
       120502FF  0003D000  0007D4E3  D9C1D5E2  | ......}...MTRANS |
       E700                                    | X.               |
      FMH-5 Request data
       120502FF  0003D000  0007D4E3  D9C1D5E2  | ......}...MTRANS |
       E700                                    | X.               |
      FMH-5 Request data
       120502FF  0003D000  0007D4E3  D9C1D5E2  | ......}...MTRANS |
       E700                                    | X.               |
Information displayed in this report includes:
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. After sessions are established, each local LU can receive incoming FMH-5 attach requests. The attach requests are allocate calls from TPs that are seeking to start conversations with TPs defined to the local LU.
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. After sessions are established, LUs can send and receive FMH-5 attach requests. The attach requests are allocate calls from TPs that are seeking to start conversations with TPs defined to LUs on your 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.

Number of FMH-5 Requests Not Yet Received
Before an FMH-5 attach request can be processed, it must be received. Once a request is received, it is available as dump data. When one or more FMH-5 requests are in the process of being received, this heading appears in the report. Otherwise, this heading does not appear.
FMH-5 Request Data
After an FMH-5 request is received, it is available as dump data, which is displayed under this heading.
Parent topic: APPCDATA FMH5MANAGER subcommand output