Creating operations

About this task

The type of operation determines the type of workstation you use:
  • Job operations run on computer workstations.
  • Started-task operations run on computer workstations that have the STC attribute.
  • Job setup operations for jobs and started tasks run on general workstations that have the SETUP attribute.
  • Print operations run on printer workstations.
  • WTO operations run on a general workstation that has the WTO attribute.
  • Shadow jobs run on remote engine workstations.
  • Operations that have events reported by EQQUSIN or OPSTAT can run on any workstation type except one that specifies no reporting.
  • Dummy operations, which are used to simplify dependencies, run on nonreporting general workstations.
  • Other tasks that you want to be represented by operations usually run on general workstations.
Follow these steps to specify the operations in an application:
  1. In the CREATING AN APPLICATION panel (EQQACGPP - Creating an application ), enter the OPER command. You see the OPERATIONS panel, shown in EQQAMOPL - Operations .
    Figure 1. EQQAMOPL - Operations
    EQQAMOPL ------------------------ OPERATIONS ----------------  ROW 1 TO 3 OF 3
    Command ===>                                                  Scroll ===> PAGE
    
    Enter/Change data in the rows, and/or enter any of the following
    row commands:
    I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete
    S - Select operation details, J - Edit JCL
    Enter the PRED command above to include predecessors in this list, or,
    enter the GRAPH command to view the list graphically.
    
    Application            : PAYDAILY         daily payroll jobs
    
    Row  Oper      Duration   Job name    Operation text            Number of
    cmd  ws   no.  HH.MM.SS                                         Conds
    '' WTO1  005   00.01.00    PAYDAILY  PAYX CLOSE DATASET______    0
    '' SETP  010   00.03.00    PAYDAILY  Job setup for paydaily__    0
    '' CPU1  020   00.05.00    PAYDAILY  Runs pay04 and pay06____    0
    ******************************* BOTTOM OF DATA **************************
  2. For each operation, type the workstation and operation number in the Oper ws and no. fields.
  3. Estimate the duration of each operation, or use the default that you specified for the workstation. When an operation runs, the real duration is fed back to the application description database. The minimum value of planned duration is 1 second, and the maximum value is 99 hours 59 minute 00 seconds. If you specify 99 hours 59 minutes 01 seconds, you do not receive an alert message if the actual duration is greater than the planned duration. For details about the duration feedback, see Options that apply to all operations.

    If the operation is defined on a general non reporting workstation, in the current plan the estimated duration of the instance is automatically set to 1 second, regardless of the value that is set in the operation definition. This rule applies for all general non reporting workstations, except the WAIT workstations.

  4. If the workstation is a job setup, computer, or printer workstation, specify the name of the job or started task that the operation represents. HCL Workload Automation for Z uses this to find the JCL for job or started-task operations. See Associating job statements with operations. The job name for setup and print operations must be the same as the associated job or started-task operation.
  5. Type, in the Operation text field, a line of text to be associated with the operation. This text forms part of any WTO message that is issued for an operation. For more details, see Using WTO operations and the description of the DEADLINE WTO option on page DEADLINE WTO (default: N). The operation text can be used to further document the processing; it can also direct operators to perform certain functions. For example, you could have an operation on a general workstation to remind the day-shift operators to collect the office supplies.
  6. Enter the PRED command to specify any internal and non conditional predecessors to the operation you are creating. For more details of operation predecessors and successors, see Specifying dependencies.
  7. Specify the details of each operation by entering S next to the operation you want to specify. For details, see Setting operation details.
  8. Check the JCL of the associated job name by entering J next to the operation you want to specify. This is only possible if you have a tool for editing JCL, and you have specified it in the 0.6 OPTION panel. For details, see Specifying operator instructions. This option applies only to jobs running in z/OS® environments.