Examples Using the DISPLAY Command

The following examples illustrate the results of DISPLAY APPC commands with various keywords and filters.

DISPLAY APPC,LU

To show the current configuration of APPC/MVS LUs, enter the following command on one system:

  D APPC,LU,ALL

This command produces output like the following:

Figure 1. Sample DISPLAY Output for System SY1 on Network USIBMY0

   ATB121I  15.55.45  APPC DISPLAY      FRAME  1     F      E   SYS=SY1
     ACTIVE LU'S    OUTBOUND LU'S    PENDING LU'S    TERMINATING LU'S
        00008           00000           00000             00000
     SIDEINFO=SYS1.APPCSI
   LLUN=Z098AP01          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00001      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=MVSLU1       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
    PLUN=USIBMY0.MVSLU1
   LLUN=Z098AP02          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00000      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=*NONE*       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
   LLUN=Z096AP02          SCHED=*NONE*        BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00001      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=*NONE*       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
    PLUN=USIBMZ0.MVSLU4
   LLUN=Z096AP03          SCHED=ASCH          BASE=YES         NQN=YES
      STATUS=ACTIVE       PARTNERS=00003      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=MVSLU1       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
    PLUN=USIBMY0.MVSLU
    PLUN=USIBMZ0.MVSLU
    PLUN=USIBMZ0.MVSLU4
   LLUN=Z098AP04          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00000      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=*NONE*       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
   LLUN=Z096AP04          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00001      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=MVSLU        RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
    PLUN=USIBMY0.MVSLU1
   LLUN=Z0A4AP03          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00001      TPLEVEL=SYSTEM   SYNCPT=YES
      GRNAME=*NONE*       RMNAME=ATB.USIBMY0.Z0A4AP03.IBM
      TPDATA=SYS1.APPCTP
    PLUN=USIBMY0.Z0A4AP04
   LLUN=Z0A4AP04          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00002      TPLEVEL=SYSTEM   SYNCPT=YES
      GRNAME=*NONE*       RMNAME=ATB.USIBMY0.Z0A4AP04.IBM
      TPDATA=SYS1.APPCTP
    PLUN=USIBMX0.Z0B4AP01
    PLUN=USIBMX0.Z0B4AP04

According to the output:

The last two LUs are capable of handling protected conversations, as illustrated by the display field SYNCPT=YES. These LUs are registered with RRS as resource managers, with the resource manager names shown in the RMNAME field. You can use these RMNAME values on the RRS ISPF panel interface when you want to:
- Obtain the resource manager token and state.
- Obtain a list of units of recovery (URs) for the resource manager. (An alternative method of obtaining UR information is using the DISPLAY APPC,UR command with LLUN as a filter keyword.)
- Remove a resource manager's expression of interest in a UR.
Two LUs, the first and fourth, are members of the same VTAM® generic resource group named MVSLU1.
The fourth LU, Z096AP03, has partners that are also members of different generic resource groups. As shown by their network-qualified names, some of those partners reside on another system, USIBMZ0.

To display information about the partners on the USIBMZ0 system, issue the same command on USIBMZ0:

  D APPC,LU,ALL

This command produces output like the following:

Figure 2. Sample DISPLAY Output for System SY2 on Network USIBMZ0

   ATB121I  15.48.39  APPC DISPLAY      FRAME  1     F      E   SYS=SY2
     ACTIVE LU'S    OUTBOUND LU'S    PENDING LU'S    TERMINATING LU'S
        00003           00000           00000             00000
     SIDEINFO=SYS1.APPCSI
   LLUN=Z098AP01          SCHED=ASCH          BASE=NO          NQN=YES
      STATUS=ACTIVE       PARTNERS=00000      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=*NONE*       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
   LLUN=Z098AP02          SCHED=ASCH          BASE=YES         NQN=NO
      STATUS=ACTIVE       PARTNERS=00001      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=MVSLU        RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
    PLUN=USIBMY0.MVSLU1
   LLUN=Z098AP04          SCHED=ASCH          BASE=NO          NQN=NO
      STATUS=ACTIVE       PARTNERS=00002      TPLEVEL=SYSTEM   SYNCPT=NO
      GRNAME=MVSLU4       RMNAME=*NONE*
      TPDATA=SYS1.APPCTP
    PLUN=USIBMY0.MVSLU1
    PLUN=USIBMY0.Z096AP02

According to this output, LUs on the two systems share the same TP profile and side information data sets. Some restrictions apply to sharing these data sets among systems; see Restrictions on Invoking the APPC/MVS Administration Utility in Using the APPC/MVS Administration Utility for further details.

DISPLAY APPC,TP

