7.3.5 CHILDJOB_EXT parameter (defines an extension for job definition script files that are to be executed as child jobs)
Syntax
#-adsh_conf CHILDJOB_EXT extension
Description
This parameter defines an extension for job definition script files that are to be executed as child jobs. When a job definition script file with the extension specified in this parameter is specified as a command name in another job definition script, the command outputs the KNAX6832-I message to the job execution logs, interprets the file as a job definition script for JP1/Advanced Shell, and then executes the file as a child job. You can use the JOBLOG_SUPPRESS_MSG parameter to suppress output of the KNAX6832-I message to the job execution logs.
Operands
- extension ~<path name>((1 to 245 bytes))
Specifies an extension for job definition script files that are to be executed as child jobs. Specifying as the value only the null character enclosed in double quotation marks (") is not permitted.
Notes
If this parameter is defined in both the system environment file and the job environment file, both definitions take effect. However, if the total number of times this parameter is specified in the system environment file and the job environment file combined exceeds 255, an error occurs.
Do not include a dot (.) in the extension specified in the operand.
If only a forward slash (/) is specified as the extension in the operand, the command will terminate with an error during parameter analysis.
Do not specify exe, bat, cmd, or com, which are executable extensions in Windows, as an extension in this operand. If these extensions are specified, the corresponding files will be executed as child jobs in the same manner as when other extensions are specified. (Windows only)
The command name output to the job execution logs is the path of the script file that was executed as a child job.
If a file that can be executed by using this parameter is evaluated by using the operator -x for evaluating file attributes, the result will be true. (Windows only)
Specifying the same extension more than once does not result in an error.
Execution of a file specified in the argument of the exec, command, or eval standard shell command or the time reserved script command is also subject to this parameter.
This parameter is not case sensitive in the Windows edition, but it is case sensitive in the UNIX edition.
To execute a file with no extension as a child job, use the CHILDJOB_PGM or CHILDJOB_SHEBANG parameter.
This parameter is applied to a command name following variable substitution or alias resolution.
Example
In this example, any file with the extension ash or sh specified as a command name is executed as a child job.
#-adsh_conf CHILDJOB_EXT ash #-adsh_conf CHILDJOB_EXT sh