Using IBM Application Development Tools for z/OS and OS/390

158 Using IBM Application Development Tools for z/OS and OS/390

The message trace records (MTRC) are obtained by specifying the operand

MSGTRACE=YES in the network definition or by using the ALTER (A) WSim operator

command. The Loglist Utility (ITPLL) can be used to format and print MTRC.

The STL trace records (STRC) can be obtained by using the following steps:

1. Request creation of correlation records (linking message generation statements with the

STL statements that produced them) by using the PROGRAM= execution parameter or

the @PROGRAM statement in the STL program.

2. Specify the operand STLTRACE=YES in the network definition, or use the ALTER (A)

WSim operator command.

The Loglist Utility can be used to format and print STRC.

To ensure that unexpected situations encountered during simulations are handled properly,

use self-checking scripts. They do not need to be used for all simulations, for example, short

and simple ones. On the other hand, they definitely should be considered for a long-running

test, which could be wasted if terminals were to go out of synchronization.

IF statement logic tests are added to the scripts to check for the expected response and to

take action if an unexpected one is received. This action could be simple, such as stopping

the device, or complex, such as including several possible courses of action based on the

actual response. The logic tests can be written in decks created by STL, one of the script

generation utilities, or manually. They can also be coded in network definitions.

4.4 WSim output

WSim provides several online and printed reports to analyze test results. Some reports are

produced by default, while some must be requested by issuing specific operator commands

or running one of the WSim utilities. There are the following types of reports:

򐂰 Operator reports indicating what is happening during operation

򐂰 The complete message log

򐂰 Reports generated by the following utilities based on the message log:

– Formatted reports produced by the Loglist Utility.

– Reports on differences between 3270 display records in two message logs produced

by the log compare utility.

– Detailed statistical analysis of response times produced by the response time utility.

򐂰 Online response time statistics

Most of the reports are intended to represent how WSim is interacting with the system under

test and not the effectiveness of the network and/or the application.

Interval reports monitor the current activity and status of each simulated resource in the

network. The statistics are accumulated until the network is canceled (operator command C)

or reset (operator command R). End of run reports provide summary data from the simulated

network. They are produced automatically and have the same format as interval reports. The

inactivity report, requested by using the SCAN operand on the NTWRK statement or by using

the S operand on the A operator command with a non-zero time interval, contains information

about each inactive resource in the network.

The log data set is the single most valuable tool for debugging the scripts. This data set

contains all data that has been transmitted or received by the WSim simulated resources.