Error Messages for Component ID 0781

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   lpstatlpq   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 print jobs? 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.