WebSphere Process Management and Spawning Facility messages

PROC0001E: User: [{0}] does not appear to be valid on this system. Process could not be created.
Explanation: An invalid username was passed into the process creation parameters. The user does not appear to exist on the system.
User Response: A valid user name needs to be entered into the process creation parameters.

PROC0002E: Group: [{0}] does not appear to be valid on this system. Process could not be created.
Explanation: An invalid group name was passed into the process creation parameters. The group does not appear to exist on the system.
User Response: A valid group name needs to be entered into the process creation parameters.

PROC0003E: Working Directory: [{0}] does not appear to be valid, or accessible by the process. Process could not be created.
Explanation: An invalid working directory was passed into the process creation parameters. The working directory does not appear to exist on the system or the user id running the process does not have access to the directory.
User Response: A valid working directory needs to be entered into the process creation parameters.

PROC0004E: Executable: [{0}] does not appear to be a valid executable. Process could not be created.
Explanation: An invalid executable was passed into the process creation parameters. The executable either does not exist or is not executable by the current user.
User Response: A valid executable needs to be entered into the creation parameters. Check the executable and its execution permissions

PROC0005E: Priority: [{0}] does not appear to be a valid value for this system or could not be set. Process could not be created.
Explanation: An invalid priority was passed into the process creation parameters. The operating system would not accept it.
User Response: A valid process priority needs to be entered into the creation parameters.

PROC0006E: Process Group: [{0}] is not valid. Process could not be created.
Explanation: An invalid process group was passed into the process creation parameters. The operating system would not accept it.
User Response: A valid process group needs to be entered into the creation parameters.

PROC0007E: Some files required by the process or the process definition were inaccessible. Please check the standard in, out, and error file redirects and directories. Process could not be created.
Explanation: Some files the process needs for execution were not accessible by the process. This is commonly log files (redirects of standard out and error, or directories they reside in) that are not set readable and writable to the use rid that will be running the process that will access them.
User Response: Check the standard out and error redirection files and their directories to make sure they're readable and writable by the user id that will be running the process.

PROC0008E: The operating system reported too many file handles are already open. Process could not be created.
Explanation: The operating system refused to create a new process due to too many file handles already being open.
User Response: Increase the maximum number of allowable file handles, or reduce the number of active processes on the system.

PROC0009E: The operating system reported not enough free memory to create the process.
Explanation: The operating system refused to create a new process due to lack of memory to contain the new process.
User Response: Reduce the memory usage on the system.

PROC0010E: Process: [{0}] is not on the system. It could not be bound to.
Explanation: A non-existent PID was passed into the process code to bind to for monitoring.
User Response: A valid PID needs to be passed to the binding call.

PROC0011E: Process termination failed. The current effective UID attempting to terminate the process [{0}] does not have authority to terminate it.
Explanation: A failure in termination has occurred.
User Response: Manually kill it through the operating system mechanisms under a user with authority to terminate the process.

PROC0012E: The parameters passed in to terminate appear to be invalid or null.
Explanation: The parameters used to terminate a process appear invalid or null, therefore termination cannot be done.
User Response: No user action.

PROC0013E: Process termination failed. The error returned from native was: {0}.
Explanation: A failure in termination has occurred.
User Response: Manually kill it through the operating system mechanisms.

PROC0014E: Process termination failed. The process identified by [{0}] did not terminate in a timely manner. It still appears to be active on the system.
Explanation: A failure in termination has occurred.
User Response: Manually kill it through the operating system mechanisms.

PROC0015E: The process creation failed. Some files that are required by the process or the process definition are inaccessible, such as standard in, out, and error redirects. Verify that user [{0}] has read and write access to the following items: Working directory: [{1}]. Standard input: [{2}]. Standard output: [{3}]. Standard error: [{4}]. Empty [] indicates the value is not set and the operating system defaults are used.
Explanation: Some files that the process needs to run are not accessible. These files are commonly log files that are not readable and writeable to the user ID that runs the process.
User Response: Check the standard out and error redirection files and the parent directories to make sure that these files are readable and writeable by the user ID that runs the process.

PROC0016E: The process creation failed. Some files that are required by the process or the process definition are inaccessible, such as standard in, out, and error redirects. Verify that the current user has read and write access to the following items: Working directory: [{1}]. Standard input: [{2}]. Standard output: [{3}]. Standard error: [{4}]. Empty [] indicates that the value is not set and the operating system defaults are used.
Explanation: Some files that the process needs to run are not accessible. These files are commonly log files that are not readable and writeable to the user ID that runs the process.
User Response: Check the standard out and error redirection files and the parent directories to make sure that these files are readable and writeable by the user ID that runs the process.