PTrace Reference Manual Abstract This manual describes how to use the PTrace utility to display trace files created through the use of the Subsystem Control Facility (SCF) or Communications Management Interface (CMI) TRACE commands. This manual is intended for people who use trace facilities for problem determination. Product Version PTrace G06 Supported Release Version Updates (RVUs) This manual supports D45.00 and all subsequent D-series RVUs, and G05.
Document History Part Number Product Version Published 122240 PTrace D40 December 1995 139164 PTrace D40 February 1998 526393-001 PTrace G06 May 2003
PTrace Reference Manual Index Examples What’s New in This Manual v Manual Information v New and Changed Information Figures Tables v About This Manual vii Audience vii Manual Organization viii Your Comments Invited viii Notation Conventions ix 1.
3. PTrace Commands Contents Using PTrace to Select, Format, and Display Trace Records Record-Selection Commands 2-7 Record-Formatting Commands 2-8 Record-Display Commands 2-10 ASCII-to-EBCDIC Translation 2-11 Ending a PTrace Session 2-12 3.
A. Subsystem-Specific Information Contents STATETABLES Command 3-30 TEXT Command 3-31 (continued) TIMESTAMP Command 3-33 TRANSLATE Command 3-33 A. Subsystem-Specific Information ATP6100 Specifics A-2 Device Type and Subtypes A-2 Commands A-2 CP6100 Specifics A-3 Device Type and Subtype A-3 Commands A-3 CSM Specifics A-4 Device Type and Subtype A-4 Commands A-4 SCP Specifics A-5 Device Type and Subtype A-5 Commands A-5 B.
Figures Contents Example 3-1. ENV Command Display 3-8 Figures Figure 1-1. Recording and Displaying Trace Data 1-2 Tables Table 2-1. Table 2-2. Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table A-1. Table A-2. Table A-3. Table A-4. Table D-1.
What’s New in This Manual Manual Information PTrace Reference Manual Abstract This manual describes how to use the PTrace utility to display trace files created through the use of the Subsystem Control Facility (SCF) or Communications Management Interface (CMI) TRACE commands. This manual is intended for people who use trace facilities for problem determination. Product Version PTrace G06 Supported Release Version Updates (RVUs) This manual supports D45.00 and all subsequent D-series RVUs, and G05.
New and Changed Information What’s New in This Manual PTrace Reference Manual—526393-001 vi
About This Manual This manual describes the PTrace (print trace) utility. PTrace selects, formats, and displays data placed in trace files by the Subsystem Control Facility (SCF), Communications Management Interface (CMI), or the Subsystem Programmatic Interface (SPI). Note. CMI is only used in systems running D-series RVUs with the Envoy ACP/XF, ATP6100, CP6100, and AM6520 communications subsystems; all other subsystems use SCF.
Manual Organization About This Manual Manual Organization The manual contains four sections and four appendixes: • • • • • • • Section 1, Introduction to PTrace and Trace Files, describes PTrace and its relation to the SCF, CMI, and SPI trace facilities. It contains background information to help you understand how PTrace works. Section 2, Using PTrace, tells how to run PTrace and how to enter commands. A description of input and output options and record formatting commands is included.
Notation Conventions About This Manual Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation for Messages About This Manual braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis.
Notation for Management Programming Interfaces About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
About This Manual Notation for Management Programming Interfaces lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords.
1 Introduction to PTrace and Trace Files The PTrace (print trace) utility formats data that is stored in unstructured trace files for output to terminals, printers, and disk files. Trace files contain records of the communication between processes. You can capture a trace file either interactively or programmatically. This section summarizes the steps involved in recording and displaying trace data and gives an overview of PTrace features.
Introduction to PTrace and Trace Files PTrace Features for Selecting and Displaying Trace Records Figure 1-1. Recording and Displaying Trace Data Start the trace with the CMI or SCF TRACE command or programmatically through SPI. Collect trace data. Stop the trace with the CMI or SCF TRACE command or programmatically through SPI. Display the trace file with PTrace or CMI PTrace mode. VST001.vsd 1. Start the trace with the SCF or CMI TRACE command or programmatically with SPI.
Introduction to PTrace and Trace Files The PTrace Program and CMI PTrace Mode: Comparison You can select or reject records based on their positions in the file, the time they were recorded, the types of events they describe, and other parameters. PTrace also provides options for specifying the way in which trace records are formatted. You can choose a hexadecimal or octal dump of trace record data; you can enable display of their ASCII or EBCDIC equivalents.
Trace File Header Record Introduction to PTrace and Trace Files data record is record 1. The newest record in the file is record number n-1, where n is the number of records in the trace file. Trace File Header Record When you enter the PTrace FROM command, formatted data from the trace file header record appears. Example 1-1 shows the trace file header record from a trace file named $ACCT.PAY.TAM; the header record includes at least the following information: • • • • • • System and device traced.
Introduction to PTrace and Trace Files 2 Trace Data Record Time at which the trace was captured The value is displayed in microseconds. This time value appears in columns 10 through 24 of the display. 3 Delta time from the previous record The value is displayed in microseconds. If the value reaches 999.999999 or greater, then 999.999999 is displayed. This value appears in columns 26 through 36 of the display. 4 Trace record number Trace records are numbered sequentially beginning at 1.
Trace Data Record Introduction to PTrace and Trace Files Example 1-2. Trace Display With Default Parameters and LABEL OFF 1 2 3 4 5 6 ?record 1/3 07/31/95 11:26:37.326994 >000.000000 #3000 MU Procure Read Buffer -- Current Read buffer is sufficient Subdevice 00 Buffer size = %001750 07/31/95 11:26:37.326827 >000.010293 #3001 DispQ Procure Write Buffer -- Current Write buffer is sufficient Subdevice 00 Buffer size = %000034 Q EXP 07/31/95 11:26:37.325739 >000.
2 Using PTrace This section describes how to start PTrace, how to control its input and output files, and how to enter PTrace commands. Section 3, PTrace Commands, contains detailed syntax and descriptions of all the commands. PTrace formats and prints the trace files that you create with CMI, SCF, or SPI. Trace files are unstructured and cannot be printed or displayed directly. PTrace includes several options for displaying trace data in different formats.
Starting an Interactive Session Using PTrace NOWAIT means that TACL/SCF does not wait while PTrace runs but returns a command input prompt after sending the startup message to PTrace. If you omit this option, TACL/SCF pauses while PTrace runs. OUT [ file-name ] designates the initial destination for PTrace display output for the session. If OUT is omitted, the output destination defaults to the output file of the TACL/SCF process through which PTrace is being initiated (usually a terminal).
Setting the Initial Input Source Using PTrace Setting the Initial Input Source PTrace accepts command input from a terminal, a disk file, or an application process. The initial input source is determined by the form of the RUN command used to initiate PTrace. The input source can be changed during the PTrace session. If you run PTrace without any special instructions, it assumes that input is to come from the input file used by the TACL/SCF process through which it is being run.
Changing the Output Destination Using PTrace disk file, or an application process. For example, the following TACL RUN command initiates PTrace and directs it to send its output to a disk file called PTRACE.DISPLAY: 4> PTRACE/OUT PTRACE.DISPLAY/ If you specify an application process as the OUT file, you must specify the same process as the IN file. See the other considerations given in Setting the Initial Input Source on page 2-3.
Entering Multiple Commands on a Line Using PTrace Entering Multiple Commands on a Line You can enter multiple PTrace commands in response to a single prompt as long as each command is separated from the next by a semicolon. For example, the command line ?ENV; FROM X25TRACE; COUNT is equivalent to the following series of commands: ?ENV ?FROM X25TRACE ?COUNT When processing a command line that contains more than one command, PTrace executes the commands one at a time from left to right.
Using PTrace to Select, Format, and Display Trace Records Using PTrace opens a trace file (and resets some parameters), and displays the number of records in the file. !This file causes PTrace to display current session !parameters, select a trace file, and display its record !count. !last update: 6/26/90 ENV FROM X25TRACE COUNT The following file includes the comments on the same line as the commands. ENV FROM X25TRACE COUNT !List the current session parameters. !Select a trace file.
Record-Selection Commands Using PTrace Table 2-1.
Record-Formatting Commands Using PTrace records that match the SELECT or SELMASK criteria previously established. Records that match are formatted and displayed; those that do not are ignored. The action of the FILTER command depends on which subsystem created the trace file. For some subsystems, the FILTER command is not implemented.
Record-Formatting Commands Using PTrace Example 2-1. Trace Display With DETAIL OFF and ON ?env detail Ptrace Detail Format: ON ?detail off Ptrace Detail Format: OFF ?record 1/3 07/31/95 10:51:55.494096 >000.000000 #1 07/31/95 10:51:55.494904 >000.000808 #2 07/31/95 10:51:55.495936 >000.001032 #3 ?detail on Ptrace Detail Format: ON ?record 1/3 07/31/95 10:51:55.494096 >000.
Record-Display Commands Using PTrace Example 2-2. Trace Display With HEX, OCTAL, and TEXT ON ?HEX ON;OCTAL ON;TEXT ON;RECORD 1/3 Ptrace Hex Print: ON Ptrace Octal Print: ON Ptrace Text Print: ON 07/31/95 11:26:37.326994 >000.000000 #3000 MU Procure Read Buffer -- Current Read buffer is sufficient Subdevice 00 Buffer size = %001750 000: 0000 03E8 4F4B 4352 ...hRBOKCR 0: 000000 001750 051102 047513 041522 ...hRBOKCR 0: NULNUL ETX... 5242 R B O K C R 07/31/95 11:26:37.326287 >000.
ASCII-to-EBCDIC Translation Using PTrace Using the NEXT Command to Start Reading From the Next Record The NEXT command starts reading at the next record and formats and displays the specified number of records that match the selection criteria. You can specify a timestamp, and PTrace will display only records generated after that time. The function keys, F1 through F16, can be used as substitutes for the NEXT command. See Table 3-1 on page 3-2 for more information.
Ending a PTrace Session Using PTrace Note that ASCII-to-EBCDIC translation is handled differently from EBCDIC-to-ASCII translation. With ASCII-to-EBCDIC translation, you can use the default ASCII-toEBCDIC translation table, or you can use a modified translation table with the SETTRANSLATE command. You would enter the SETTRANSLATE command and include the translation table. Then you would set the TRANSLATE flag to ON. The EBCDIC-to-ASCII translation table is fixed; you cannot change the translation table.
3 PTrace Commands This section describes all PTrace commands in a general way, independent of subsystem-specific features. Appendix A, Subsystem-Specific Information, describes each subsystem's implementation of those features. The information in Appendix A, Subsystem-Specific Information, is based on the syntax and other general information presented in this section.
Command Overview PTrace Commands • file-id identifies a particular file within the subvolume, for example, EXSPEC. For convenience, default values are provided for all parts except file-id. The initial default values are the values provided by the TACL or SCF process through which you invoked PTrace. For example, if you invoked PTrace while your current system, volume, and subvolume are \WASH.$DATA.RESDEV, then your default system, volume, and subvolume are \WASH.$DATA.RESDEV.
ALLOW Command PTrace Commands Table 3-1. Summary of PTrace Commands (page 2 of 2) Command Description PAGESIZE Sets the terminal screen size for interactive mode. RECORD Displays record(s) selected by record number. RESET Resets session parameters to their default values and closes the trace file. SELECT Establishes selection criteria for displaying trace records. SELMASK Selects the 32-bit mask trace option value. SETTRANSLATE Changes the ASCII-to-EBCDIC translation table.
COUNT Command PTrace Commands WARNINGS are messages that normally do not affect the execution of the current command or the status of an command file. Considerations: ALLOW Command • • • • If the ALLOW command is not used, the default setting is ALLOW NO ERRORS and ALLOW ALL WARNINGS. If ERRORS or WARNINGS is specified, but ALL, NO, and count are omitted, ALL is assumed. If ALL, NO, or count is specified, but ERRORS and WARNINGS are omitted, ERRORS is assumed.
DESELECT Command PTrace Commands ALL is a keyword that, when specified, results in the deselection of all criteria from the currently selected list (refer to the description of the SELECT command for information about selection criteria). keyword is one of the keywords listed in Table 3-4 (refer to the SELECT command description). Table 3-4 shows the SELECT keywords available. Note that the keyword CURRENT is not applicable to the DESELECT command. Not all keywords are available for a specific subsystem.
DETAIL Command PTrace Commands Ptrace Select Key: All except the following: LCB OCB ?SELECT (ACSE,ASNI,L5) Ptrace Select Key: ACSE Selects the keywords ACSE, ASNI, and L5. ASNI L5 ?DESELECT (ASNI,L5) Ptrace Select Key: Deselects the keywords ASNI and L5. ACSE DETAIL Command The DETAIL command controls the level of detail of the information displayed by PTrace. The specific action of the DETAIL command depends on the subsystem for which PTrace is displaying records.
ENV Command PTrace Commands Considerations: EBCDIC Command • • • • • If the EBCDIC command is not used, OFF is assumed. If EBCDIC is specified without ON or OFF, ON is assumed. The TRANSLATE command enables and disables EBCDIC display mode. The RESET and FROM commands set EBCDIC to OFF. See the discussions of ASCII-to-EBCDIC Translation on page 2-11 and RecordFormatting Commands on page 2-8. ENV Command The ENV (environment) command displays the current values of the PTrace session parameters.
ENV Command PTrace Commands Example 3-1. ENV Command Display ?env Ptrace Output File: Ptrace Data File: Ptrace Log File: Pagesize: Ptrace Count: Ptrace Record: Ptrace Select mask: Ptrace Select key: Ptrace Limit: Ptrace Translation: Ptrace Alphanumerics Ptrace LABEL: Ptrace Detail Format: Ptrace Octal Print: Ptrace Hex Print: Ptrace Text Print: Ptrace Timestamp : Errors allowed: Warnings allowed: $T79A $LAACCT.PAY.TAM $LAACCT.PAY.
EXIT Command PTrace Commands Examples: ENV Command ?ENV COUNT Displays the number of records in the current trace file. If the PTrace COUNT command has not been issued since the last FROM command, the count is not available. ?ENV RECORD Displays the record number of the current record. EXIT Command The EXIT command stops PTrace. E[XIT] Consideration: EXIT Command The end-of-file character (CTRL-Y) has the same effect as the EXIT command.
FIND Command PTrace Commands filter-option is a subsystem-specific option that selects records for display. Consideration: FILTER Command Be sure to select a trace file with the FROM command before setting filter options. FIND Command The FIND command searches formatted trace records for a specified string of characters. When the string is found, the entire record is displayed. Optionally, you can include a range of record numbers within which the search occurs.
FIND Command PTrace Commands begin-integer is an integer that defines the beginning record number for the search. This value is followed by either a comma or a slash and an end-integer. end-integer is an integer that defines the ending record number for the search. If the value of end-integer is greater than the total record count of the trace file, End of Trace file is displayed. Considerations: FIND Command • • • • • • • No records are displayed until search-string is found.
FROM Command PTrace Commands Examples: FIND Command ?F B "File" Finds the first instance of any string consisting of the uppercase or lowercase letters f, i, l, e. ?FIND Finds the next instance of the string specified in the previous FIND command. ?F B "miss" 100,300 Finds the first instance of any string consisting of the uppercase or lowercase letters “m, i, s, s” (in that order) within records 100 through 300.
HELP Command PTrace Commands If your subsystem uses a state-machine file name in a different form, you can use the STATETABLES command to identify it. • The FROM command resets current session parameters to their default values. For more information, see RESET Command. • The FROM command resets current SELECT options to their default values if the device type and subtype of the new trace file are different from the last trace file.
LABEL Command PTrace Commands Considerations: HEX Command • • • • If the HEX command is not used, OFF is assumed. If HEX is specified without ON or OFF, ON is assumed. The RESET and FROM commands set HEX to OFF. See Record-Formatting Commands on page 2-8. LABEL Command The LABEL command controls the formatted display of trace records. The exact format of the display depends on the subsystem for which PTrace is displaying records. LABEL [ ON ] [ OFF ] ON enables the formatted display of trace records.
LISTPM Command PTrace Commands • The RESET and FROM commands reset the limit to 1,073,741,823. Examples: LIMIT Command ?LIMIT 10 Displays no more than ten records in response to any PTrace command. ?LIMIT Displays the maximum number of records in response to a PTrace command. LISTPM Command The LISTPM command shows all the product modules accessible to PTrace from where the command is executed.
LISTPM Command PTrace Commands Definitions: LISTPM Command PTRACE KERNEL The version of the PTRACE kernel that is running. KERNEL INTERFACE The interface version ID sent to the product module when a new process of the product module is run. USER LIBRARY The version of the PTRACE UTILITY library that is currently running. Subsystem The name of a supported subsystem. This subsystem has the file name ZxxxPTR where xxx is the three character mnemonic of the subsystem.
LOG Command PTrace Commands modules, but they are not currently running. The displayed version information is strictly PTrace related. 4-> listpm PTRACE KERNEL KERNEL INTERFACE USER LIBRARY T9082C21-(31OCT91)(11JUN91) T9082C20.
LOG Command PTrace Commands STOP causes logging to be stopped and the log file to be closed. Considerations: LOG Command • • If TO file-name is specified and logging is already in progress, the previous log file is closed and logging begins to the named file. If there is data in the file, data is appended to it. Issuing a FROM command neither stops logging nor changes the log file. Examples: LOG Command The following is an example of a log file for a PTrace session: Ptrace Log File: $DATA.PTRACEC30.
NEXT Command PTrace Commands ?select ios Ptrace Select Ptrace Select ?select 5 Ptrace Select Ptrace Select ?select mux Ptrace Select Ptrace Select ?e mask: Key: 1000 0000 0000 0000 0000 0000 0000 0000 IOS mask: Key: 0000 0000 0000 0000 0000 0000 0000 0101 MUX mask: Key: 0000 0000 0000 0000 0000 0000 0000 0000 MUX Command Meaning ?LOG TO INSPLOG Closes previous log file (if any), opens the log file INSPLOG, and begins sending input commands and output displays to the file.
OBEY Command PTrace Commands • The function keys on a Tandem 6530 terminal can be used as shorthand for various NEXT count commands. Table 3-2 shows the number of records displayed by each function key. Table 3-2.
OCTAL Command PTrace Commands Considerations: OBEY Command • Pressing the BREAK key terminates processing of the command file, and input reverts to the terminal. • You cannot use nested command files in PTrace. If PTrace encounters a nested command file, the program terminates (abends). Examples: OBEY Command FROM PTRACE.TRAM (IOS,L2,L3,L4) FILTER SM FILTER INTERNALS This is a sample command file for a SELECT X25AM trace file. ?O ABC.INSPCOM Reads commands from the file ABC.
OUT Command PTrace Commands OUT Command The OUT command changes the PTrace listing file. OUT { TO file-name [, LENGTH line-len] [, LINES page-len] } { STOP } TO file-name specifies the file that is to receive PTrace output. If an output file is currently open, it is closed and the specified file is opened. LENGTH line-len specifies the length of the records written to the output device. line-len must be an integer in the range 80 through 132.
RECORD/REC Command PTrace Commands Considerations: PAGESIZE Command • • • If the PAGESIZE command is not used, PTrace does not count the number of lines. Press RETURN to display the next page. Press BREAK to return to the PTrace prompt. Examples: PAGESIZE Command ?PAGESIZE 20 Displays 19 lines. ?PAGESIZE 0 Does not count lines; displays data continuously. RECORD/REC Command The RECORD or REC command displays records selected by record number.
RESET Command PTrace Commands Examples: RECORD/REC Command ?RECORD 5/25 Displays records in the range 5 to 25 that satisfy the selection criteria. ?RECORD (5,25) Same as above. RESET Command The RESET command closes the current trace file and resets DISPLAY and SELECT options to their default values. RESET Table 3-3 lists the commands that are affected by the RESET command and shows their default settings. Table 3-3.
SELECT Command PTrace Commands determine whether the record is of a type that you want to display. PTrace also checks many other session parameters, such as those established by FILTER and LIMIT. You select specific records in two ways, depending on how your subsystem implements PTrace: 1. Through a keyword that is translated into an enumerated value or through a number that is saved as an enumerated value. 2. Through a 32-bit selection mask.
SELECT Command PTrace Commands number can be specified in decimal, octal, hexadecimal, or binary notation. When you specify number, it is saved as an enumerated value.
SELECT Command PTrace Commands Valid Keywords for Subsystem OSN MEM SYSMSG DSM MSG SM PROV ASN1 Valid Keywords for Subsystem QIO QIODRIV Subsystem SCP SPI QIOMEM QIOMOD QIOMSG QIOQUEValid Keywords for MODULE Valid Keywords for Subsystem SCS LOGIC CLIENTREQ CLIENTREPLY SERVERREQ SERVERREPLY Valid Keywords for Subsystem SX1 ASM BM CS CSFSM XSFSM SMFSM LM HS SS XM ASMBIU PCPIU APNSOXFSM APNCRTFSM APNITIFSM APNLV5FSM LMGRFSM APNLV5BIU Valid Keywords for Subsystem TCI SOCKCR MBUF IPC TCP UDPI
SELMASK Command PTrace Commands then Ptrace Select key shows the keyword. If you did not specify the trace file (through the FROM command), then Ptrace Select key shows the enumerated value. • • The SELECT command accepts all valid keywords including those that translate into bit masks; however, the confirmation text displays the 32-bit mask value only if that value is nonzero. The enumerated list of keywords (or the numeric values, if no trace file is currently open) is always displayed.
SETTRANSLATE Command PTrace Commands value can be specified in decimal, octal, hexadecimal, or binary notation. The range of values are listed below: decimal: 0 octal: %0 hexadecimal: %H0 binary: %B0 - 2147483647 %37777777777 %HFFFFFFFF %B11111111111111111111111111111111 Consideration: SELMASK Command Execution of the SELMASK command does not affect the enumerated keyword list.
STATETABLES Command PTrace Commands Considerations: SETTRANSLATE Command • • • • • • • One number or one character in a string represents one position in the table. The table is changed from the position specified by offset for as many positions as there are characters specified in xlate-specs. An error occurs if offset plus the number of characters specified is greater than 256. If SETTRANSLATE is specified with no offset and xlate-spec, the table returns to its default setting.
TEXT Command PTrace Commands TEXT Command The TEXT command controls the textual display of trace records, excluding the header record. The textual display appears below labeled data, the HEX display, and the OCTAL display, if they are present. The display consists of ASCII characters, with control codes represented by 2-character or 3-character mnemonics. The exact format of the display depends on the subsystem for which PTrace is displaying records.
TEXT Command PTrace Commands Table 3-4.
TIMESTAMP Command PTrace Commands TIMESTAMP Command The TIMESTAMP command determines whether the trace record time displayed will be the Local Civil Time (LCT) or the original time of the system where the trace was taken. Note. This command only applies to trace records created by version C30 (or greater) of the SCF TRACE facility. If the TIMESTAMP command is specified for an older trace file, PTrace issues a warning message and ignores the command.
TRANSLATE Command PTrace Commands • • • • If TRANSLATE appears without ON or OFF, ON is assumed. The data read by PTrace is translated. The translation has no effect on the contents of the trace file. The RESET and FROM commands set TRANSLATE to OFF. See ASCII-to-EBCDIC Translation on page 2-11 and Record-Formatting Commands on page 2-8.
A Subsystem-Specific Information This appendix lists the subsystems that support PTrace and the manuals that contain subsystem-specific information for PTrace. (Information for a few subsystems whose manuals do not contain recent PTrace information is included in this appendix. Some subsystems have no published subsystem-specific PTrace information.
ATP6100 Specifics Subsystem-Specific Information Subsystem Manual Title SLSA ServerNet LAN Systems Access Configuration and Management Manual SNAX/APN SCF Reference Manual for SNAX/APN (D-series) SNAX/XF and SNAX/APN Configuration and Management Manual (G-series) SNAX/CDF SNAX/CDF Configuration and Control Manual (D-series) SNAX/XF SCF Reference Manual for SNAX/XF (D-series) SNAX/XF and SNAX/APN Configuration and Management Manual (G-series) SNMP SCF Reference Manual for the SNMP Agent (D-serie
CP6100 Specifics Subsystem-Specific Information SELECT Command Table A-1 shows the keywords and mask bits for formatting trace files generated by ATP6100. Table A-1.
CSM Specifics Subsystem-Specific Information SELECT Command Table A-2 shows the keywords and mask bits for formatting trace files generated by CP6100. Table A-2.
SCP Specifics Subsystem-Specific Information Table A-3.
Commands Subsystem-Specific Information PTrace Reference Manual—526393-001 A- 6
B Syntax Summary RUN Command PTRACE [ / run-option-list / ] [ ptrace-command ; ] ... run-option-list IN file-name NOWAIT OUT [ file-name ] ptrace-command Integers IntegDecimal Octal { % Binary { %B Hex { %H { { 0|1|2|3|4|5|6|7|8|9 }... { 0|1|2|3|4|5|6|7 }... { 0|1 }... { 0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F }... } } } } File Names [\system-name.] [$volume-name.] [subvolume-name.
PTrace Commands Syntax Summary COUNT DESELECT [ [ [ [ ALL keyword number [ ( ] keyword [ , keyword ]...
PTrace Commands Syntax Summary F[IND] [ [ B[OTH] ] [ A[LL] ] "search-string" [ range-spec ]] FROM file-name HELP [ ptrace-command ] HEX [ ON ] [ OFF ] LABEL [ ON ] [ OFF ] LIMIT [ records ] LISTPM LOG { TO file-name } { STOP } N[EXT] [ count ] [ AFTER [date]time ] date /mm/dd/yyyy time h[h]:mm[:ss[.
PTrace Commands Syntax Summary OUT { TO file-name [, LENGTH line-len] [, LINES page-len] } { STOP } PAGESIZE size RECORD { first [ , last ] } { ( first [ , last ] ) } { ALL } RESET SELMASK value SELECT [ [ [ [ [ ALL CURRENT number keyword ( keyword [ , keyword ]... ) ] ] ] ] ] SETTRANSLATE [ offset , xlate-spec ] [ offset , ( xlate-spec [ , xlate-spec]...
C Errors, Warnings, and Informational Messages This appendix lists the PTrace messages, describes the probable cause of each message, and suggests recommended action. PTrace issues four types of messages: fatal errors, nonfatal errors, warnings, and informational messages. Fatal errors cause a program to terminate. Nonfatal errors cause the command line to terminate or an command file to abort. Warnings do not affect the execution of the current command or the status of an command file.
Errors, Warnings, and Informational Messages Nonfatal Errors Error threshold exceeded. Cause. The errors-per-command limit has been exceeded. Recommended Action. Use the ALLOW command to increase the errors-percommand limit and reenter the command. Internal Error: FORMAT2 CALL. Cause. This is an internal procedural interface error. Recommended Action. Refer to the Guardian Procedure Errors and Messages Manual for more information about this file system error. UseSegment Error n. Cause.
Errors, Warnings, and Informational Messages Nonfatal Errors Data exceeds maximum attribute size. Cause. The argument of an input command was too long. Recommended Action. Refer to the description of the command in Section 3, PTrace Commands, for information on attribute size limits and reenter the command. Effective input record exceeds n bytes. Cause. The input line is too long. It has been truncated. Recommended Action. No action is necessary. Error n opening log file file-name. Cause.
Errors, Warnings, and Informational Messages Nonfatal Errors Error n opening trace file file-name. Cause. An error was encountered when opening the trace file. Recommended Action. Refer to the Guardian Procedure Errors and Messages Manual for more information about this file system error. Error n positioning trace file. Cause. An error was encountered when positioning the trace file. Recommended Action.
Errors, Warnings, and Informational Messages Nonfatal Errors Recommended Action. Determine the action to be taken from the file system error and correct the problem. Restart the PTrace kernel. Error retrieving filenames using NEXTFILENAME. Cause. There was an error using the procedure NEXTFILENAME when attempting to search for product modules. Recommended Action. Verify that the param PTRACE^PM^LOC is set correctly and retry the command. FC when not interactive invalid. Cause.
Errors, Warnings, and Informational Messages Nonfatal Errors Identifier too long. Cause. There is an identifier in the input that exceeds 30 characters. Recommended Action. Reenter the command using an identifier of 30 characters or less. Integer conversion error. Cause. A value you entered as an integer was either too large or contained an invalid character (for example, 9 appeared in an octal constant). Recommended Action. Reenter the command using an allowable integer value. No FIND string specified.
Errors, Warnings, and Informational Messages Nonfatal Errors $SYSTEM.SYSTEM.ZPTRLIB, and the other references a library other than $SYSTEM.SYSTEM.ZPTRLIB. Recommended Action. Exit PTrace. Secure the product with the write access. Set the TACL parameter PTRACE^LIB^MOVED to YES. Restart PTrace and reissue the command. PTRACE Product module, \System.$vol.subvol.ZsubsysPTR stopped PROCESS_GETINFOLIST_error error#. Cause.
Nonfatal Errors Errors, Warnings, and Informational Messages Specified translate table exceeds 256 bytes. Cause. The translate table you entered in the SETTRANSLATE command was too long. Recommended Action. Check your input and reenter the command. State tables not read. Bad statetable file. Cause. The state tables specified in the STATETABLES command were not read in because the end-of-file was encountered while the header of the statetable file was being read. Recommended Action.
Nonfatal Errors Errors, Warnings, and Informational Messages System name specified, Param PTRACE^PM^LOC ignored. Cause. The TACL param PTRACE^PM^LOC has a system name specified. Recommended Action. Exit PTrace. Reenter the TACL parameter without the system name. Restart PTrace. Only $vol.subvol is accepted. Trace file error: Blocksize (n) exceeds maximum (m). Cause. The blocksize specified in the trace file header is more than the maximum value that PTrace allows. Recommended Action.
Errors, Warnings, and Informational Messages Nonfatal Errors Recommended Action. Reenter the command specifying a value between 0 and 255. Unable to allocate extended segment for PM use, PM=ZsubsysPTR, ERROR=Segment Number. Cause. The PTrace kernel was unable to allocate an extended segment used for communication with the PM. Recommended Action. Try running PTrace in a CPU with more memory, or allocate a swap disk when starting up PTrace. Unable to open Select Mask File, $vol.subvol.
Warnings Errors, Warnings, and Informational Messages \system.$vol.subvol.ZsubsysPTR, Product module has incorrect format. Cause. The file code of ZsubsysPTR file is not a valid value. Recommended Action. Check the file code of ZsubsysPTR file. It must be 0, 100, or 700. Warnings Warnings inform you of possible problems. They have no effect on the execution of your program or on the status of your command file. Hour specified is out of range (0-24). 0 assumed. Cause. This message is self-explanatory.
Warnings Errors, Warnings, and Informational Messages No trace file currently open. Cause. The command you entered is invalid when no trace file is open. Recommended Action. Open a trace file and reenter the command. Record Length specified is out of range (40-150). Cause. This message is self-explanatory. Recommended Action. Reenter the command specifying a record length between 40 and 150. Second specified is out of range (0-59). 0 assumed. Cause. This message is self-explanatory. Recommended Action.
Informational Messages Errors, Warnings, and Informational Messages Trace terminated improperly. not be consistent. The structure of this file may Cause. The trace was terminated due to an error condition and the trace file was not closed properly. Some or all of the trace records may not be viewable. Recommended Action. You may need to retry the trace. Informational Messages Informational messages inform you of changes that affect the execution environment.
Errors, Warnings, and Informational Messages Informational Messages Recommended Action. No action is required. Use PTTNT utility for proper interpretation of TELSERV trace files. Cause. This message is self-explanatory. Recommended Action. No action is required.
D ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
ASCII/EBCDIC Codes Translation Table Table D-1.
Index Numbers 32-bit mask 3-4, 3-28 A ALLOW command 3-3 ASCII-to-EBCDIC translation description 2-11 TRANSLATE command 3-33 translation table D-1 B Binary numbers 3-1 BREAK key 2-5, 3-4, 3-21, 3-24 C Commands ALLOW 3-3 ASCII-to-EBCDIC translation 2-11 correcting 3-9 COUNT 3-4 default parameters 2-6 DESELECT 3-4 DETAIL 3-6 EBCDIC 3-7 entering 2-4 ENV 3-7 EXIT 3-9 FC 3-9 FILTER 3-9 FIND 3-10 FROM 3-12 HELP 3-13 HEX 3-13 LABEL 3-14 LIMIT 3-14 LOG 3-15, 3-17 Commands (continued) longer than one line 2-5 mul
E Index Device type and subtype ATP6100 subsystem A-2 CP6100 subsystem A-3 CSM subsystem A-4 displayed 1-4 SCP subsystem A-5 Displaying records by record number 3-23 E I IN file 2-2 informational messages C-13 Input source changing 2-3 initial 2-2, 2-3 Integers 3-1 Interactive PTrace 2-2 EBCDIC command 2-11, 3-7 translation table D-1 End-of-file 2-12, 3-9 Entering comments 2-5 Enumerated value 3-4, 3-24 Errors 2-12, 3-3, C-1 EXIT command 2-2, 2-12, 3-9 Extended format 1-4 K F M Fatal error messages
P Index S OCTAL command 3-21 display 3-21 numbers 3-1 Online help 3-13 Opening trace file 3-12 OUT command 2-4, 3-22 OUT file 2-2 Output destination changing 2-4 initial 2-2, 2-3 P PAGESIZE command 3-22 Prompt character (?) 2-2 PTrace command input 1-3 features 1-3 interactive 2-2 output 1-3, 3-22 prompt 2-2 run examples 2-2 Q Quitting PTrace 3-9 R RECORD command 2-11, 3-23 Records capture time 1-4 displaying by record number 3-23 number 1-4 specifying maximum to be displayed 3-14 type 1-4 Record-disp
W Index Timestamp 1-4, 1-5, 3-19 TIMESTAMP command 3-33 Trace file header record 1-4 TRACE command CMI 1-2 SCF 1-2 Trace data 1-1 Trace data record header line 1-4 introduced 1-4 Trace display 1-4 Trace entry size 1-4 Trace file defined 1-1 generating 1-2 introduced 1-3 opening 3-12 Trace record label 1-5 Trace record number 1-5 Trace record text 1-5 Trace records, counting 3-4 TRANSLATE command 2-11, 3-33 Translation table ASCII/EBCDIC D-1 setting 3-29 W Warnings 3-3, C-11 Wraparound 1-4 Special Charac
