Verifying job submission

When Tivoli Workload Scheduler for z/OS submits work, a submit event is written to the event data set. A submit event is prefixed with an I, and can be one of these:

IJ1
Job JCL. A job has been submitted.
IJ2
Started-task JCL. A started task has been started.
IWTO
An operation has been initiated for a general workstation with the WTO option. The submit task causes message EQQW775I to be issued.

Check each system on which Tivoli Workload Scheduler for z/OS is installed to ensure that the destination can be reached by the controller and that the relevant submit events are being created in the event data set. That is, if Tivoli Workload Scheduler for z/OS will submit jobs, start started tasks, and initiate WTO operations, verify that all the event types are created in the event data set. You need not test all these functions if Tivoli Workload Scheduler for z/OS will not be used for a particular operation.

To perform this test for all type I events, start an operation on each of three workstations, all of which specify the destination of the system you are testing. The workstations must be a computer automatic workstation for IJ1 events, a computer automatic workstation with the started-task option for IJ2 events, and a general WTO workstation for IWTO events. Follow this procedure to verify workload submission:

  1. Ensure that you have the correct workstations specified in the workstation description database.
  2. Create a test application with an operation for each workstation you want to test, and add it to the current plan.
  3. When the application has completed, browse the event data set, and verify that the required type I events have been created.
  4. If the operations are not started, check that the workstation status is ACTIVE and that the workstation is not WAITING FOR CONNECTION, which means that the controller is waiting for the corresponding tracker to communicate.