To investigate existing APPC/MVS work, you can issue the DISPLAY APPC command to see all TPs currently executing or awaiting execution.

   DISPLAY APPC,TP,ALL

This command produces output like the following:

Figure 3. Sample DISPLAY Output

  D APPC,TP,ALL
  ATB122I  19.26.54  APPC DISPLAY 422
    LOCAL TP'S      INBOUND CONVERSATIONS      OUTBOUND CONVERSATIONS
      00003                 00002                      00002
  LTPN=*UNKNOWN*
     LLUN=Z0A4AP03   WUID=*UNKNOWN*    CONVERSATIONS=00001   ASID=0016
     SCHED=*NONE*    ASNAME=DBUTLERA   TPID=0622891000000002
   PTPN=TBDRIVER
     PLUN=USIBMZ0.MVSLU4
     PROTECTED=YES   USERID=DBUTLER    DIRECTION=OUTBOUND
     VERBS=00000006  IT=040.662S
     MODE=TRANPAR    VTAMCID=01000005  SYNC POINT IN PROG=YES
     LUWID=USIBMY0.Z0A4AP03 4AAE3101D784 0001
  LTPN=TBDRIVER
     LLUN=Z0A4AP04   WUID=A0000001     CONVERSATIONS=00002   ASID=0022
     SCHED=ASCH      ASNAME=VSTEST     TPID=06228A7000000004
   PTPN=*UNKNOWN*
     PLUN=USIBMZ0.Z0A4AP03
     PROTECTED=YES   USERID=DBUTLER    DIRECTION=INBOUND
     VERBS=00000003  IT=*NONE*
     MODE=TRANPAR    VTAMCID=01000006  SYNC POINT IN PROG=NO
     LUWID=USIBMY0.Z0A4AP03 4AAE3101D784 0001
   PTPN=TBDRIVER
     PLUN=USIBMZ0.MVSLU3
     PROTECTED=YES   USERID=*NONE*     DIRECTION=OUTBOUND
     VERBS=00000003  IT=*NONE*
     MODE=TRANPAR    VTAMCID=0100000B  SYNC POINT IN PROG=NO
     LUWID=USIBMZ0.Z0A4AP03 4AAE3101D784 0001
  LTPN=TBDRIVER
     LLUN=Z0A4AP03   WUID=A0000002     CONVERSATIONS=00001   ASID=0041
     SCHED=ASCH      ASNAME=VSTEST     TPID=06228BD000000006
   PTPN=*UNKNOWN*
     PLUN=USIBMZ0.MVSLU4
     PROTECTED=YES   USERID=*NONE*     DIRECTION=INBOUND
     VERBS=00000002  IT=*NONE*
     MODE=TRANPAR    VTAMCID=0100000C  SYNC POINT IN PROG=NO
     LUWID=USIBMY0.Z0A4AP03 4AAE3101D784 0001

According to the output:

All of the TPs have protected conversations with their partner TPs.
For one outbound conversation, a syncpoint operation (either Commit or Backout) is in progress.

DISPLAY APPC,UR

To determine whether any APPC/MVS protected conversations require or are undergoing resynchronization processing, enter the following command:

  D APPC,UR,ALL

This command produces output like the following:

Figure 4. Sample DISPLAY Output

ATB104I  19.33.55  APPC DISPLAY 431
  APPC UR'S                 EXPRESSIONS OF INTEREST
    00003                            00004
URID=AC964AAE7F36A0000000000101010000
   EXPRESSION OF INTEREST COUNT=00001          SYNC POINT IN PROG=YES
   LUWID=USIBMZ0.Z0A4AP03 4AAE3101D784 0001
 LTPN=*UNKNOWN*
 PTPN=TBDRIVER
   CONV CORRELATOR=062313F800000001
   PLUN=USIBMZ0.MVSLU4      LLUN=Z0A4AP03      DIRECTION=OUTBOUND
   RESYNC REQUIRED=NO       IMPLIED FORGET=NO
URID=AC964ABD7F36A2280000000201010000
   EXPRESSION OF INTEREST COUNT=00002          SYNC POINT IN PROG=NO
   LUWID=USIBMZ0.Z0A4AP03 4AAE3101D784 0001
 LTPN=TBDRIVER
 PTPN=TBDRIVER
   CONV CORRELATOR=06231CC800000005
   PLUN=USIBMZ0.MVSLU3      LLUN=Z0A4AP04      DIRECTION=OUTBOUND
   RESYNC REQUIRED=NO       IMPLIED FORGET=NO
 LTPN=TBDRIVER
 PTPN=*UNKNOWN*
   CONV CORRELATOR=062313F800000001
   PLUN=USIBMZ0.Z0A4AP03    LLUN=Z0A4AP04      DIRECTION=INBOUND
   RESYNC REQUIRED=NO       IMPLIED FORGET=NO
