Compaq AAR-88LB-TE manual Monitoring, User Parsing of Monitor Output, User Customized Monitors

Page 27
5.5 Monitoring

 

System Management

 

5.5 Monitoring

Table 5–3 New RTR Version 3 Monitor Pictures

 

 

 

Picture

Description

 

 

 

accfail

Shows most recent links on which a connection attempt was declined.

acp2app

Shows RTRACP-to-application message counts.

app2acp

Shows application-to-RTRACP message counts.

broadcast

Shows information about RTR user events by process.

connect

Renamed to netstat.

connects

Shows connection status summary.

dtx

Shows distributed transaction calls status.

dtxrec

Shows distributed transaction recovery status and journal states.

event

Shows event routing data by facility.

frontend

Shows frontend status and counts by node and facility, including frontend state,

 

current router, reject status, retry count, and quorum rejects.

group

Shows server and transaction concurrency by partition.

ipc

Shows interprocess communication counts for messages and connects.

jcalls

Displays counts of successful (success), failed (fail), and total journal calls for local

 

and remote journals.

netstat

Shows link counters relating to connection management, with link state and

 

architecture of remote nodes.

rdm

Shows memory used by each RTR subsystem.

rejects

Displays the last rtr_mt_rejected message received by each running process.

rejhist

Displays the last ten rtr_mt_rejected messages received by each running

 

process.

response

Displays the elapsed time that a transaction has been active on the opened channels

 

of a process.

rfb

Displays router failback operations, both a summary and detail by facility.

routing

Displays statistics of transaction and broadcast traffic by facility.

rscbe

Displays the most recent calls history for the RSC subsystem on a backend node.

system

Displays high level summary of critical monitor pictures.

tpslo

Shows transaction commits by process.

trans

Displays transactions by frontend, facility, and user for each frontend, router, and

 

backend.

V2calls

Shows RTR Version 2 system service calls.

XA1

Displays status of XA interface activities.

1UNIX and NT only

5.5.3 User Parsing of Monitor Output

Because of changes to many monitor screens with RTR Version 3, user scripts that parse monitor output may need to be reviewed and changed.

5.5.4 User Customized Monitors

User monitors customized for use with RTR Version 2 may or may not work with RTR Version 3. DIGITAL recommends that user-customized monitors be tested with RTR Version 3 before being put into production.

System Management 5–3

Image 27
Contents Compaq Computer Corporation Houston, Texas Reliable Transaction Router Migration GuideJune Operating SystemFirst Printing, December Revised, June Preface ContentsInstallation Network IssuesPerformance Tips 8 Problem Diagnosis and ReportingSystem Management 6 Running Version 2 ApplicationsIndex Tables Page Preface AudienceOrganization of This Guide Related Documents Readers CommentsConventions monospace Page Introduction 1.1 Why Migrate?Introduction 1.1 Why Migrate? 1.2 Goals and Nongoals1.3 Reading Guidelines 2.1 Cleaning Up the Old Version 2 Environment Installation2.5 Process Quotas Installation 2.2 Preserving the Old Environment2.2 Preserving the Old Environment 2.3 Can Both RTR Version 2 and Version 3 Coexist On the Same Node?2.6 Journal Issues Installation 2.5 Process QuotasTable 2-1 OpenVMS Limits 2.6.2 Journal Compatibility Installation 2.6 Journal Issues 2.6.1 Removing the Old Journal2.7 Rights and Privileges 2.8 Memory and Disk RequirementsTable 2-2 OpenVMS Disk Requirements 2.9 Rollback to RTR Version2.8 Memory and Disk Requirements DEASSIGN/SYSTEM/EXEC RTRSHRPage 3.3 The Shared Library LIBRTR.EXE 3.2 Command Server ProcessArchitectural Changes 3.1 RTR Daemon Process3.7 Counters 3.4 The ACP Process3.5 Interprocess Communication 3.6 Shared Memory Parameters3.8 Quorum Issues Architectural Changes 3.8 Quorum Issues3.9 Server-Process Partition States Page Network Issues 4.1 DECnet Support4.2 TCP/IP Support Network Issues 4.3 Specifying a Preferred Transport 4.3 Specifying a Preferred Transport4.3.1 Supported Products 5.3 Creating Facilities System Management5.1 OpenVMS Quotas 5.2 Startup5.5.1 RTR Version 2 Screens 5.4 Interoperability5.5 Monitoring System Management 5.4 InteroperabilityTable 5-3 New RTR Version 3 Monitor Pictures 5.5 Monitoring5.5.3 User Parsing of Monitor Output 5.5.4 User Customized Monitors5.11 Interpreting Output from SHOW Commands 5.6 Remote Command Support5.9 Using RTR Version 2 Command Procedures 5.10 Command Line Interface Support for RTR Version 2 APITable 5-5 Obsolete OpenVMS RTR Utility Commands 5.12 Comparing RTR Version 2 and Version 3 Utility CommandsSystem Management 5.11 Interpreting Output from SHOW Commands Table 5-4 Cont. Changed SHOW COMMANDSTable 5-6 Cont. New OpenVMS RTR Utility Commands 5.12 Comparing RTR Version 2 and Version 3 Utility Commands6.1 Comparison of OpenVMS API and Portable API Running Version 2 ApplicationsTable 6-1 OpenVMS API and Portable API Comparison 6.2 Recompiling and RelinkingRunning Version 2 Applications 6.1 Comparison of OpenVMS API and Portable API6.2.1 RTR Version 2 Applications Running on RTR Version Running Version 2 Applications 6.2 Recompiling and Relinking6.5 Support for $GETTXI 6.3 Running Applications Installed with Privileges6.3 Running Applications Installed with Privileges 6.4 Application Level InteroperabilityRunning Version 2 Applications 6.6 Threaded Applications 6.8 Current Issues6.6 Threaded Applications 6.7 DDTM SupportPage 7.3 RTR Startup Qualifiers Performance Tips7.1 Process Quotas 7.2 Journal SizingPerformance Tips 7.6 Simultaneous Multiprocessing 7.6 Simultaneous Multiprocessing8.3 Dump File Problem Diagnosis and Reporting8.2 RTRERROR.LOG File 8.1 RTR Operator Log4. Enter the OpenVMS ANALYZE/SYSTEM SET PROCESS RTRACP command 8.6 Contents of the RTR Journal FileProblem Diagnosis and Reporting 8.4 Producing and Directing a Trace 1. Enter the SHOW PROCESS RTRACP/CONTINUOUS OpenVMS commandIndex