1.2.4 Confirming the files that can be used in JP1/Advanced Shell

The following lists the files that are used in JP1/Advanced Shell, and provides notes on specifying files and paths.

Organization of this subsection

(1) List of files used in JP1/Advanced Shell
(2) Notes on file systems

(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 the description in Files used in JP1/Advanced Shell in the manual JP1/Advanced Shell.

Table 1‒2: Files used in JP1/Advanced Shell
File name (icon)	Extension	File contents
Job definition script file ()	`.ash`	A job definition script. The user can assign any file name.
Environment file^#	`.ase`	JP1/Advanced Shell environment settings.
System environment file	`.ase`	System environment settings.
Coverage information file	`.asc`	Coverage environment information for JP1/Advanced Shell.
Debugging information file	`.asd`	Debugging information used by the editor (development environment)
System execution log^#	`.log`	Log information that provides overall batch job execution logs for the system administrator.
Trace information^#	`.log`	JP1/Advanced Shell's internal trace logs.
Temporary file	`.tmp`	Temporary file used internally by the system.
Coverage display temporary file	`.txt`	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`	Log information that is collected when the user-reply functionality's management daemon is started and stopped.
`pid` file (UNIX only)	`.pid`	File used by the user-reply functionality management daemon and `adshmdctl` command.
Log of the application-execution agent functionality^# (Windows execution environment only)	.log	Internal log of the application-execution agent functionality.

#: You can collect these files by using the adshcollect command. For details about how to collect the files, see the description in adshcollect command in the manual JP1/Advanced Shell.

Notes about specifying files and paths

As the directory delimiter, you can use a backslash (\)^# for Windows or a forward slash (/) for UNIX. If you use other characters, the operation cannot be guaranteed.
- If you use a backslash (\) as the directory delimiter for UNIX, the character will not be recognized as the directory delimiter and JP1/Advanced Shell will not operate correctly.
- If you use a forward slash (/) as the directory delimiter for Windows, the character might be recognized as the directory delimiter. Note that, depending on how the forward slash is used, the character might not be recognized as the directory delimiter and JP1/Advanced Shell might not operate correctly.
#:

A backslash (\) specified in a job definition script is considered an escape character. For this reason, you need to specify two consecutive backslashes (\\) or enclose the character string that includes the backslash in single quotation marks (').
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 the junction functionality (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)

UNC formats that can be used:

\\server\share\dir

\\10.111.222.33\share\dir

UNC formats that cannot be used:

\\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) Notes on file systems

Be careful when using JP1/Advanced Shell with either of the following file systems:

NFS

Not supported.
HSFS

When using HSFS, note the following:
- You cannot install JP1/Advanced Shell on HSFS.
- You cannot create a system execution log or traces on HSFS.
- If you use the user-reply functionality, you cannot specify a directory located on HSFS as the spool job directory.
- If you are using a version earlier than HSFS 07-00 and you want to use a UNIX-compatible command to reference or update the files and directories on HSFS, you will need to specify NOCACHE for the HSFS system option CPFS_CACHE_POLICY beforehand.
- If you are using HSFS 07-00 or later and you want to use a UNIX-compatible command to reference or update the files and directories on HSFS, you will need to specify 0 for the HSFS system option CPFS_COMPAT_LINKCNT beforehand. By default, 0 is specified for CPFS_COMPAT_LINKCNT.

To Page Top