Chapter 4. Recovery Methods for Seven-Digit Error Messages

0105-706

AIX Operating system error code

Possible Causes

• You attempted to start an SNA attachment without a configured data link control.

• You attempted to start an SNA attachment without a modem link.

• You attempted to start an SNA attachment with an incorrect remote setup.

Procedures for Recovery

• Configure a data link control.

• Verify the modem link.

• Correct the remote setup.

  Verify that the logical and physical characteristics match the remote.

  The syslog file has physical and logical netware failures. Make sure that both calling and listening attachments have names defined in the physical link profile under LOCAL LINK name (if the attachment routing is by name).

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 PATHvariable.

  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

0403-005

Cannot create the specified file

Possible Causes

• From the command line, you issued the following command:

  cat Filename > Printdevice

  The printer device was either not attached, was busy, was down, or was on the network.

• You attempted to create a file in a directory for which you do not have write or execute permissions.

• You attempted to write to a file system that is mounted as read-only.

Procedures for Recovery

• Ensure that the printer device is attached to the system.

  Run the lpstat command to check if the printer is busy, or if the print queue is down. If the printer is busy, wait until the currently queued job is complete, and rerun the command.

  If the print queue is down, run the su command to become the root user, and then run the qadm command to restart the queue:

  qadm -U Queuename

• Run the su command and become the root user.

  Add read/write permission to the directory and to the parent directories.

• Unmount the file system with the unmount <filesystem> command.

  Remount the file system with read/write access:

  mount -o rw Filesystem Directory

0403-011

The specified substitution is not valid for this command

Possible Causes

• You attempted to change directories using a pattern-matching character that incorrectly specified the directory name.

Procedures for Recovery

• Verify the directory name and run the command again.

  For example, if you have a directory chap1.boo and a directory chap10.boo, you cannot change directories by typing cd chap*. You must type cd chap1.*.

0460-018

-C option requires an argument - CardID

Possible Causes

• adfutil was invoked without an argument to the -c option.

Procedures for Recovery

• If you started adfutil with the -c option and have the card identifier as:

  adfutil -c

  it should be changed to:

  adfutil -c cardidxxxx

• If the -c option is supplied, a card identifier must be specified.

0481-067

Cannot change to the DirectoryName directory

Possible Causes

• You entered the at, cronadm, crontab, or atq command and either the directory /usr/spool/cron/crontabsor the directory /usr/spool/cron/atjobs does not exist.

Procedures for Recovery

Ensure that the directories under the /usr/spool/cron exist with the correct attributes, and reenter the command.

1. Enter the ls -al1 /usr/spool/cron command to list the directories under the /usr/spool/cron directory. The crontabs or atjobs directories should display with permissions set to drwxrwx---, ownership set to bin, and group set to cron.

2. Enter the su command to change to the root user.

3. Enter the cd /usr/spool/cron command to change to the proper directory.

4. If the crontabs directory is missing, enter the mkdir crontabs command to create it.

5. If the atjobs directory is missing, enter the mkdir atjobs command to create it.

6. Enter the chown bin.cron * command to give the proper ownership to both directories.

7. Enter the chmod 770 * command to give the proper permissions on both directories.

8. Reenter the at, cronadm, crontab or atq command.

0481-071

Cannot access the FileName file

Possible Causes

• You used the crontab command and specified a file name that does not exist, or is not in the current directory.

Procedures for Recovery

Ensure that the file exists, and reissue the crontab command.

1. To get a list of valid file names, enter the ls command in the directory from which the crontab command was issued.

2. Reissue the crontab command using a valid file name.

Note: If the file does not exist in the directory from which the crontab command is issued, you must specify the full path name or the complete relative path name. For more information on relative path names, see Using BNU Path Names in AIX Version 4.3 System User's Guide: Communications and Networks.

0481-074

Reached an end-of-line that is not expected

Possible Causes

• The crontab file in the /usr/spool/cron/crontabs file contains a syntax error.

• The crontab file in the /usr/spool/cron/crontabs file is not in text format.

Procedures for Recovery

• Edit the crontab file to remove the syntax error.

  Enter the crontab -ecommand to edit the crontab file and correct the syntax error.

• Remove the old crontab file and create a new one.

  1. Enter the crontab -r command to remove the existing crontab file.

  2. Create a new file by using any editor. Be sure to save your new file.

  3. Convert your new file to a crontab file by entering the crontab NewFile command.

0481-079

Reached a symbol that is not expected

Possible Causes

• An incorrect entry exists in the crontab file.

Procedures for Recovery

Edit the crontab file and reenter the crontab command.

1. Correct the incorrect entry in the crontab file using the crontab -e command for your default crontab file, or using an editor if you specified another file when the crontab command was issued.

2. Reenter the crontab command, using the corrected file as input.

0481-103

Cannot open a file in the DirectoryName directory

Possible Causes

• The at command cannot create a temporary file in the /usr/spool/cron/atjobs directory because the directory does not exist.

• You have issued the crontab -l or-v command but have not placed any cron jobs in the crontab directory.

Procedures for Recovery

• Create the /usr/spool/cron/atjobs directory.

  1. Enter the su command to change to the root user.

  2. Enter the mkdir /usr/spool/cron/atjobs command to create the missing directory.

• Create a new crontab file by doing one of the following:

  • Enter the crontab -e command to create a new crontab file or to edit an existing one.

  • Enter the su command to change to the root user. The root user has access to all files.

0481-106

Your user identification is not valid

Possible Causes

• The /etc/passwd file does not have an appropriate entry for your login name.

Procedures for Recovery

• Ensure that the /etc/passwd file contains your login name and the correct user identification number (uid).

  1. Enter the id command to display your UID.

  2. Enter the vi /etc/passwd command to see the /etc/passwd file.

  3. Ensure that the UID obtained by the id command is the same one that is in the /etc/passwd file. If the UID in the /etc/passwd file does not match the UID obtained by the id command, edit the /etc/passwd file by doing the following:

     1. Enter the su command to change to the root user.

     2. Enter the vi /etc/passwd command to edit the /etc/passwd file using the vi editor. (You can use another editor.) Change your UID if it is incorrect, or add your uid to the /etc/passwd if it is missing, using any existing names as a template.

     OR

     Use the System Management Interface Tool (SMIT) to delete and recreate the user.

     Note: The /etc/passwd file normally is accessible only to the system administrator. An ordinary user cannot take any corrective measures without root user privileges.

     Commands that access the /etc/passwd file (such as the at, atq, atrm, cronadm, or crontab commands) to get your user identification number (UID) display this error if the /etc/passwd file has been modified. The modification removed your login name and occurred between the time you logged on and the time you issued one of these commands.

0481-115

Specify a queue name with the -q flag

Possible Causes

• You specified the -q flag at the command line to schedule a job for submission to a particular queue, but did not specify a queue name.

Procedures for Recovery

• Specify the -q flag with a queue name, with a, b, e, and f available as queue names.

  By default, at jobs are scheduled in the a queue. The b, c, and dqueues are reserved for batch jobs, cron jobs, and sync jobs, respectively. The e queue is used to run the command as a ksh job, and the f queue is used to run the command as a csh job.

0481-124

Cannot create the cron file in the /usr/spool/cron/crontabs directory

Possible Causes

• You entered the crontab command and the crontabs directory does not exist.

• The file system containing the directory is full.

Procedures for Recovery

• Ensure that the crontabs directory exists.

  1. Use the ls-l command to check the crontabs directory. This directory should display with permissions set to drwxrwx---, ownership set to bin, and group set to cron.

  2. If the crontabs directory does not exist, create it and give it the proper permission, ownership, and group by doing the following:

     1. Enter the su command to change to the root user.

     2. Use the cd command to change to the proper directory.

     3. Enter the mkdir crontabs command to create the directory.

     4. Enter the chown bin.cron crontabs command to give the proper ownership to the directory.

     5. Enter the chmod 770 crontabs command to give the proper permissions on the directory.

• Verify that there is space left on the file system and the status is correct.

  1. Enter the df command on the command line to list the available space in the /var file system.

  2. If there is no available space on the file system containing the crontabs directory, remove any unnecessary files.

0481-125

There is an error in the minute or hour specification

Possible Causes

• You used the at command and specified an invalid minute or hour setting.

Procedures for Recovery

• Reissue the at command with hours and minutes in the appropriate format.

  The format for an at command using hours is hhmm[.SS] where:

  hh	Specifies the hour of the day (00 through 23).
  mm	Specifies the minute of the hour (00 through 59).
  SS	Specifies the second of the minute (00 through 59).

0481-126

Specify an hour in the range 1 through 12

Possible Causes

• You entered the at command, specified the am or pm suffix in the required Time parameter, but did not specify an hour between 1 and 12.

Procedures for Recovery

• Reissue the at command using a valid time parameter.

  Do one of the following:

  • Specify an hour between 1 and 12 if you use the am or pm suffix in the Time parameter.

  • Omit the use of the am or pm suffix in the Time parameter and use the 24-hour clock (the default setting).

0481-127

There is an error in the month or the day specifications

Possible Causes

• You used the at command, but specified a day that does not exist for a given month, or is not between 1 and 31.

Procedures for Recovery

• Reenter the at command with a day that occurs in the specified month.

  The format for the at command using months is MMDDhhmm[.SS], where:

  MM	Specifies the month of the year (01 through 12).
  DD	Specifies the day of the month (01 through 31).
  hh	Specifies the hour of the day (00 through 23).
  mm	Specifies the minute of the hour (00 through 59).
  SS	Specifies the second of the minute (00 through 59).

0481-129

String is not a recognized date or time specification

Possible Causes

• You issued the at command with an incorrect date or time flag.

Procedures for Recovery

• Ensure that you specify the date and time correctly with the at command.

  The format for the at command is:

  [[CC]YY]MMDDhhmm[.SS] where

  CC	Specifies the first two digits of the year (the century).
  YY	Specifies the last two digits of the year (the decade).
  MM	Specifies the month of the year (01 through 12).
  DD	Specifies the day of the month (01 through 31).
  hh	Specifies the hour of the day (00 through 23).
  mm	Specifies the minute of the hour (00 through 59).
  SS	Specifies the second of the minute (00 through 59).

  Note: The CC and YY digits are optional.

  For specific format information see the at command in AIX Commands Reference.

0481-130

Specify the a, b, e, or f queue

Possible Causes

• You entered the at command, specifying an invalid queue name with the -q flag.

Procedures for Recovery

• Reissue the at command, using a, b, e, or f as the queue name after the -q flag.

0481-131

The specified flags cannot be used together

Possible Causes

• You used the at command but specified some mutually exclusive flags at the same time.

Procedures for Recovery

• Reenter the at command but do not specify mutually exclusive flags.

  The following sets of flags for the at command are mutually exclusive:

  -c, -k, -qe, -qf, -r, -s

  -l, -r, -s

  Do not specify more than one flag from each set with the at command.

0481-151

Cannot find or access /bin/ksh

Possible Causes

• You do not have permission to access the /bin/ksh file.

• The /bin/ksh file does not exist.

Procedures for Recovery

• Change permissions on the /bin/ksh file.

  1. Enter the su command to change to the root user.

  2. Use the chmod command to change permissions. Follow the procedures described in Recovering from File and Directory Permission Errors .

• Create a new /bin/ksh file.

  Create a new /bin/ksh file using the original system installation software.

  OR

  Copy the /bin/ksh file from another machine that contains the same version of the operating system.

0481-501

Cannot find or access /bin/csh

Possible Causes

• You do not have permission to access the /bin/csh file.

• The /bin/csh file does not exist.

Procedures for Recovery

• Change permissions on the /bin/csh file.

  1. Enter the su command to change to the root user.

  2. Use the chmod command to change permissions. Follow the procedures described in Recovering from File and Directory Permission Errors .

• Create a new /bin/csh file.

  Create a new /bin/csh file using the original system installation software.

  OR

  Copy the /bin/csh file from another machine that contains the same version of the operating system.

0503-006

Cannot create the directory DirectoryName. Check path name and permissions

Possible Causes

• When installing or rejecting your software, your command specified a directory to which you do not have write access.

Procedures for Recovery

• If you are not logged in as the root user, log in as root and reissue your command.

• Edit the /etc/filesystems file to check if the file system where the directory is located is mounted as read-only.

