280 IBM Application Development Tools for z/OS and OS/390
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
is 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 and
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. The log data set is defined in the LOGDD DD statement.
The message logging facility is active for the entire network, but it can be
deactivated in whole or just partially for a VTAMAPPL in the network by
specifying MLOG=NO on the NTWRK statement or VTAMAPPL statement. The
NTWRKLOG statement is used to specify that a separate log data set to be used
for that network. This is convenient when running multiple networks as the
results will be logged separately.
The loglist utility uses the log data set. The control commands can be contained
in a file or, as an alternative, the CONSOLE execution parameter can be
specified to allow to enter the control commands at the operator console. Use the
WSim/ISPF interface, JCL or TSO CLIST to start the utility, to name the input
files and to specify where the formatted log will be printed.
The loglist utility uses different formats for each type of log records. One
particularly useful feature is the printing of screen image records. These images
are updated each time a message is sent or received by the device. Use the
LOGDSPY operand on the NTWRK statement to request. The output from the
Loglist Utility for this type of log records looks the same as the screen images a
user would see at the real device.
8.5 Operating WSim
WSim can be run using JCL, TSO CLIST and by using the WSim/ISPF Interface.
The sample JCL can be found in the WSIMPRC6 member of the data set
HLQ
.SITPSAMP. The sample TSO CLIST can be found in the member
WSIMRUN of the data set
HLQ
.SITPCLS. The value of
HLQ
depends on how
WSim is installed on the site. The method to invoke the WSim/ISPF Interface
depends on how this interface is installed on the site. Select Option 5 from the
WSim/ISPF Interface main panel (Figure 8-1) and press Enter.
Chapter 8. Introduction to Workload Simulator 281
Figure 8-1 WSim/ISPF Interface main panel: Option 5 is selected to run WSim
After performing start-up tasks, WSim displays message ITP003I, WSIM
INITIALIZATION COMPLETE.
WSim can be stopped at any time by issuing the ZEND operator command,
which causes all active networks to be stopped and canceled.
Operator commands can be entered from a console or be generated
automatically by using OPCMND statements in message generation decks, so
the network can control itself during operation.
8.5.1 Initializing, starting, and stopping a network
When WSim start-up process is completed, a network to be simulated must be
initialized. The initialization consists of checking the syntax of all statements in
the network and building of all control blocks for it. The network definition
statements must reside in the INITDD DD data set and the message generation
decks must reside in the MSGDD DD data set. The network is idling after
initialization until the operator command to start simulation activities is received.
Example 8-7 shows the I (Initialize) operator command to initialize the network
RESNET1 and print the network definition statements:
Example 8-7 Initializing network RESNET1
I RESNET1,LN

Get Introduction to the IBM Application Development Tools on z/OS and OS/390 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.