HPlogo APPC Subsystem on MPE XL Node Manager's Guide: HP 3000 MPE/iX Computer Systems > Chapter 2 Interactive Control Operator Commands

APPCCONTROL PERFORMANCE

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

Displays session statistics and performance-related data, if the gathering of performance statistics has been enabled.

Syntax

APPCCONTROL PERF[ORMANCE]
                 [;STYPE=Session Type Name]
                [;SID=Session ID]

Parameters

Session Type Name

An active session type name. Performance statistics are displayed for all active sessions of the session type specified. The name you specify must be configured in the APPC subsystem configuration file. See Chapter 4 “APPC Subsystem Configuration” of this manual for more information on configuring session type names.

Default: All active session type names.

Session ID

The identification number of the session for which you are requesting performance data. You can obtain session ID numbers by issuing the APPCCONTROL STATUS command, described later in this chapter.

Description

This command displays session performance statistics for the session type or session specified. If no session type or session ID is specified, statistics will be displayed for all active sessions.

If APPC subsystem logging is configured (through the LOGGING branch of NMMGR), the same types of statistics that APPCCONTROL PERFORMANCE displays will be logged whenever an APPC session is brought down, locally or remotely.

NOTE: The APPCCONTROL PERFORMANCE command does not write performance data to the log file. If APPC subsystem logging is configured and performance statistics gathering is enabled, performance data is written to the log file whenever a session is brought down.

Executing the APPCCONTROL PERFORMANCE command will not interrupt the sessions for which statistics are being gathered.

The APPCCONTROL PERFORMANCE display pauses at the end of every screen of data. To see the next screen of data, press [RETURN].

NOTE: You must enable the gathering of performance statistics before issuing the APPCCONTROL PERFORMANCE command, or no statistics will be available for display.

To enable statistics gathering at startup, specify PERFON = YES in the APPCCONTROL START command, or set the PerformanceOn parameter of the APPCStart intrinsic to 1. To enable statistics gathering once the APPC subsystem is active, issue the APPCCONTROL PERFORMANCEON command.The APPCCONTROL START and APPCCONTROL PERFORMANCEON commands are described later in this chapter. The APPCStart intrinsic is described in Chapter 3 “Control Operator Intrinsics”

If you want to print the output from the APPCCONTROL PERFORMANCE command, you can redirect the output to a disk file and then print the file. Redirecting the output creates a temporary file, and you must save the file before you can print it. The following commands send the output from the APPCCONTROL PERFORMANCE command to the temporary file outfile and then save outfile to disk:

     :APPCCONTROL PERFORMANCE > outfile
     :SAVE outfile

Examples

In this example, the APPCCONTROL PERFORMANCE command was issued for the independent session type SESS1. Two sessions of session type SESS1 are active on the independent LU INDLU1.

:APPCCONTROL PERFORMANCE;STYPE=SESS1
 
   Current Time      : FRI, JUN 20, 1990,  4:36 AM
   Subsystem Started : FRI, JUN 20, 1990,  1:50 AM
   Duration          : 2 hours 46 minutes 39 seconds
   TPs Started per Subsystem          = 26
 
SESS1   , LU = INDLU1  , NODE = SNANODE , SID = 6612
 
   Session Started   : FRI, JUN 20, 1990,  3:37 AM
   Duration          : 59 minutes 2 seconds
   Bytes Sent                         = 0
   Bytes Received                     = 5
   RUs Sent                           = 0
   RUs Received                       = 1
   Negative Responses Sent            = 0
   Negative Responses Received        = 0
   Avg. Remote Response Time (msec)   = 0
   Avg. CONFIRM Time (msec)           = 0
   Conversations Started              = 0
   Avg. bytes per Conversation        = 0
   Avg. Conversation Time (sec)       = 0
 
SESS1   , LU = INDLU1  , NODE = SNANODE , SID = 7534
 
   Session Started   : FRI, JUN 20, 1990,  3:40 AM
   Duration          : 43 minutes 3 seconds
   Bytes Sent                         = 0
   Bytes Received                     = 34
   RUs Sent                           = 0
   RUs Received                       = 1
   Negative Responses Sent            = 0
   Negative Responses Received        = 0
   Avg. Remote Response Time (msec)   = 0
   Avg. CONFIRM Time (msec)           = 0
   Conversations Started              = 0
   Avg. bytes per Conversation        = 0
   Avg. Conversation Time (sec)       = 0

In this example, the APPCCONTROL PERFORMANCE command was issued for an individual active session (session ID 2298).

:APPCCONTROL PERFORMANCE;SID=2298
 
   Current Time      : FRI, JUN 20, 1990,  5:36 AM
   Subsystem Started : FRI, JUN 20, 1990,  1:50 AM
   Duration          : 2 hours 46 minutes 39 seconds
   TPs Started per Subsystem          = 26
 
SESS3   , LU = DEPLU8  , NODE = IBMNODE , SID = 2298
 
   Session Started   : FRI, JUN 20, 1990,  2:37 AM
   Duration          : 30 minutes 2 seconds
   Bytes Sent                         = 1011
   Bytes Received                     = 5
   RUs Sent                           = 5
   RUs Received                       = 1
   Negative Responses Sent            = 0
   Negative Responses Received        = 0
   Avg. Remote Response Time (msec)   = 0
   Avg. CONFIRM Time (msec)           = 0
   Conversations Started              = 0
   Avg. bytes per Conversation        = 0
   Avg. Conversation Time (sec)       = 0

Reading the Display

Each line of the APPCCONTROL PERFORMANCE display is described below:

Current Time

The time at which APPCCONTROL PERFORMANCE was issued.

Subsystem Started

The time at which APPCCONTROL START was issued.

Duration

The length of time the APPC subsystem has been active.

TPs Started per Subsystem

The number of transaction program processes started since APPCCONTROL START was issued.

Session Type Name, LU Name, Node Name, and Session ID

The session type name, local LU name, and SNA node name configured for this session type, and the session identification number being used for the session. A separate set of statistics will be seen for each active APPC session for which performance data is requested.

Session Started

The time at which the APPC session was activated.

Duration

The length of time the APPC session has been active.

Bytes Received

The total number of bytes received since session initiation.

Bytes Sent

The total number of bytes sent since session initiation.

RUs Sent

The total number of RUs sent since session initiation.

RUs Received

The total number RUs received since session initiation.

Negative Responses Sent

The total number of negative responses sent over this session since session initiation.

Negative Responses Received

The total number of negative responses received over this session since session initiation.

Avg. Remote Response Time (msec)

The average time, in milliseconds, that the remote system has taken to respond after the last message has been sent and the local system has prepared to receive messages from the remote system.

Avg. CONFIRM Time (msec)

The average time, in milliseconds, that the remote system has taken to send a CONFIRMED reply after a confirmation request has been issued.

Conversations Started

The total number of conversations initiated since session initiation.

Avg. Bytes per Conversation

The average number of bytes sent and received per conversation over this session.

Avg. Conversation Time (sec)

The average time, in seconds, that each conversation being conducted over this session has taken.

Feedback to webmaster