• If the file system is mounted as read-only, then change it to read-write.

  1. Unmount the file system by using the unmount command.

  2. Mount the file system by using the mount command.

  3. Reissue your command.

0503-020

There is not enough disk space for installation of the software on file system FileSystem

Possible Causes

• You were unable to install the software on the specific file system mentioned in the error message because you ran out of space.

Procedures for Recovery

• Add -X to your command if you are installing software through the command line in order to extend the size of the file system.

• If you are using System Management Interface Tool (SMIT), then set the EXTEND file systems if space needed? attribute to yes.

0503-350

installp: An error occurred while running the restore command

Possible Causes

• You attempted to run the installp command with a damaged tape or drive.

• You attempted to run the installp command but the /var or /tmp directory is too small.

• You attempted to run the installp command but you had too little paging space.

Procedures for Recovery

• Fix the tape or drive.

• Increase the size of the /var or /tmp directory.

• Increase the paging space.

0506-204

Specify a vfs type

Possible Causes

• The mkfs command cannot resolve the virtual file system (VFS) type.

Procedures for Recovery

• Specify a valid file system type.

  Enter the mkfs -V VFSTypeName /dev/DeviceName command to create a new file system on the specified device. The new file system must be one of the types listed for that device in the filesystems file or must be specified by the mkfs command.

  Note: The vfs file lists the allowed file system types. The vfs file must contain the VFS type name you specify.

  If you use this option to recover from this error, you do not need to change the filesystems file.

• Ensure the filesystems file contains the vfs type.

  With an editor, check the filesystems file to see whether the stanza referring to the device parameter exists. If the stanza is not in the file, add it to the file. If the stanza exists, but does not contain a VFS line, add a line similar to the following:

  vfs = VFSTypeName

  The vfs file must contain the specified VFSTypeName.

0506-324

Cannot mount Device on DirectoryName

Possible Causes

• You attempted to mount a device, but you do not have root authority or you are not a member of the system group.

• You attempted to mount a directory over a regular file, for example:

  mount Directory File

• You tried to use a nonexistent file or directory as a mount point.

• A device (for example, a diskette drive) to be mounted is either not ready or is write- protected.

• You attempted to mount a file system that is already mounted.

Procedures for Recovery

• Run the id command from the command line to ensure that you have the correct authority.

• Ensure that the mount point that you specify for a directory is a directory, and the mount point for a file is a regular file.

• Create the file or directory to be used as the mount point.

• Ensure that the device is ready (for example, the diskette is in the drive) and is not write-protected.

0506-349

Cannot unmount String

Possible Causes

This error message is displayed with the following text:

Only the owner or a privileged user can perform the operation.

for one of the following reasons:

• You used the System Management Interface Tool (SMIT) to unmount a file system and do not own the file system, do not belong to the system group, or do not have access permissions.

• You used the unmount or umount command to unmount a file system and do not own the file system, do not belong to the system group, or do not have access permissions.

This error message is displayed with the following text:

A device is already mounted or cannot be unmounted.

for one of the following reasons:

• Using SMIT, you specified the name of a file system that has an active device mounted over it.

• You used the unmount or umount command to unmount a file system that has an active device mounted over it.

Procedures for Recovery

• Obtain the proper access permissions.

  1. Select the SMIT Physical and Logical Storage--> File Systems--> Unmount a File System--> NAME of file system to unmount menu option.

  2. Select List to display a list of available file systems.

  3. Choose a file system to unmount.

  4. Select Do to unmount the file system.

  OR

  1. Use the su command to change to the root user, or to a user who belongs to the system group and has write permission to the directory in which the file system is mounted.

  2. Use the umount or unmount command to unmount the file system.

• Remove active devices before unmounting a file system.

  1. Select the SMIT Physical and Logical Storage--> File Systems--> Unmount a File System--> NAME of file system to unmount menu option.

  2. Select List to display a list of available file systems.

  3. Select a file system to unmount.

  4. Select Do to unmount the file system.

  OR

  1. Use the ps -ef command to ensure that none of the files contained in the file system are being accessed by any user.

  2. When all file access stops, use the umount or unmount command to unmount the file system.

0506-519

Device open failed

Possible Causes

• You tried to mount or unmount a file system that may be damaged.

• You ran the ff or fsck command on a file system after modifying the /etc/filesystems file and specifying an incorrect device.

• You attempted to run the fsck command on a cdrfs (CD-ROM) file system.

Procedures for Recovery

• Run the fsck FileSystem command on the file system to check whether there are errors in the output.

  1. If the fsck output displays errors, reboot the system from the boot media. Select the Maintenance option, then select Access a Root Volume Group.

  2. After identifying the correct volume group, select Access this Volume Group and start a shell before mounting filesystems.

  3. Run the fsck command on all the file systems, including the damaged one.

  4. Enter exit after all the file systems are checked.

  5. Shut down the system:

     shutdown -Fr

• Ensure that the device specified in the /etc/filesystems file is correct, or use SMIT to remove and then recreate the file system.

• Check the /etc/filesystem file for the FileSystem stanza. If the vfs field is crdfs, do not run the fsck command.

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 described 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 -p flag.

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.

0511-023

Cannot write to the DirectoryName directory

Possible Causes

• The directory you specified using the cpio -p command does not exist.

• You do not have write access permissions in the directory you specified for copying files.

Procedures for Recovery

• Verify that the directory exists.

  Enter the ls -ld/ DirectoryName command to check if the directory exists. If it does not exist, create the directory with the mkdir DirectoryName command.

• If the directory exists, verify that you own the directory and that you have access permissions to it.

  If you are not the owner but you are in the group, enter the chmod 770 xxx command, where xxx is the directory on which you want to change the access permissions.

  If you are not the owner and are not in the group, enter the chmod 777 xxx command, where xxx is the directory on which you want to change the access permissions.

  For more information, see Recovering from File and Directory Permission Errors .

0511-037

Cannot read from the specified input

Possible Causes

• From the command line, you issued the cpio command, with the -c flag, to extract an archived file that was not created initially with the -c flag.

• You attempted to use the cpio command to extract archived files that were not created using the cpio format.

Procedures for Recovery

• Rerun the cpio command without the -c flag.

• Run one of the following formats from the command line to check the correct format of the file/device:

  For tar format:

  tar -tvf FileOrDeviceName

  For backup format:

  restore -Tv FileOrDeviceName

0511-038

Cannot write to the specified output

Possible Causes

• You issued the cpio command to create an archive but specified an incorrect blocking factor with the -C or -B flag.

• The tape is damaged.

Procedures for Recovery

• Use the tctl command to check the block size of the tape device.

  tctl -f /dev/rmt# status

• Use the -C# flag to specify a multiple block factor of the physical device, for example, if the tape block size is set to 1024, use the -C2 flag.

  Note: Do not use the -B flag if the tape device block size is 4096.

• Check the error log for tape errors:

  errpt -a

0511-051

The read failed

Possible Causes

• The tape is backed up on a tape device with a block size that differs from the one on which it is currently set.

• The value specified with either the bs, ibs, or obs flag is not a multiple of the block size of the tape device.

• The value specified for the fskip flag is greater than the number of end-of-file marks on the tape.

• The tape is damaged.

Procedures for Recovery

• Use the chdev command to change the block size on the tape device:

  chdev -1 rmt# -a block size=0

• Use the tctl command to check the block size of the tape device:

  tctl -f /dev/rmt# status

  Then, specify the value of the bs, ibs, or obs flag as a multiple of the block size.

• Use the tcopy command to check the number of files or records that can be accessed on tape.

• Check the error log for tape errors:

  errpt -a

0511-053

The write failed

Possible Causes

• From the command line, you issued the following command:

  dd if=Filename of=Device conv=block

  but did not specify the cbs parameter.

• You issued the dd command, but the length of the data was not a multiple of 512 bytes, and you did not use the conv=sync parameter.

• You issued the dd command with the obs or bs parameter, which did not have a corresponding value as a multiple of the tape device block size.

• You attempted to write data to a diskette with the dd command, but the length of the data was greater than the capacity of the diskette.

Procedures for Recovery

• Use the cbs=value parameter with the conv=block parameter.

• Use the conv=sync parameter if the data length is not a multiple of 512 bytes.

• Use the lsattr command to check the block size of the tape drive:

  lsattr -1 rmt# -E

  Specify the obs or bs parameter with a value that is a multiple of the tape block size.

• If the data is greater than the capacity of the diskette, use a different medium.

0511-079

The backup media may be damaged

Possible Causes

• From the command line, you issued the backup command naming a tape device with the block size set to 0, but specified a value with the -b flag that is larger than the maximum allowable write size for the tape device.

• From the command line, you issued the backup command naming a tape device, but specified a value with the -b flag that does not yield a whole number multiple of the tape device's physical block size.

• From the command line, you issued the following command:

  find File -print| backup -ivf FileSystem/FileName

  but the specified FileSystem was full.

• The backup media is damaged.

Procedures for Recovery

• Specify a value with the -b flag that does not exceed the maximum allowable write size for the tape device, or do not use this flag.

• Specify a value with the -b flag that yields a whole number multiple of the tape device's physical block size (-b Number, where Number is the number of 512-byte blocks).

  Note: You can use the lsattr command to check the physical block size of the device:

  lsattr -l rmt# -E

• Remove unnecessary files from the file system, or use the chfs command to increase the file system and rerun the backup command.

• Check the error log for media errors:

  errpt -a

• Use a different tape or disk to run the backup.

0511-080

Pathname is too long

Possible Causes

• During the backup process, the find command could not locate data because the path name specified was too long.

Procedures for Recovery

• Limit the path name to one that is less than 255 characters.

• Start the backup process from a lower directory.

Error message "0511-088 The backup tape may be damaged. Use a different disk to run the backup.

0511-103

The volume not correct restore expects volume X

Possible Causes

• This message indicates that the number X tape was inserted in the incorrect order.

• If it is a single volume archive, then it is possible that the archive is corrupt and is making the tape device think that it has reached end-of-file when this is not the case.

Procedures for Recovery

• Check the tape and see if it is damaged or corrupted.

• If it is a multi-volume archive, it is likely that tapes got misnumbered.

• Check and see if the disks were inserted into the tape drive in the correct order.

0511-123

The volume on String is not in backup format

Possible Causes

• You attempted to access data beyond the end of the tape marker, using the restore command.

• From the command line, you issued the restore command, with the -s flag, but did not specify the no-rewind tape device.

• From the command line, you issued the installp command and specified the device as:

  /dev/rmt#.1.

• You tried to access a file or device with the restore command, but the file or device was not in the backup format.

• The /var or /tmp directory is too small.

• The tape or drive is damaged.

Procedures for Recovery

• Use the tctl command to rewind the tape, then rerun the restore command. For example:

  tctl -f /dev/rmt# rewind
  restore -xvf /dev/rmt#.1

  1. Specify the no-rewind tape device, /dev/rmt#.1 with the -s flag.

  2. Specify the tape device as /dev/rmt#.

  3. Run one of the following formats from the command line to check the correct format of the file or device:

     For tar format:

     tar -tvf DeviceOrFileName

     For cpio format:

     cpio -itv DeviceOrFileName

• Increase the size of the /var or /tmp directory.

• Fix the tape or drive.

0511-133

There is a data read error

Possible Causes

• From the command line, you issued the following command:

  restore -sNumber -f Device

Procedures for Recovery

• Use the tcopy command to check the number of records on the tape, and specify a correct value with the skip flag.

  tcopy Device

0511-160

Cannot read the backup media

Possible Causes

• The tape is backed up on a tape device with a block size that differs from the one on which it is currently set.

• The backup medium is damaged.

Procedures for Recovery

• Log in as the root user and use the chdev command to change the block size on the tape device:

  chcev -1 rmt# -a block size=0

  You can also change the block size by selecting the SMIT Devices-> Tape Drive->Change/Show Characteristics of a Tape Drive menu options. Select the appropriate drive and change the block size.

• Check the error log for tape errors:

  errpt -a

0511-169

A directory checksum error on media: MediaName not equal to Number

Possible Causes

• From the command line, you issued the tar command to extract files from an archive that was not created with the tar command.

• You issued the tar command for a file that became damaged while being copied over the network.

• You issued the tar command for a file that was copied over the network, using the ftp command, but did not specify the binary flag.

Procedures for Recovery

