A command line is processed from column 1 to 72. A command cannot exceed column 72. Columns 73 to 80 are ignored.
A command line can contain all blanks.
A command line with * in column 1 is considered a remark.
Each line in a script can optionally have one continuation line. To add a continuation line, place an asterisk (*) in column 72 of the initial line.
A KSL variable must start with the character % and can be 2 through 40 characters long. A blank designates the end of the variable name.
KSL variables are only accessible by the KSL script in which they are defined. Any reference to the same variable in another command member (or in another invocation of the same command member) is totally independent and has no effect on the current member environment.
The value of an AutoEdit variable applies in all command members invoked by a KSL script.
To share information between a KSL script and other command members invoked in the same KSL run, either store the information in local AutoEdit variables, or specify the relevant information using the CALL, CALLMEM, or EXEC command.
Values for the variables %A1 through %A9 (arguments) cannot be set by the SETVAR command. They can only be specified as parameters of a CALLMEM command.
Special variables %RC and %MSG are also valid during the same invocation of a command member. Therefore, if you use the SETVAR command to assign a value to the variable %RC and then execute RETURN, the value of the variable is lost.
Special AutoEdit variables and functions must start with characters %%$. They are set using command SETOLOC and are resolved according to the same rules that apply to the IOA AutoEdit facility.
When an expression contains both KSL and special AutoEdit variables and functions, the KSL variables are resolved first.
A label is valid through the same invocation of a command member. Any reference to the same label in another command member (or in another invocation of the same command member) is totally independent and has no effect on the current member environment.
The IOA KSL and SAMPLE libraries contain general purpose command members that can be used to solve typical report functions (for example, scroll and print).
BMC recommends that you active the TRACE ON command when performing an update function with the KeyStroke Language. It is also more convenient to write new reports with the TRACE ON.
KSL scripts may not work in a customized environment. For this reason, it is highly recommended that you run KSL using backup libraries that specify the default values for the IOA environment.
Note: KSL and Control-M have different AutoEdit processors. Therefore, if a KSL script containing KSL AutoEdit terms is submitted under Control-M, the Control-M AutoEdit %%RANGE statement must be used in the JCL to ensure that the Control-M AutoEdit processor skips (that is, it does not process) the KSL script.
