CL Programming


Effect of Changing the Command Definition of a Command in a Procedure or Program

When a CL module or program is created, the command definitions of the commands in the procedure or program are used to generate the module or program. When the CL procedure or program is run, the command definitions are also used. If you specify a library name for the command in the CL procedure or program, the command must be in the same library at procedure creation time and at run time. If you specify *LIBL for the command in the CL procedure or program, the command is found, both at procedure creation and run time, using the library list (*LIBL).

You can make the following changes to the command definition statements for a command without re-creating the modules and programs that use the command. Some of these changes are made to the command definition statements source, which requires the command to be re-created. Other changes can be made with the Change Command (CHGCMD) command.

The following changes can be made to the command definition statements depending on what was specified in the CL procedure or program in which the command is used:

The following changes can be made to the command definition statements, but may cause the procedure or program that uses the command to function differently:

The following changes to the command definition statements require that the procedures or program using the command be re-created.

In addition, if you specify *LIBL as the qualifier on the name of the command processing program or the validity checking when the command is created or changed, you can move the command processing program or the validity checking to another library in the library list without changing the command definition statements.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]