• Ensure that the file is in the correct format by running the cpio or the restore command.

• Run the sum command on the copied file and also on the original file. Recopy the file if the sizes are different.

• Rerun the ftp command using the binary flag to copy the file, then rerun the tar command.

0511-193

An error occurred while reading from the media

Possible Causes

• You issued the tar command to read an archive from a tape device that has a different block size than when the archive was created.

• The tape is damaged.

Procedures for Recovery

• From the command line, run the tctl command to check the tape block size.

  tctl -f /dev/rmt# status

• Use the chdev command to change the block size, for example:

  chdev -1 rmt0 -a block size=0

• Check the error log for tape errors:

  errpt -a

0511-195

An error occurred while writing to the storage media

Possible Causes

• You issued the tar command without the -b flag, but the tape drive had an incorrect block size (4096).

• You attempted to create a new archive beyond the end of the tape marker using the tar command.

• The tape density is incorrect.

• The tape medium is defective.

Procedures for Recovery

• From the command line, run the tctl command to check the tape block size:

  tctl -f /dev/rmt# status

  If a block size of 4096 is desired, specify the -b flag with a value of 8 or multiple of 8;

  OR

  run the chdev command to change the tape block size, for example:

  chdev -1 rmt0 -a block size=1024

  A block size 512 or 2048 can also be used.

• Rewind the tape and reissue the command:

  tctl -f /dev/rmt# rewind

• Change the tape density with the chdev command, and rerun the original command:

  chdev -1 rmt# -a density_set_1=value

• Check the error log for tape errors:

  errpt -a

  and take action as indicated; for example, clean the drive head if it is dirty.

0511-317

The specified restore level is higher than expected

Possible Causes

• You made several incremental backups of a file system, with the levels in nonsequential order (for example: 0, 1, 3, 2) and tried to restore them in sequential order (0, 1, 2, 3). Each backup level is marked with a time stamp. When a backup with a lower level (but a higher time stamp) than the next in sequence is restored, the restore command fails.

• You tried to restore the same backup level more than once.

Procedures for Recovery

• Restore the backups in the order of the level in which they were created.

  To ensure that the most current changes are restored, restore sequentially, ignoring the higher level that is out of sequence.

  Using the previous example, restore levels 0, 1, 2. The most recent changes in level 2 are restored, and level 3 changes are lost.

• Select the next backup level to be restored.

0511-432

A write error occurred

See Error Message 0511-079 .

0511-903

Out of phase! cpio attempting to continue

See Error Message 0511-037 for recovery information.

0512-004

The /FileName file does not exist. System backup canceled

Possible Causes

• The / or /tmp file system is not large enough.

• You ran the mksysb command outside of SMIT without running the mkszfile command first.

Procedures for Recovery

• Extend the file system.

  See Managing File Systems in the AIX Version 4.3 System Management Guide: Operating System and Devices for information on extending file systems.

  Run the mkszfile command and then run the mksysb command again.

0512-005

Backup Completed

The backup command completed with errors. The messages displayed on Standard Error contained additional information.

Note: If SMIT was used to do the system or volume group backup, then check the smit.log for errors.

Possible Causes

• A file was removed during the system or volume group backup.

Procedures for Recovery

• Quiesce the system and rerun the backup.

• Verify the backup tape, as described in the AIX Installation Guide, section: To Verify a Backup Tape

0512-009

Invalid or Missing Volume Group Name

The volume group name, specified for the volume group backup, does not refer to an existing volume group on the system.

Possible Causes

• The volume group name may be misspelled.

• The volume group name was not specified on the command line.

Procedures for Recovery

• Choose the volume group name from a list of volume groups.

0512-016

Attempt to create a bootable tape failed

This message is displayed with one of the following:

bosboot -d /dev/device -a failed with return code Number

mkinsttape /dev/device failed with return code Number

Possible Causes

• The media is write-protected (return code 2).

• There is not enough space in the file systems (return code 5 or 1).

• The tape is defective (return code 11).

• The /usr/lib/boot/unix directory is damaged (0 length), or the link to /unix is missing (return code 52 or 45).

• The tape drive cannot be written to or /dev/blv/ cannot be read.

  This may be caused by an incorrect density setting for the tape-drive/tape-type/device-name combination, dirty tape drive heads, or a tape drive hardware problem.

Procedures for Recovery

• Ensure that the media is not write-protected.

• Extend the file system.

  The / directory must have at least 500 1KB blocks. The /tmp directory must have at least 7400 1KB blocks, and the /usr directory must have at least 4000 1KB blocks. See Managing File Systems in the AIX Version 4.3 System Management Guide: Operating System and Devices for information on extending file systems.

• Replace the tape.

• Restore the directories from the original tape or create the missing link to /unix.

• Ensure the status of the tape drive.

  If cleaning the tape drive heads does not correct the problem, contact your system administrator.

0513-001

The System Resource Controller daemon is not active

Possible Causes

• The System Resource Controller (SRC) master daemon record in the /etc/inittab file is either missing or damaged.

Procedures for Recovery

• Use the mkitab command to create a record of the SRC master daemon in the /etc/inittab file:

  mkitab -i fbcheck srcmstr:2:respawn:/etc/srcmstr

• Reprocess the /etc/inittab file by entering:

  telinit q

0513-021

The subserver is not on file or subserver is not currently active. Check your subserver entries and try again

Possible Causes

You attempted to access a subserver that either does not exist or is not currently active.

Procedures for Recovery

• Include the subserver or make the subserver active.

  1. To check the status of your subservers, enter:

     lssrc -a

  2. If it is not active, select the SMIT Processes and Subsystems->Subservers->Start a Subserver menu option. Select the subsystem you want to start.

0513-053

The System Resource Controller is experiencing problems with its socket communications

Possible Causes

• You ran a System Resource Controller (SRC) command that tried unsuccessfully to access a remote host.

• You ran a command that tried to access the /dev/SRC file, but that file is either damaged or no longer available.

• The root (/) file system was full, and an SRC command cannot be completed.

• There is a loose network cable connection.

Procedures for Recovery

• Reconfigure the Internet socket.

  1. Check if you are able to contact the remote hosts through the network. Use the ping command to see if you can access the host files.

  2. If you suspect that your system is having problems with the network, enter smit tcpip at the command line to reconfigure your system.

  3. If you suspect that the host is having communication problems, try to attach it to the network.

• Check if the /dev/SRC file or the /dev/.SRC-unix directory exists.

  1. Change to the /dev directory by using the cd command and run the ls command.

  2. If the /dev/SRC file or the /dev/.SRC-unix directory does not exist, reboot your system by running the shutdown -Fr command. The shutdown -Fr command automatically creates the /dev/SRC file when the system comes up.

• If the /dev/SRC file or the /dev/.SRC-unix directory does exist, your file or directory may be damaged.

  1. Rename the file and directory by using the mv command to the /dev/SRC file or the/dev/.SRC-unix file, respectively.

  2. Reboot your system by running the shutdown -Fr command, which automatically creates the /dev/SRC file and the /dev/.SRC-unix directory when the system comes up.

  3. Reissue your command.

• Run the df command to check the file system capacity. Remove the unnecessary files if the file system is full, and rerun the SRC command.

• Check to see that the network cables are correctly attached. Run the errpt  -a command to check for network or cabling errors.

0513-056

Timeout waiting for command response

If you specified a foreign host, see the /etc/inittab file on that foreign host. By viewing the file you are able to verify that the SRC daemon (srcmstr) was started with the -r flag to accept remote requests.

Possible Causes

• You ran the /usr/bin/refresh command or another SRC command with the -h (host-name) to access the System Resource Controller on another system, but the system was not physically attached to the network.

• You ran the /usr/bin/refresh command or another SRC command with the -h (host-name) parameter to access the System Resource Controller on another system , but the srcmstr daemon does not accept remote requests.

  Note: By default the srcmstr daemon does not accept remote requests.

• You ran the /usr/bin/refresh command or another SRC command to access the System Resource Controller on the local system, but the srcmstr process was not responding.

Procedures for Recovery

• If you were trying to access the System Resource Controller on a foreign host:

  1. Verify that the System Resource Controller on the foreign host is accepting remote requests.

     1. Use the ping command to verify that you can access the foreign host.

     2. Check the /etc/inittab file on the foreign host. The srcmstr entry must include the -r flag on the srcmstr command to allow srcmstr to accept remote requests.

        Note: From a security perspective this is not recommended.

     3. See the srcmstr command for the required /etc/hosts.equiv or /.rhosts configuration.

     4. If you require remote SRC support, add the -r flag to the srcmstr /etc/inittab entry, and restart the foreign host.

     5. Issue your command again to complete this procedure.

  2. If you cannot ping the foreign host, reconfigure the Internet socket. If you suspect that your system is having problems with the network, enter smit tcpip at the command line to reconfigure your system, then run your command again.

  3. Check your physical network cable connections.

     1. Check your cables and adapters, ensuring they are correctly attached.

     2. Run diagnostics by using the diag command.

     3. Ensure that the cable is attached and is switched on.

  4. Reboot your system by running the shutdown -Fr command.

  5. Issue your command again.

• If your were trying to access the System Resource Controller on the local system, run the ps -ef | grep srcmstr command to verify that the srcmstr daemon is running.

  To start the srcmstr daemon requires access to the file /etc/objrepos/SRCsubsys and a minimum amount of space in the root file system to create local sockets. To communicate, the srcmstr daemon requires AF_UNIX local socket support. See the netstat command.

0514-018

The values specified for the following attributes are not valid

Possible Causes

• From the command line, you specified an attribute that is out of the range of legal values.

• The Object Data Management (ODM) database is damaged.

Procedures for Recovery

• Check the attributes in your command to be sure they are in legal range.

  1. Run the lsattr -R command to display the range of legal attribute values for that specific device, then run your command with the correct attributes.

• Check to see if your ODM database is damaged, then try replacing the PdAt file.

  1. Copy the PdAt file from another system that has the same release level as your system, either through the network by running the ftp command or through a diskette by using the backup and restore commands.

  2. Restore the file making sure that it preserves the permission code, the ownership, and the location of your previous file.

• Reenter your command.

0514-022

The specified connection is not valid

Possible Causes

• Using the System Management Interface Tool (SMIT), you supplied an invalid connection location to define a device or make a device available.

• From the command line, you specified an invalid connection location with the mkdev command to define a device or make a device available.

Procedures for Recovery

• Using SMIT, supply a valid connection location.

  1. Return to the SMIT screen where the error occurred.

  2. Locate the screen containing the PORT number field. You may need to select Cancel to page back through the screens.

  3. Position the cursor in the PORT number field of this screen and select List. A list of valid connection locations is displayed.

  4. Select the desired connection location from the list.

  5. Select Do to insert the proper value into the PORT number field.

• Locate a valid connection location, then use it with the mkdev command.

  1. Enter the lsconn -p command to list the valid connection locations.

  2. Select a connection location from the list.

  3. Reenter the mkdev command using the new connection location.

0514-031

A device is already configured at the specified location

Possible Causes

• You attempted to add a device at a location that is already occupied by a different device.

Procedures for Recovery

• Determine which device occupies the location, and either remove it or find a new location for the new device.

  1. Select the System Management Interface Tool (SMIT) Devices-> List Devices-> List All Defined Devicesmenu option. SMIT displays the name, status, location, and description of all defined devices. The device status is one of the following:

     Available	The device is defined and configured.
     Defined	The device is currently defined but not configured. The location is still reserved for the device and no other device can be added at that location. See Devices Overview for System Management in AIX Version 4.3 System Management Guide: Operating System and Devices for more information.
     Undefined	The system does not recognize the device.

  2. Choose the location where you want to add the device.

     OR

  3. Choose a location where you want to add the device. See Location Codes in AIX Version 4.3 System Management Guide: Communications and Networks for more information.

  4. Use the lsdev command to determine which device currently occupies the specified location, as follows:

     lsdev -C | grep aa-bb-cc-dd

     where aa-bb-cc-dd is the location code (found in step 1). The location code can range from 2 to 12 characters in length.

     The name of the device is displayed, along with its present status.

  5. With the information from steps 1 and 2, either delete the existing device from the specified location and add the new device, or add the new device at a different location.

0514-040

Error initializing a device into the kernel

Possible Causes

