Tracker for OS/2

The sample library members EQQOS2TR, EQQOS2ST, and EQQX9OS2 can be used to create a tracker for OS/2 operating environments. When installed, the tracker enables you to schedule an operation on a computer workstation which, when ready to be started, sends commands to be executed on an OS/2 workstation. Status is reported back to the controller from OS/2.

To install an OS/2 tracker based on the samples in your environment, follow these steps:

• Specify a symbolic destination ID in the USER keyword of the ROUTOPTS initialization statement.
• Create a computer automatic workstation which specifies the same destination ID.
• Workstations that specify a user-defined destination are initially set to unknown status every time the controller is started. You are responsible for setting the status of the OS/2 workstation to ACTIVE status. You can use the WSSTAT command, the EQQUSINW subroutine or the IBM Tivoli Workload Scheduler for z/OS modify current plan (MCP) dialog. You should consider setting the workstation to ACTIVE status in EQQUX000, the start/stop exit. The sample library member EQQUX0N contains a sample EQQUX000 to set workstation status using the EQQUSINW subroutine.
• Download the EQQOS2TR and EQQOS2ST sample library members to your OS/2 workstation. EQQOS2TR contains code which executes in OS/2, EQQOS2ST contains parameters that are passed to EQQOS2TR. The program is written in REXX and OS/2 command language, instructions for modifying the code and installing can be found in a comment block in EQQOS2TR.
• The sample library member EQQX9OS2 contains an operation-initiation exit (EQQUX009), written in assembler, which is loaded by the controller. The exit is called by the external router subtask when an operation is ready to be started at a workstation which specifies a user-defined destination ID. You need to update the sample to define the destination ID and details about the receiving OS/2 workstation.
• Specify EXITS CALL00(YES) LOAD(EQQUX0N) and CALL09(YES) LOAD(EQQX9OS2) for the controller.

The commands you want to execute in the OS/2 environment can be defined in EQQJBLIB and sent to OS/2 by the EQQX9OS2, or you can choose to keep the information only in OS/2. Status of the operation is reported to the controller by batch jobs executing the EQQEVPGM submitted from the OS/2 tracker.