2.2.3 Files used in JP1/Advanced Shell

Organization of this subsection

(1) List of files used in JP1/Advanced Shell
(2) Handling of files that are larger than 2 GB (large files)

(1) List of files used in JP1/Advanced Shell

The table below lists and describes the files that are used in JP1/Advanced Shell. To determine whether a file size can exceed 2 GB, see (2) Handling of files that are larger than 2 GB (large files).

Table 2‒9: Files used in JP1/Advanced Shell
File name (icon)	Extension	File location	File contents
Job definition script file ()	`.ash`	Any location	A job definition script. The user can assign any file name.
Environment file^#1	`.ase`	Any location	JP1/Advanced Shell environment settings.
System environment file	`.ase`	See 2.6.1(1) Specifying the system environment files.	System environment settings.
Coverage information file	`.asc`	Any location	Coverage environment information for JP1/Advanced Shell.
Debugging information file	`.asd`	Same directory as for the job definition script files^#2	Debugging information used by the editor (development environment)
System execution log^#1	`.log`	Directory specified in the `LOG_DIR` parameter in the environment file	Log information that provides overall batch job execution logs for the system administrator.
Trace information^#1	`.log`	For the `adshexec` command, the directory specified in the `TRACE_DIR` parameter in the environment file In all other cases, the directory specified by the program	JP1/Advanced Shell's internal trace logs.
Temporary file	`.tmp`	For a temporary file specified in the `#-adsh_file_temp` command, the directory specified in the `TEMP_FILE_DIR` parameter in the environment file In all other cases, the directory specified by the program	Temporary file used internally by the system.
Coverage display temporary file	`.txt`	Temporary file directory specified by the system	Temporary file used in displaying coverage information. The format of file name is as follows: `adshexec_view_job-definition-script-file-name_year-month-date_hour-minute-second.txt`
Start log (UNIX only)	`.log`	`/opt/jp1as/system`	Log information that is collected when the user-reply functionality's management daemon is started and stopped.
`pid` file (UNIX only)	`.pid`	`/opt/jp1as/system`	File used by the user-reply functionality management daemon and `adshmdctl`.

#1

You can collect these files by using the adshcollect command. For details about how to collect the files, see adshcollect command (collects information).

#2

Because a debugging information file cannot be saved, an error is displayed in the following cases:

[Figure] The job definition script file being edited is in a directory for which the user does not have write permissions.

[Figure] The job definition script file being edited is in a compressed folder.

Notes about specifying files and paths

Do not use a file name that begins with a dot (.).
The permitted maximum length for path names must comply with the specifications of the OS being used.
The maximum file name length is 246 bytes (Windows only).
Do not use reserved device names (such as CON, AUX, and NUL) for file names (Windows only).
Do not use NTFS streams for file names (Windows only).
Do not use hard links, symbolic links, or junctions (Windows only).
You can use UNC names for file names and path names (example: \\computer-name\shared-name\file-name); however, make sure that a path name specified in this format does not end with shared-name (or shared-name\). The cd standard shell command does not support the UNC format. (Windows only)

Examples of valid specification:

\\server\share\dir

\\10.111.222.33\share\dir

Examples of invalid specification:

\\server\share

\\10.111.222.33\share
Do not use UNC names for the folder path names for traces, system execution logs, spool, and temporary files (Windows only).

To Page Top

(2) Handling of files that are larger than 2 GB (large files)

JP1/Advanced Shell supports some of the large files (that are larger than 2 GB). Of the files supported by JP1/Advanced Shell, the files and commands that correspond to large files are as follows:

Of the files created in the spool job directories, files STDOUT, STDERR, step-number_step-name_STDOUT, and step-number_step-name_STDERR to which user data is output

Note that large files might adversely affect the overall system processing because the jobs executed from JP1/AJS3 transfer the contents of files STDERR and step-number_step-name_STDERR to JP1/AJS3's manager host. For details, see the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Note that when you use the spool job creation suppression functionality, no spool job is created when the job definition script is run. For details about the spool job creation suppression functionality, see 2.6.8(1)(a) Determining whether the spool job creation suppression functionality is to be used.
In redirect specifications, the files specified in >file, < file, >>file, >|file, <>file, n>file, and n<file
Files specified in conditional expressions other than -t fd of the conditional expressions that are evaluated with the test or let command
Files that are allocated by the extended script commands #-adsh_file, #-adsh_file_temp, and #-adsh_spoolfile
Files handled by UNIX-compatible commands

However, a file cannot be exceed 2 GB if it is used for the following operations:
- Editing and displaying the number of bytes that exceeds 2 GB
- Editing and displaying the number of lines that exceed 2 GB
- Executing UNIX commands (such as diff and sort) that use a large amount of memory when large-sized files are specified

Whether large files are supported depends on the types of file systems and OS settings (example: ulimit setting). Before you design your operations, check if your environment supports large files.

To Page Top