Reference Manual

UNISYS • A Series

System Softwa re

Support

Reference Manual

, I,

J

UNISYS • A Series

System Softwa re

Support

Reference Manual

Copyright © 1992 Unisys Corporation All Rights Reserved

Unisys is a registered trademark of Unisys Corporation.

Release Mark 4.0.0 Priced Item

July 1992

Printed in U S America 8600 0478-100

Any similarity or likeness of the names, places, and/or events with the names of any individual, living or otherwise, or that of any group or association, is purely coincidental and unintentional.

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages.

You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.

The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions.

RESTRICTED RIGHTS LEGEND. Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.227-7013 and FAR 52.227-14 for commercial computer software.

Correspondence regarding this publication may be forwarded using the Product Information card at the back of the manual, or may be addressed directly to Unisys, Technical Publications, 25725 Jeronimo Road, Mission Viejo, CA 92691-2792.

Page Status

Page Issue

iii through iv -110

v through vi -100

vii thro~gh viii -110

ix through xiii -100

xiv through xvi -110

xvii through xix -100

xx Blank r

xxi through xxii -100

xxiii through xxiv -110

1-1 through 1-9 -100

1-10 Blank

2-1 through 2-3 -100

2-4 Blank

3-1 through 3-10 -100

4-1 through 4-142 -100

5-:-1 th rough 5-3 -100

5-4 Blank

6-1 th rough 6-3 -100

6-4 Blank

7-1 through 7-2 -110

7-3 through 7-6 -100

7-7 -110

7-8 -100

7-9 -110

7-10 -100

7-11 through 7-16 -110

7-16Athrough7-16C -110

7-16D Blank

7-17 through 7-69 -100

7-70 Blank

8-1 through 8-7 -100

8-8 -110

8-9 th rough 8-53 -100

8-54 Blank

9-1 through 9-17 -100

9-18 Blank

10-1 -110

10-2 through 10-9 -100

10-10 Blank

11-1 through 11-2 -110

11-2A through 11-2B -110

11-3 through 11-13 -100

continued

86000478-110 iii

continued Page 11-14

12-1 through 12-2 12-3 through 12-6 12-7 through 12-8 12-9 through 12-13 12-14 through 12-32 12-33 through 12-36A 12-36B

12-37 through 12-70 12-71

12-72 through 12-268 12-269

12-270thfuugh 12-275 12-276

12-277 through 12-278 12-279 through 12-293 12-294 through 12-298 12-298A through 12-298C 12-2980

12-299 through 12-301 12-302 through 12-304 13-1 through 13-16 A-I th rough A-8 Glossary-1 through 13 Glossary-14

Bibliography-1 through 2 Index-1 through 16

Issue Blank -100' -110 -100 -110 -100 -110 Blank -100 -110 -100 -110

Deleted by -110 Blank

-110 -100 -110 -110 Blank -100 -110 -100 -100 -100 Blank -110 -110

Unisys uses an II-digit document numbering system. The suffix of the document number (1234 5678-xyz) indicates the document level. The first digit of the suffix (x) designates a revision level; the second digit (y) designates an update level. For example, the first release of a document has a suffix of -000. A suffix of -130 designates the third update to revision 1. The third digit (z) is used to indicate an errata for a particular level and is not reflected in the page status summary.

About This Manual

Purpose

Scope

This manual brings together a set of various software utilities that are used to monit01;

analyze, and control tre computer system.

The utilities described in this manual are for A Series systems. These utilities perform such functions as recording system events, testing or analyzing data communications (data comm) facilities, initiating and analyzing memory dumps, and managing system resources.

Information on memory dump procedures can be found in the A Series System Operations Guide.

Audience

This manual is a reference manual intended primarily for use by systems support personnel. It is also useful to operations personnel, programmers, and managers.

Prerequisites

The users of this manual should know the information in both the A Series System Operations Guide and the A Series System Administration Guide.

How to Use This Manual

The majority of the sections of this manual discuss system utilities used for system monitoring. Each section is named after the utility it documents. A tab marks the beginning of each section.

Unless stated otherwise, all books referred to are for U nisys A Series systems.

Appendix A describes how to use railroad syntax diagrams that appear in U nisys manuals.

86000478-100 v

Organization

This manual comprises the following sections and appendix. In addition, a glossary, a bibliography, and an index appear at the end of the manual.

Section 1. BARS

This section describes the BARS utility program, which is used to monitor the performance of the system by sampling various system utilization information.

Section 2. DCAUDITOR

This section describes the DCAUDITOR program that performs analysis of an NSPAUDIT file produced by the data comm subsystem procedures of the operating system.

Section 3 •. DCSTATUS

This section describes the DCSTATUS utility, which makes use of the

DCSYSTEMTABLES installation intrinsic to produce an analysis of the data comm tables maintained by the operating system and the network support processor (NSP) data comm subsystem.

Section 4. DUMPANALYZER

This section describes the DUMPANALYZER utility, which can be invoked with various options to analyze a memory dump.

Section 5. HARDCOPY and PRINTCOPY

This section describes the HARDCOPY and PRlNTCOPY utility programs, which provide a way to capture system input commands and system messages within a disk file and print the contents of that file.

Section 6. HDU System Balancing

This section describes the functions that are used to monitor and change system utilization for the A 12 and A 15 systems.

Section 7. LOGANALYZER

This section describes the LOGANALYZER utility program, which produces reports of SUMLOG entries based on specified parameters.

Section 8. LOGGER

This section describes the LOGGER utility program, which produces reports that aid in the analysis of system performance and utilization.

About This Manual

Section 9. Peripheral Test Driver (PTD)

This section describes the peripheral test driver (PTD) program that interprets op-codes that are found in test case S-code files created to test peripheral equipment on a system.

Section 10. REPORT_LOG_ENTRIES

This section describes the exported master control program (MCP) procedure

REPORT_LOG_ENTRIES, which DCALGOL programs can use to monitor the logging of selected types of log entries.

Section 11. STATUS_CHANGE_REQUEST

This section describes the exported MCP procedure STATUS_CHANGE_REQUEST, which DCALGOL programs can use to monitor changes in process status and system initialization status.

Section 12. SUMLOG

This section describes the system summary log file, SUMLOG, which is used on A Series systems to record information concerning jobs previously run, past operating system activity, and other related information concerning the past status of the machine environment.

Section 13. System Stability Reporting .

This section explains how to use the system stability reporting (SSR) interactive support tool (ISTUTILITY) to record information about system disruptions.

Appendix A. Understanding Railroad Diagrams

This appendix explains how to use the railroad syntax diagrams that appear in U nisys manuals.

Related Product Information

A Series System Administration Guide (8600 0437)

This guide provides the reader with information required to make decisions about system configuration; peripheral configuration, file management, resource use, and other matters related to system administration. This guide is written for users with some, little, or no A Series experience who are responsible for making decisions about system administration.

A Series System Commands Operations Reference Manual (8600 0395) This manual gives a complete description of the system commands used to control system resources and work flow. This manual is written for systems operators and administrators.