• You were unable to configure a specific device. While trying to initialize your device driver, you were unable to load it as part of the kernel extension. The specific device driver file in the /etc/drivers file is damaged or contains software errors.

• Your Object Data Management (ODM) database file is damaged, and you are unable to configure your device.

Procedures for Recovery

• Check for possible software errors if you are modifying your configuration method or device driver.

• Try replacing the device driver file if you suspect that the device driver is damaged.

  1. Copy the device driver file from another system that has the same release level as your system, either through the network by running the ftp command, or through a diskette by using the backup and restore commands. When you restore the file, make sure that it preserves the permission code, ownership, and location of your previous file.

  2. Enter your command again.

• If you suspect that the ODM database is damaged, try replacing the PdAt file.

  1. Copy the PdAt file from another system that has the same release level as your current system, either through the network by running the ftp command, or through a diskette by using the backup and restore commands. When you restore the file, make sure that it preserves the permission code, ownership, and location of your previous file.

  2. Enter your command again.

0514-047

Cannot access a device

Possible Causes

• You specified the wrong connection address to make a device available.

• The device that you are trying to add is not attached to your system or has hardware problems.

Procedures for Recovery

• Check your device to make sure that you entered the correct connection address.

  If your device is connected to a SCSI card, the number is on the back of the device. This number is a single-digit number. In order to convert it to a connection number, add a 0 (zero) digit to this number; that is, if the number is 1 (one), the connection number is 10, and if the number is 2, the connection number is 20.

• Check to make sure that no other device attached to the SCSI card has the same connection number as your device.

  Use the lsdev command to check the connection numbers of the device attached to the SCSI card. If there is one number that matches your connection number, change the number on the back of your device to a unique number.

  If you are using SMIT, return to the SMIT screen where the error occurred and enter the appropriate connection number. Otherwise, reenter the mkdev command with the appropriate connection address.

• If your device is connected to a serial port, check to see if it is plugged in to the correct serial port, then rerun your command.

  If you suspect there is a hardware problem:

  1. Check your cables to make sure that they are attached correctly.

  2. Check to see if your device is turned on.

  3. Run diagnostics by using the diag command.

0514-050

Cannot perform the requested function because the specified device was not detected

Possible Causes

• The device you are trying to add is not attached to your system or has hardware problems.

Procedures for Recovery

• If your device is connected to a serial port, check to see if it is plugged in to the correct serial port, then rerun your command.

  If you suspect there is a hardware problem:

  1. Check your cables to make sure that they are attached correctly.

  2. Check to see if your device is turned on.

  3. Run diagnostics by using the diag command.

0514-062

Cannot perform the requested function because the specified device is busy

Possible Causes

You specified a device that is being used by one or more processes.

Procedures for Recovery

• Check to make sure you selected the correct device.

If that is not the problem:

• Remove the process that is allocating your device.

  1. Run the ps -ef command to list which process is using the device you specified.

  2. Remove the process by using the kill command.

If that does not resolve the problem:

• Reboot your system and reenter your command if your system is still busy.

  1. Use the sync command to update your i-node table.

  2. Run the shutdown -Fr command. Wait for the login prompt.

  3. After you log in, reenter your command.

If your device is still busy:

• Run your command in single user mode.

  1. Shut down your system and turn the key mode switch to Service.

  2. Reboot your system using the boot media.

  3. Select the Maintenance option from the Installation and Maintenance menu, then select Access a Root Volume Group.

  4. After identifying the correct volume group, select Access this Volume Group and start a shell.

0514-063

The specified device driver name is too long

Possible Causes

• The name of the device driver you want to configure is too long. The device name must be less than 20 characters in length in order to be added to the CuDvDr Object Data Management (ODM) database file.

• Your libcfg.a library file is damaged.

Procedures for Recovery

• Change the name of your device driver to a name with less than 20 characters.

• Replace the libcfg.a library file.

  1. Copy the libcfg.a file located on your /lib directory from another system that has the same release level as your current system, either through the network by running the ftp command, or through a diskette by using the backup and restore commands. If you use the ftp command, use the bin subcommand.

  2. When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.

• Reenter your command.

0514-516

Device configuration database lock service timed out

Possible Causes

• You ran a command that tried to access a Configuration Object Data Management (CODM) file that is presently in use or was closed incorrectly.

Procedures for Recovery

• Run the df command to check if there is a process currently using any CODM file.

  Wait until the process is done and reissue your command.

• If you suspect that the CODM file was incorrectly closed, run the cd command to go to the /etc/objrepos directory.

  Rename the config_lock file to config_lock.old using the mv command.

• Issue your command again.

0514-521

Cannot find information in the predefined device configuration database for the customized device: DeviceName

Possible Causes

• Your predefined device configuration database PdDv file, located in the /usr/lib/objrepos file, is damaged.

Procedures for Recovery

• Replace the PdDv file.

  Copy the PdDv file from another system that has the same release level as your current system, either through the network by running the ftp command, or through a diskette, by using the backup and restore commands. When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.

• Reenter your command.

0516-005

String: The physical volume is already a member of the requested volume group

Possible Causes

• You attempted to add a physical volume to a volume group, but you specified a physical volume that is already a member of the volume group.

• You attempted to add a physical volume to a volume group, and a discrepancy exists between the volume group descriptor area (VGDA) and the Object Data Manager (ODM).

  If the VGDA does not match the ODM, the following error message may display even though the physical volume is actually a member of a volume group:

  0516-320 String:Physical volume String is not assigned to a 
  volume group

  If you attempt to assign the physical volume to the volume group, error message 0516-005 is displayed.

Procedures for Recovery

• Ensure that the physical volume you specified is not already a member of the volume group.

  Enter the lsvg -p VolumeGroupName command to list the members of the volume group.

  Reenter the extendvg command to add a physical volume to a volume group, and specify a valid physical volume that is not a member of the volume group.

• Update the ODM database with information from the VGDA.

  If the physical volume is a member of the volume group but error message 0516-320 is displayed anyway, enter the redefinevg -d PhysicalVolumeName VolumeGroupName command to update the ODM database with information from the VGDA. The VGDA contains current information.

0516-010

Volume group must be varied on: use varyonvg command

Possible Causes

• You specified a volume group that is currently unavailable on your system.

Procedures for Recovery

• Check for misspelling in the volume group name.

• Make your volume group available.

  1. Use the lsvg command to verify whether your volume group is available.

  2. If the volume group is not available, use the varyonvg command to make it available.

• See if one of the disks in the volume group is available.

  1. You can check to see if the disk is available by using the lspv command.

  2. If the disk is not available, issue the mkdev command to make it available and run the varyonvg command to make the volume group available.

  3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command. It may be necessary to use the Object Data Manager (ODM).

0516-013

The volume group cannot be varied on because there are no good copies of the descriptor area

Possible Causes

• Most of the volume group descriptor area (VGDA) cannot be accessed or is damaged.

Procedures for Recovery

• See if one of the disks where the volume group is located is available.

  1. Issue the lspv command to see if the disk is available.

  2. If the disk is not available, issue the mkdev command to make it available.

  3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.

  4. If the disk is available, run the odmdelete command to delete the damaged VolumeGroup from the configuration database:

     odmdelete -q name=VolumeGroupName -o CuAt

  5. Use the System Management Interface Tool (SMIT) to add a new volume group.

• Shut down your system and check for any loose or faulty cables around the fixed- disk area.

  1. Check adapters and power sources.

  2. Reboot your system and enter your command again.

• For volume groups with multiple physical volumes:

  1. If the varyon operation reports a missing physical volume, use the chpv -vr command to temporarily remove the volume from the volume group.

  2. Reissue your command to make the volume group partially available.

  3. Once the problem is corrected and the physical volume is brought back online, issue the chpv -va command to return the physical volume and make it available again to the volume group.

     Note: This procedure should be used as a last resort because data integrity cannot be guaranteed.

0516-022

Illegal parameter or structure value

Possible Causes

• The Object Data Management (ODM) database was damaged, and the physical volume ID (pvid) of a disk was listed as None.

• One of your Customize Device Configuration database files was damaged, and while you ran your command, the file collected some illegal parameters or structure values.

• You attempted to create a logical volume with the System Management Interface Tool (SMIT), or from the command line with the mklv command. The physical volume name specified was not configured.

Procedures for Recovery

• Verify that the disk is recognized by the system. From the command line, run:

  lqueryvg -p hdisk# -At

• Deactivate the volume group.

  1. Use the lsvg -o command to determine if your volume group is active.

  2. If it is active, run the varyoffvg command.

  3. Remove the definition of the volume group from the system by using the exportvg command.

  4. Add the definition of the volume group to the system by using the importvg command.

0516-304

Unable to find device ID in the Device Configuration Database

Possible Causes

• One of your Customize Device Configuration database files was damaged, and while you ran your command, this file collected some illegal parameters for the device ID.

Procedures for Recovery

• Deactivate the volume group.

  Use the lsvg -o command to find out if your volume group is active. If it is active, run the varyoffvg command.

• Remove the definition of the volume group from the system by using the exportvg command.

• Add the definition of the volume group to the system by using the importvg command.

• Activate the volume group by using the varyonvg command.

0516-306

Unable to find VolumeGroupName VolumeGroupDescription in the Device Configuration Database

Possible Causes

• You issued one of the following commands:

  • extendvg

  • getlvodm

  • lsvg

  and the specified device does not exist in the Object Data Manager (ODM) database.

  Note: The getlvodm command is an internal command. InfoExplorer currently contains no information about this command.

Procedures for Recovery

• Ensure that the device is defined in the database.

  1. Enter the lsdev -C command to display a list of devices defined in the database.

  2. If the device is not listed, use one the following methods to define it, depending on the type of device:

     • Define a physical volume using the mkdev command or the SMIT menu option Devices--> Fixed Disk--> Add a Disk.

     • Define a logical volume using the mklv command or the SMIT menu option Physical and Logical Storage--> Logical Volume Manager--> Volume Groups--> Add a Volume Group.

0516-320

ProgramName: Physical volume String is not assigned to a volume group

Possible Causes

• You issued one of the following commands:

  • getlvodm

  • lspv

  • lsvg

  and the specified physical volume is not assigned to a volume group in the Object Data Manager (ODM) database.

  Note: The getlvodm command is an internal command. There is no information available in InfoExplorer about this command.

Procedures for Recovery

• Ensure that the physical volume is defined in your system and its name is spelled correctly in the ODM database.

  1. Enter the lsvg command to list all the volume groups defined in your system.

  2. Enter the lsvg -p VolumeGroupName command to list all the physical volumes in the specified volume group.

  3. Ensure that the physical volume name is spelled correctly. For information on editing the ODM database, see Object Data Manager (ODM) Overview in in AIX General Programming Concepts: Writing and Debugging Programs.

  4. If the physical volume is undefined or its name misspelled, add the correct physical volume in one of the following ways:

• With the System Management Interface Tool (SMIT), use the Physical and Logical Storage--> Define a Fixed Disk to the Operating System menu option to add the physical volume to the volume group. Then select one of the following three menu options to add the definition of the physical volume to a volume group:

  • Add a Fixed Disk to an Existing Group

  • Add a Fixed Disk without Data to a New Group

  • Add a Fixed Disk with Data

• From the command line, use one of the following commands:

  mkvg
  	Creates a new volume group containing the physical volume.
  extendvg
  	Defines a physical volume to an existing volume group.
  importvg
  	Imports a new volume group definition from a set of physical volumes. Note: Use the importvg command only if the volume group definition was previously exported using the exportvg command.

0516-366

Volume group VolumeGroupName is locked. Try again

Possible Causes

• You ran a command that tried to access a Configuration Object Data Management file that was in use or was closed incorrectly.

• The installation of a software product was interrupted, causing the system to lock the root volume group.

Procedures for Recovery

• Log in as the root user and run the odmdelete command to remove the lock from the configuration database:

  odmdelete -q name=VGname and attribute=lock -o CuAt

• Issue your command again.

0516-404

Not enough resources available to fulfill allocation

Possible Causes

• You used the mklv or extendlv command, specifying a physical volume without enough partitions (free space) to fulfill the requested logical volume size.

• You used the mklv or extendlv command without specifying a physical volume, and the volume group specified does not have enough free partitions (free space) to fulfill the requested logical volume size.

Procedures for Recovery