URID=AC964AD07F36A4500000000301010000
   EXPRESSION OF INTEREST COUNT=00001          SYNC POINT IN PROG=NO
   LUWID=USIBMZ0.Z0A4AP03 4AAE3101D784 0001
 LTPN=TBDRIVER
 PTPN=*UNKNOWN*
   CONV CORRELATOR=06231CC800000005
   PLUN=USIBMZ0.MVSLU4      LLUN=Z0A4AP03      DIRECTION=INBOUND
   RESYNC REQUIRED=NO       IMPLIED FORGET=NO

According to the output:

The first unit of recovery, which represents the outbound conversation that appears in DISPLAY APPC,TP, does not require resynchronization processing.
The URID and logical work unit identifier (LUWID) values can serve as input for the RRS ISPF panel interface.

DISPLAY APPC,SERVER

To investigate APPC work processed by APPC/MVS servers, enter the following command:

   DISPLAY APPC,SERVER,ALL

This command produces output like the following:

Figure 5. Sample DISPLAY Output

ATB100I  14.27.48  APPC DISPLAY      FRAME LAST   F      E   SYS=MVS520
  ALLOCATE QUEUES               SERVERS               QUEUED ALLOCATES
       00002                     00002                     00000
STPN=LOOKUP
   LLUN=Z01BAP03       PLUN=*                      USERID=*
   PROFILE=*           REGTIME=12/07/1995 19:05:56 QUEUED=00000
   OLDEST=*NONE*       LAST RCVD=00.21.02          TOT ALLOCS=00000001
   SERVERS=00001       KEEP TIME=0000              TIME LEFT=*N/A*
 ASNAME=RMILLER1
   ASID=001C           REGTIME=12/07/1995 19:05:56 TOT RCVD=00000001
   RCVA ISS=19:05:56   RCVA RET=19:06:46
STPN=UPDATE
   LLUN=Z01BAP03       PLUN=*                      USERID=*
   PROFILE=*           REGTIME=12/07/1995 19:04:25 QUEUED=00000
   OLDEST=*NONE*       LAST RCVD=*NONE*            TOT ALLOCS=00000000
   SERVERS=00001       KEEP TIME=0000              TIME LEFT=*N/A*
 ASNAME=RMILLER2
   ASID=000F           REGTIME=12/07/1995 19:04:25 TOT RCVD=00000000
   RCVA ISS=19:04:25   RCVA RET=19:04:25

According to the output, two APPC/MVS servers (shown by ASNAME) are running on the system: RMILLER1 and RMILLER2.

For RMILLER1, the output shows that the server:

Has registered to serve allocate requests from the LOOKUP TP (shown by STPN=) that arrive on LU Z01BAP03.
Has received 1 allocate request.

For RMILLER2, the output shows that the server:

Registered to serve allocate requests from the UPDATE TP that arrive on LU Z01BAP03.
Has not received any allocate requests for processing.

To view server processing from the perspective of the served TPs, enter the following command:

   DISPLAY APPC,TP,ALL

This command produces output like the following:

Figure 6. Sample DISPLAY Output

ATB122I  14.26.53  APPC DISPLAY
  LOCAL TP'S      INBOUND CONVERSATIONS      OUTBOUND CONVERSATIONS
    00003                 00001                      00001
LTPN=UPDATE
   LLUN=Z01BAP03   WUID=*UNKNOWN*    CONVERSATIONS=00000   ASID=000F
   SCHED=*NONE*    ASNAME=RMILLER2   TPID=034ECC2800000001
STPN=LOOKUP
   LLUN=Z01BAP03   WUID=*UNKNOWN*    CONVERSATIONS=00001   ASID=001C
   SCHED=*NONE*    ASNAME=RMILLER1
 PTPN=*UNKNOWN*
   PLUN=USIBMZ0.Z01BAP01
   PROTECTED=NO    USERID=*NONE*     DIRECTION=INBOUND
   VERBS=00000001  IT=*NONE*         LCID=034E2330
   MODE=TRANPAR    VTAMCID=*NONE*    SYNC POINT IN PROG=NO
   LUWID=*NONE*

Note that the TP ID field does not appear in the D APPC,TP,ALL output for RMILLER1 because RMILLER1 has received an inbound request. The TP ID appears for the server in address space RMILLER2 because it is not currently processing any allocate requests. Also, the TP running in address space RMILLER2 is also listed in the LTPN= field.