The Work with OptiConnect Activity (WRKOPCACT) command, allows you to view information about database transactions, fiber-optic bus activity, and connection status for client and server systems. When running this command, three views of the WRKOPCACT display are available. To display the Work with OptiConnect Activity display, enter:
WRKOPCACT
Work with OptiConnect Activity
System: SYSTEMA
Collection Start Time . . . . . . . . : 15:03:46
Collection End Time . . . . . . . . . : 15:54:56
Collection Elapsed Time . . . . . . . : 00:51:10
Type options, press Enter.
1=Vary on 2=Vary off
System Total Trans Data Data % Connection
Opt Resource Trans /Sec Count Rate Used Status
SYSTEMB 8 0 4 1 0 Varied on
SOC13 2 1 0 Active
SOC02 2 0 0 Active
SYSTEMC 0 0 1 0 0 Active
SOC08 1 0 0 Varied on
SOC10 0 0 0 Active
SYSTEMD 3 0 3 0 0 Varied on
SOC07 1 0 0 Active
SOC04 2 0 0 Active
Totals 11 0 8 1 0
Bottom
F3=Exit F5=Refresh F13=Reset F11=Client Statistics View F12=Cancel
F14=Jobs and Tasksshows an example of the Work with OptiConnect Activity display from the perspective of an application system. The screen shows information about the Connection Status and Total Transactions between the system issuing the command, and other systems in the OptiConnect network.
The activity is broken down by individual OptiConnect adapter cards for each system and defined over the collection period. The collection period is shown at the top of the display. To reset the collection data on this display, press F13 (Reset). Using the options listed, you can vary on or vary off the systems or resources shown on this display.
The next display shows this systems activity as a client. It can be accessed by pressing the
F11=Client Statistics View
function key.
The next display shows this system's activity as a server. It can be accessed by pressing the
F11=Server Statistics View
function key.
OptiConnect jobs and tasks
The Work with OptiConnect Jobs function, accessible from the F14=Jobs and Tasks function key, allows the user to view a list of OptiConnect jobs and tasks. OptiConnect jobs and tasks have one or more OptiConnect conversations attached. The initial prompt panel, shown in Figure 17, allows for the division of jobs and systems into subsets. If any of the input character strings are ended with an '*', then that '*' will be treated as a wildcard.
Work with OptiConnect Jobs SYSTEMA
00/00/00 00:00:00
Type choices, press Enter.
Job name . . . . . . . . . . . . . *ALL Name, generic*, *ALL
Job user . . . . . . . . . . . . *ALL Name, generic*, *ALL
Remote job name . . . . . . . . . . *ALL Name, generic*, *ALL
Remote job user . . . . . . . . . *ALL Name, generic*, *ALL
Remote system . . . . . . . . . . . *ALL System, generic*,
*ALL
F12=Cancel
After the selection information has been entered, the Work with OptiConnect Jobs and Tasks screen is displayed and shows the following information:
The name of the job or task that exists on the system where WRKOPCACT is run.
The user of the local job. This field is blank if the entry is a task.
The name of the job or task that exists on the remote system.
The user of the remote job.
The job number of the remote job.
The system where the remote job or task exists.
To select an option, type the option number in the Opt column and press Enter. The function associated with the selected option will be performed for each of the selected jobs. For more information about the options available, move the cursor to the Opt column and press Help. The options are not available for tasks.
You can select the following options:
Use this option to display the Work with Job (WRKJOB) menu. WRKJOB may be used to end the local job, and consequently, the remote job as well. While the jobs are ending, the path status shows close pending (CLSPND). If F13=Reset is pressed after both jobs have ended, the job entry disappears from the list.
Use this option to run the End Job (ENDJOB) command on the remote system. When the remote job is ended, the path status shows close pending, CLSPND. Local and remote job names remain in the job list entry until the local job either ends, or Distributed Data Management (DDM) conversations are reclaimed. You can reclaim these conversations using the Reclaim DDM Conversations (RCLDDMCNV) command. If RCLDDMCNV is used, the local job will not end, but will be removed from the list once it is refreshed. At this point, it is no longer considered to be an OptiConnect job, although it is still available for other work.
If you press the
F11=Display Statistics View
function key, Figure 18, Work with OptiConnect Jobs and Tasks appears.
Work with OptiConnect Jobs and Tasks SYSTEMA
09/16/98 16:54:26
Type options, press Enter.
5=Work with Job 9=End Remote Job
Local Local Path Transaction Response Data
Opt Job User Status Count Time Count
USRRESTART QTMHHTTP IDLE 12 12.00 12
USRRESTART QTMHHTTP IDLE 14 14.00 14
USRRESTART QTMHHTTP BUSY 16 15.00 15
WEBDY020 QTMHHTTP IDLE 8 8.00 8
WEBDY020 QTMHHTTP BUSY 10 9.00 9
WEBDY020 QTMHHTTP IDLE 10 10.00 10
WEBDY020 QTMHHTTP BUSY 14 13.00 13
WEBDY020 QTMHHTTP IDLE 8 8.00 8
WEBDY020 QTMHHTTP BUSY 10 9.00 9
WEBDY020 QTMHHTTP IDLE 10 10.00 10
WEBDY020 QTMHHTTP BUSY 14 13.00 13
WEBDY020 QTMHHTTP IDLE 8 8.00 8
WEBDY020 QTMHHTTP BUSY 10 9.00 9
WEBDY020 QTMHHTTP IDLE 10 10.00 10
More...
F3=Exit F4=Prompt F5=Refresh F11=Display Remote View F12=Cancel
F13=Reset F14=Display Jobs Only F15=Display Tasks Only F16=Resequence
The display above shows the following information:
Busy: the job or task has at least one outstanding OptiConnect transaction that has not completed.
Idle: there is no outstanding OptiConnect transactions and the job, or task, is not doing any OptiConnect communications work at this time.
CLSPND: an OptiConnect close path is pending and the path, or conversation, is in the process of closing down.
LBUSY: at least one transaction has not completed and it has been outstanding for 1 second or more.
The total number of OptiConnect requests that have been initiated since the last WRKOPCACT restart. The transactions count is expressed in individual transactions and is accumulative since either the last time OptiConnect started, or the job and task data collection were reset.
The total time, in seconds, waiting for OptiConnect transactions to complete, divided by the completed transaction count. The completed transaction count is the previously defined transaction count if idle, or the transaction count minus one, if busy. Response time is an average that is measured since the last time OptiConnect started, or the job and task data collection were reset.
The data that is transferred by the job or task in Kilobytes. This figure is accumulative since either the last time OptiConnect started, or the job and task data collection were reset.