PATH_CONV_ACCESS parameter (defines path conversion details when files are input and output)

Format

#-adsh_conf PATH_CONV_ACCESS path-name-1 path-name-2

To Page Top

Description

This parameter defines the path names before and after conversion for converting file path names in job definition scripts when files are input and output.

If an input or output operation occurs while a job definition script is running and the path name of the file subject to the input or output operation matches the specified path-name-1, this parameter converts it to path-name-2. Both path-name-1 and path-name-2 must be specified.

If different rules are defined for the same file path name, the first rule defined takes effect.

External scripts specified in . (dot) commands and #-adsh_script commands are not subject to conversion by the COMMAND_CONV_ARG parameter. For details about the COMMAND_CONV_ARG parameter, see COMMAND_CONV_ARG parameter (defines a rule for converting an argument in job definition scripts during command execution).

The conversion results are output to the job execution logs as the KNAX6803-I or KNAX6805-I message.

If the PATH_CONV_ENABLE parameter is not defined in the environment file, the PATH_CONV_ACCESS parameter is ignored.

To Page Top

Operands

path-name-1 ~<path name>((1 to 247 bytes))

Specifies the file path before conversion. To specify a file path containing a space, enclose the entire file path in double quotation marks ("). A value enclosed in double quotation marks cannot consist of only a space, tab character, or null character. None of the following characters is permitted:

* ? < > | ` (grave accent mark) $

If path-name-1 is omitted or the value specified in path-name-1 is invalid, the command will terminate with an error during parameter analysis.

path-name-2 ~<path name>((1 to 247 bytes))

Specifies the file path after conversion. To specify a file path containing a space, enclose the entire file path in double quotation marks ("). A value enclosed in double quotation marks cannot consist of only a space, tab character, or null character. None of the following characters is permitted:

* ? < > | ` (grave accent mark) $

If path-name-2 is omitted or the value specified in path-name-2 is invalid, the command will terminate with an error during parameter analysis.

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 parameters is specified in the system environment file and the job environment file combined exceeds 255, an error occurs.

• This parameter performs conversion in such a manner that a variable substitution and a file name substitution have been resolved.

• The conversion rules are searched in the order they are defined and only the first rule satisfying the conversion condition is applied.

• If conversions are defined for the same path name by applying both this parameter and the PATH_CONV parameter, the conversion defined by the PATH_CONV parameter is performed first. To convert the path name obtained after conversion by the PATH_CONV parameter further by the PATH_CONV_ACCESS parameter, specify the path name converted by the PATH_CONV parameter.

• To specify a character string containing a backslash (\), not a metacharacter, in path-name-2, specify \\ instead of \.

To Page Top

Example

• This example converts"/dev/null" to "nul" to run in UNIX a job definition script created for Windows:

  #-adsh_conf PATH_CONV_ENABLE / :
  #-adsh_conf PATH_CONV_ACCESS /dev/null nul

• This example converts "nul" to "/dev/null" to run in Windows a job definition script created for UNIX:

  #-adsh_conf PATH_CONV_ENABLE \\ ;
  #-adsh_conf PATH_CONV_ACCESS nul /dev/null

To Page Top