• Allocate enough disk space by specifying different characteristics. Do one of the following:

  • Enter the mklv or extendlv command and specify a different physical volume, ensuring that the physical volume specified includes enough free partitions to fulfill the requested logical volume size.

  • Enter the mklv or extendlv command specifying fewer partitions to be allocated for the logical volume.

  • Do not specify a physical volume. If you do not specify a physical volume, the command uses all the physical volumes available in the volume group.

• Add or create more disk space. Do one of the following:

  • Add another physical volume (fixed disk) to the volume group.

  • Delete an unused logical volume.

0516-787

extendlv: Maximum allocation for logical volume Name is Value

Possible Causes

• Using the System Management Interface Tool (SMIT), you specified a value in the Number of ADDITIONAL logical partitions field to try to increase the logical volume size beyond the maximum number of logical partitions.

• From the command line, you used the extendlv command (or the chfs command, which calls the extendlv command) to try to increase the logical volume size beyond the maximum number of logical partitions.

Procedures for Recovery

• Use SMIT to change the logical volume.

  Use the SMIT Physical and Logical Storage--> Logical Volume Manager--> Logical Volumes--> Set Characteristic of a Logical Volume--> Change a Logical Volume menu option to specify a new number of logical partitions in the MAXIMUM NUMBER of LOGICAL PARTITIONS field.

• Use the chlv command to change the logical volume.

  1. Increase the maximum number of logical volume partitions for the named logical volume with the chlv command, as follows:

     chlv -x MaximumLogicalPartitions LogicalVolumeName

  2. Rerun the chfs command or the extendlv command.

     Note: In both cases, you must change the logical volume before you can extend or increase it.

0516-794

String not configured. Please configure the disk before trying this command again

Possible Causes

• You used the System Management Interface Tool (SMIT) to add an undefined physical volume to the volume group, but the physical volume specified is not defined or installed on the system, or does not exist.

• From the command line, you used the mkvg or the extendvg command to add an undefined physical volume to the volume group.

Procedures for Recovery

• Use SMIT to add a disk.

  Use the Devices--> Fixed Disk--> Add a Disk menu option to define the disk.

• Use the mkdev command to define a disk.

  Once the disk is defined, you can add it to an existing volume group or use it to create a new volume group.

  Note: These commands are for disks without data. If the disk contains data, use the importvg command rather than the mkvg command or the extendvg command.

0516-822

Unable to create logical volume

Possible Causes

• You specified a logical volume name that already exists.

• You specified a volume group that currently does not have enough disk space for your logical volume.

• You specified a volume group that is currently unavailable on your system.

Procedures for Recovery

• Name your logical volume to a name not already in use.

  1. List all of the current logical volumes by issuing the following command:

     lsvg -o| lsvg -i -1

  2. Rerun your command with the correct logical volume name.

• Check the disk space in your volume group.

  1. Run the lsvg command to check how many free partitions you have available in your volume group.

  2. Repeat your command with the correct number of partitions or correct volume name.

• Verify that your volume group is available.

• See if one of the disks in the volume group is available.

  1. Check to see if the disk is available by using the lspv command.

  2. If the disk is not available, issue the mkdev command to make it available and run the varyonvq command to make the volume group available.

  3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.

0516-952

Unable to vary on volume group uvgl

Possible Causes

• You specified a volume group that is currently unavailable on your system.

Procedures for Recovery

• Check for misspelling in the volume group name you specified.

• See if one of the disks in the volume group is available.

  1. Check to see if the disk is available by using the lspv command.

  2. If the disk is not available, issue the mkdev command to make it available and run the varyonvq command to make the volume group available.

  3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.

0519-002

The CLASS_SYMBOL does not identify a valid object class

Possible Causes

• You specified an invalid parameter, path name, or permission in the profiles load file used to convert the Systems Network Architecture (SNA) profile.

• The profiles load file does not exist.

• The Object Data Manager (ODM) files for SNA Services have been damaged.

Procedures for Recovery

• Import a profiles load file that contains valid information.

  1. Use the print command in the SNA configuration file to send the profiles to a file.

  2. Move the created file to the desired system.

  3. Enter the following on the command line:

     awk -f /usr/lpp/sna/bin/sna_update.awk profiles.rt > profiles.r s

  4. Enter the following on the command line:

     importsna -l profiles.rs -e profiles.err

• Remove all SNA Services profiles from the ODM database and import them again.

  1. Enter the following commands to remove all SNA Services from the ODM database:

     cd /usr/lpp/sna/objrepos
     rm *
     /usr/lpp/sna/bin/peu

  2. Enter the following command to import the profiles again:

     importsna -l profiles.rs -e profiles.err

0551-001

Character is not a recognized field descriptor

Possible Causes

• You specified a field descriptor that is not supported by the date command.

Procedures for Recovery

• Reenter the date command with valid field descriptors.

  See the Field Descriptor section for a list of the valid field descriptors that are allowed with the date command.

0551-006

Cannot reach the time server; time set locally

Possible Causes

• You attempted to set the date or time using the date command on a machine controlled by timed daemons, but the attempt failed because of a network problem.

Procedures for Recovery

• Verify network connectivity.

  Enter the ping MachineName command to determine the availability of a particular machine on the network. Press the Ctrl-C key combination to stop the ping command. If the ping command indicates that the machines are not communicating or that data is being lost, a network problem exists. See the Network Overview in AIX Version 4.3 System Management Guide: Communications and Networks for information on how to resolve it.

  Note: The timed daemon should be controlled using the System Resource Controller (SRC) or the System Management Interface Tool (SMIT). Entering the timed daemon at the command line is not recommended.

0551-099

The Character flag is not valid

Possible Causes

• You specified an invalid flag or combination of flags with the sa command.

Procedures for Recovery

• As root user, reenter the sa command with a valid flag.

  1. Use the whoami command to ensure that you are the root user. Use the su command to change to the root user if necessary.

  2. See the Flags section of the sa command for a list of valid flags.

  3. Reenter the sa command with a valid flag or flag combination.

0551-118

The interval value is not valid

Possible Causes

• You specified an invalid interval value using the vmstat command.

Procedures for Recovery

• Specify a valid interval value.

  The vmstat command requires a positive, nonzero interval value. Reenter the command, specifying a valid interval value.

0551-119

The count value is not valid

Possible Causes

• You specified an invalid count value using the vmstat command.

Procedures for Recovery

• Specify a valid count value.

  The vmstat command requires a positive, nonzero integer for a count value. Reenter the vmstat command, specifying valid interval and count values.

• Do not specify a count value.

  Reenter the vmstat command, specifying a valid interval value and no count value. When no count value is specified, the vmstat command generates output at the specified interval until you stop the command by entering the Ctrl-C key combination.

0551-128

Drive Name is not found

Possible Causes

• You used the vmstat command to specify a physical volume that does not exist.

Procedures for Recovery

• Specify a valid physical volume.

  1. Enter the getlvodm -C command to display a list of all valid physical volumes.

     Note: The getlvodm command is an internal command. InfoExplorer currently contains no information about this command.

  2. Reenter the vmstat command, specifying a valid physical volume or volumes.

0551-154

Disk Name is not found

Possible Causes

• You entered the iostat command to report statistics on I/O activity on terminals or disks, but specified a name that does not match any of the names on the internal list of disks.

Procedures for Recovery

• Supply valid physical volume names.

  1. Enter the getlvodm -C command to list all disk names.

  2. Reenter the iostat command, specifying valid device names.

0551-201

Cannot open FileName

Possible Causes

Using the sar command, you cannot open /usr/adm/sa/FileName for one of the following reasons:

• The file does not exist.

• You do not have valid permissions on the file or the directory.

Procedures for Recovery

• Create the file.

  1. Enter the su command to change to the root user.

  2. Enter the /usr/lib/sa/sa1 command.

  3. Reissue the sar command.

• Ensure that you have correct file and directory permissions.

  1. Enter the su command to change to the root user.

  2. Enter the chmod 754 /usr/adm/sa command to obtain valid permissions on the directory.

  3. Enter the chmod 644 /usr/adm/sa/FileName command to obtain valid permissions on the file.

  4. Reissue the sar command.

0551-203

ending time (etime) <= starting time (stime)

Possible Causes

• You used the sar command with the -e and -s flags to specify the starting and ending time for reporting, but the specified ending time was less than or equal to the starting time.

Procedures for Recovery

• Ensure that the -e flag is greater than the -s flag when using the sar command.

0551-213

Try running /usr/lib/sa/sa1 Increment Number

Possible Causes

• You entered the sar command to extract the contents of the /usr/adm/sa/saDD FileName file that was not previously created.

Procedures for Recovery

• Create the /usr/adm/sa/saDD FileNamefile with the sa1 command.

  1. Use the su command to change to the root user.

  2. Enter the /usr/lib/sa/sa1 <increment><number> command with the proper increment and number settings.

  3. Reenter the sar command.

0551-250

The argument String is not valid

Possible Causes

• You specified an invalid command line argument.

Procedures for Recovery

• Use a valid command line argument with the sysline command.

  1. See the Flags section in the sysline command for a list of valid command line arguments.

  2. Reenter the sysline command using a valid command line argument.

0551-256

There is no status capability for String

Possible Causes

• You entered the sysline command, but the terminal type defined does not have status line capabilities.

Procedures for Recovery

• Define a terminal type that has status line capabilities.

  Use the env command to determine if the TERM environment variable is set correctly. If the variable is not set to a terminal type that has status line capability, enter export TERM=TerminalType to reset the variable.

  If the error message is still displayed, the terminal does not have screens to display the status line. See the terminfo file in AIX Files Reference for more information on terminal types.

0551-257

The Character option is not valid

Possible Causes

• You specified an invalid option value for the sysline command.

Procedures for Recovery

• Ensure that the option value you selected is correct.

  1. Check the Flags section in the sysline command for a list of valid options, and verify that the option you entered is correct.

  2. Reenter the sysline command using a valid option value.

0551-404

Specified value of date/time is out of range

Possible Causes

• You specified an invalid range value when using the date command to display the date or time.

Procedures for Recovery

• Use valid range values with the date command.

  1. Check the following list of valid ranges for the date command values to ensure that you enter a proper one:

     mm (01-12)	Specifies the month.
     dd (01-31)	Specifies the day.
     HH (00-23)	Specifies the hour.
     MM (00-59)	Specifies the minute.
     SS (00-59)	Specifies the second.
     YY (00-37)	Specifies the year from 2000 to 2037.
     YY (70-99)	Specifies the year from 1970 to 1999.

  2. Reenter the date command using a valid range value.

0575-528

Cannot find database DatabaseName in info configuration file

Possible Causes

• The .rom file for a database is missing from the InfoExplorer database.

Procedures for Recovery

• Ensure that the <database>.rom file is present in the database directory.

  1. Run the ls command to check if the file is present:

     ls /usr/lpp/info/LANG/DatabaseDirectory

  2. If the file is not present, copy it from another system (with the same version of InfoExplorer), or install InfoExplorer again.

0602-145

There are no preserved files

Possible Causes

• You attempted to recover a file with the vi -r command and there are no saved files.

Procedures for Recovery

• None.

0652-050

Cannot open FileName

Possible Causes

• You attempted to use the cat command on a file that is in the process of being downloaded.

Procedures for Recovery

• Wait until downloading has finished, and try again.

0652-019

The status on FileName is not valid

Possible Causes

This error message may be displayed during a backup operation.

• The system looked for a file that either does not exist or was specified incorrectly.

• The system looked for a file for which you do not have write permission.

Procedures for Recovery

• Ensure that the file exists and verify the file name.

• Add write permission to the file or parent directory.

  Run the su command to become the root user and add the appropriate permission.

0652-033

Cannot open FileName

Possible Causes

• You used the grep command to search a file on which you do not have read permission.

• You used the grep command to search a file, and you do not have execute permission on one or more of the parent directories containing the file.

Procedures for Recovery

• Establish read permission for the file.

  1. Use the li -l command to determine access and ownership permissions on the file.

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

• Establish execute permission for the directories containing the file.

  1. Determine which directory is causing permission problems by entering the cd ParentDirectory command, where ParentDirectory is the parent directory of the file in question. If an access error is displayed from the cd command, reenter the command using the parent directory of the directory specified in the previous usage of the cd command.

     Repeat this process until the cd command changes to the specified directory without returning an error. The child of this directory is the directory causing access problems.

  2. Use the ls -l command to determine the access permissions and ownership of the directory.

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

     Note: You may need to repeat one or both of the recovery procedures presented in this article because permission problems may be found in multiple directories under which the file resides.

