gtpm3m0sMulti-Processor Interconnect Facility Reference

Keywords Specifications For Report Generation

A list of acceptable keywords for MPIF post-processing has been provided below.

The keywords are:

BLK
Number of 4K blocks to be printed from the trace tape containing MPIF trace entries. Default = 1,000 4K blocks.

MSG
Number of message entries to be printed per 4K block. Default = all messages within each 4K block.

USER
A specific USER that was traced on the MPIF trace tape.

ORG
A specific origin (or source) that was specified on MPIF message transmissions.

DEST
A specific destination that was specified for MPIF message transmissions.

*DATE
A specific DATE for traced messages on the MPIF trace tape.

*TIME
A specific TIME for traced messages on the MPIF trace tape, using the TIME stamp in the 4K HDR.

If a time is provided (HH.MM.SS), this program will select all messages within the hour (HH), on-or-after the minute (MM) specified.

Example: 02.15.45 says "Give me any messages on or after 2:15 PM (through 2.59.59)."

DUR
A MM (minutes) notation signifying elapsed time. If the elapsed time exceeds the current hour, an "end of hour" STOP-TIME will be assigned.

PATH
A specific PATH that was used during MPIF message transmission.

*CPU1
The primary CPU or system ID where MPIF trace is active.

*CPU2
The connected CPU or system ID used in a COMPARE analysis between two CPUs.
Note:
An asterisk (*) above denotes required keywords that must be entered for the COMPARE command.

Each of the above keywords (if specified) must be entered as spelled above; using uppercase or lowercase letters. The arguments must be entered as they appear on the MPIF log tape, using the DCTTRC DSECT for format lengths. If arguments are truncated, when entered as KEYWORD= arguments, they will be blank-padded from left to right. That is, a 4-character USER=aaaa, will be placed in an 8-character field with blanks in positions 5 through 8. Blank padding will only occur for alphanumeric fields that include USER, DEST, ORG, PATH, CPU1 AND CPU2.

Numeric-only arguments (BLK=, MSG=, and DUR= ) must be zero-filled, according to their size. Both the argument size and range of values have been specified below:

BLK=
A four-position value ranging from 0001 through 9999 in numeric value. Default = 1,000

MSG=
A two-position value ranging from 01 through 63 in numeric value. Default = ALL (messages in 4K BLK).

DUR=
A two-position value ranging from 01 through 59 in numeric value. Default = "end of hour" STOP-TIME.

Any mixture of keyword parameters can be specified for PRINT and COMPARE commands. With the PRINT command, at least one parameter must be specified. With the COMPARE command, however, four keyword parameters are required; denoted by an asterisk (*) in the keyword list. For quick reference, however, these required COMPARE keywords are repeated below:

CPU-to-CPU Required Keywords

DATE=
What date do you want CPU-to-CPU tape compares?

TIME=
What time do you want CPU-to-CPU tape compares?

CPU1=
What CPU or System ID are you troubleshooting?

CPU2=
What connected-to CPU or System ID is it linked to?

Command/Search Argument Examples

If several search arguments are used, only those messages that meet the search criteria will be printed on reports. The following is an example of concatenated search parameters for report generation:

PRINT USER=mpif01,DEST=tpf01,ORG=tpf02

A program will scan one mounted trace tape for MPIF MSRB logged entries. If the record ID = X'00E3', this program will then scan for a USER=mpif01, ORG=tpf02 and DEST=tpf01. Only those messages that were sent from tpf02 to tpf01 under USER=mpif01 will be printed.

When an argument is specified (for example, tpf01), the use of uppercase or lowercase letters depends solely on the conventions used in MPIF.

PRINT BLK=0010,USER=mpif01,DEST=tpf01,ORG=tpf02

If BLK=0010 is specified, then only 10 4K Blocks will be printed if they contain a USER of mpif01, a DEST of tpf01 and ORG of tpf02. Note that the BLK= parameter only affects the number of blocks appearing on reports, not the number of blocks scanned on the log tape.

COMPARE CPU1=TPFXX1,CPU2=TPFXX2,DATE=15Dec,TIME=10:00:00,
        DEST=tpf01

In the above example, a CPU-to-CPU message analysis will be performed for December 15 from 10:00AM through 10:59AM only for those messages sent from TPFXX1 to TPFXX2 with a destination of tpf01. TPFXX2's trace tape will also be searched for the same date and time for messages received by tpf01.

Reducing the Report Size

The user can reduce the volume of information being printed by using two volume-associated keywords. They include:

BLK=
Reduce my report size by printing the number of 4K blocks I specifically request.

MSG=
Reduce my report size by printing the number of messages I specifically request within each 4K block.

DEFAULT, CANCEL Commands

Finally, two commands were added that enable the user to bypass keyword entry or cancel the request. DEFAULT can be used instead of PRINT to bypass entering parameters. If used, it equates to: PRINT 1,000 4K blocks; all messages within a 4K block. The CANCEL command will cause the program to terminate.

Summary of Post-Processing Commands

The following list summarizes available commands for MPIF post-processing.

PRINT
Generate a report of one CPU's MPIF activity for messages that meet user-defined search criteria.

DEFAULT
Generate a report of one CPU's MPIF activity for all messages. A search criteria will not be provided. To reduce the size of report output, however, only 1,000 4K trace blocks will be printed.

COMPARE
Perform a CPU-to-CPU compare of MPIF messages sent and/or received between two specific CPU's and generate a summary of your analysis.

CANCEL
Cancel execution at the time user's input search criteria is requested by the program. For this command to be valid, JCL statements must be converted to a C-list.

Only the COMPARE and PRINT commands can have keywords that provide a search criteria. When provided, each keyword must be entered as formatted below:

Command/Keyword Format Requirements

COMMAND KEYWORD=ARGUMENT,KEYWORD=ARGUMENT

The command must begin in column 1. The first keyword must be separated from the command with a blank. If the user enters more than one KEYWORD=ARGUMENT search parameter, each parameter must be separated by a comma to signify continuation. Imbedded blanks are prohibited between a list of KEYWORD=ARGUMENT entries. The program that reads and interprets the user's entry will scan the entry from right to left, looking for a blank (end of KEYWORD=ARGUMENT list) or comma as the last character entered. If a comma is found, the program will expect a second (continuation) record that begins in column 1.