12.4.1 Details of errors (Windows)

The messages issued by JP1/Advanced Shell might contain information about the C run-time function and Win32^(R) API errors.

The table below lists and describes the causes of typical C run-time function errors that are most likely to occur in a JP1/Advanced Shell environment (Windows) and the actions to be taken. For information about other errors that are not listed in the table and Win32 API errors, see the documentation for the Windows being used.

Table 12‒5: Causes of and actions in response to C run-time function errors (Windows)
Mnemonic	Error details	Cause	Action
`ENOENT`	`No such file or directory`	The following causes are expected. The file or directory is not found. The nesting of the symbolic link is too deep.	Take the following countermeasures: Check the existence of the file. Change the number of nests of the symbolic link so that the upper limit of the OS is not exceeded.
`EIO`	`Input/Output error`	An input/output error occurred.	Take appropriate action according to the Windows or hardware information.
`ENXIO`	`No such device or address`	There is no access permission for the file.	Check if there is such a device or that the device is enabled. If the device is disabled, enable it. For other causes, check the documentation for the Windows being used.
`E2BIG`	`Arg list too long`	There is a shortage of area for the processing program's arguments or environment variables.	Check the processing program's arguments. Check and, if necessary, revise the environment variables specified in parameters such as `export` and the usage of extended script commands in the file management function, and then delete any unneeded environment variable settings.
`EAGAIN`	`Resource temporarily unavailable`	There are too many processes, or a temporary memory shortage has occurred.	If the error recurs when the command is re-executed, terminate unneeded processes.
`ENOMEM`	`Not enough space`	Possible causes are as follows: A new process cannot be created due to a shortage of swap area or virtual memory. There are too many processes, or some processes are using too much memory.	Take the following actions: If there is a shortage of swap area or virtual memory, expand it. If the swap area or virtual memory cannot be expanded, terminate unneeded processes. If some processes are using too much memory, evaluate whether they can be terminated.
`EACCES`	`Permission denied`	Possible causes are as follows: The access permission is invalid. A file must be specified in an argument of a JP1/Advanced Shell command, but a directory was specified. The extension of the file that is to be executed as a command is not `exe`, `bat`, `cmd`, or `com`. You accessed a symbolic link in which the link destination of the symbolic link to a file or the link destination of a symbolic link to a directory is a normal file.	Take the following actions: Check if the file access permission is correct. Check the argument of the JP1/Advanced Shell command to determine whether a directory is specified instead of a file. If you specified the `CHILDJOB_SHEBANG` parameter, check the specified parameter value and `#!` `executable-program-path` at the beginning of the file whose execution was attempted. When specifying the `CHILDJOB_EXT` parameter, check the specification value of the parameter and the extension of the file to be executed. Check if the reference destination of the symbolic link is correct.
`EFAULT`	`Bad address`	An attempt was made to write data into an inaccessible area. The disk to which the data is to be written might have been disconnected.	If disks are being switched during system switchover, ignore this error message because there is no problem. If you disconnected the disk by mistake, restore the corresponding file from its backup or initialize the file first before using it. If neither of the above applies, contact the system administrator.
`EEXIST`	`File exists`	An attempt was made to create a file, but the file already exists.	Rename the file and re-execute the command. If the existing file is not needed, delete it and re-execute the command.
`EINVAL`	`Invalid argument`	The following causes are expected. An error was detected in the memory management information. The nesting of the symbolic link is too deep. A user who does not have the administrative role for creating symbolic links attempted to create, copy, or move a symbolic link. A user attempted to create, copy, or move a symbolic link on or to a file system other than NTFS.	Take the following countermeasures: Contact the system administrator. Change the number of nests of the symbolic link so that the upper limit of the OS is not exceeded. The operation must be executed as a user having an administrative role for creating symbolic links. Use NTFS when using a symbolic link.
`ENFILE`	`Too many open files in system`	The number of open files exceeded the maximum.	Check the total number of files in use in the system and close unneeded files.
`EMFILE`	`Too many open files`	Too many files are open in the corresponding process.	Contact the system administrator.
`EFBIG`	`File too large`	The file size exceeded the system limit.	Check and, if necessary, revise the size of a file to be used.
`ENOSPC`	`No space left on device`	There is not enough free space in the file system.	Allocate more free space.

To Page Top