Error Messages for Component ID 0509

0509-004 Cannot open the directory /dev

Possible Causes

• You entered the ps command, which relies on information contained in the /dev directory, but access to the /dev directory was not granted by the system.

Procedures for Recovery

• Ensure that you have the proper file permissions on the /dev directory.
  1. Enter the ls -ld /dev command to see the permissions. The output should look similar to the following:

     drwxrwxr-x 3 root system 2048 Feb 20 10:58 /dev

  2. If the ownership and the permissions do not match the preceding output, enter the su command to change to the root user.
  3. Use the chown, chgrp, and chmod commands to give the proper ownership and permissions. For more information, see "Recovering from File and Directory Permission Errors".
  4. Reenter the ps command.

0509-005 Cannot change the current directory to /dev

Possible Causes

• You used the ps command, but you do not have execute permission on the /dev directory.

Procedures for Recovery

• Obtain execute permission on the /dev directory.

  Follow the procedure in "Recovering from File and Directory Permission Errors".

0509-010 An error occurred on the read process

Possible Causes

You used the ps command, and one of the following occurred:

• There was a physical problem on the disk.
• The ps_data file is set to Null.

Procedures for Recovery

• Run disk diagnostics using the fsck or dfsk command and correct the physical problem on the disk.
• Reset the ps_data file.
  1. Enter the rm ps_data command to remove the ps_data file.
  2. Enter the su command to change to the root user, and reenter the ps command.

0509-011 An error occurred on the write process. Check path name and permissions

Possible Causes

• The ps command failed in writing the internal database file even though it succeeded in opening the file.

Procedures for Recovery

• Ensure that the correct /etc file is mounted in the file system and has enough space.
  1. Enter the df /etc command to check if the /etc file is mounted and how much of the file system is being used.
  2. If the file is full, remove unnecessary files from the file system or increase the size of the file system by using the "System Management Interface Tool"(SMIT).
  3. Reenter the ps command.

0509-013 Permission denied

Possible Causes

• You are not the root user and you tried to use the kill command to stop a process that you did not start.
• You tried to stop a process and entered an incorrect process ID (PID) number.

Procedures for Recovery

• Change to the root user and reissue the kill command.
  1. Enter the su command to change to the root user.
  2. Reissue the kill command.
• Obtain a valid process ID number and reissue the kill command.
  1. Enter the ps -eaf command to list the currently running processes.
  2. Select the process you wish to stop.
  3. Reissue the kill command with the proper PID number.

0509-015 The specified process does not exist

Possible Causes

• You used the kill command to stop a process with a nonexistent or invalid process ID (PID).

Procedures for Recovery

• Locate a valid PID, then specify it with the kill command to stop the process.
  1. Enter the ps -eaf command to list the existing processes with their PIDs.
  2. Locate the process that you wish to stop.
  3. Enter the kill command, specifying the correct PID.

     Note: You can only use the kill command on processes that you own. You may need to enter the su command to change to the root user (which owns all processes) or to the user who owns the process you wish to stop.

0509-018 Flag must be numeric

Possible Causes

• You entered the nice command with a flag that is not numeric.

Procedures for Recovery

• Enter a numeric flag after the nice command, as in the following example:

  nice -10 CommandArgument

0509-019 Cannot open or create the nohup.out file

Possible Causes

You used the nohup command, and one of the following occurred:

• Your HOME variable is not set, and you do not have write permission on your home directory.
• Your HOME variable is set, but you do not have write permission on your home directory.
• Your HOME variable is set and a nohup.out file already exists in your home directory, but you do not have write permission on the $HOME/nohup.out file.

Procedures for Recovery

• Ensure that your HOME environment variable reflects your home directory.
  1. Enter the echo $HOME command to see the value of your HOME environment variable.
  2. If the two do not match, enter export HOME=PathName, where PathName is the full path of your home directory.
  3. Reissue the nohup command.
• Obtain write permission on the current directory.
  1. Enter the ls -ld command to display the permissions on the current directory.
  2. If you do not have write permission, see "Recovering from File and Directory Permission Errors".
  3. Reissue the nohup command.
• Verify that the nohup.out file exists and obtain write permission.
  1. Enter the ls -l nohup.out command to verify that the nohup.out file exists in the current directory and that you have write permission on the file.
  2. If the nohup.out file exists but you do not have write permission, see "Recovering from File and Directory Permission Errors".
  3. Reissue the nohup command.

     Note: The nohup command creates a nohup.out file in the current directory. If the nohup.out file exists, the output from the nohup command is appended to the existing file.

0509-029 Alignment of text does not match required alignment

Possible Causes

• The format of the code for an executable is not correct.

Procedures for Recovery

• Recompile the code using the ld command.

0509-039 The process or process group String is not an integer

Possible Causes

• You entered the renice command to reset the scheduling priority of one or more running processes, but specified an invalid process ID (PID) or process group ID with the -pflag.

Procedures for Recovery

• Reenter the renice command, specifying a valid PID.
  1. Enter the ps -eaf command to list the system processes and obtain a valid PID.
  2. Reenter the renice command, specifying a valid PID.

0509-040 Number: getpriority: The process does not exist

Possible Causes

• You attempted to change the renice value of an invalid or nonexistent process.

Procedures for Recovery

• Reenter the renice command, specifying a valid process ID (PID) and options.
  1. Use the ps -eaf command to list the system processes and obtain a valid PID.
  2. Reenter the renice command using a valid PID and valid command options.

0509-041 ProgramName: 0509-041: Number

Possible Causes

• You used the renice command and do not have root user authority.

Procedures for Recovery

• Change to root and reenter the renice command.
  1. Enter the su command to change to root.
  2. Reenter the renice command.

0509-048 Flag -F was used with invalid list

Possible Causes

• You specified an invalid or unknown name or names of field specifiers.

Procedures for Recovery

• Use the proper recognized name with the -F flag when using the ps command.
  1. Use the following names with the -F flag:

     args	ppid
     comm	rgname
     etime	runame
     gname	time
     nice	tty
     pcpu	uname
     pgid	vsz
     pid

  2. See the ps command for -F flag descriptions and use of the field specifier names.