|
|
|
|
|
The following methods are available for activating KOA scripts:
Activate the script within a Control-O rule.
Example
ON COMMAND ...
DO KSL=scriptname %%x %%y %%z
DO ...
In the above example, Control-O continues to process the rest of the rule while the script is executing. This is the default method of script processing when activated by a rule. The example below processes the script in a different manner.
DO SET=%%WAITKSL = YES
DO KSL=scriptname %%x %%y %%z
WAITMODE x
DO IF %%KSLRC EQ 0
DO ...
ENDIF
Activate the script as a batch job. The script can also be activated under Control-M. The same method is used to run KSL reports.
Procedure IOARKOA is used to activate the KOA script. Important DD statements are:
Table 9 IOARKOA Important DD Statements
DD Statement |
Description |
|---|---|
//DAKSLPRM DD |
Script parameters (input) – record length must be 80. (Columns 73-80 are ignored.) |
//DAKSLOUT DD |
A listing of all invoked command members, and error/execution messages. When TRACE ON is activated, it contains a listing of all executed commands and screen images of all the input/output screen functions performed during the script execution. |
//DAREPORT DD |
A report, when created by KOA. |
//DACALL DD |
PDS name containing script members (for command CALLMEM). Multiple libraries can be concatenated. |
Activate the script as a started task. Pass the script name and script parameters as procedure parameters, using the following syntax:
S IOARKOA,PARM=`TRANID=KOA,scriptname script-parameters’
Parent Topic |