0652-048

Cannot change the modification time on FileName or DirectoryName

Possible Causes

• You used the touch command to change the time stamp information on a file or a directory for which you do not have write permission.

Procedures for Recovery

• Establish write permissions on the file.

  1. Determine the current ownership of the file or directory by entering the ls -dl Name command, where Name specifies the file or directory.

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

0653-309

Cannot open the directory Name

Possible Causes

• Access to a directory using the ls command was denied because of incorrect user permission.

Procedures for Recovery

• Determine the current directory ownership and obtain the proper user permissions.

1. Enter the ls -ld DirectoryName command to determine ownership and permissions for the directory. See File and Directory Access Modes in AIX Version 4.3 System User's Guide: Operating System and Devices for more detailed information.

2. 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 give yourself the proper permissions, or ask the owner or system administrator to give you the proper permissions.

0653-341

The file FileName does not exist

Possible Causes

• You attempted to access a file or a directory that is not in your current directory or in the directory that you specified.

Procedures for Recovery

• Check your command to ensure that you did not incorrectly enter the file name, directory, or path name.

• Check for unmounted file systems.

  1. Issue the mount command to ensure that all file systems are mounted.

  2. Use the mount command to mount the file system you need.

• Replace the missing file.

  • Copy the libcfg.a library file located on your /lib directory from another system that has the same release level as your current system, either through the network by running the ftp command or through a diskette by using the backup and restore commands.

  • If you use the ftp command, use the bin subcommand. When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.

• Reenter your command.

0653-343

Cannot read DirectoryName

Possible Causes

• You used the ls command to list the contents of a directory for which you do not have read access permission.

Procedures for Recovery

• Establish read access permissions for the directory.

  1. Enter the ls -l ParentDirectory command, where ParentDirectory is the directory that contains the directory for which you are determining access permissions. Determine the owner and the current access permissions for the directory on which you want to use the ls command.

  2. Use the su command to change to the root user or to a user that has read permission for the required directory.

     Note: If you are unable to change users with the su command, ask your system administrator or the owner of the required directory to change the permissions of the directory to provide you with read access.

  3. Reenter the ls command to display the contents of the required directory.

0653-401

Cannot rename String1 to String2

Possible Causes

• The source file or source directory you attempted to move or copy does not exist.

• You do not have read and write permissions to move or copy the source file or directory you specified.

Procedures for Recovery

• Verify the location and the name of the source file or directory.

  1. Use the ls command to verify that the file or directory to be moved or copied exists. Remember, AIXwindows is case-sensitive: Characters and spaces must be exact.

  2. Enter the cp or mv command using a valid file or directory name to copy or move the file.

• Obtain the proper read or write permissions.

  1. Use the ls-al command to determine access permissions of each directory or file involved. See File and Directory Access Modes in AIX Version 4.3 System User's Guide: Operating System and Devices for more detailed information.

  2. 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 give yourself the proper permissions, or ask the owner or system administrator to give you the proper permissions.

  3. Enter the cp or mv command to copy or move the file.

0653-603

Cannot remove directory DirectoryName

Possible Causes

• You attempted to remove a directory that contains files.

Procedures for Recovery

• Remove the files in the directory and try again.

• Force the deletion of the directory and its files.

  Run the rm command with the -r flag as follows:

  rm -r DirectoryName 

0653-609

Cannot remove FileName

Possible Causes

• You attempted to remove a file for which you do not have write permission by overriding the write protection.

Procedures for Recovery

• Establish write permissions on the file.

  1. Determine the current ownership of the file or directory by entering the ls -dl Name command, where Name specifies the file or directory.

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

0653-611

Directory DirectoryName is not empty

Possible Causes

• You attempted to remove a directory with the rmdir command, but the directory contains files.

Procedures for Recovery

• Remove the files in the directory and run the rmdir command again.

• Force the deletion of the directory and its files.

  Run the rm command with the -r flag as follows:

  rm -r DirectoryName 

0653-650

Cannot locate the temporary directory or /tmp

Possible Causes

• The sort command could not create its temporary files because the /usr/tmp and /tmp directories do not exist.

• The sort command could not create its temporary files because you do not have write permission to the /usr/tmp and /tmp directories.

• You used the sort command with the -T flag to specify a directory that does not exist.

• You used the sort command with the -T flag to specify a directory for which you do not have write permission.

Procedures for Recovery

• Create the /usr/tmp and /tmp directories using the mkdir command.

• Establish write permission to the /usr/tmp or /tmp directories.

  1. Use the su command to change to the root user. If you already own the /usr/tmp or /tmp directories, you can omit this step.

  2. Enter the chmod 777 /tmp or the chmod 777 /usr/tmp command to gain write permission to the specified directory.

     Note: The chmod 777 command gives read, write, and execute permissions to all users. If you do not want this, see File and Directory Access Modes in AIX Version 4.3 System User's Guide: Operating System and Devices for more information about files and directories.

• Use the -T flag to specify an existing directory.

  Note: Ensure that you have write permission to the specified directory. See the following procedure for information on how to get write permission to a directory.

• Establish write permission to the directory specified by the -T flag.

  As the root user or as a user with proper permissions, enter the chmod 777 /DirectoryName command to give yourself write permission to the directory specified by the -T flag.

0653-657

A write error occurred while sorting

Possible Causes

• You used the sort command, and the file system became full, while the file was being processed.

• Write permission to the directory containing the temporary files was removed, while the sort was in progress.

Procedures for Recovery

• Ensure that there is enough disk space for the sort to be completed.

  Enter the df FileSystem command while the sort command is processing the file. The df command displays information about space available on a file system.

  The sort command creates temporary files in either the /usr/tmp directory or the /tmp directory. Writing is unsuccessful if the file system containing the temporary directory becomes full. If you are not sure which directory is used for temporary file storage, enter the sort -T /usr/tmp FileName command to create the temporary files in the desired directory.

  If the sort fails because the file system containing the temporary directory is full, do one of the following:

  • Use a directory in a file system that has more space.

  • Increase the file system size using the chfs command.

• Verify that you have write permission on the directory containing the temporary files.

  Enter the ls -la DirectoryName command to list permissions. Use the chmod 777 command to change write permissions, if necessary.

0703-201

There is no manual entry for Name

Possible Causes

• You entered the man command to obtain information on a subject for which there is no manpage.

Procedures for Recovery

• Respecify your inquiry.

• Use the info command to obtain information.

0703-203

Cannot open the database of manual pages

Possible Causes

• You attempted to obtain help information with the man command but InfoExplorer is not installed.

• You attempted to obtain help information with the man command but the manpage directory is empty.

• The language environment variable setting does not match the help database path names.

Procedures for Recovery

• Install the InfoExplorer database.

• Create the directory for manpages.

• Verify the environment variable and the help database path names.

  For example, if the current setting of $LANG is EN_US, the help database files must be the following:

  /usr/lpp/info/EN_US/aix/aix.key
  /usr/lpp/info/EN_US/aix/aix.rom
  /usr/lpp/info/EN_US/sys.sys

0703-303

%s: The path is missing

Possible Causes

• You attempted to obtain help information with the man command but InfoExplorer was not installed.

Procedures for Recovery

• Install InfoExplorer.

0706-010

Binder killed by signal Signal

Possible Causes

• You ran out of memory while linking your object files.

Procedures for Recovery

• Issue the lsps command to check if you have enough paging space.

  You can increase the paging space through the smit command.

• Increase the default limits set by the /etc/security/limits file.

  1. Edit the /etc/security/limits file.

  2. Increase the settings of the fsize, cpu, data, stack, core, and rss process resource limits for your user ID, starting with the fsize parameter.

  3. Issue your command again.

0706-103

Allocation of Number bytes failed

Possible Causes

• You ran out of memory while linking your object files.

Procedures for Recovery

• Issue the lsps command to check if you have enough paging space.

  You can increase the paging space through the smit command.

• Increase the default limits set by the /etc/security/limits file.

  1. Edit the /etc/security/limits file.

  2. Increase the settings of the fsize, cpu, data, stack, core, and rss process resource limits for your user ID.

  3. Issue your command again.

0706-317

Unresolved or undefined symbols detected

Possible Causes

• You attempted to compile a program that has functions, characters, or variables that are not defined. These symbols must be resolved to create the binary executable.

Procedures for Recovery

• Check for spelling errors.

  1. Edit the file you are compiling or linking and check for discrepancies.

  2. Change the symbols to the correct name.

  3. Issue your command again.

• Check to ensure that you are incorporating all of the libraries and the include files that are needed by your program.

0781-012

No device line in queue stanza

Possible Causes

This error message is displayed when the digester attempts to digest the qconfig file and encounters a problem in a device line. Error message 0781-017 Error in config file Name, line Number is always displayed before this message.

The following problems can occur with the device line:

• The device line is missing from the qconfig file.

• The device line is incomplete (An element such as a keyword is missing).

• The syntax of the device line is incorrect (The line breaks, tabs, or spaces are incorrect).

• The device name is incorrect.

  Note: These problems occur only when you edit the qconfig file directly. Changing the qconfig file with system commands or the System Management Interface Tool (SMIT) does not cause these errors.

Procedures for Recovery

• Determine which file caused the error message by looking at the preceding error message. Use one of the following procedures for recovery, depending on the cause of the error message:

  • If the device line is missing from the stanza, do the following:

    1. Edit the ConfigFileName file with a text editor.

    2. Add the device line immediately after the QueueName: line so that the two lines display as follows:

       QueueName:
          device = DeviceName1[, DeviceName2 . . . ]

       Include a tab before the device keyword and one space on each side of the = (equal sign).

       OR

       If the stanza containing DeviceName: is missing as well as the device line, delete the entire stanza containing the QueueName: line.

    3. Save the file.

  • If the device line in the stanza is incomplete, do the following:

    1. Edit the ConfigFileName file with a text editor.

    2. Change the device line so that it matches the following format:

       device = DeviceName1[, DeviceName2 . . . ]

       Make sure the spacing is correct.

    3. Save the file.

  • If the syntax is incorrect in the device line in the stanza, do the following:

    1. Edit the ConfigFileName file with a text editor.

    2. Make sure that the order and spacing are correct in the device line and that the line matches the following format:

       device = DeviceName1[,DeviceName2 . . . ]

       Note: Make sure the device and backend lines include a tab before the device and backend keywords, and a space before and after the Equals sign (=).

    3. Save the file.

  • If the device name is incorrect, do the following:

    1. Edit the ConfigFileName file with a text editor, ensuring the device name is correct.

    2. Save the file.

0781-017

Error in config file Name, line Number

Possible Causes

• The digester encountered a problem in the qconfig file. Any command that calls the digest command to create the qconfig.bin file can generate this message. A supplementary error message sometimes follows, specifying the problem. Sometimes no supplementary error message follows.

Procedures for Recovery

• Determine the nature of the error from the supplementary error message and follow the recovery instructions for that message.

• Change the qconfig file and reenter the command that caused the error to display.

  1. Change the qconfig file by using one of the following methods:

     • Restore the backup of the qconfig file, if one exists. If no backup exists, edit the existing qconfig file.

     • Use one of the following file-manipulating commands at the command line to change the qconfig file:

       chque	mkquedev
       chquedev	rmque
       mkque	rmquedev

     • Use options from the SMIT menus to edit the qconfig file.

     • Edit the qconfig file directly, using a text editor, and then save the file.

       Note: File-manipulating commands and System Management Interface Tool (SMIT) options do not make changes directly to the qconfig file. Instead, they make changes to a temporary file. If the temporary file is successfully digested by the digest command, it is copied to the qconfig file.

  2. Reenter the original command that caused the error message to display.

0781-035

No such request in queue Name -- perhaps it's done?

Possible Causes

• Using the System Management Interface Tool (SMIT), you specified an invalid job number to cancel a print job.

• From the command line, you specified an invalid job number with the qcan-x command or the enq -x command.

• You are not the owner of the job specified by the job number. The root user is an exception to this cause.

• The job specified by the job number is already processed; therefore, it is not in the specified queue.

Procedures for Recovery

