ADDOP
The ADDOP instruction adds an operation into an occurrence in the current plan.
Keywords used in the Addop Instruction describes the keywords that can be used.
| Keyword | Requirement | List of Values Allowed | Description | Abbrevi-ation | Format |
|---|---|---|---|---|---|
| APPL() | Required | No | The name of the application to be modified. | ||
| OPNO() | Required | No | The operation to be added. | OP | |
| WSNAME() | Required | No | The name of the workstation on which the added operation is executed. | WS | |
| ASUB() | Optional | No | Automatic job submission option (Y or N). | ||
| AUTFUNC | Optional | No | Automated function for the system automation integration. It can be up to 8 characters. | ||
| CLNTYPE() | Optional | No | Cleanup type:
|
||
| COMMTEXT | Optional² | No | Command text for the system automation integration. It can be up to 255 characters. | ||
| COMPINFO | Optional | No | Completion information for the system automation integration. It can be up to 64 characters. | ||
| CONDRJOB() | Optional | No | Specifies if the operation might recover a conditional predecessor (Y or N). The default is N. | ||
| DESC() | Optional | No | Operation descriptive text. If you do not specify DESC(), it defaults to: '* OCL added this oper *' | ||
| DURATION() | Optional¹ | No | The operation estimated duration. EDUR() and DURATION are mutually exclusive. | HHMMSS | |
| EDUR() | Optional¹ | No | The operation estimated duration. EDUR() and DURATION are mutually exclusive. | HHMM | |
| EXPJCL | Optional | No | Expanded JCL used (Y or N). If not specified the default is N. | ||
| EXTNAME() | Optional | No | A free-format name for the operation. It can include blanks and special characters for a maximum of 54 characters. Do not include parentheses in the extended name value. | ||
| EXTSE() | Optional | No | The scheduling environment name. The maximum length can be 16 characters. | ||
| IADATE() | Optional¹ | No | The input arrival date of the application occurrence. IADATE() and IA() are mutually exclusive. | IAD | YYMMDD |
| IATIME() | Optional¹ | No | The input arrival time of the application occurrence. IATIME() and IA() are mutually exclusive. | IAT | HHMM |
| IA() | Optional¹ | No | The input arrival date and time of the application occurrence. It defaults to the earliest or latest input arrival date and time of the application occurrence occurrence found in the current plan, depending on the SORT parameter specified in PARMLIB or in the INIT instruction. IA() cannot be used with IADATE() or IATIME(). | YYMMDDHHMM | |
| JOBCRT() | Optional | No | Specifies whether
the operation is critical or eligible for WLM assistance, if late.
Possible values are:
|
||
| JOBNAME() | Optional | No | The jobname. If the workstation is a job setup, printer, or computer workstation, the jobname is required. | JOB | |
| JOBPOL() | Optional | No | Specifies the
WLM assistance policy to apply, if the job was defined as critical.
Possible values are:
|
||
| MONITOR | Optional | No | Specifies if the operation is monitored by an external product (Y or N). | ||
| OPDL() | Optional | No | Operation deadline. | YYMMDDHHMM | |
| OPIA() | Optional | No | Operation input arrival time. | YYMMDDHHMM | |
| PREOPNO() | Optional | No | The internal predecessor of the added operation. It defaults to the default operation number specified in the DEFOPNO initialization parameter. | PO | |
| SECELEM | Optional | No | Security element for the system automation integration. It can be up to 8 characters. | ||
| TIMEDEP() | Optional | No | Time-dependent option. | ||
| USRSYS() | Optional | No | User sysout needed (Y or N). If not specified the default is N. | ||
| WLMSCLS | Optional | No | The WLM service class. | ||
|
¹ Mutually exclusive with another keyword. | |||||
Examples:
- ADDOP APPL(TEST01) OP(30) PO(20) WS(CPU1) JOB(JOB11111)
- Operation 020 will be added to the occurrence TEST01 with the latest or earliest input arrival date and time (depending on the RT parameter specified in PARMLIB or in the INIT instruction)
- ADDOP APPL(TEST01) OP(30) WS(CPU1) JOB(JOB11111) TIMEDEP(Y), OPIA(&OYMD1.2000) OPDL(&OYMD1.2300)
- Operation 30 will be added as a successor of the default operation number (for example, 001) and it will be scheduled at 08.00 p.m.
- ADDOP APPL(TEST01) WS(FTW1) IA(0310160000) DESC(EXTNAME) PREOPNO(001) JOBNAME(TEST) OPNO(002) EXTNAME(DAILY PAYROLL JOB)
- Operation 002 will be added to occurrence TEST01 with Extended Name DAILY PAYROLL JOB.
- ADDOP APPL(TEST01) WS(FTW1) IA(0310160000) DESC(Extname Blank) PREOPNO(001) JOBNAME(TEST) OPNO(002) EXTNAME( )
- Operation 002 will be added to occurrence TEST01 with Extended Name blank .
The EXTNAME keyword is mandatory when the following two conditions coexist:
- When you add an operation that is to be inserted into the Symphony file.
- When the TWSJOBNAME value is EXTNAME or EXTNOCC.
Note: You cannot add a Job setup operation.
The ADDOP instruction returns one of the following return codes:
- RESULT = 0
- Operation was successfully added to the occurrence.
- RESULT = 4
- Not possible to add the operation.
- RESULT = 8
- Invalid instruction or PIF problem. Refer to the error messages.