8600 0478-110 vii

A Series System Operations Guide (8600 0387)

This guide describes the basic concepts and procedures required· to operate Micro A through A 6 systems and, more generally, all A Series systems. This guide is written for A Series operators, especially those with little or no experience.

BNA Version 2 Network Encoded Messages Programming Reference Manual, Volumes 1 and 2 (3787 5127), (3787 7598), and (3787 7529)

This manual provides in reference format the encoded formats of BNA,

CP 2000/CPDLP/MACP100 SNA PUT2, CP 2000 SNA PUT5, NCF, OSI, and TCP/IP Operations Interface Messages (OIMs), depending on the version of BNA being documented. The part number for the 1.2 version of the manual is 3787 7529, the part number for the 3.0 version of the manual is 3787 5127, and the part number for the 3.1 version of the manual is 3787 7598.

Contents

About This Manual . . . v

Section 1. BARS

General Information . . . 1-1 BARS Commands. . . . 1-2 BYE Command. . . . . . . . . . . . . . . . . . . . . . . . . 1-2 CYCLE Command . . . . . . . . . . . . . . . . . . . 1-2 DISPLAY Command . . . 1-2 HELP Command. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 LOAD Command. . . . . . . . . . . . . . . . . . . . . 1-3 NEWDISPLAY Command. . . . . . . . . . . . . . . . . . . . . 1-4 PACK Command. . . . . . . . . . . . . . . . . . . . . . . 1-5 PERIOD Command . . . . . . . . . . . . . . . . . . . 1-5 SAVE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 WORDS Command. . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Keywords ... 1-6 MONITOR File Format ... 1-7 MONITOR Record 1 (Operational Information} . . . . . . 1-8 MONITOR Record 2 (Utilization Times and Counts

Information) . . . . . . . . . . . . . . . . . . . . . . 1-8 MONITOR Record 3 (Queue Information). . . . . . . . 1-9

Section 2. DCAUDITOR

DCAUDITOR RUN Statement

Options . ... . Sa m pie Report . . .

Section 3. DCSTATUS

2-1 2-1 2-2

Execution ... 3-1 CANDE DCSTATUS Command . . . . . . . . . . . . . . . . . 3-1 DIAGNOSTICMCS DP Command . . . 3-2 CANDE and WFL Run Statements. " . . . . . . . . 3-3 DCSTATUS Options ... 3-4

Section 4. DUMPANALYZER

General Information. . . . 4-1 DUMPANALYZER Files . . . . . . . . . . . . . . . 4-2 Saved Memory Du mps . . . 4-4 Compatibility of MCP Levels. . . . . . . . . . . . . . . . . . . 4-4

8600 0478 ... 100 Ix

Running DUMPANALYZER . . . 4-5 Remote Operation: . . . 4-5 ODT Operation .'. . . . 4-6 Batch Operation . . . 4-8 Analyzing Program Dumps ... 4-9 Input to DUMPANALYZER. . . . 4-10 Basic Constructs . . . 4-10 Simple Address.. . . . 4-10 Multiple Addresses . . . 4-13 Simple Value . . . 4-15 DUMPANALYZER Commands. . . . 4-18 ALLPORTS . . . 4-18 AREAS. . . . .. . . 4-18 ARRAYLIMIT ... 4-24 ASDNUMBER. . . . 4-24

ASDTABLEBASE... 4-26

ASN ... 4-26 BOXINFO . . . 4-26 BYE .... ",'. ~ . . . 4-28 CAND . . . .. . . 4-28 CB ... '... 4-28 CODEFI LE . . . 4-30 CODEINFO (HDU Systems) . . . 4-31 COREMAP . . . 4-31 DC ... . . . .. . . 4-32 DCTRACE ... 4-35 DEADLOCK. . . . 4-37 DEBUG ... '. . . . .. . . 4-38 DESCANAL ... 4-39 DISKFILE . . . 4-41 FIB. . . 4-41 FINDIOCB (EMS Systems) . . . 4-44 FINDSTACKS . . . 4-45 GC (EMS Systems) . . . 4-45 GRAPHS .. . . 4-48 HARDINFO (RMM Systems). . . . 4-48 HDR . . . .. . . 4-50 HEADING ... 4-52 HEAP ... 4-53 HEAPSTACK. . . . 4-58 HELP ... 4-60 10 .. . . .. . . .. . . 4-60 IOCB. . . .. . . .. . . 4-66 IOTABLE . . . 4-68 KEEP. . . . 4-68 LIB. . . 4-69 LlNKCHECK. . . . 4-71 LINKS. . . . 4-72 LOADXREF. . . . 4-75 LOCKS .,. . .. . . 4-76 MASK. . . . .. . . .. . . 4-78 MD . . . 4-80

Contents

MDCODE (HDU Systems) ... 4-80

MEM... 4-80

MESSAGES ... 4-81 MIX.. . . .. . .. . . . .. .. . . .. .. . 4-82 MODE.. . . .. . .. .. . . . .. . . .. . . . 4-82

MSCW... 4-86

NAMES. . . .. . .. .. . . . .. . . .. . . . 4-87 NSP ... 4-89 OLAYINFO . . . 4-91 OPT". . . . 4-91 PATHCNTRL (Selected EMS Systems) . . . 4-93 PATTERN. . . . 4-95 PC or PRI NTCODE . . . 4-96 PIB . . . 4-97 PORT. . . 4-99 PRINTARRAY ... 4-100 PRINTER. . . . .. 4-101 PRINTVAL . . . .. 4-102 PROC (EMS Systems) . . . .. 4-102 PROCS". . . . .. 4-102 PROCSTACKS ... ". . . . .. 4-102 PROGRAMDUMP . . . .. 4-102 PV. . . . .. 4-104 QUEUE . . . .. 4-105 READYQ ... 4-108 RECESS. . . . .. 4-108 RELEASE. . . . .. 4-108 RELX. . . . .. . . .. 4-109 REMOTE . . . .. 4-109 REPEAT. . . . .. 4-109 RESULTQ (EMS Systems) ... 4-110 RJ. . . . .. 4-112 SAVE. . . . .. 4-112 SEARCH ... 4-112 SHOW. . . . .. ... . . ... .. . . .. . .. 4-115 SIB. . . .. . . .. 4-115 STACK. . . . .. 4-115 STACKWINDOW . . . .. 4-123 STOP. . . . . .. . . .. 4-124 SUBPORT . . . .. 4-124 SUMMARY. . . . .. 4-127 SWAPANAL . . . .. 4-131 TAB.. . . .. . . ... . . .. 4-131 TCPINFO (RMM Systems) . . . .. 4-134 TERMINAL. . . . .. 4-136 TRACE ... '. . . . .. 4-137 USE. . . .. . . .. . . .. 4-140 WHERE. . . . .. 4-140

WHO... 4-140

Error Messages. . . . .. 4-141

86000478-100 xl

Section 5. HARDCOPY and PRINTCOPY