• Using SMIT, locate a valid job number and cancel the print job.

  1. Use the Spooler (Print Jobs)--> Cancel a Print Job menu option.

  2. Enter a valid queue name in the PRINT QUEUE field. Select List to list valid queue names.

  3. Next to the JOB NUMBER field, select List to list valid job numbers.

  4. Select a job number. If a job is not listed, it has already been processed or does not exist.

  5. Select Do to delete the selected job.

• Using the qchk command, locate a valid job number.

  Enter the qchk -P(QueueName) command. The resulting display lists the job numbers and status for the specified queue.

  Specify a valid job number with the qcan -x or the enq -x command to cancel a print job.

• Change to the owner of the file, or to the root user.

  Enter the su command to change to the root user or to the owner of the file. Then use SMIT or commands to cancel the print job.

• The print job has been processed and cannot be canceled or queried.

0781-039

qdaemon appears to be dead

Possible Causes

• The qdaemon is not running, and a command is issued to update or digest the /etc/qconfig file.

Procedures for Recovery

• Shut down the qdaemon subsystem, then restart it.

  1. Use the lssrc -a command to show the status of the defined subsystems. The qdaemon subsystem is active if it is listed in the resulting table with a status of active.

  2. If the qdaemon is listed as active, stop the qdaemon subsystem with the stopsrc -s qdaemon command.

  3. Restart the qdaemon subsystem with the startsrc -s qdaemon command.

  4. Verify that the qdaemon is running with one of the following methods:

     • Use the ps - ef | grep qdaemon command to show the process status. The qdaemon is running if the /etc/qdaemon file appears in the resulting list.

     OR

     • Use the lssrc -a command to show the status of the defined subsystems.

0781-046

Illegal burst page option

Possible Causes

• You specified an invalid burst page option using the enq -B command.

Procedures for Recovery

• Specify a valid burst page option.

  1. Obtain a valid character pair for the page burst option from the -B Flag section of the enq command.

  2. Reenter the enq command, specifying a valid page burst option.

0781-047

Bad job number: String

Possible Causes

• You used the enq -x command to cancel a print job, and entered a job number that does not correspond to a job on the print queue.

Procedures for Recovery

• Reissue the enq -x command using a valid job number.

  1. Enter the lpstat command to obtain a list of valid job numbers. See the examples section for a more detailed explanation of the output of this command.

  2. Reenter the enq -x command, specifying a valid job number, to cancel the print job.

0781-048

Bad queue or device name: String

Possible Causes

• You issued a print request to a nonexistent queue or device. This error message can occur when you are using any of the following commands, each of which has an option to specify a print queue and printer device:

  cancel	lprm
  disable	qadm
  enable	qcan
  enq	qprt
  lpr

Procedures for Recovery

• Determine the name of existing queues or printers, and reenter the command with valid specifications.

  At the command line, enter one or more of the following commands to get the information you need:

  lpstat

  Lists all the queues and corresponding devices defined for the system.

  lsallq

  Lists all configured queues.

  lsquedev

  Lists all devices (printers) configured for a specified queue.

• Reenter the command without specifying a printer or printer-queue combination.

  This causes the print request to go to the default queue, which is the first queue defined in the /usr/lib/lpd/qconfig file.

0781-050

Bad PRINTER or LPDEST env. variable String

Possible Causes

• You used one of the following commands without specifying a print queue or printer device, and the PRINTER and LPDEST environment variables specify nonexistent queues or devices:

  cancel	qadm
  enq	qcan
  lp	qpri
  lpr	qprt
  lprm

Procedures for Recovery

• Ensure that the PRINTER or LPDEST environment variables specify valid queue or printer names.

  Note: The system checks the LPDEST environment variable first; if it is set, it is used. If the LPDEST environment variable is not set, the PRINTER environment variable is checked.

  1. Determine the name of existing queues or printers by issuing one of the following commands at the command line:

     lpstat

     Lists all the queues and corresponding devices defined for the system.

     lsallq

     Lists all configured queues.

     lsquedev

     Lists all devices (printers) configured for a specified queue.

     Change the value of the PRINTER or LPDEST environment variable in one of the following ways:

     • If you are in sh (Bourne) shell, enter one of the following commands:

       PRINTER=NewValue; export PRINTER

       OR

       LPDEST=NewValue; export LPDEST

     • If you are in csh (C) shell, enter one of the following commands:

       setenv PRINTER=NewValue

       OR

       setenv LPDEST=NewValue

     • If you are in ksh (Korn) shell, enter one of the following commands:

       export PRINTER=NewValue

       OR

       export LPDEST=NewValue

  2. Verify the current value of the PRINTER or LPDEST environment variables by entering one of the following commands:

     echo $PRINTER

     OR

     echo $LPDEST

0781-063

Error reading FileName. Errno = Number

Possible Causes

• You ran the qadm command with the-K, -U, -D, or -X flag, which created a job description file with a length of 0 bytes, in the /var/spool/lpd/qdir directory.

• The error was generated when the qdaemon was started.

Procedures for Recovery

• Use the df /var command to check if the /var filesystem is out of space.

  1. Manually clear the /var/spool/lpd subdirectories of unnecessary files.

  2. Run the qadm command again.

0781-088

Queue PrinterName went down, job is still queued:

Default short form

Backend: Complete backend command

Backend Exit Value: Exit value of the backend command

Job Submit Time: date/time Current Time: date/time

Optional long form

Backend: Complete backend command

Backend Exit Value: Exit value of the backend command

Job Submit Time: Date and time the print job was submitted

Current Time: Date and time this message is generated

Host Name: Hostname of the machine where this message is generated

JDF File Name: File name of the job definition file

Print Command: Base name of the print command issued by user

Enq Options: Option flags of the print job

Job Title: Title string of the print job

Job Size: Number of blocks occupied by the data files in this print job. A block is a 1024 byte space on the file system.

File(s): A list of the file names in this print job as well as the file modes, file type, uid, gid, and file size in bytes.

Possible Causes

• You tried printing to a printer on a remote host, but your host name was not in either the /etc/hosts.lpd or the /etc/hosts.equiv file on the remote host.

• You attempted to print to a remote printer, but the lpd daemon on the remote host was not active.

• The file name in the /etc/qconfig file has an incorrect queue device name. This caused a write error which caused the print queue to die.

Procedures for Recovery

• Ensure that your host name is in either the remote /etc/hosts.lpd or /etc/hosts.equiv file. Use the refresh command to implement the changes.

  refresh -h HostName -s lpd

• Use the startsrc command to start the lpd daemon on the remote printer:

  startsrc -h HostName -s lpd

• Ensure that the file name in the etc/qconfig file has the name of a valid print device. Run the qadm command to bring the print queue back up.

  qadm -U QueueName

0781-100

Failure to create QueueName

Possible Causes

Note: This error message is displayed on the system console only.

• Using the System Management Interface Tool (SMIT), you specified an invalid device name when adding a queue device.

• From the command line, you specified an invalid device name with the mkquedev command when adding a queue device.

Procedures for Recovery

• Using SMIT, remove the invalid device name, enter a valid device name, and restart the qdaemon subsystem.

  1. Using SMIT, go to the Devices--> Printer/Plotter--> Manage Local Printer Subsystem--> Local Printer Queue Devices--> Remove a Queue Device menu option.

  2. Select the queue from which to remove the device, and press the Enter key.

  3. At the Remove a Queue Device screen, select List to list the devices in the queue.

  4. Select the invalid device name and press Enter.

  5. Go to the Devices--> Printer/Plotter--> Manage Local Printer Subsystem--> Local Printer Queue Devices--> Add Another Local Queue Device to an Existing Queue menu option, and enter a valid device name in the NAME of device to add field.

  6. Press the F6 key to verify that the device name following the -d flag is valid.

  7. If the device name is invalid, select Cancel, type a valid device name, and press the Enter key.

  8. Exit SMIT and return to the command line.

  9. At the command line, use the startsrc -s qdaemon command to restart the qdaemon subsystem.

• From the command line, remove the invalid device name, enter a valid device name, and restart the qdaemon subsystem.

  1. Use the rmquedev command to remove the invalid device name, as follows:

     rmquedev -q QueueName -d DeviceName . . .

  2. Use the mkquedev command to enter a valid queue device name, as follows:

     mkquedev -q QueueName -d DeviceName . . .

  3. Use the startsrc -s qdaemon command to restart the qdaemon subsystem.

0781-102

Invalid printer name: String

Possible Causes

• You issued a printer status request to a nonexistent queue or device using one of the following commands:

  enq   lpstat
  lpq   qchk

Procedures for Recovery

• Reenter the command.

  Reenter one of the commands listed above without specifying a queue or queue-printer combination. The status of all valid queues and associated printers is displayed.

  OR

  Determine the names of existing queues or printers, and reenter the command with valid specifications. Use the following commands to get the information you need.

  lsallq

  Lists all configured queues.

  lsallqdev

  Lists all devices (printers) configured for a specified queue.

0781-104

No queue devices detected

Possible Causes

• A job was submitted to the queue with no queue device attached to it.

Procedures for Recovery

• Resubmit the job, specifying a valid queue device.

  1. Use the enq -A command to list the available queue devices.

  2. Resubmit your job, specifying a valid queue device.

0781-113

Insufficient memory

Possible Causes

• The system has run out of both virtual and real memory.

Procedures for Recovery

• Remove any unnecessary processes from the system.

  1. Enter the su command to change to the root user.

  2. Enter the ps -eaf command to list all processes currently on the system.

  3. Use the kill command to remove any unnecessary processes.

• Add more page space with the System Management Interface Tool (SMIT) utility (Use the Physical and Logical Storage option in the Main Menu).

• Add more physical memory.

0781-117

Cannot execute digester FileName

Possible Causes

• The /usr/lib/lpd/digest file does not exist.

• You do not have execute permission on the /usr/lib/lpd/digest file.

Procedures for Recovery

• Verify that the /usr/lib/lpd/digest file exists.

  1. Enter the su command to change to the root user.

  2. Enter the cd /usr/lib/lpd command to change to the proper directory.

  3. Enter the ls -l digest command to verify that the file exists.

  4. If the digest file does not exist, reload it from the original system software. See your system administrator for assistance.

• Ensure that you have execute permission on the /usr/lib/lpd/digest file.

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

0781-132

Cannot open message file FileName

Possible Causes

• You used an invalid or incorrect message file path or specification with the qprt command.

• You do not have read access on the specified message file.

Procedures for Recovery

• Specify a valid file name when using the -M option.

  1. Use the li -l FileName command to verify the existence of the specified message file.

  2. If the message file does not exist, use an editor to create the desired file.

  3. Reissue the qprt command, specifying a valid message file.

• Ensure that you have read access to the message file specified.

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

0781-156

Cannot find config file Name

Possible Causes

• You issued the enq command and the /etc/qconfig file does not exist.

Procedures for Recovery

• Ensure that the /etc directory contains a qconfig file.

  1. Enter the cd /etc/qconfig command to verify that the qconfig file exists in the /etc directory.

  2. If the qconfig file does not exist, use the su command to change to the root user, and use an editor to create a qconfig file.

  3. Reenter the enq command.

0781-161

fatal: Argument PrinterID is not an accessible file

Possible Causes

• You attempted to print a file but you do not have access permission for the file.

• You attempted to print a file but you misspelled the file name.

Procedures for Recovery

• Obtain access permission for the file you want to print.

• Verify the file name and try again.

0781-162

Cannot awaken qdaemon (request accepted anyway)

Possible Causes

• The qdaemon is not running or has been stopped.

Procedures for Recovery

• Restart the qdaemon subsystem.

  1. Enter the startsrc -s qdaemon command to start the qdaemon subsystem.

  2. Verify that the qdaemon is running by doing one of the following:

     • Enter the ps -ef | grep qdaemon command to show the process status.

     OR

     • Enter the lssrc -a command to show the status of the defined subsystems.

0781-182

Problem with line Number in FileName

Possible Causes

• The /etc/qconfig file has been damaged. The qconfig file contains printer queue information, and the error is caused by the lsque or lsallq command.

Procedures for Recovery

• Correct errors in the /etc/qconfig file.

  1. Enter the cd /etc command to change to the /etc directory, where the qconfig file is located.

  2. Using an editor, view the qconfig file and correct any errors you find.

0781-183

