CHILDJOB_SHEBANG parameter (defines an executable program path for job definition script files that are to be executed as child jobs)

Format

#-adsh_conf CHILDJOB_SHEBANG path-name

To Page Top

Description

This parameter defines an executable program path that is specified, following #!, as a job definition script file to be run as a child job. The character string immediately following #! through the end of the line is treated as the comparison path name.

When a job definition script file is specified as a command name in another job definition script and the path name specified in this parameter appears on the first line of the job definition script file in the format #!path-name, the command outputs the KNAX6831-I message to the job execution logs and executes the job definition script file as a child job. You can use the JOBLOG_SUPPRESS_MSG parameter to suppress output of the KNAX6831-I message to the job execution logs.

The CHILDJOB_SHEBANG parameter has the following two default definitions:

Default definition	Output mode when the child job starts
/opt/jp1as/bin/adshexec	Operation is performed according to the specification of the OUTPUT_MODE_CHILD parameter.
/opt/jp1as/bin/adshexec -mMINIMUM	Operation is performed in the minimum output mode.

For details about the default definitions for the CHILDJOB_SHEBANG parameter, see 3.2.3(1)(b) Executing child jobs by using a default definition for the parameter.

To Page Top

Operands

path-name ~<any character string>((1 to 1,023 bytes))

Defines an executable program path that, when specified beginning with #! in a job definition script file, is to be executed as a child job.

To Page Top

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 job environment file combined exceeds 255, an error occurs.

• Do not include the leading characters #! in the path name specification in this operand.

• If only a forward slash (/) is specified in this operand as the path name, the command will terminate with an error during parameter analysis.

• The command name output to the job execution logs becomes the path of the directly specified script file.

• 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 executable program path more than once does not result in an error.

• A file that is specified in the argument of the exec, command, or eval standard shell commands or the time reserved script command is also subject to this parameter.

To Page Top

Example

The following examples execute a job definition script file that contains a specific code at the beginning as a child job:

• Executing a file that begins with #!/bin/sh or #!/bin/ksh as a child job

  #-adsh_conf  CHILDJOB_SHEBANG  /bin/sh
  #-adsh_conf  CHILDJOB_SHEBANG  /bin/ksh

• Executing a file that begins with #!/bin/ksh -x as a child job

  #-adsh_conf  CHILDJOB_SHEBANG  "/bin/ksh -x"

• Executing a file that begins with #!/usr/bin/env ksh as a child job

  #-adsh_conf  CHILDJOB_SHEBANG  "/usr/bin/env ksh"

To Page Top