HARDCOPY . ... '.. . . .. . . 5-1 Running HARDCOPY ... '. . . . 5-2 Disk File Format. . . . 5-2 PRINTCOPY . ... ; . . . 5-2 Running PRINTCOPY . . . 5-3 Section 6. HDU System Balancing

Dynamic Variation of System-Balancing Parameters ... 6-1 INTERVAL Parameter .. . . 6-2 IOINTERRUPT Parameter. . . . 6-2 Implementation. . . . 6-2 System-Balancing Usage. . . . 6-3 Section 7. LOGANALYZER

Installing Related Libraries . . . 7-1 Analyzing Logs from Different Releases ... 7-1 Finding Missing Log Entries. . . . 7-2 Running LOGANALYZER . . . 7-2 Option List. . . . 7-3 LOGANALYZER Options .. '... . . . . 7-6 Selection Options . . . 7-6 Configuration and Maintenance Options. . . . 7-6 Data Comm Options. . . . 7-11 Diagnostics Options. . . . 7-11 Job, Task, and Session Options. . . . 7-13 Additional Selection Options. . . . 7-17 Output Options . . . .. . . . 7 -21 Examples. . . . 7-22 DLP Type Abbreviations .. . . 7-24 Output Illustrations. . . . 7-26 Section 8. LOGGER

LOGGER Operation. . . . 8-2 LOGGER Input . . ',' . . . 8-3 Input-Specification Commands. . . . 8-4 CORRECTION Command. . . . 8-4 MAXRECORDS Command . . . 8-5 OPTION Command . . . 8-5 SORT PARAMETERS Command . . . 8-7 STOP Command. . . . 8-8 USE Command. . . . 8-8 Report-Specification Commands. . . . 8-9 BREAK Command. . . . 8-10 END Command ... 8-11

Contents·

EXCLUDE Command. . . . . . . . . . . 8-11 HEADING Command. . . . . . . . . . . . . . . 8-12 INCLUDE Command . . . . . . . . . . . . . . . 8-13 OUTPUT Command . . . 8-14 PAGE SIZE Command. . . . . . . . . . . . . . . 8-15 REPORT Command. . . . . . . . . . . . . . . . . . 8-15 REPORTS Command. . . . . . . . . . . . . . . . . . . . 8-16 SORT Command. . . . . . . . . . . . . . . . . 8-16 SOURCE Command . . . 8-17 Report-Specification Command Examples . ... '. . . . 8-18 File Data Items ... 8-36 Long-Term Report Generation. . . . . . . . . . . . . . 8-42 Extended Time Period Reports . . . . . . . . . . . .. . . 8-42 Year-to-Date Totals Reports . . . 8-43 Year-to-Date File Updates . . . 8-44 Year-to-Date Totals File Format. . . . . . . . . . . 8-44 Program Operation Characteristics. . . . 8-45 REPORT Commands and LOGREPORTS File . . . . 8-45 Calculation of Charges. . . . . . . . . . . . . . . . 8-46 Corrections. . . . . . . . . . . . . . . . . . . . . . . . 8-47 Files and File Equation . . . 8-47

$NODUMP Compile-Time Option . . . . . . . . . . . . . . . 8-47 Program Information . . . . . . . . . . . . . . . . . . . . 8-48 Overall Organization .... . .. . . . . . . . . . . . . . 8-48 Structure of Program Files . . . . . . . . . . . . 8-48 Tables Used by the EDITOR Procedure . . . . . 8-49 Files Used by the Program. . . . . . . . . . . . . . . . . . . . 8-51

Section 9. Peripheral Test Driver (PTD)

PTD Statement ... 9-2 General Execution Syntax. . . . . . . . . . . . . . . . 9-2 ODT Execution Examples. . . . . . . . . . . . . . 9-3 ODT Initiation, Remote (Data Comm) Dialog Device

Examples. . . . . . . . . . . . . . . . . . . . . . . 9-3 Remote Execution Examples. . . . . . . . . . . . . . . . 9-3 PTO Directives. . . . .. . . 9-4 lOP PTO Directives. . . . . 9-7 Selecti ng Test Devices ... 9-9 Reserving a Unit and Selecting a Path to That Unit. . . 9-10 PACKSCANNER Tests (PTD/CONF/PS) .. ~ . . . . 9-11 BADDISK Tests (PTD/CONF/BD20X and

PTD/CONF/BD2X5) . . . '.' . 9-12 All Other Confidence Tests (such as

PTD/CONF/IVR and PTD/CONF/MT) . . . . . . . 9-12 All Maintenance Tests (such as PTD/MAINT/=). 9-13 EMS Path Selection Example 1 . . . . . . . . . 9-14 EMS Path Selection Example 2 . . . . . . . . . 9-14 LS Path Selection Example. . . . . . . . . . . . 9-15 PTD Operator Interruption . . . . . . . . . . . . . . . . 9-15 Test Case Example. . . . 9-16

86000478-100 xiii

Section 10. REPORT LOG ENTRIES

- -

User Program Requirements for REPORT_LOG_ENTRIES 10-1

Declaring the REPORT_LOG_ENTRIES Procedure. . . . 10-2

Selecting Log Entry Types. . . . 10-2

Using the Security Mask Field . . . 10-4

Allocating an Intercom Queue for REPORT_LOG_ENTRIES . . . . 10-4

Detecting Error Conditions for REPORT_LOG_ENTRIES . . . 10-5

Waiting for Log Entries. . . . 10-5

I nterpreting the Log Entries. . . . 10-6

REPORT_LOG_ENTRIES User Program Example ... 10-6

Section 11. STATUS_CHANGE_REQUEST

Us~r Program Requirements for STATUS_CHANGE_REQUEST ..

Declaring the STATUS_CHANGE_REQUEST Procedure . ... . Selecting Events for Notification ... . Allocating an Intercom Queue for STATUS CHANGE REQUEST.

Detecting Queue Allocation Errors for - -

STATUS_CHANGE_REQUEST ... . Waiting for Event Messages . ... . Interpreting the Event Messages ... . STATUS_CHANGE_REQUEST User Program Example . ... .

Section 12. SUMLOG

Understanding Log Releases . ... . Controlling Log Contents ... . Selecting the Entry Types to be Logged ... . Requesting Copies of Configuration Files ... . Using Anonymous Task and File Accounting ... . Defining Installation Log Entries ... . Using Log Analysis Utilities . ... . Using Standard Utilities ... . Customizing Log Analysis ... . Writing Log Analysis Programs ... . Understanding Log Structure ... . Understanding Log Entries and Physical Records Understanding the First Four Words ... . Understanding Variations from Chronological

Order ... . Understanding the LINK Words ... . Format of Standard LINK Words ... . Format of Hardware and Software

Configuration LINK Words ... . Format of I/O Exception LINK Words .... . Format of BNA and HLCN LINK Words .. . Format of Volume Directory LINK Words ..

Preparing for Log Entry Format Changes ... . Understanding Log Access Security ... .

