Error Messages for Component ID 0481

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 -e command 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.