Cannot delete QueueName. Queue contains devices

Possible Causes

• Using the System Management Interface Tool (SMIT), you attempted to remove a queue, but the queue contained associated devices.

• From the command line, you entered the rmque command to remove a queue, but the queue contained associated devices.

Procedures for Recovery

• Using SMIT, remove the associated devices before removing the queue.

  1. Select Devices--> Printer/Plotter-->Manage Local Printer Subsystem--> Local Printer Queue Devices-->Remove a Queue Device.

  2. Select the name of the queue you want to delete.

  3. Select List to display a list of devices.

  4. Select the queue device you wish to remove.

  5. Select Do to remove the queue device.

  6. Repeat until all queue devices are removed.

  7. After the devices have all been removed, use the following SMIT menu option to remove the queue: Devices-->Printer/Plotter--> Manage Local Printer Subsystem-->Local Printer Queues--> Remove a Queue.

  8. Select List to display a list of queues.

  9. Select the name of the queue you want to delete.

  10. Select Do to remove the queue.

• Remove the associated devices before using the rmque command to remove the queue.

  1. Enter the lsallq command to list the queues configured for your system.

  2. Enter the lsallqdev -q QueueName command to list all the devices associated with the queue you want to delete.

  3. For each device in that queue, enter rmquedev -q QueueName -d DeviceName command to remove the device.

  4. After deleting all the devices, enter the rmque -q QueueName command to delete the queue.

0781-189

Queue:device, String: not found in qconfig file. Not deleted

Possible Causes

• Using the System Management Interface Tool (SMIT), you attempted to remove a queue device not contained in the /etc/qconfig configuration file.

• From the command line, you used the rmquedev command with an invalid queue device.

Procedures for Recovery

• Using SMIT, verify the queue device name and then remove it.

  1. From SMIT, select the menu option Devices--> Printer/Plotter--> Manage Remote Printer Subsystem--> Server Services--> Manage Local Printers Subsystem--> Local Printer Queue Devices--> Remove a Queue Device--> (queue name).

  2. Select List to display all valid device names.

  3. Select the desired device from the device name list.

  4. Select Do to remove the selected device.

• Verify the queue device name and then remove it using the rmquedev command.

  1. Enter the lsallq command to list the queues configured for your system.

  2. Enter the lsallqdev -q QueueName command to list all the queue devices for that queue.

  3. Enter the rmquedev -q QueueName -d DeviceName command, ensuring that you enter a valid device name.

0781-194

Syntax error in qconfig file

Possible Causes

• An invalid queue stanza entry was entered into the /etc/qconfig file when the lsque or lsallq command was issued.

Procedures for Recovery

• Ensure that all queue stanza entries are correct.

  1. See the list of valid queue stanza (configuration) entries for the qconfig file.

  2. Use an editor to correct any invalid entries contained in the qconfig file.

  3. After correcting the qconfig file, reenter the lsque or the lsallq command.

0781-209

Option not supported

Possible Causes

• A print request with an invalid option was placed in the /usr/spool/lpd directory.

Procedures for Recovery

• Check the remote print jobs to ensure that the print request was made correctly.

  1. Use the following System Resource Controller (SRC) commands that control the lpd daemon subsystem to gain more information about the source of the error condition:

     startsrc

     Starts a subsystem, group of subsystems, or a subserver.

     stopsrc

     Stops a subsystem, group of subsystems, or a subserver.

     refresh

     Causes the subsystem or group of subsystems to reread the appropriate configuration file.

     traceson

     Enables tracing of a subsystem, group of subsystems, or a subserver.

     tracesoff

     Disables tracing of a subsystem, group of subsystems, or a subserver.

     lssrc

     Gets the status of a subsystem, group of subsystems, or a subserver.

  2. See the lpd command for a list of valid options and their functions, as well as more information.

     The following flags to the lpd command enable debugging and logging:

     -d	Sends debugging information to the syslogd daemon.
     -l	Sends logging information to the syslogd daemon.

0781-254

No print server specified

Possible Causes

• At the command line, you entered the rembakcommand without specifying a print server. The rembak command should be called only by the qdaemon command.

Procedures for Recovery

• Specify a valid printer server.

  See the rembak command for a list of valid options and flags and their functions.

• Use the enq command or the System Management Interface Tool (SMIT) to request a print job.

Notes:
 

1. The rembak command is not intended to be entered on the command line by a user.

2. Always use a flag with the enq command.

0781-277

Error from digester String, status = Number, rv = Number

Possible Causes

• A program called the digest command and an error occurred when the digester attempted to convert the qconfig file. One or more additional and more specific error messages precede this message.

Procedures for Recovery

• Follow the recovery procedure for each error message that accompanies this message.

0781-282

Not enough args to digest

Possible Causes

• The bin and config files were not specified for the digest command.

Procedures for Recovery

• Ensure that the digest command is being issued properly.

  1. The digest command should only be called by the qdaemon command, not entered from the command line. See the qdaemon command for more information.

  2. Check the qconfig file for invalid entries. A list of examples of proper queue stanza configuration entries can be found at the top of the qconfig file.

0781-304

Unable to open PrinterID as standard out

Possible Causes

• There is a printer cabling problem.

• The printer is not configured to the system correctly.

Procedures for Recovery

• Verify printer configuration.

• Verify that the cable to the printer is not damaged or disconnected from the system or printer.

0781-305

Retrying qdaemon

Possible Causes

• The printer is not responding.

• There is a printer cabling problem.

Procedures for Recovery

• Ensure that the printer is on.

• Reset the printer, then disable and enable it again.

  Note: See error message 0781-304 for more information.

0781-310

No such request in any local queue -- perhaps it's done?

Possible Causes

• You tried to change the priority of a print job or delete a print job, but the job number does not exist.

• You tried to change the priority of a print job or delete a print job that does not belong to you.

Procedures for Recovery

• Ensure that the job number exists.

  Note: The job number may not exist because the job has already printed or because you entered an invalid job number. If the job number is valid, ensure that you either own the job or are logged on as root. If you are not logged on as root, you cannot delete or modify jobs issued by other users.

  Using SMIT, list jobs in the queues by selecting the Spooler (Print Jobs)--> Show the Status of Print Jobs option. In the Show the status of ALL printjobs? field, select Yes and then press the Enter key. A table of print job numbers and user IDs is displayed.

  OR

  At the command line, use the lpstat command, the enq -A command, or the qchk -A command to display a table of print job numbers and user IDs.

• Ensure that the print job belongs to you.

  Check your user logon identity. At the command line, enter the whoami command (with no spaces) to display the current user name. Enter the who am i command (with spaces separating the words) to display the user identity initially used to begin the current logon session. To delete or change the priority of a print job, you must either own the print job or be logged on as the root user. Use the su command to change users if needed.

0781-320

No accounting file specified for queue: QueueName

Possible Causes

• The pac command was used to generate a summary file without defining an accounting file in the /etc/qconfig file.

Procedures for Recovery

• Add a line to the qconfig file to define the accounting file.

  1. Use an editor to place an acctfile = clause in the appropriate location within the /etc/qconfig file. See the qconfig article for more specific information.

  2. Reenter the pac command.

0781-321

Problem opening account file. Errno = Number

Possible Causes

• You issued the pac command, but the accounting file specified in the acctfile = clause in the /etc/qconfig file does not exist.

Procedures for Recovery

• Locate and create the correct path name for the accounting file by doing the following:

  1. Enter the view /etc/qconfig command.

  2. Scroll down to the acctfile = PathName line.

  3. Enter the touch command to create the path name assigned by the acctfile line.

  4. Reissue the pac command.

0791-001

Argument not valid

Possible Causes

• You entered the iconv command without using both the -f and the -t flags.

Procedures for Recovery

• Reissue the iconv command using the -f and the -t flags.

  The iconv command requires you to specify the -f flag with the code set from which you are converting and the -t flag with the code set to which you are converting.

0791-004

Cannot open converter

Possible Causes

• You entered an invalid converter value when using the iconv command.

• A memory allocation was attempted and the memory allocation failed, producing an allocation failure return code.

Procedures for Recovery

• Reenter the iconv command using a valid converter value.

  Ensure that you specify the correct flags, as well as a valid converter value, when you reenter the iconv command.

• Ensure that you have adequate memory available.

  Follow the procedure described in Recoveringfrom Insufficient Memory Errors .

0803-005

Cannot open the String directory

Possible Causes

• You used the news command, but access was denied because you do not have read-execute permission to the /usr or the /usr/news subdirectories.

Procedures for Recovery

• Establish read-execute permissions by doing one of the following:

  • Determine ownership of the /usr/news directory by entering the ls -ld /usr/news command. If you are the owner of the directory, enter the chmod +rx /usr/news command to establish the necessary permissions.

    If you are not the owner of the directory, obtain the necessary permissions by entering the su command to change to the root user. Change access permission on the directory by entering the chmod +rx /usr/news command.

    OR

  • Ask the system administrator or the owner of the directory to make the necessary permissions changes. See Recoveringfrom File and Directory Permission Errors.

    Note: There is a symbolic link between the /usr/news and the /var/news directories. If the link between these directories is broken, Error Message 0803-007 is displayed. If the permissions are correct on /usr and /usr/news, see Error Message 0803-007.

0803-006

There is not enough memory available now

Possible Causes

This error occurs when using the news command. The system attempts to allocate memory using the malloc subroutine while space is unavailable in the /usr/news subdirectory. This occurs for one of the following reasons:

• Too many processes are running.

• A file is too large or there are too many files.

Procedures for Recovery

• Remove unnecessary processes or wait for them to stop running.

  Enter the ps -eaf command to check the number of processes that are running. If there are too many processes running, do one of the following:

  • Wait until some of the processes are completed.

  • Use the kill command to stop a process that you started. If you did not start the process, use the su command to change to the root user and stop the process with the kill command, or ask the owner of the process to stop the process.

• Remove unnecessary files or free up sufficient memory for the files.

  Use the li -ld command to check the size and the number of files that exist in the /usr/news subdirectory. If there is not enough memory because of the size or the number of files, more memory can be freed by doing one of the following:

  • Remove unnecessary files using the rm or delete command.

• Increase the paging space. For information on adding paging space, see Understanding Paging Space Allocation Policies in AIX Version 4.3 System Management Guide: Operating System and Devices or Managing Paging Spaces in AIX Version 4.3 System Management Guide: Operating System and Devices.

0803-007

Cannot move to the String directory

Possible Causes

You used the news command, but access was denied for one of the following reasons:

• You do not have read-execute permission to the /var or var/news directories, or they do not exist.

• The symbolic link between the /usr/news directory and the /var/news directory does not exist.

Procedures for Recovery

• Verify that the /var and /var/news directories exist with the correct ownership and permissions.

  1. Enter the ls -ld /var/news command to verify the directory's existence.

  2. If the directories do not exist, do the following:

     1. Create the directory by entering the mkdir /var/news command.

     2. Ensure that the ownership for the /var/news directory is bin for group and bin for owner by entering the ls -ld /var/news command.

     3. Establish full permissions for the directory by entering the chmod 777 /var command and the chmod 777 /var/news command.

  3. If the directories do exist, check the ownership and permissions using the procedures outlined in steps b and c.

• Ensure that the symbolic link exists.

  1. Use the su command to change to the root user. See if the link exists by entering the ls -ld /usr/news command. A symbolically linked directory is indicated by an arrow and the contents of the symbolic link listed after the directory name, as follows:

     /usr/news -> /var/news

  2. If the /usr/news directory is not followed by an arrow pointing to the /var/news directory, enter the ls -ld /var/news command to verify that the /var/news directory exists. If it does not exist, do the following:

     1. Create the directory by entering the mkdir /var/news command.

     2. Ensure that the ownership for the /var/news directory is bin for group and bin for owner by entering the ls -ld /var/news command. Also, check that all users have the following read-write-execute permissions:

        drwxrwxrwx 3bin bin 512 Mar 04 11:48 /var/news

        Enter the chgrp bin /var/news command to change the group. Enter the chown bin /var/news command to change the owner. Enter the chmod 777 /var/news command to obtain full read-write-execute permissions.

     3. If the /usr/news file exists as an unlinked file, remove it using the rmdir /usr/news command.

     4. To create the link between the /usr/news and the /var/news files, enter the ln -s /var/news /usr/news command.