2.6.6 Specifying definitions for using UNIX-compatible commands

(1) Definitions for using executable UNIX-compatible commands in existing job definition scripts

If you will be using executable UNIX-compatible commands in existing job definition scripts, set the path to the directory in which the UNIX-compatible commands are installed in the PATH environment variable. This method eliminates the need for correcting the existing job definition scripts. If there is a command having the same name as a UNIX-compatible command, you can always run the UNIX-compatible command in JP1/Advanced Shell's job definition scripts by specifying the path at the beginning of the PATH environment variable value by using the export parameter in the environment file. For details about the export parameter, see export parameter (defines an environment variable) in 7. Parameters Specified in the Environment Files. Before you run your job definition scripts, make sure that the correct paths have been set in each environment in which the job definition scripts are to be run.

To Page Top

(2) Preparations for using the script-format UNIX-compatible commands (Windows only)

The script-format UNIX-compatible commands use sample script files provided by JP1/Advanced Shell.

Execute the script-format UNIX-compatible commands (such as chmod and su) according to the sample script file provided by JP1/Advanced Shell.

To execute script-format UNIX-compatible commands:

1. Copy to a desired folder the files that you will be using of the sample script files stored at the following location:

   • Windows execution environment

     installation-folder\JP1ASE\sample

   • Windows development environment

     installation-folder\JP1ASD\sample

   For the types of sample script files, see 8.5 UNIX-compatible commands (script format) (Windows only).

2. Rename the copied files to applicable command names.

   For example, rename sample script files script_chmod1 and script_su1 as chmod and su, respectively. If you want to define a command that does nothing, copy sample script file script_0 and then rename it.

3. To specify only the file name of the sample script, not its absolute or relative path, do either of the following:

   • Store the sample script to be run in the folder defined in the PATH environment variable.

   • Add to the PATH environment variable the path of the folder containing the sample script that is to be run.

4. If necessary, define KNAX6831-I message output suppression.

   If you do not want the KNAX6831-I message to be output after the sample script has run, specify the following coding in the job environment file:

   #-adsh_conf JOBLOG_SUPPRESS_MSG     KNAX6831-I

   If you want to suppress output of the KNAX6831-I message for all job definition scripts in the system, specify the above coding in the system environment file.

5. Run the job definition scripts.

   Run the job definition scripts by using the job environment file created in step 4. If you specified the definition in the system environment file, the information specified in step 3 is imported automatically.

To Page Top