11-2 11-2A 11-2B 11-3 11-4 11-4 11-4 11-11

12-1 12-1 12-2 12-3 12-3 12-4 12-6 12-6 12-7 12-8 12-8 12-9 12-9 12-11 12-11 12-12 12-12 12-13 12-13 12-14 12-14 12-14

Contents

Using the SDASUPPORT Library . . . . Understanding SDASUPPORT Filtering ... . Objects Exported by SDASUPPORT . . . . LOG ATIRI BUTE . . . . LOG CLOSE . . . . LOG GET . . . . LOG OPEN . . . . LOG READ . . . . LOG SEEK . . . . LOG SELECT . . . . LOG SKIP . . . . SDASUPPORT VERSION . . . . SDASUPPORT Usage Examples . . . . Log Entry Types . . .

Major Type = 0 Establish Identity Entry

(LOGMAJ -' DENTYTIV) . . . . Major Type

=

=

=

Major Type = 10 Date/fime Reset Entry

(LOGMAJDATETIMERESET) . . . . Major Type = 11 BNA Version 1 Entry (LOGMAJBNA) Major Type = 13 BNA Version 2 Entry (LOGMAJBNAE) Major Type = 14 MLS Message Entry (LOGMAJMLS) . Major Type = 15 Volume Status Entry (LOGMAJVOL) . Major Type = 16 File Status Entry (LOGMAJFILE) ...

Major Type = 17 DATA COMM Configuration Entry (LOGMAJ DCCONFIGV) . . . . Major Type;; 18 COMS Configuration Entry

(LOGMAJ COMSCONFIGV) . . . . Major Type;; 19 Diagnostics Entry

(LOGMAJ DIAGNOSTICS) ... . Major Type;; 25 Host LAN Connection

(LOGMAJ_HLCN) . . . . Major Type = 27 TCP/IP (LOGMAJ_ TCPIP) . . . . Major Type = 28 Network Management

(LOGMAJ NMS) . . . . Major Type;; 30 Systems Network Architecture

(LOGMAJ _ SNA) . . . .

Section 13. System Stability Reporting

12-15 12-15 12-16 . 12-16 12-17 12-17 12-18 12-18 12-19 12-19 12-22 12-23 12-23 12-26 12-37 12-39 12-71 12-175 12-176 12-185 12-190 12-205 12-206 12-208 12-277 12-278 12-279 12-285 12-287 12-289 12-294 12-299 12-302 12-303 12-304

Understanding the Stability Log. . . . 13-1 Structure and Capacity . . . 13-2 Where the Log Resides . . . . . . . . . . . . . . . . . . . . 13-2 Recording the Initial Halt/Load Description. . . . 13-3 Viewing and Commenting On Stability Data . . . 13-4 Installing ISTUTILITY . . . . . . . . . . . . . . . . . . . . . . . . 13-4

86000478-110 xv

I nstalling the Transfer Schedule Feature ... " ..

Initiating ISTUTILITY ... : ... . Using ISTUTILITY Screens ... . Using the Main Menu Screen ... . Reviewing and Entering Halt Data ... . Selecting Criteria for Halt Record Display ... . Reviewing the Halt Records ... . Reviewing and Entering the Halt Evaluation Data Entering Halt Comments ... . Viewing Internal Failure Summaries ... . Reviewing and Entering Daily Comments ... . Configuring the Halt Review Criteria ... . Initiating and Scheduling Data Transfers ... .

Appendix A. Understanding Railroad Diagrams

13-4 13-6 13-6 13-7 13-8 13-8 13-9 13-10 13-11 13-11 13-13 13-14 13-14

What Are Railroad Diagrams? . . . A-I Constants and Variables. . . . A-2 Constraints. . . . A-2 Following the Paths of a Railroad Diagram . . . A-5 Railroad Diagram Examples with Sample Input. . . . A-6

Glossary. . . . 1

Bibliography. . . . 1

Index. . . . 1

Figures

2-1.

3-1.

3-2.

3-3.

3-4.

4-1.

4-2.

4-3.

4-4.

4-5.

4-6.

4-7.

4-8.

4-9.

4-10.

4-11.

4-12.

4-13.

4-14.

4-15.

4-16.

4-17.

4-18.

4-19.

4-20.

4-21.

4-22.

4-23.

4-24.

4-25.

4-26.

4-27.

4-28.

4-29.

4-30.

4-31.

4-32.

7-1.

7-2.

7-3.

7-4.

7-5.

7-6.

86000478 .... 100

DCCONTROl Option Output ... . NETWORK Option Output ... . GRAPH Option Output ... . TERMINAL Option Output ... . STATION Option Output ... . AREAS Command Output ... . BOXINFO Command Output ... . CB Command Output ... . DC Command Output ... . DCTRACE Command Output ... . DESCANAl Command Output ... . FIB Command Output ... . HARDINFO Command Output ... . HDR Command Output ... . Heap Analysis Examples ... . 10 Command Output ... . 10 Command Output With NAMES Option ... . IOCB Command Output ... . LINKS Command Output: In-Use Area ... . LINKS Command Output: Available Area ... . lOCKS Command Output ... . Mask Word Example ... . NAMES Command Output ... . NSP Command Output ... . OPT Command Output ... . PATHCNTRl Command Output ... . Pattern Word Example ... . PIB Command Output ... . QUEUE Command Output ... . RESUlTQ Command Output ... . STACK Command Output: Process Stack ... . STACK Command Output: PIB ... . STACK Command Output: TAB ... . STACKWINDOW ... . TAB Command Output. ... . TCPINFO Command Output ... . TRACE Command Output ... . DATE Option Output ... . All Option Output ... . RAW Option Output ... . CONFIG Option Output ... . CONFIG Option Output (A 10 Systems) Record ... . FASUMMARY Option Output ... .

2-3 3-7 3-8 3-9 3-10 4-23 4-27 4-29 4-34 4-36 4-40 4-43 4-49 4-51 4-56 4-64 4-65 4-67 4-73 4-74 4-77 4-79 4-88 4-90 4-92 4-94 4-95 4-98 4-107 4-111 4-120 4-121 4-122 4-124 4-133 4-135 4-139 7-27 7-28 7-29 7-30 7-31 7-32

xvii

7-7.

7-8.

7-9.

7-10.

7-1 I.

7-12.

7-13.

7-14.

7-15.

7-16.

7-17.

7-18.

7-19.

7-20.

7-21.

7-22.

7-23.

7-24.

7-25.

7-26.

7-27.

7-28.

7-29.

7-30.

7-31.

7-32.

7-33.

7-34.

7-35.

7-36.

7-37.

7-38.

7-39.

7-40.

7-41.

7-42.

7-43.

8-I.

8-2.

8-3.

8-4.

8-5.

8-6.

8-7.

8-8.

8-9.

8-10.

8-1I.

8-12.

8-13.

8-14.

HL Option Output ... . IOSUMMARY Option Output ... . MAINFRAME Option Output ... . IOERROR Option Output (EMS Systems) ... . IOERROR Option Output (HDU Systems) ... . MAl NT Option Output (EMS Systems) ... . MAINT Option Output (HDU Systems) ... . MAINT CPU Option Output (A 10 Systems) ... .

<device option> Output ... ~ ... . BNA Version 1 Option Output ... . BNA Version 2 Option Output ... . MCS Option Output ... . NSP Option Output ... . DIAGNOSTICS (DSS) Option Output ... . DIAGNOSTICS (MHS) Option Output ... . DIAGNOSTICS (NIS) Option Output. ... . ABORT Option Output ... . BOJ Option Output ... . BOT Option Output ... . DMS Option Output ... . EOJ Option Output ... . EOT Option Output ... . ERRORS Option Output ... . FI LE Option Output ... . JOB Option Output ... . LIB Option Output ... . MIX Option Output ... . SESSION Option Output ... . TASK Option Output ... . COMMENT Option Output ... . DEIMPLEMENTATION Option Output ... . MSG Option Output ... . OPERATOR Option Output ... . SECU RITY Option Output ... . DUMP Option Output ... ; ... . UNSORTED Option Output ... . SORTED Option Output ... . LOGGER Example 1 Output ... . LOGGER Example 2 Output ... . LOGGER Example 3 Output ... . LOGGER Example 4 Output ... . LOGGER Example 5 Output ... . LOGGER Example 6 Output ... . LOGGER Example 7 Output ... . LOGGER Example 8 Output ... . LOGGER Example 9 Output ... . Year-to-Date Record 1 Format ... . Year-to-Date Record 2 Format ... . Year-to-Date Record 3 Format ... . BREAKINFO Table ... . EDITORINFO Table ... .

7-33 7-34 7-35 7-36 7-37 7-38 7-39 7-40 7-41 7-42 7-43 7-44 7-45 7-46 7-47 7-48 7-49 7-50 7-51 7-52 7-53 7-54 7-55 7-56 7-57 7-58 7-59 7-60 7-61 7-62 7-63 7-64 7-65 7-66 7-67 7-68 7-69 8-19 8-21 8-23 8-25 8-27 8-29 8-31 8-33 8-35 8-44 8-45 8-45 8-50 8-50

Figures

8-15. INCLCHECK and EXCLCHECK Tables . . . 8-51 8-16. TAITEMS Table. . . . 8-51 12-1. DLP Result Format for lOP I/O Errors. . . . .. 12-101 12-2. DLP Result Format for Error 10CBs . . . .. 12-168 13-1.

13-2.

13-3.

13-4.

13-5.

13-6.

A-I.

86000478 ... 100

Main Menu ... . Review Halt Data Screen ... . View Summary Data Screen ... . Review Daily Comments Screen ... . Collection Configuration Screen ... . Transfer Schedule Screen ... . Railroad Constraints ... .

13-6 13-8 13-12 13-13 13-14 13-15 A-5

)(IX

Tables

7-1.

7-2.

7-3.

8-1.

8-2.

8-3.

8-4.

8-5.

10-1.

10-2.

10-3.

11-1.

11-2.

11-3.

11-4.

12-1.

12-2.

12-3.

12-4.

12-5.

12-6.

12-7.

12-8.

12-9.

12-10.

12-11.

12-12.

12-13.

12-14.

12-15.

12-16.

12-17.

12-18.

12-19.

12-20.

12-21.

12-22.

12-23.

12-24.

12-25.

12-26.

12-27.

86000478-100

DIAGNOSTICS Examples . . . . LOGANALYZER Examples . . . . DLP Abbreviations . . . . JOBSUMMARY File Data Items . . . . STATISTICS File Data Items . . . . FILEIODATA File Data Items . . . . DRCDATA File Data Items . . . . Files Used by LOGGER . . . . INFO Parameter Format . . . . VAL Parameter Security Field . . . . Q Parameter Log Entry Format . . . . Event Types . . . . Event Message Basic Format . . . . Event Message Variable Formats . . . . SERIAL Word Format . . . . Events Logged by MCP _ LOGG ER . . . . First Four Log Entry Words . . . . Link to Variable Items . . . . I/O Exception LINK Word -Format . . . . Log Entry Classes . . . . . . . . . Major Type O-Minor Type 1 . . . . Major Type O-Minor Type 2 . . . . Major Type I-Minor Types 1 and 3 . . . . Major Type I-Minor Types 2 and 4 . . . . Major Type I-Minor Type 5 . . . . Major Type I-Minor Type 6 . . . . Major Type I-Minor Type 7 . . . . Major Type I-Minor Type 8 . . . . Major Type I-Minor Type 9 . . . . Major Type I-Minor Type 10 . . . . Major Type I-Minor Types 11 through 14 . . . . Major Type I-Minor Types 15 and 16 . . . . Major Type I-Minor Types 17 and 18 . . . . Major Type I-Minor Types 19 and 20 . . . . Major Type I-Minor Types 21 and 22 . . . . Major Type I-Minor Type 25 . . . . Peripheral Logical Types . . . . Peripheral Subtypes . . . . Peripheral Densities . . . . Peripheral DLP Types . . . . Major Type 2-Minor Type 11 . . . . Major Type 2-Minor Type 12 . . . .

7-13 7-23 7-24 8-36 8-38 8-39 8-41 8-52 10-3 10-4 10-6 11-2 11-4 11-6 11-10 12-5 12-10 12-12 12-13 12-26 12-37 12-38 12-39 12-43 12-49 12-53 12-59 12-61 12-61 12-62 12-62 12-65 12-66 12-68 12-69 12-70 12-71 12-72 12-75 12-75 12-77 12-78

xxi

12-28.

12-29.

12-30.

12-3l.

12-32.

12-33.

12-34.

12-35.

12-36.

12-37.

. 12-38.

12-39.

12-40.

12-41.

12-42.

12-43.

12-44.

12-45.

12-46.

12-47.

12-48.

12-49.

12-50.

12-5l.

12-52.

12-53.

12-54.

12-55.

12-56.

12-57.

12-58.

12-59.

12-60.

12-61.

12-62.

12-63.

12-64.

12-65.

12-66.

12-67.

12-68.

12-69.

12-70.

12-7l.

12-72.

12-73.

12-74.

12-75.

12-76.

12-77.

12-78.

12-79.

Major Type 2-Minor Type 14 ... . Major Type 2-Minor Type 16 ... . Major Type 2-Minor Type 17 ... ' ... . Major Type 2-Minor Type 18 ... . Major Type 2-Minor Type 19 ... . Major Type 2-Minor Type 20 ... . Major Type 2-Minor Type 21 ... . Major Type 2-Minor Type 22 ... . Major Type 2-Minor Type 23 ... . Major Type 3-Minor Types 1 through 9 ... . Major Type 4-Minor Type 1 ... . Major Type 4-Minor Type 2 ... . Major Type 4-Minor Type 3 ... . Major Type 4-Minor Type 4 ... . Major Type 4-Minor Type 5 ... . Major Type 4-Minor Type 6 ... . Major Type 4-Minor Type 7 ... . Major Type 4-Minor Types 8 through 10 ... . Major Type 4-Minor Type 11 ... . Major Type 5-Minor Type 1 ... . Major Type 5-Minor Type 2 ... . Major Type 5-Minor Type 4 ... . Major Type 5-Minor Type 6 ... . Major Type 5-Minor Type 7 ... . Major Type 6-Minor Type 1 ... . Major Type 6-Minor Type 3 ... . Major Type 6-Minor Type 4 ... . Major Type 6-Minor Type 5 ... . Major Type 6-Minor Type 6 ... . Major Type 6-Minor Type 7 ... . Major Type 6-Minor Type 8 ... . Major Type 6-Minor Type 9 ... . Major Type 6-Minor Types 10 and 11 ... . Major Type 6-Minor Type 12 ... . Major Type 6-Minor Type 13 ... . Major Type 6-Minor Type 14 ... . Major Type 6-Minor Type 15 ... . Major Type 6-Minor Type 16 ... . Major Type 10-AII Minor Types ... . NS Error Codes ... . NSM Error Codes ... . Station-Level Reason Codes ... . Station-Level Reports ... . Station Types ... . X-25 PDNs ... . Major Type II-Minor Types 1 through 4 ... . Major Type II-Minor Type 5 ... . Major Type II-Minor Types 6 and 7 ... . Major Type II-Minor Type 8 ... . Major Type II-Minor Types 9 and 10 ... . Major Type II-Minor Type 11 ... . Major Type II-Minor Type 12 ... .

12-94 12-95 12-102 12-142 12-156 12-157 12-158 12-172 12-173 12-175 12-176 12-177 12-178 12-179 12-179 12-180 12-181 12-183 12-184 12-185 12-185 12-186 12-187 12-189 12-190 12-191 12-192 12-196 12-197 12-198 12-199 12-200 12-201 12-202 12-202 12-202 12-203 12-204 12-206 12-208 12-216 12-217 12-220 12-222 12-222 12-223 12-224 12-225 12-226 12-227 12-228 12-228

Tables

12-80. Major Type II-Minor Type 13 . . . .. 12-230 12-81. Major Type II-Minor Type 14 . . . .. 12-231 12-82. Major Type II-Minor Type 15 . . . .. 12-231 12-83. Major Type II-Minor Types 16 and 17 . . . .. 12-232 12-84. Major Type II-Minor Type 18 . . . .. 12-232 12-85. Major Type II-Minor Type 19 . . . .. 12-234 12-86.' Major Type II-Minor Type 20 . . . .. 12-235 12-87. Major Type II-Minor Type 21 . . . .. 12-235 12-88. Major Type II-Minor Type 24 . . . .. 12-236 12-89. Major Type II-Minor Type 25 . . . .. 12-237 12-90. Major Type II-Minor Type 26 . . . .. 12-239 12-91. Major Type II-Minor Type 27 ... ~ . . . .. 12-240 12-92. Major Type II-Minor Type 28 . . . .. 12-241 12-93. Major Type II-Minor Type 29 . . . .. 12-241 12-94. Major Type Il-Minor Types 30 and 31 . . . .. 12-242 12-95. Major Type Il-Minor Type 32 . . . .. 12-243 12-96. Major Type II-Minor Type 33 . . . .. 12-244 12.:...97. Major Type II-Minor Type 34 . . . .. 12-245 12-98. Major Type II-Minor Type 35 . . . .. 12-246 12-99. Major Type II-Minor Type 36 . . . .. 12-247 12-100. Major Type II-Minor Types 37 and 38 . . . .. 12-247 12-101. Major Type II-Minor Type 39 . . . .. 12-248 12-102. Major Type II-Minor Type 40 . . . .. 12-248 12-103. Major Type II-Minor Type 41 . . . .. 12-249 12-104. Major Type II-Minor Type 42 . . . .. 12-249 12-,-105. Major Type II-Minor Type 43 . . . .. 12-250 12-106. Major Type II-Minor Types 44 and 45 . . . .. 12-250 12-107. Major Type II-Minor Type 46 . . . .. 12-251 12-108. Major Type II-Minor Type 47 . . . .. 12-251 12-109. Major Type Il-Minor Type 48 . . . .. 12-252 12-110. Major Type II-Minor Type 49 . . . .. 12-253 12-111. Major Type II-Minor Type 50 . . . .. 12-253 12-112. Major Type II-Minor Type 51 ... . . .. 12-253 12-113. Major Type II-Minor Type 52 . . . .. 12-254 12-114. Major Type II-Minor Type 53 . . . .. 12-255 12-115. Major Type II-Minor Type 54 . . . .. 12-256 12-116. Major Type II-Minor Type 55 . . . .. 12-257·

12-117. Major Type II-Minor Type 56 . . . .. 12-260 12-118. Major Type II-Minor Type 57 . . . .. 12-260 12-119. Major Type II-Minor Type 58 ... 12-261 12-120. Major Type II-Minor Type 59 . . . .. 12-261 12-121. Major Type II-Minor Type 60 ... ~. 12-261 12-122. Major Type II-Minor Type 61 ... . . . .. 12-262 12-123. Major Type II-Minor Types 62 through 64 . . . .. 12-262 12-124. Major Type II-Minor Types 65 through 67 . . . .. 12-263 12-125. Major Type II-Minor Type 68 . . . .. 12-264 12-126. Major Type II-Minor Type 69 . . . .. 12-265 12-127. Major Type II-Minor Type 70 . .. . . .. 12-265 12-128. Major Type II-Minor Type 71 ... . . .. 12-2'66 12-129. Major Type II-Minor Type 72 . . . .. 12-267 12-130. Major Type II-Minor Type 73 . . . .. . . .. 12-268 12-143. Major Type 13-Minor Types 0 and 1 . . . .. 12-277

86000478-110 xxiii

12-144. Major Type 14-Minor Types 1, 4, 9 and 10 . . . .. 12-278 12-145. Major Type 15-Minor Types 1 through 5 . . . .. . . . .. 12-279 12-146. Major Type 15-Minor Types 6 through 11 . . . .. 12-283 12-147. Major Type 16-Minor Types 1 through 6 . . . .. 12-285 12-148. Major Type 17-Minor Type 1 ... . . .. 12-287 12:-149. Major Type 17-Minor Types 2 and 3 . . . .. 12-288 12-150. Major Type 18-Minor Types 1 through 11 . . . .. 12-289 12-151. Major Type 18-Minor Types 12 and 13 . . . .. 12-293 12-152. Major Type 19-Minor Types 1, 4,5,6,7,11, 12, 13, and 16 ... , 12-294 12-153. Major Type 25:-Minor Type 1 ... '. . . . .. 12-299 12-154. Major Type 25-Minor Type 2 . . . .. 12-300 12-155. Major Type 25-Minor Types 3 and 4 . . . .. 12-300 12-156. Major Type 25-Minor Type 5 . . . .. 12-301 12-157. Major Type 25-Minor Type 6 . . . .. 12-301 12-158. Major Type 25-Minor Type 7 . . . .. 12-301 12-159. Major Type 27-Minor Types 1 through 11 ... ' . . . .. 12-302 12-160. Major Type 28-Minor Types 1 through 4 . . . .. 12-303 12-161. Major Type 30-Minor Types 1 through 3 . . . .. 12-304

Section 1 BARS

This section describes the BARS utility program, which provides a way to monitor system performance by sampling various system utilization information.

General Information

The BARS utility program monitors the performance of the system and displays it in the form of numeric values and bar graphs. Various system utilization information is sampled and displayed dynamically on screen-type terminals. The information displayed and the format of the screen are user-controllable.

A sample is taken and the display updated every "cycle" seconds. The values displayed are the average of the samples taken over the last "period" seconds. The default value for the cycle is five seconds. The default value for the period is 15 seconds.

The numeric values represent either actual values (for example, the number of core-to-core moves) or percentages (for example, the percent of available processor time).

The plus signs (+) and minus signs (-) that follow numeric values indicate that the values have increased or decreased, respectively, since the last cycle, even if the actual values or bar graphics have not visibly changed (that is, a fractional change, which cannot be displayed, has occurred).

Values are also represented by bars on the screen. The format of each bar consists of number signs (#), followed by (depending on the system) capital Xs, or small, solid rectangles (the DEL character), followed by periods (.), where the number signs extend to the minimum value, the Xs extend to the current value, and the periods extend to the maximum value. The minimum and maximum values are based on the values that existed when the program was initiated or updated from the terminal by the user.

When the user enters the following command, the program executes a LOAD DEFAULT command, which displays the default screen for that system:

E $SYSTEM/BARS

The program is initialized to a different display if the file DISPLAY is label equated to a saved file. For example,

E $SYSTEM/BARS; FILE DISPLAY(TITLE MY/SCREEN)

86000478-100 1-1

If the file MONITOR is label equated, the program writes the raw performance data to that file as it is received from the operating system. For example,

RUN $SYSTEM/BARS; FILE MONITOR(TITLE

=

BARS Commands

The following commands can be used as input to the BARS utility program.

<bars commands>

<bye c o m m a n d > - - - r - - - 1

<cyc 1 e command>·---1

<display command>----

<he 1 p command"'>----I

<load command.>-"'---I

<newdisplay command>-

<pack command,>----I

<period command>---

<save command>·---1

<words command>·---'

BYE Command

The BYE command ends the program.

<bye command>

-- BYE ---~

CYCLE Command

The CYCLE command controls the sampling and display update interval.

<cycle command>

-- CYCLE --<i nteger>>---I Explanation

The variable <integer> represents the interval in seconds.

DISPLAY Command

The DISPLAY command displays the NEWDISPLAY input required for a specified display screen.

<display command>

-- DISPLAY

L

BARS

The following text describes the meaning of each option:

DISPLAY Entering DISPLAY causes the NEWDISPLAY input required for the current screen (either a user-specified screen or the default screen) to be displayed.

DEFAULT

<file name>

Example

The DEFAULT option displays the NEWDISPLAY input for the default screen for that system.

The <file name> displays the NEWDISPLAY input for the screen saved in the specified file.

The following command causes the NEWDISPLAY input for the screen saved in the file called

XIY

DISPLAY X/Y ON P

HELP Command

The HELP command (or TEACH command) displays information that helps the user in using the BARS utility.

<help command>

L ~~k~H ]

LOAD Command

The LOAD command loads a previously generated screen as the new screen. The maximums, minimums, and averages for the system utilization information are reinitialized.

<load command>

- LOAD - , - - - , - - - j

L DEFAULT

-J

L<file name~

Entering LOAD causes the current display to be loaded as the new screen. Essentially, this means that the current screen does not change, though the maximum, minimum, and average values displayed are reinitialized.

The following text describes the meaning of each option:

DEFAULT

<file name>

86000478-100

The DEFAULT option loads the default screen for that system.

The <file name> is the name of the file that contains the screen information to be loaded.

1-3

NEWDISPLAV Command

The NEWDISPLAY command generates a new screen that is used to display system utilization information.

<newdisplay command>

- NEWDISPLAY - - - 1 Explanation

In order to use the NEWDISPLAY command to modify an existing screen, which is the typical case, the user enters DISPLAY followed (optionally) by one of its options and is presented with a screen in a form suitable for modification and transmission as NEWDISPLAY input.

Mter the DISPLAY command is entered, the keyword NEWDISPLAY appears on a line by itself in the upper left-hand corner of the screen. The NEWDISPLAY line is followed by the screen keywords, a group of Ns, and a group of Bs. The N s are used to designate the field for displaying the numeric value of the keyword item. The Bs are used to designate the bar graph field for that item.

The user can then modify the screen by adding, deleting, or rearranging the keywords, Ns, and Bs. Optional text placed in single quotation marks (') can also be added. The screen is then transmitted by placing the cursor at the upper left-hand corner of the screen. Mter the screen is transmitted, it is presented as a dynamic display, which can be saved by using the SAVE command.

Rather than modifying an existing screen, the user can also use the NEWDISPLAY command to d~sign a new one. The keyword NEWDISPLAY must be entered in the upper left-hand corner of the screen and any other information on that line must be deleted. Then any keywords can be entered on the screen, followed by optional Ns and Bs. Optional text placed in single quotation marks can also be added.

As in the case above, after the screen is transmitted, it is presented as a dynamic display, which can be saved by using the SAVE command.

In order for NEWDISPLAY input to be accepted, the following requirements must be met:

• The keyword NEWDISPLAY must appear on a line by itself in the upper left-hand corner of the screen.

• The keywords must be valid keywords (available through the WORDS command).

• The entire screen must be transmitted by placing the cursor at the upper left-hand corner of the screen.

• Optional comments or text nlust be placed in single quotation marks (').

BARS

Example

IDLE NN BBBBBBBB 'on PACK, system XYZ'

The preceding code produces a display like the following:

Idle 45 ###XX •••

on PACK, system XYZ

PACK Command

The PACK command displays the unit numbers, family indexes, and labels of the packs currently on line. On A Series I/O processor (lOP) systems, the channel or base unit identification of the pack string is also displayed. PK and PERPK are synonyms for PACK.

<pack conmand>

L

[ ^~~RiKJ

PERIOD Command

The PERIOD command changes the value of the period. If PERIOD is less than CYCLE, no averaging of system utilization information is done; that is, the exact value of each sample is displayed.

<period command>

- PERIOD - - - 1 Explanation

Several values are computed as running averages using the following formula:

NEWAVERAGE := «OLDAVERAGE

*

*

/ PERIOD

The variable < integer> represents the period in seconds.

SAVE Command

The SAVE command saves the current display in a specified file.

<save conunand>

- SAVE -<fil e name> [

>J

ON -<family name

86000478-100

1-5

Example

The following command saves the current display in the specified file (namely, x/y):

SAVE X/V ON P

WORDS Command

The WORDS command displays the allowed keywords for the NEWDISPLAY input, plus a short description of the meaning of each.

<words command>

- WORDS - - ' - - - l

Keywords

The following table includes all allowed keywords for the BARS utility:

Keyword LAST CYCLE AVGCYCLE IDLE MCP USER OVHD PBIT INIT FREE SAVE

o

Description

Number of seconds since last display Average number of seconds between displays Percentage of available processor time spent idling

Percentage of available processor time spent on nonvisible user or operati ng system processes

Percentage of available processor time spent on visible user or operating system processes

Percentage of available processor time spent stack switching or stack searching, and IOfinish time

Percentage of total available processor time spent performing presence bit operations

Percentage of total available processor time spent doing initial presence bit operations

Percentage of total available processor time spent performing presence bit operations after resumption

Save memory Overlayable memory Available memory

Overlay-file words for overlayable memory Number of core-to-core moves

Number of overlays

Number of overlay-file presence bit operations Number of code file presence bit operations

continued

Keyword CLACT CCWRD COWRD OCWRD PCWRD CLWRD TRFC MIX STED

READY

SCHED

Description

Number of core-to-limbo overlays Number of words moved core-to-core Number of words overlayed

Number of words read from overlay files Number of words read from code files Number of read-only words overlayed

Percentage of time when overlay I/O in process Number of tasks in mix

Number of tasks suspended by the system Number of tasks waiting for processors Number of scheduled tasks

BARS

In addition, a keyword is shown for each online labeled pack, which allows the number ofIlO operations waiting for that unit to be displayed.

MONITOR File Format

If you give the file MONITOR a label equation when you run the BARS program, the resulting performance data is written to that file as the data is received from the operating system. You can analyze the resulting captured performance data by using the MONITOR file information that follows.

The MONITOR file has the following format:

Record 1 Record 2 Record 3 Record 1 Record 2 Record 3

Each record is 180 words long. The record contents are displayed below:

Record Number 1

2 3

Information

Operational information

Utilization times and counts information Queue information

The contents of MONITOR records 1, 2, and 3 are detailed below.

86000478-100 1-7

MONITOR Record 1 (Operational Information)

You can obtain information in this record by making a type 2 SYSTEMSTATUS call.

Refer to the A Series SYSTEMSTATUSProgramming Reference Manual for more information.

The following table shows the structure of record 1:

Corresponding Type 2

Word Data Type Name SYSTEMSTATUS Word

0 Integer MIXCOUNT 6

1 Integer AVAILCORE 9

2 Integer OLAYCORE 10

3 Integer SAVECORE 11

4 Real CCOLAY 15

5 Real CCWORDS 16

6 Real COOLAv 17

7 Real COWORDS 18

8 Real OCOLAV 19

9 Real OCWORDS 20

10 Real PCOLAV 21

11 Real PCWORDS 22

12 Real CLOLAY 23

13 Real CLWORDS 24

14 Integer OLAVCHANNELS 27

15 Integer SUSPENDEES 29

16 Integer BATCHOLAVDISKSIZE 41

MONITOR Record 2 (Utilization Times and Counts Information)

You can obtain the information in this record by making a type 7, subtype 1 SYSTEMSTATUS call. Refer to the SYSTEMSTATUS Reference Manual for more information.

The following table shows the structure of record 2:

Word

o

1-39

40

Data Type Integer Integer

Integer

Contents

Writes the current time to the MONITOR file in increments of 2.4 microseconds.

Equivalent to words 0 through 38 of a type 7, subtype 1 SYSTEMSTATUS CALL

Total time spent by all processors in operating system tasks

continued

Word 41

Data Type Integer

Contents

Total time spent by all processors in user tasks

MONITOR Record 3 (Queue Information)

BARS

You can obtain the information in this record by making a type 23 SYSTEMSTATUS call. Refer to the SYSTEMSTATUS Reference Manual for more information.

The structure of record 3 is equivalent to the structure of the type 23 SYSTEMSTATUS call.

86000478-100 1-9

Section 2

DCAUDITOR

DCAUDITOR is a program that performs analysis of an NSPAUDIT file produced by the data comm subsystem procedures of the operating system.

The user can identify the items to be audited by using the ID (Initialize Data Comm) system command audit options. When one more more of the audit options is set, the system takes the following actions:

• Begins writing the requested types of audit information to a file called NSPAUDIT/DCCONTROL/<NSP unit ID>

• The next time data comm is initialized, writes data comm initialization information to a file called NSPAUDIT/DCINITIAL/<NSP unit ID>

DCAUDITOR performs detailed analysis for NSP requests and results; however, only the TYPE/CLASS field is analyzed for DCWRITE formatted requests and results.

DCAUDITOR RUN Statement

The run statement of DCAUDITOR is as follows:

RUN *SYSTEM/DCAUDITOR("<DCAUDITOR options>"}; VALUE

=

In this statement, <DCAUDITOR options> is a string of options separated by spaces and < nnn> is the unit number of the NSP whose audit file is to be analyzed.

Options

<DCAUDITOR options>

DCINITIAl - - - - I

DCCONTROl - - - - I

<backspace count LINES -<range lSNS -<range>---I STATIONS -<range

<backspace count>

- < i n t e g e r > > - - - , - - - f

<range>

-<integer-I>

L<i nteger-2>~

86000478-100

2-1

The following text describes the meaning of each option:

DCINITIAl and DCCONTROl

<backspace count>

LINES

lSNS

STATIONS

The DCI NlTlAl and DCCONTROl options specify which file is to be analyzed. DCINITIAl selects the NSPAUDIT file created during NSP initialization, and DCCONTROl selects the NSPAUDIT file created after the NSP has initialized.

If these options are not specified, the file that is label-equated to SCAUDITF is analyzed.

The <backspace count> option restricts the analysis to <backspace count> records of the NSPAUDIT file. Valid integers are 1 through 1048575.

The LINES option allows the selective analysis of NSP requests and results that pertain to a range of line numbers. A line number is assigned by the Network Definition language II (NDLlI) compiler and is the ordinal number of the line in the SOURCENDLlI, starting at 1.

If this option is used, no DCWRITE requests and results are displayed.

The lSNS option allows the selective analysis of NSP requests and results that pertain to a range of logical station numbers. A logical station number is assigned by the operating system and is the ordinal number of the station in the SOURCENDLlI, starting at 2.

If this option is used, no DCWRITE requests and results are displayed.

The STATIONS option allows a selective analysis of NSP requests and results that pertain to a range of station numbers. A station number is assigned by the NDLII compiler and is the ordinal number of the station in the SOURCENDLlI, starting at 1.

If this option is used, no DCWRITE requests and results are displayed.

Sample Report

Figure 2-1 is an example of output from the DCCONTROL command. Messages for DCWRITE formatted requests and results are printed in hexadecimal (hex) characters.