Error Messages for Component ID 0402

0402-001 You cannot trap on SIGSEGV

Possible Causes

• You specified an illegal trap command to the SIGSEGV signal (signal number 11) in a shell script.

Procedures for Recovery

• Remove the illegal trap command from your shell script, and restart your system.
  1. Using an editor, locate the illegal trap command and delete it from the shell script. The illegal trap command looks similar to the following:

     trap 'echo SIGSEGV received' 11

     Note: To save the shell script, you need write permission to the file. You may need to use the su command to change to the root user or to a user who has write permission.

  2. Restart your system to remove the trap.

0402-002 Cannot find FileName

Possible Causes

• You attempted to use a file in a directory that is not listed in your PATH environment variable.
• You entered the type command with a file for which you do not have execute permission.
• You attempted to use a file that does not exist.

Procedures for Recovery

• Add the directory where the file is located to your PATH variable.
  1. Run the echo $PATH command to determine which directories are in your PATH variable.
  2. If the directory where the file resides is not listed, enter the PATH=DirectoryName: $PATH; export PATH command, where DirectoryName specifies the directory that you wish to add.
  3. If you want the DirectoryName directory included in your PATH variable every time you create a new session, edit your .profile file and change the line where the PATH variable is set to include the DirectoryName directory. Otherwise, this modification is active only for your current session.
• Add execute permissions to the file.
  1. Run the ls -ld command to determine the permissions on the file.
  2. Run the su command to change to a user that has execute permission on the file, or run the chmod +x command to give yourself execute permission on the file. See "Recovering from File and Directory Permission Errors" .
• Create the file.
  1. Using an editor, create and save the file.
  2. Run the ls -ld command to ensure that you have permissions on the file. If needed, run the chmod +x command to give yourself execute permission on the file.

0402-004 There is not enough memory available now

Possible Causes

• A process running under the Bourne shell (bsh) requires more memory than is available on the system. The following may cause this condition:
  • A process is being forked and the fork fails with errno ENOMEM.
  • A process is being run and the run fails with errno ENOMEM.
  • A setbrk() is being performed to increase the shell stack space and fails.

Procedures for Recovery

• Increase the amount of memory allocated per process.
• Increase the amount of physical memory in your system.

  Follow the procedures described in "Recovering from Insufficient Memory Errors".

0402-011 Cannot create the specified file

Possible Causes

• The path for the specified file name does not exist.
• The path exists, but you do not have permission to create a file within the specified path.

Procedures for Recovery

• Ensure that the path for the specified file exists.

  Run the ls command to list each directory in your path. If the path is valid, a list of the contents of the directory is displayed. If the path does not exist, the following message is displayed:

  The file /Directory1/Directory2 does not exist

  If the path does not exist, further isolate the problem by using the ls command for each directory in the path. Use the mkdir command to create any directories that are missing from the path. If the specified path is valid, the error message indicates that you do not have permission to create a file within that path.

• Obtain permission to create a file within the specified path.

Run the ls -ld command to display the permissions for the specified path. If you do not have access permission to a file or directory, enter the su command to switch to the root user or owner of the file or directory. Then use the chmod command to change permissions. See "File and Directory Access Modes" in AIX Version 4.3 System User's Guide: Operating System and Devices for more detailed information.

0402-021 Cannot run the command as specified

Possible Causes

Using the Bourne shell, you issued from the command line:

/Path/Command

where path is the path name of the command you wanted to run, but you did not have execute permission for the command.

Procedures for Recovery

• You need to be the root user to run this command.

  Enter the su command to switch to the root user or owner of the file or directory.

• The command has group execute permission.

  Ask your system administrator to include you as a member of this group.

0402-026 The specified data is not a valid identifier

Possible Causes

• Using the Bourne shell, you issued the following command:

  export Variable=Value

• Using the Bourne shell, you attempted to use a variable that does not begin with an alphanumeric character, or has unsupported characters.
• Using the Bourne shell, you attempted to assign a variable as read-only, without first setting the value of the variable. For example:

  readonly Variable=Value

Procedures for Recovery

• When using the Bourne shell, the syntax for the export command is:

  Variable=Value
  export Variable

• Change the variable name to begin with a letter or underscore ( _ ), and remove any invalid characters.
• When using the Bourne shell, the syntax for the readonly command is:

  Variable=Value
  readonly Variable