The print request requested a printer definition that is not defined in the Infoprint Server Printer Inventory. The printer definition name might have been specified on a command, such as the lp or lpr command, or in the SUBSYS parameter on the DD statement.

In the message text, printer-name is the name of the requested printer definition. lp1 is the name of the Infoprint Server default printer definition, which is used if no other printer definition name is specified.

The request was not completed.

Make sure that you have spelled the name of the printer definition correctly, using the correct uppercase and lowercase characters. If you specify the name of the printer definition in the SUBSYS parameter of a DD JCL statement, enclose the printer definition name in single quotation marks if it contains lowercase characters.

If the name is lp1, specify the name of the printer definition on the print command or in the SUBSYS parameter on the DD JCL statement. If you use the lp command, you can instead specify the name of the printer definition in the PRINTER or LPDEST environment variable.

You can run the z/OS UNIX lpstat -p command to get a list of available printers in the Printer Inventory. If an appropriate printer definition exists, enter the command or run the job again, specifying that printer. Otherwise, ask your administrator to define an appropriate printer.

Not applicable.

Define a printer in the Printer Inventory if requested.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

All data sets allocated on the system spool for the print job with job ID jobid have completed processing. After this message, the job ID and final status of the data set is reported. The final status can be completed, failed, or purged.

completed

The file has been processed successfully.

failed

Processing has failed.

purged

The file was deleted before printing.

For completed or failed data sets, the files remain on the JES spool for one of these reasons:

• Your administrator has specified that files should be retained after transmission to a LAN printer or to a print server. The file will be removed from the spool when the retention period expires.
• An error caused the data set to be retained on the spool.

Data sets are removed from the spool for reasons such as:

• The data set finished printing.
• The data set was transmitted to a remote system or printer for printing. In this case, the data set might not yet be finished printing, or a transmission failure might have occurred.
• The operator deleted the data set from the system spool.
• The system programmer off-loaded all SYSOUT data sets from the JES spool.

Processing continues.

None.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A file error, filter error, or system error has occurred. objectname is the name of the file, filter program, sendmail command, printer address, or other object in error. errmsgno errmsgtext is the message number, if available, and the message text generated by a system program or by the filter program.

The request was not completed.

If you specified objectname, make sure that the name is valid. Also, see the description for message errmsgno. If you did not specify objectname, contact your system programmer for assistance.

Not applicable.

See the description for message errmsgno.

• If objectname is a printer address and the error message indicates a TCP/IP connection error, ping the printer to check that the printer is turned on and the TCP/IP network is working.
• If an Infoprint Server module could not be found, make sure that the LIBPATH environment variable is set correctly in the aopstart EXEC.
• If the error text indicates a RACF® error, a SAF error, or a permission error, run the aopsetup EXEC to set permissions. For example, if you use the default group names for Infoprint Server operators (AOPOPER) and administrators (AOPADMIN), enter:

  /usr/lpp/Printsrv/bin/aopsetup aopoper aopadmin

For more information about the aopstart and aopsetup EXECs, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A system error has occurred during the processing of the request. This message might be followed by message AOP047E, which contains diagnostic information.

The request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

Look for other messages that indicate the reason for the failure on the terminal where Infoprint Server was started or in the console log.

If a message indicates a RACF or SAF error (such as, message EDC5164I):

• Make sure the user ID that starts Infoprint Server is a valid z/OS® UNIX user ID. The user ID must have an OMVS segment, the default group for the user ID must have an OMVS segment with a group identifier (GID), and the user ID must have a home directory. The user identifier (UID) for the user should be different from other UIDs in the installation.
  Note:

  If you use the AOPSTART procedure to start Infoprint Server, check the user ID that is associated with this procedure.
• Make sure that the password for the user ID that starts Infoprint Server has not expired.
• Run the aopsetup shell script to set up the correct z/OS UNIX permissions for Infoprint Server directories and executable files.

For information about how to set up security for Infoprint Server and how to run the aopsetup shell script, see z/OS Infoprint Server Customization.

If you cannot correct the problem, contact the IBM® Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A request was submitted with a job ID that is not valid.

The request was not completed.

Submit the request with a valid job ID.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server created a print job and successfully allocated at least one document on the JES spool. If an error occurs processing a document, Infoprint Server issues a separate message for that document.

In the message text:

infoprint-jobid

The ID of the print job that Infoprint Server assigned.

zos-jobid

The ID of the print job that JES assigned.

printer-name

The name of the printer to which the job was submitted. The printer name is the name assigned to the printer definition for the printer in the Infoprint Server Printer Inventory.

Processing continues.

None.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A request was submitted with an option that is missing a required argument.

The request was not completed.

For the lp, lpstat, or cancel command, view the appropriate man page for the correct options. For other requests, see the necessary documentation. Enter the request again with the required argument.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This message can be sent by most commands and filters. It indicates that the user specified an option character with the command, with the filter-options attribute, or on the filter defined for the printer. The message is usually preceded by the program that sends it. The message is often followed by the usage message for the command or filter.

The request was not completed.

Reenter the command with the correct options character. If you are not entering an incorrect options character, contact the system programmer.

For the lp, lpstat, or cancel command, view the appropriate man page for the correct options. For other requests, see z/OS Infoprint Server User’s Guide.

Not applicable.

Check the printer definition associated with the print job for the cause of the error. If the printer definition did not cause the error, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A Dynamic Allocation error has occurred. An error occurred attempting to dynamically allocate a data set.

In the message text:

dsname

The data set name.

retcode

The Dynamic Allocation return code.

errorcode

The Dynamic Allocation error code.

infocode

The Dynamic Allocation information code.

The print request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

See Dynamic Allocation diagnostic information in the z/OS MVS Programming: Authorized Assembler Services Guide.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The data set does not exist or is not cataloged.

In the message text, dsname is the name of the data set.

The request was not completed.

Catalog the data set or specify the correct data set name.

Not applicable.

Mount the volume that contains the data set.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The volume on which the data set resides is not currently mounted.

In the message text:

dsname

The name of the data set.

volser

Specifies the serial number of the magnetic tape or DASD volume to contain the data set.

The request was not completed.

Notify your system programmer that this error has occurred.

Not applicable.

Mount the volume that contains the data set.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The job jobid specified in the request was not found.

The request was not completed.

Use the lpstat command to display job IDs known to the system. Submit the request again with a valid job ID specified.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Print Interface received an exception of unknown value.

The request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

Contact the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The cancel request for job jobid was successfully completed.

The job was canceled.

None.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A query jobs request (for example: lpstat -u userid) did not find any jobs for userid.

Processing continues.

None.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A query jobs request (for example: lpstat -p printer-name) did not find any jobs for printer-name.

Processing continues.

None.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

attributevalue specified for attributename in the print request (for example: lp -o attributename=attributevalue) exceeds the maximum value (maximumvalue) allowed by the destination printer definition (printer-name). For example, the copies attribute in the print request exceeds the maximum copies defined in the printer definition.

The request was not completed.

Submit the request again with attributevalue less than or equal to maximumvalue.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The value of an Infoprint Server job attribute was specified correctly. However, the printer definition for the selected printer does not permit that value. For example, the lp command might have specified the duplex=tumble attribute. However, the printer definition indicates that the printer does not support the tumble option.

In the message text:

printer-name

Name of the printer definition that you requested or that Infoprint Server selected to print the file. This printer definition is defined in the Infoprint Server Printer Inventory.

attribute-name

Name of the Infoprint Server job attribute whose value is not supported. If you used z/OS JCL to submit the request, you might have specified a JCL parameter that corresponds to this job attribute. Or, Infoprint Server might have internally specified this job attribute.

attribute-value

The attribute value that is not supported.

If attribute-name is "document-format", this means that the printer definition does not accept files with the specified data format. For example, if attribute-value is "modca-p", this means that the printer definition does not accept the MO:DCA-P (AFP) data format. If attribute-value is "other", Infoprint Server might not have been able to detect the data format of your file. Infoprint Server automatically detects the data format unless you specify the document-format job attribute.

The request was not completed.

If you specified the attribute-name attribute or a corresponding JCL parameter, specify a value for the attribute or JCL parameter that printer definition printer-name supports. Contact your administrator to determine, or change, the attribute values that are supported in the printer definition.

If attribute-name is "document-format", resubmit your print request to a printer that your administrator says accepts the data format indicated in attribute-value. Or, your administrator might be able to specify a data transform in the printer definition to transform your data format to one that the printer supports.

If you think that Infoprint Server did not accurately detect the data format of your data, make sure that your data is not corrupted and make sure that the logical record length (LRECL) specified on the DD statement, if one is used, is correct. In some cases, you might be able to correct the problem by specifying the data format in the Infoprint Server document-format job attribute. For example, if you use JCL to print the data set, you can specify the document-format attribute in the PRTATTRS parameter on the OUTPUT JCL statement.

For information about Infoprint Server job attributes and the PRTATTRS JCL parameter, see z/OS Infoprint Server User’s Guide.

Not applicable.

If you want the printer definition to accept the attribute-value, use the Infoprint Server ISPF panels to change the supported data formats or other supported values in the printer definition. For information about how to control the validation that Infoprint Server does, see z/OS Infoprint Server Operation and Administration.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The system OUTADD macro detected an error when Print Interface attempted to add the print job on the JES spool. An error was detected in a parameter in the output descriptor. The message text contains the parameter in error, return code, and reason code from the OUTADD macro.

The request was not completed.

Correct the attribute on the print request that corresponds to the errorparameter. Or, notify your system programmer that this error occurred.

Not applicable.

Correct the attribute in the printer definition that corresponds to the errorparameter. If the error persists, contact the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An error has occurred with object name objectname. objectname is the name of the file, filter program, or other object in error. errmsgno errmsgtext are the message number and message text generated by a system program or by the filter program.

Processing continues.

If you specified objectname, make sure that the name is valid. Also, see the description for message errmsgno. If you did not specify objectname, contact your system programmer for assistance.

Not applicable.

See the description for message errmsgno.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A print request was not accepted because the number of job IDs is at the system limit.

The request was not completed.

Enter your print request again. If the error persists, notify your system programmer that this error occurred.

Not applicable.

Reduce the total number of jobs currently in the system.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The line printer daemon (lpd) received a client request that contained a control file with a control code that is not defined by Request For Comments (RFC) 1179.

In the message text, reqid identifies the control code.

The request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

Make sure that the line printer requestor (lpr) on the client system creates control files that contain only control codes that are defined by RFC 1179.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The print request failed because the attempt to write the SYSOUT data set to the JES spool failed.

The request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

Investigate why the write attempt failed. For example, the JES spool might be full, or the size limit of a JES SYSOUT data set might have been exceeded.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A cancel request for job jobid failed and the job could not be deleted from the JES spool. To cancel a print job, the job must have completed spooling and cannot already be selected for processing.

In the message text, printer-name is the name of the printer definition to which the job was directed.

The request was not completed.

To cancel a print job printed to a LAN printer in your TCP/IP or SNA network, ask your IP PrintWay™ operator to cancel it.

To cancel a print job transmitted to a LAN printer using IP PrintWay and already selected for processing, do one of these:

• IP PrintWay basic mode: Use the Infoprint Server ISPF panels to delete the transmission-queue entry for the data set. For information, see z/OS Infoprint Server Operation and Administration.
• IP PrintWay extended mode: Use Infoprint Central to delete the data set.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The program indicated before the message number is not running APF-authorized. This is most likely due to an error during installation.

The request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

Do not use NFS to mount the bin directory (for example, /usr/lpp/Printsrv/bin) that contains Print Interface executables because this action bypasses APF-authorization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The attribute attributename is an abbreviation for any one of the attributes listed in attributelist.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Correct the attribute name, specifying enough characters in the attribute name to make the name unique. Then enter your print request again.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The print request was not allocated on the JES spool. This might have occurred because JES is not at the required level.

The request was not completed.

Notify your system programmer that this error occurred.

Not applicable.

Make sure that JES is at required level, as documented in z/OS Infoprint Server Customization. If JES is at the required level, investigate why the SYSOUT data set allocation failed. For example, the JES spool might be full, or the system might have exceeded the maximum number of SYSOUT data sets allowed on the spool.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An error occurred during allocation of an output data set on the JES spool.

In the message text, printdestination is either the destination name or the destination node specified in the printer definition for the printer in the Printer Inventory.

The request was not completed.

Notify your system programmer or administrator that this error occurred. After the error is corrected, enter your print request again.

Not applicable.

Change printdestination in the printer definition to a valid value. You can use Infoprint Server ISPF panels to list all printer definitions in the Printer Inventory with the value in error. If printdestination is a valid value, contact the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The attribute named attributename is not valid. The problem might be that a JCL parameter, such as FSSDATA or PRTATTRS, specified a job attribute that is not valid. For example: FSSDATA='myprinter' instead of FSSDATA='printer=myprinter'.

In the message text, optionsource generally identifies where the error occurred.

For example, if optionsource is:

• The name of an attributes file, the error occurred in the named attributes file
• “FSSDATA”, the error occurred in the FSSDATA parameter on the OUTPUT JCL statement
• “job-attributes”, the error occurred in a job attribute
• “-o”, the error occurred in the -o option
• “PRTATTRS”, the error occurred in the PRTATTRS parameter on the OUTPUT JCL statement

If the FSSDATA or PRTATTRS JCL parameter contains an incorrect attribute, IP PrintWay rejects the print job and does not process it. The print job remains on the JES spool with a status of "rejected" so that IP PrintWay does not attempt to process the print job again until the operator releases it.

If the -o option, an attributes file, or the LPD control file contains an incorrect attribute, Infoprint Server does not write the print job to the JES spool.

Submit the request again with a valid attribute assignment.

If the print job is on the JES spool, delete it.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Print Interface expected a matching value for stringvalue but did not find one.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with a matching value for stringvalue.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The value stringvalue is not valid for optionsource.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file. If optionsource is printer-uri, the Uniform Resource Identifier (URI) specified in the printer definition is not valid.

The request was not completed.

Correct the error and submit the request.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Print Interface expected to find stringvalue1 in this context, but instead found stringvalue2. The problem might be that a JCL parameter, such as FSSDATA or PRTATTRS, specified a job attribute that is not valid. For example: FSSDATA='myprinter' instead of FSSDATA='printer=myprinter'.

In the message text, optionsource generally identifies where the error occurred.

For example, if optionsource is:

• The name of an attributes file, the error occurred in the named attributes file
• “FSSDATA”, the error occurred in the FSSDATA parameter on the OUTPUT JCL statement
• “job-attributes”, the error occurred in a job attribute
• “-o”, the error occurred in the -o option
• “PRTATTRS”, the error occurred in the PRTATTRS parameter on the OUTPUT JCL statement

If the FSSDATA or PRTATTRS JCL parameter contains an incorrect attribute, IP PrintWay rejects the print job and does not process it. The print job remains on the JES spool with a status of "rejected" so that IP PrintWay does not attempt to process the print job again until the operator releases it.

If the -o option, an attributes file, or the LPD control file contains an incorrect attribute, Infoprint Server does not write the print job to the JES spool.

Submit the request again with the correct value. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

If the print job is on the JES spool, delete it.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

stringvalue is shorter than the acceptable minimum length of minimumlength.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with the correct value for stringvalue. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

Not applicable.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

stringvalue is longer than the acceptable maximum length maximumlength.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with the correct value for stringvalue. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

Not applicable.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

value1 is less than the acceptable minimum value minimumvalue.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with the correct value for value1. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

Not applicable.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

value1 exceeds the acceptable maximum value maximumvalue.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with the correct value for value1. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

Not applicable.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A request was sent with less than the minimum number of values minimumnum.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with the correct number of values. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

Not applicable.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A request was sent with more than the maximum number of values maximumnum.

In the message text, optionsource identifies where the error occurred. For example, if optionsource is “-o”, the error occurred in the -o option. If optionsource is the name of an attributes file, the error occurred in the named attributes file.

The request was not completed.

Submit the request again with the correct number of values. If optionsource is the name of an Infoprint Server configuration file, notify your system programmer that this error occurred.

Not applicable.

If the error occurred in an Infoprint Server configuration file, correct the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The size of the job submitted for printing, including all files in the job and all copies, exceeds the maximum size print job allowed for the selected printer. The administrator defines the maximum size allowed in the printer definition in the Printer Inventory.

In the message text, source file is the name of the document that is too large to print, maximumvalue is the number of bytes allowed in the printer definition, and printer-name is the name of the selected printer.

The print request was not completed.

Make the print job smaller or select another printer, and submit your print request again. Or ask your administrator to increase the maximum job size allowed for this printer in the printer definition.

Not applicable.

To increase the size limit for jobs submitted to this printer, use Infoprint Server ISPF panels to edit the printer definition. In the printer definition, specify the maximum number of bytes allowed.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The attributes file refers to an attributes file that also refers to an attributes file. The number of these nested attributes files has exceeded 16 files.

The print request was not completed.

Change the attributes files to limit the number of nested attributes files to 16, and submit your print request again.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The daemon named before the message number has shut down.

The named daemon has shut down.

If you want to restart the daemon, enter this MVS™ command to run the AOPSTART JCL procedure:

START AOPSTART 

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

When you specify attribute attributename2 on the lp command, you must also specify attribute attributename1.

The print request was not completed.

Correct the attributes, and submit the print request again.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You are not the same user who submitted the job.

The job was not canceled.

To cancel a print job submitted by another user, contact your system operator.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This message is displayed with message AOP004E and contains diagnostic information that might be helpful in solving the problem.

The request is not completed.

Contact your system programmer.

Not applicable.

Use the information in this message to find the source of the problem.

If you cannot identify the cause of the problem, contact the IBM Support Center, or use your electronic link with IBM service for assistance.

If the exception-information in the message indicates a problem with permissions (for example, message EDC5139I Operation not permitted. ), run the aopsetup shell script. For example, if you use the default group names for Infoprint Server operators (AOPOPER) and administrators (AOPADMIN), enter:

/usr/lpp/Printsrv/bin/aopsetup aopoper aopadmin

For more information about aopsetup, see z/OS Infoprint Server Customization.

If the exception-information in the message is EDC5164I SAF/RACF error., make sure:

• The user ID that starts Infoprint Server is a valid z/OS UNIX user ID. The user ID must have an OMVS segment, the default group for the user ID must have an OMVS segment with a group identifier (GID), and the user ID must have a home directory.
• The password for the user ID that starts Infoprint Server has not expired.

One possible message text is:

aopd: AOP047E Cannot allocate memory

This message indicates that the daemon (aopd) requested more memory than was available. Check these:

1. The region size might be too small. For information about setting the region size for daemons, see z/OS Infoprint Server Customization.
2. The Infoprint Server Inventory databases might be corrupted, causing Infoprint Server to request an unreasonable amount of memory. For information about restoring the inventory databases from backups, see z/OS Infoprint Server Customization.

Another possible message text is:

aoplpd: AOP047E Bind() failed in TCPListener::
TCPListener(const IPAddress&) at
./src/tcpconnect.cpp 98:
EDC8115I Address already in use. errno2=0x744c7247

This message text indicates that the Infoprint Server LPD (aoplpd) attempted to use a port that is already used by another process. The process could be another instance of aoplpd that was started earlier, the standard MVS LPD (shipped with TCP/IP), or another process if the port is not 515. Check these:

1. From a z/OS UNIX System Services shell, logged in as root or superuser (UID=0), enter the ps command to determine whether an aoplpd process is already running:

    ps -ef | grep aoplpd

   If so, enter the aopstop or kill command to end this process:

    aopstop -d lpd

    kill process_id

   Then restart aoplpd. For example, enter this MVS command to run the AOPSTART JCL procedure:

   START AOPSTART

2. If the ps command does not show aoplpd already running, enter these commands to determine if any other process is listening at the same port:

    onetstat | grep port   

   port is the port number specified in the lpd-port-number attribute. If the result shows the port in a Listen state, determine which process is using the port and do one of these:
   • Stop the process using the port.
   • Change the port number at which aoplpd listens in the lpd-port-number attribute in the aopd.conf file or, if dynamic configuration is enabled, in the system configuration definition.
   • Configure TCP/IP with two stacks so that the MVS LPD and aoplpd can both listen at port 515.
3. Check the TCP/IP configuration file, hlq.PROFILE.TCPIP, to determine whether the port is reserved. Port numbers specified in the PORT statement are reserved. If you want aoplpd to listen at port 515, comment out the line in hlq.PROFILE.TCPIP that lists port 515.

For more information about how to customize TCP/IP and the Print Interface LPD, see z/OS Infoprint Server Customization.

Another possible message text is:

aopoutd: AOP047E bad allocation

This message text indicates that IP PrintWay extended mode (daemon aopoutd) requested more memory than is available. Try these possible solutions:

1. Increase the region size for Infoprint Server daemons. For information about how to increase the region size, see z/OS Infoprint Server Customization.

   After you increase the region size, stop and restart Infoprint Server. When Infoprint Server starts again, it automatically attempts to print the job again.

2. If the print job still does not print, increase the default heap size. To do this, edit the aopstart EXEC to specify the following environment variable:

   n=n+1; env.n='_CEE_RUNOPTS=HEAP(32M,8M)'

   For information about how to edit the aopstart EXEC, see z/OS Infoprint Server Customization.

   After you edit the aopstart EXEC, stop and restart Infoprint Server. When Infoprint Server starts again, it automatically attempts to print the job again.

If the problem persists, contact the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server tried to resolve the printer's host name, but the gethostbyname() function could not resolve it. This situation can occur for one of these reasons:

• The Domain Name Server (DNS) is not accessible from z/OS.
• No DNS entry exists for this host name.
• This host name is spelled incorrectly in the printer definition.
• This host name is spelled incorrectly in the DEST=IP: parameter on the JCL statement or in the printer-ip-address job attribute.

IP PrintWay extended mode requires that your DNS be able to map a host name to an IP address if the host name is specified in a printer definition, DEST=IP: JCL parameter, or in the printer-ip-address job attribute. If an IP address is specified (in a printer definition, DEST=IP: JCL parameter, or in the printer-ip-address job attribute) and the IP address maps to a host name in the DNS, the DNS must also map the host name to an IP address. IP PrintWay extended mode also requires that the DNS be able to do reverse lookup (from IP address to host name) if the host name or IP address is specified in a printer definition, DEST=IP: JCL parameter, or in the printer-ip-address job attribute. For more information, see z/OS Infoprint Server Customization.

If this message is received for a print job request, IP PrintWay rejects the print job. The print job remains on the JES spool with a status of "rejected" so that IP PrintWay does not attempt to process the print job again until the operator releases it.

If you see this message when IP PrintWay extended mode starts, or when the administrator creates a printer definition, IP PrintWay does not create an internal representation of the printer. Therefore, Infoprint Central cannot display this printer.

If you specified this host name in the print request, make sure that the host name is correct. After you correct the host name, resubmit the print job. If you did not specify the host name in the print request, or if the host name is correct, contact the system programmer.

Do one of these after the problem is corrected:

• If the job submitter corrected the host name and resubmitted the print job, delete the rejected print job.
• If the administrator corrected the host name in the printer definition or in the DNS, release the print job.

If the host name is incorrect in the printer definition, correct it. When you correct the host name, you receive this message again because IP PrintWay tries to resolve the host name one more time. You can ignore the second AOP048E message.

If the host name is correct in the printer definition, verify that the DNS is accessible and functioning and that there is a DNS entry for this host name. If no DNS entry exists, create an entry. After you create a DNS entry, Infoprint Central can display the printer after someone submits a print job to it or after the administrator modifies any field in the printer definition.

After you correct the problem, ask the operator to release the print job that was rejected.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

There was no subpool 241 storage available to the program.

Infoprint Server does not initialize.

Not applicable.

If all programs are consuming normal amounts of common storage, increase the storage amount specified in SYS1.PARMLIB (IEASYSxx) and re-run initial program load (IPL) at a convenient time. Infoprint Server common storage area (CSA) requirements depend upon system load but are generally modest. 64 K of ECSA (extended common storage area) should be more than enough.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Printer Inventory inventory is not currently active.

The print request is not completed.

Wait until the Printer Inventory is active, or contact the system programmer.

Not applicable.

Start the Printer Inventory. For example, use the AOPSTART procedure to start the Printer Inventory.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

All daemons started successfully. This message is for information only.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You must specify a filter name with the filter command. No filter name was specified.

The print request is not completed.

If you are using the filter command directly, specify a filter name. For more information, see cfilter.h and cfilter.c in the /usr/lpp/Printsrv/samples/ directory. If the message is coming from an installation-supplied program, contact the system programmer.

Not applicable.

If you are using the filter command directly, specify a filter name. Use the filter man pages for more information. If the message is coming from an installation-supplied program, make sure the installation-supplied program is generating a filter name with a filter command.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The specified program ended with a non-zero status.

Processing continues.

The current output request might be incomplete. Verify the request and resend it. If the problem recurs, contact the system programmer.

Not applicable.

If the error was sent by the transform daemon (aopxfd) and the program named is an IBM-supplied transformer, contact the IBM Support Center, or use your electronic link with IBM service for assistance. Otherwise, treat the problem as originating with program_name.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The specified program was ended because it received the specified signal.

The named program terminates.

The current output request might be incomplete. Verify the request and resend it. If the problem recurs, contact the system programmer.

Not applicable.

If no user entered the kill command against the program, and if the error was sent by the transform daemon (aopxfd), and if the program named is an IBM-supplied transformer, contact the IBM Support Center, or use your electronic link with IBM service for assistance. Otherwise, treat the problem as originating with program_name.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

If this message was displayed in message AOP003E, message was received and was not valid.

This error might have occurred in the HTTP protocol when IP PrintWay attempted to transmit data to a printer using the Internet Printing Protocol (IPP).

In the message text, message is a message, data is the HTTP protocol data that has an error.

The request is not completed.

IP PrintWay attempts to retransmit the document to the printer. If this is the last retry attempt, IP PrintWay either deletes the print job from the JES spool or retains it on the JES spool. When the retention time expires, IP PrintWay automatically deletes the print job from the JES spool.

Notify your system programmer.

Not applicable.

If this message is contained in message AOP003E, that message indicates the source of the error. If this message is not contained in message AOP003E or if the source is an IBM-supplied program, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance. Otherwise, treat the problem as originating with the named source.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The specified filename was not spooled. Messages that follow indicate the reason.

The request is terminated.

See other messages sent with this one.

Not applicable.

See other messages sent with this one.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The first specified attribute requires that a value also be supplied for the second specified attribute.

The request is terminated.

Supply a value for attribute_name2.

Not applicable.

Make sure the user supplies a value for attribute_name2.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The specified attribute specification is not valid for the specified attribute.

The request is terminated.

Either do not set attribute_spec for this attribute, or do not supply a value for attribute_name.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The specified second attribute must be set if the first attribute has the value indicated.

If Infoprint Server wrote the message when it started and attribute_name1 is "hardcopy-messages" and value is "list", Infoprint Server continues processing but ignores the hardcopy-messages=list attribute and does not write any additional messages to the hardcopy log.

If the pidu command wrote the message, the pidu command was not accepted.

Either do not specify value for attribute_name1, or supply a value for attribute_name2.

For information about attribute_name1 and attribute_name2, see z/OS Infoprint Server Customization.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A value of value for attribute_name1 precludes specifying attribute_name2.

The request is terminated.

Either do not specify value for attribute_name1, or do not supply a value for attribute_name2.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This message is sent by the Print Inventory Definition Utility (PIDU). The indicated object was not found in the Printer Inventory.

The request is terminated.

Check that you requested the right printer for your print job. If not, re-enter the request with the right printer. If so, contact your system programmer.

Not applicable.

If the indicated object is a printer definition, either create the printer definition in the Printer Inventory, or re-enter the request with a different printer definition. If the indicated object is part of a printer definition, change the printer definition to include a valid object.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This informational message is sent by the Print Inventory Definition Utility (PIDU). The indicated object was created in the Printer Inventory as requested.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This informational message is sent by the Print Inventory Definition Utility (PIDU). The indicated object was replaced in the Printer Inventory as requested.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This informational message is sent by the Print Inventory Definition Utility (PIDU). The indicated object was deleted from the Printer Inventory as requested.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The specified number of printer definitions were exported to filename filename.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The type of this attribute precludes its use in predicates.

The request is terminated.

Specify a typed attribute name.

Not applicable.

Specify a typed attribute name.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server SNMP printer subagent (AOPSNMPD) failed to connect to the z/OS Communications Server SNMP agent (OSNMPD). Common causes might be:

• OSNMPD might not be active. For instructions about starting OSNMPD, see z/OS Communications Server: IP Configuration Reference. This error returns return code -2.
• The default community name (public) has been overridden in either the OSNMPD daemon or the AOPSNMPD daemon, creating a mismatch. This error returns return code -2.
• Another instance of the AOPSNMPD daemon is active.

If the return code is greater than -90, its values will be documented in the header file /usr/lpp/tcpip/snmp/include/snmp_dpi.h

Other return code values are:

-90

failed on mkDPIopen

-91

failed on pDPIpacket

-92

no response to DPI-register

The AOPSNMPD daemon is not started.

Contact your system programmer.

Verify that the OSNMPD daemon is active and available and that the community name matches if it has been overridden. Otherwise contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance. If possible, recreate the error with the Infoprint Server trace active. For more information about the Infoprint Server trace facility, see Tracing Infoprint Server.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The transform class transform_class appears multiple times in filename.

None.

Not applicable.

Make sure that the transform class specified appears only once.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Some print data requires transformation from one data format to another, such as from PCL to AFP, from PostScript to AFP or from PDF to AFP. For such data sets, Print Interface sends the print data to a transform process for conversion prior to writing the data to the JES spool. This error message indicates that communication with the transform process was either never established or failed before the transform completed.

In the message text, transform_class is the name of the transform (such as, pcl2afp) concatenated with the class specified in the -c filter option (such as, letter_240). For example, pcl2afp_letter_240.

The transform request was not completed.

Submit the request with a valid -c filter option. If the -c option is valid, notify your administrator.

Not applicable.

Make sure that a valid transform class is specified in the -c filter option in the printer definition. The transform class must be defined in the transform configuration file, aopxfd.conf. If you change the configuration file, stop and restart the Infoprint Server Transform Manager daemon to pick up the changes.

Also, make sure that you have installed the requested transform and have correctly specified the name of the transform daemon in the transform configuration file. The name of the transform is the first part of the class_name (for example, afpxpcl.) If the DLL for the transform daemon (for example, afpxpcl.dll) is not installed, you also receive message EDC5129I on the console.

View the /var/Printsrv/xfd/transform_class.#.stderr file for an indication of the cause of the transform failure.

If the problem persists, contact your IBM service representative.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The request failed because it exceeded a time limit associated with the resource identified in the message.

The request was not completed.

Notify your system programmer.

Not applicable.

Increase the time limit associated with the named resource.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A request was submitted without a required operand, which is identified in the message.

The request was not completed.

If you entered the command from the command line, submit the request with the required operand. If you did not enter the command missing the operand, notify your administrator.

Not applicable.

Add the required operand to the printer definition.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This product is not enabled for use. It must be enabled in SYS1.PARMLIB.

The program terminates.

Not applicable.

Enable the product in the IFAPRDxx member of SYS1.PARMLIB. For information, see z/OS Planning for Installation.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Printer Inventory function function_number failed for the Printer Inventory indicated in inventory.

The request terminates.

Contact your system programmer.

Not applicable.

Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This message involves the application programming interface (API) library that is shipped with Infoprint Server. The API lets customers develop their own printing applications.

Message AOP074E is sent when a programmer uses an API function in error. For example, calling WritePrintFile() or ClosePrintFile() before calling CreatePrintFile(). A print file must be created before it can be written to or closed.

The API does not run, and no print file is created.

If you are the application programmer using the API, rewrite the code to eliminate the error. If you are not the application programmer, notify your system programmer of this error.

Not applicable.

Have the application developer rewrite the code that uses the API to eliminate the error.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The daemon was started successfully.

In the message text, daemon is the name of the daemon.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The daemon could not be started. In the message text, daemon is the name of the daemon.

If another error message indicates a RACF or SAF error, the file permissions might not be set correctly or the user ID that started Infoprint Server might not be a valid z/OS UNIX user ID.

The request terminates.

Contact your system programmer.

Not applicable.

Look for other messages that indicate the reason for the failure on the terminal where Infoprint Server was started or in the console log.

If a message indicates a RACF or SAF error (such as, message EDC5164I):

• Make sure that the user ID that starts Infoprint Server is a valid z/OS UNIX user ID. The user ID must have an OMVS segment, the default group for the user ID must have an OMVS segment with a group identifier (GID), and the user ID must have a home directory.
• Make sure that the password for the user ID that starts Infoprint Server has not expired.
• Run the aopsetup shell script to set up the correct z/OS UNIX permissions for Infoprint Server directories and executable files.

For information about how to set up security for Infoprint Server and how to run the aopsetup shell script, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The daemon is already active and cannot be started again.

In the message text, daemon is the name of the daemon.

The request to start the daemon again has no effect on the system.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An attempt was made to stop a daemon that is not running.

In the message text, daemon is the name of the daemon.

The request has no effect on the system.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The system has begun to end the daemon. The termination is not complete until message AOP044I, which indicates daemon termination, is displayed.

In the message text, daemon is the name of the daemon.

Not applicable.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A daemon received an unexpected signal it cannot process.

The daemon terminates abnormally.

Notify your system programmer.

Not applicable.

Restart the daemon.

If the error condition persists, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The user does not have correct authority to run the Printer Inventory Definition Utility (PIDU).

PIDU terminates.

Notify your system programmer.

Not applicable.

To permit the user to run PIDU, give the user either READ or UPDATE access to the AOP.ADMINISTRATOR profile in the PRINTSRV class. The user must also be a member of the AOPADMIN group. For more information, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An attempt was made to create an inventory object that would conflict with an existing object.

The new inventory object is not created.

If you need the new object, give it a class and name that do not conflict with an existing object.

Not applicable.

If the message refers to the Infoprint Server search database daemon (aopsdbd), the search database files are not consistent. The program might have failed. To correct the inconsistency, run the z/OS UNIX sdbu -z command to create the search database. For information about creating the search database, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The object of class object_class named object_name already exists in the inventory, and its attribute_spec prevents the definition of the current object.

The new object is not created.

Choose values for the attribute that do not conflict with those of the named object_class object_name.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

While building the object of type object_class2 named object_name2 from the Printer Inventory, the object of type object_class1 named object_name1 was not found. The object will be treated as not found until object_class1 object_name1 is defined.

The request which tried to process object_class2 named object_name2 fails.

If you want to create a new object that contains object_class1 object_name1 in its definition, you must first create object_class1 object_name1.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Printer Inventory interface GTF tracing was started.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Printer Inventory interface GTF tracing has stopped.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

As requested, object object_class object_name was renamed as indicated.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An active connection to the specified address was unexpectedly terminated due to a network failure, a software error, or user action.

Activity on the connection is terminated.

Retry the request that caused the error. If errors persist, notify your system programmer.

Not applicable.

Use network problem determination procedures to determine if the failure is network-related or is caused by the machine at address. If the problem is not network-related and the software causing the message is IBM-supplied, or if the problem appears to be caused by the Infoprint Server component sending the message, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance. Otherwise, contact the vendor of the software causing the message.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A value is required for attributename to complete the request.

The request is terminated.

Supply a value for attributename and resend the request.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The utility has connected to the inventory or host name.

None.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The user (userid) is not authorized to access the data set.

In the message text:

userid

The z/OS user ID of the job submitter or *NONE*. *NONE* means that either no z/OS user ID was associated with the print job or that the z/OS user ID could not be authenticated.

access

The type of access to the data set. The access type is READ.

dsname

The name of the data set.

The print request is not completed.

If userid is your user ID, ask the data set owner to grant you read access to the data set.

If userid is *NONE*, Infoprint Server could not authenticate your z/OS user ID. You must resubmit the job in one of these ways so that your z/OS user ID can be authenticated:

• Use the lp, afp2pcl, afpxpcl, afp2ps, apfxps, afp2pdf, or afpxpdf command
• Use SAP R/3, using the Infoprint Server SAP Output Management System (OMS)
• Use the Windows SMB protocol
• Use the AOPPRINT or AOPBATCH JCL procedure
• Use z/OS job control language (JCL) to submit a print job to the Infoprint Server subsystem or to IP PrintWay extended mode

If you cannot resubmit the job in one of these ways, the data set owner must grant universal read access to the data set.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The token passed to the API is incorrect.

Not applicable.

Notify your application or system programmer.

Not applicable.

The token is dumped in hex. Look for a token being used before it is initialized (for example, with CreatePrintFile()) or after it has been invalidated (for example, with AbortPrintFile()).

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The buffer that the caller provides to an API function is not large enough to satisfy the request.

Not applicable.

Notify your application or system programmer.

Not applicable.

Use the BufferSizeRequired() function to determine the size of the buffer required and change the program using the API to supply a buffer at least that size. Consider modifying the program so that it checks for ErrorNumber() == AOP_BUFFER_OVERFLOW and dynamically allocates the buffer size required.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The API could not be initialized and there was not enough storage to describe the reason better.

Not applicable.

Increase the amount of storage available for the application or notify your application or system programmer.

Not applicable.

Increase the amount of storage available for the application.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You attempted to modify a component in the Infoprint Server Printer Inventory. This component is included in another object in the Printer Inventory. Infoprint Server could not update the component because an error would result in the object that includes this component.

In the message text:

component_type

Type of component that you attempted to modify.

component_name

Name of the component that you attempted to modify.

object_type

Type of object in the Printer Inventory that would have an error if the component were modified.

object_name

Name of the object that would have an error if the component were modified.

message

Message that describes the error that would result if the component were modified.

The component was not modified in the Printer Inventory.

None.

Not applicable.

Correct the problem indicated in message message, and then modify the component. To correct the problem, you might need to modify the object that includes the component.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You attempted to delete a component from the Infoprint Server Printer Inventory. This component is included in one or more objects in the Printer Inventory. Infoprint Server can delete a component only if no other objects include it.

In the message text:

component_type

Type of component you attempted to delete.

component_name

Name of the component you attempted to delete.

The component was not deleted from the Printer Inventory.

None.

Not applicable.

Remove the component from the objects that include it, and then delete the component. To find the objects that include the component, use the Infoprint Server ISPF panels to list all components of the same component type and use the P action to show the other objects that include the component. As an alternative, you can use the pidu command to display objects that include the component. For more information about how to use the Infoprint Server ISPF panels and the pidu command, see z/OS Infoprint Server Operation and Administration.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You attempted to create or modify an object in the Infoprint Server Printer Inventory. However, this object includes a component that does not exist in the Printer Inventory. You must create the component before you can include it in another object.

In the message text:

object_type

Type of object you attempted to create or modify.

object_name

Name of the object you attempted to create or modify.

component_type

Type of component that does not exist in the Printer Inventory.

component_name

Name of the component that does not exist in the Printer Inventory.

The object was not created or modified in the Printer Inventory.

None.

Not applicable.

Verify the spelling of the component name. Because component names are case-sensitive, use the correct uppercase and lowercase letters. If the component name is spelled correctly, create the component that the object includes, and then create or modify the object that includes the component.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Uniform Resource Identifier (URI) for the printer, which is specified in the printer definition for the target printer, is not valid. Start the URI with a valid scheme, for example http: or ipp:.

In the message text, scheme is the first part of the URI value as specified in the printer definition.

IP PrintWay attempts to retransmit the document to the printer. If this is the last retry attempt, IP PrintWay either deletes the print job from the JES spool or retains it on the JES spool. When the retention time expires, IP PrintWay automatically deletes the print job from the JES spool.

Not applicable.

Use the Infoprint Server ISPF panels to correct the value specified in the URL field of the printer definition for the target printer. The URL field is displayed on the IPP Protocol panel.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

IP PrintWay used the Internet Printing Protocol (IPP) to send a data set to the target printer, and the printer reported an error.

In the message text, printer-uri is the Uniform Resource Identifier (URI) of the target printer as specified in the printer definition. scheme is either HTTP or IPP. code is either the message or code returned by the target printer.

IP PrintWay attempts to retransmit the document to the printer. If this is the last retry attempt, IP PrintWay either deletes the print job from the JES spool or retains it on the JES spool. When the retention time expires, IP PrintWay automatically deletes the print job from the JES spool.

Not applicable.

Look up the status codes in either RFC 2068 for HTTP or RFC 2566 for IPP.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server IPP server (daemon aopippdxp) encountered an error when it attempted to establish a server socket connection at the requested port.

In the message text, portnumber is the port number at which the IPP server attempted to establish a connection. This port number is specified in the ipp-port-number attribute. The default port is 631. message is a message that contains additional error information.

The IPP server cannot accept any print requests from remote IPP clients.

Not applicable.

Verify that the port number in the message is correct and available to the IPP server. Look up message for more information about the error. If message indicates that the port number (that is, the address) is already in use, either stop the other process that is using the port number or specify another port for the IPP server in the ipp-port-number attribute in the aopd.conf file or, if dynamic configuration is enabled, in the system configuration definition. For information about the ipp-port-number attribute, see z/OS Infoprint Server Customization.

If you see message EDC5111I Permission denied, make sure that the port is not reserved for any other process in the TCP/IP profile data set. For example, if you see this line in the PORT or PORTRANGE statement, delete it or comment it out (the semicolon in the first column indicates the line is a comment):

; 631 TCP process-name

After correcting the problem, stop and restart the IPP server so that the IPP server attempts to establish a server socket connection again. You can use these MVS commands to stop and restart the IPP Server:

START AOPSTOP,OPTIONS='-d ippd'
START AOPSTART

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server LPD (daemon aoplpd) failed when it attempted to read an LPD command.

The Infoprint Server LPD did not allocate an output data set on the JES spool. Processing continues.

Resubmit the print request.

Not applicable.

If this message occurs often, it might indicate a network problem between the submitting client and the Infoprint Server host system. Investigate and correct the source of the problem.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You must not select the Use DEST, CLASS, and FORMS for IP PrintWay printer selection option in the printer definition named DFLTNTRY. IP PrintWay uses the printer definition named DFLTNTRY to obtain default values for certain attributes when it prints a data set submitted with the DEST=IP: parameter and no FSSDATA=printer parameter on an OUTPUT JCL statement.

Infoprint Server did not create the printer definition in its Printer Inventory.

If you used ISPF panels to create the printer definition, either deselect the Use DEST, CLASS, and FORMS for IP PrintWay printer selection field in the printer definition or change the name of the printer definition, and save the printer definition again. If you used the pidu command to create the printer definition, either remove the dcf-routing attribute or change the name of the printer definition, and enter the command again.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You must not select the IP PrintWay basic mode Resubmit for filtering option in the printer definition named DFLTNTRY. IP PrintWay uses the printer definition named DFLTNTRY to obtain default values for certain attributes when it prints a data set submitted with the DEST=IP: parameter and no FSSDATA=printer parameter on an OUTPUT JCL statement. If you run IP PrintWay basic mode, you must set the Resubmit for filtering option in the printer definition for the printer, not in the default printer definition.

Infoprint Server did not create the printer definition in its Printer Inventory.

If you used ISPF panels to create the printer definition, either deselect the Resubmit for filtering field in the printer definition or change the name of the printer definition, and save the printer definition again. If you used the pidu command to create the printer definition, either remove the resubmit-for-filtering attribute or change the name of the printer definition, and enter the command again.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The data set could not be completely transmitted to the printer because the time specified in the Response timeout field of the printer definition in the Printer Inventory expired.

In the message text, printer-uri is the Uniform Resource Identifier (URI) for the printer.

IP PrintWay attempts to retransmit the document to the printer. If this is the last retry attempt, IP PrintWay either deletes the print job from the JES spool or retains it on the JES spool. When the retention time expires, IP PrintWay automatically deletes the print job from the JES spool.

Correct the problem at the printer.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server Transform Manager attempted to connect to a transform daemon. The connection attempt failed probably due to a failure that occurred during initialization of the transform daemon.

In the message text:

transform_class

The name of the transform concatenated with the transform class that was requested in the -c option.

errmsgno errmsgtext

The message number, if available, and the message text generated by a system program.

The transform was not done.

Notify your system programmer.

Not applicable.

View the /var/Printsrv/xfd/transform_class.#.stderr file for the cause of the failure to initialize the transform daemon. A probable error is that an AFP resource library is not specified correctly in the transform configuration file, aopxfd.conf. If you change the transform configuration file, stop and restart the Infoprint Server Transform Manager daemon to pick up the changes.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Print Interface subsystem did not have sufficient resources to process a data set that was submitted to Infoprint Server using the SUBSYS JCL parameter on a DD statement. One possible reason for this error is that the job step contained a large number of DD JCL statements.

In the message text:

function

The name of the function that the subsystem was doing when the error occurred. Possible values are: allocate, open, close, put, and unallocate.

The Print Interface subsystem does not allocate output data sets on the JES spool for any data sets in the job step.

Reduce the number of resources required by the job step, and rerun the job. For example, decrease the number of DD JCL statements.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A z/OS system error occurred while Infoprint Server was processing a data set that was submitted to Infoprint Server with the SUBSYS JCL parameter on the DD statement.

In the message text:

function

The name of the function that Infoprint Server was doing when the error occurred. Possible values are: allocate, open, close, put, and unallocate.

reason code

A code that indicates the reason for the error, in the format: 00xxyyzz.

If the function is allocate, open, close, or put, the Print Interface subsystem does not allocate output data sets on the JES spool for any data sets in the job step. If the function is unallocate, the Print Interface subsystem might have allocated an output data set on the JES spool for this data set.

Resubmit the job after the error is corrected.

Notify your system programmer that this error occurred.

If the function is allocate, open, close, or unallocate, save the associated dump in case you need to contact your IBM service representative. Follow the system programmer response for the reason code in Infoprint Server system completion code and reason codes.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Either the operator stopped the Print Interface subsystem or the Print Interface subsystem ended abnormally.

The Print Interface subsystem does not allocate any output data sets on the JES spool for this job step.

Notify the operator that this error occurred. Resubmit the job after the operator restarts the Print Interface subsystem.

If you did not stop the Print Interface subsystem, notify your system programmer that this error occurred. Enter the z/OS UNIX aopstart command or run the AOPSTART procedure to restart Infoprint Server daemons after the problem is corrected.

If the operator did not stop the Print Interface subsystem, the system log contains another message that indicates the error that caused the subsystem to end abnormally. Follow the system programmer response for that message.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Print Interface subsystem is not active.

In the message text:

subsystem

Name of the Print Interface subsystem, which is specified in the inventory attribute in the Infoprint Server configuration file (aopd.conf).

The print request is not completed.

Notify your system programmer that this error occurred. Resubmit the job after the Print Interface subsystem has been started.

Notify your system programmer that this error occurred.

Edit the start-daemons attribute in the Infoprint Server configuration file (aopd.conf) to specify the subd value. Then, start Infoprint Server so that the Print Interface subsystem starts. You do not need to first stop Infoprint Server.

For example, enter this MVS command to start Infoprint Server:

START AOPSTART

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Print Interface subsystem is not active.

In the message text:

subsystem

Name of the Print Interface subsystem specified in the inventory attribute.

The Print Interface subsystem is not started.

None.

Notify your system programmer that this error occurred. After the problem is corrected, stop and restart all Infoprint Server daemons, IP PrintWay, and NetSpool. You might also have to stop and restart PSF.

For information about how to stop and start Infoprint Server daemons, IP PrintWay, and NetSpool, see z/OS Infoprint Server Operation and Administration.

Change the value in the inventory attribute in the Infoprint Server configuration file (aopd.conf) to specify a valid subsystem name. Make sure that the first character of the name is an uppercase letter. Because the subsystem name is also the name of the Printer Inventory, you also need to change the name of the inventory on the IP PrintWay and NetSpool startup procedures. If PSF uses the Printer Inventory, you also need to change the name on the PSF startup procedures. Do these steps:

1. Change the name in the configuration file and startup procedures.
2. Stop all Infoprint Server daemons, IP PrintWay, NetSpool, and (optional) PSF.
3. Restart the Infoprint Server daemons.
4. Restart IP PrintWay, NetSpool, and PSF.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You requested to write to the Infoprint Server Printer Inventory. However, you are not authorized to write to the Printer Inventory.

The function is not done.

Ask your administrator to give you RACF authorization to write to the Printer Inventory, or ask an Infoprint Server administrator to do the function.

Not applicable.

If you want this user to do the function, authorize the user to write to the Printer Inventory. For information about how to authorize users, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You selected an action on a NetSpool logical unit. This action requires that the NetSpool component of Infoprint Server is started. However, NetSpool is not started.

The function is not done.

Ask your administrator to start a NetSpool task.

Not applicable.

Start a NetSpool task. For information about how to start NetSpool, see z/OS Infoprint Server Operation and Administration.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server search database daemon, aopsdbd, failed. Infoprint Server cannot record information about printers and print jobs that Infoprint Central requires.

Processing continues. However, Infoprint Central reports a logic error when the operator tries to find print jobs or printers.

Contact the Infoprint Server operator.

Notify your system programmer that this error occurred.

Follow the procedure in z/OS Infoprint Server Customization to recover the search database.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server Historical Inventory daemon, aophinvd, failed. Infoprint Server cannot record information about historical print jobs, that is, print jobs that could not be spooled or that have completed and are no longer on the JES spool.

Processing continues. However, Infoprint Central reports a logic error when the operator tries to find Infoprint Server print jobs.

Contact the Infoprint Server operator.

Stop and restart Infoprint Server daemons. See z/OS Infoprint Server Operation and Administration.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The printer pool definition associated with the LU name for the Netspool print request is not defined in the Infoprint Server Printer Inventory.

In the message text, printer-pool-name is the name of the requested printer pool definition.

Infoprint Server stops processing the print request.

No response is necessary.

Notify your system programmer.

This error indicates a possible logic error. Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server did not finish writing all the data to the JES spool for this document because an unexpected error occurred. The data set on the JES spool, if any, is probably incomplete.

This situation can occur when:

• The document contains no data.
• The job submitter cancels a print request while Infoprint Server is writing the data to the JES spool.

In the message text:

jobid

The ID of the print job.

document-name

The name of the document in the print job that had the error.

Processing continues, but the document is not printed. However, other documents in the same job might print.

None.

None.

None

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server started writing the document to the JES spool.

In the message text:

jobid

The ID of the print job.

document-name

The name of the document to be printed.

printer-definition

The name of the printer definition for the printer.

None.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server finished writing the document to the JES spool.

In the message text:

jobid

The ID of the print job.

document-name

The name of the document to be printed.

status

The status of the print job. Possible values for status are:

not-spooled

An error prevented the document from being written to the JES spool.

held

The document was successfully written to the JES spool but is in the held state. Either the job submitter or the printer definition requested the hold.

pending

The document was successfully written to the JES spool and is ready to print.

None.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server started writing the document to the JES spool. As the document is written to the spool, it is being transformed to another data stream format.

In the message text:

jobid

The ID of the print job.

document-name

The name of the document to be printed.

printer-definition

The specified printer.

transform

The path to the transform DLL (Dynamic Link Library). Examples are:

aopfiltr.so
/usr/lpp/Printsrv/lib/afpxpcl.dll

None.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Historical Inventory, which contains information about print jobs that have been completed and are no longer on the JES spool, has reached its maximum size. As a result, Infoprint Central cannot display information in the Infoprint Server Print Job History table for older print jobs.

Consider increasing the maximum size of the Historical Inventory so that it can hold historical information for the number of days specified in the log-retention attribute.

In the message text:

size-limit

Maximum size, in megabytes, of the Historical Inventory specified in the max-historical-inventory-size attribute.

objects

The number of objects that are currently stored in the Historical Inventory. Each object contains information about one or more documents (data sets) in a print job.

Infoprint Server deletes information for the oldest print job from the Historical Inventory.

None.

None.

Consider increasing the maximum size of the Historical Inventory in the max-historical-inventory-size attribute. For information about this attribute, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You selected an action on a NetSpool logical unit. This action requires that the NetSpool component of Infoprint Server be started. However, Infoprint Central cannot determine whether NetSpool is started. This situation can occur when more than one NetSpool task is running on the same z/OS system.

The function is not done.

If your installation runs more than one NetSpool task on the same system, use NetSpool operator commands instead of Infoprint Central to do actions on NetSpool logical units. For information about NetSpool commands, see z/OS Infoprint Server Operation and Administration.

Not applicable.

If you want operators to use Infoprint Central to work with NetSpool logical units, run only one NetSpool task.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server used the iconv utility to convert data between the code pages specified in the message text. The iconv utility detected an error. Typically an error occurs when either (1) the document code page or the printer code page specified in the printer definition or configuration file is incorrect or (2) a conversion table for the code pages does not exist.

In the message text:

to-code-page

The name of the target code page.

from-code-page

The name of the source code page.

errno

The error description.

The print request is not completed.

Resubmit the print job after the administrator corrects the problem.

Notify your administrator that this error occurred. After the problem is fixed, you can use Infoprint Central to release the print job if it has been retained on the JES spool. Otherwise, ask the job submitter to resubmit the job.

Make sure the code page names are valid for your level of z/OS. For IBM-supplied code pages, see information about code set converters in z/OS XL C/C++ Programming Guide. If one of the code pages is a custom code page, make sure that a conversion table exists to convert between the code pages.

If the code page names are not correct, change them in the Document code page and Printer code page fields in the printer definition in the Printer Inventory. Or, change the ascii-codepage and ebcdic-codepage attributes in the Infoprint Server configuration file (aopd.conf) or, if dynamic configuration is enabled, in the system configuration definition. For information about how to create conversion tables, see information about code set conversion utilities in z/OS XL C/C++ Programming Guide.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An Infoprint Server internal processing limit was exceeded. This is probably due to an unusually large number of objects specified in a print request. For example, if one print job contains many documents, the Printer Inventory limit for a print job might have been exceeded.

The request fails.

Retry the request with fewer objects in the request. If you submitted an lp command with many documents, reduce the number of documents in the lp command. If a batch job contains many output data sets, print the output data sets in separate jobs if possible.

Not applicable.

This message can indicate a logic problem in Infoprint Server.

Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You specified search criteria to find objects such as print jobs or printers. However, the number of objects that meet the search criteria exceeds the limit of objects that Infoprint Central is allowed to display. The administrator can specify the maximum limit in the AOPLIMIT, AOPLIMIT_DOCS, and AOPLIMIT_JOBS environment variables.

The aoplogu command provides more information in fields before the message text. For information about the contents of these fields, see Format of messages in the Infoprint Server common message log.

Infoprint Central displays the maximum number of objects.

If Infoprint Central does not return the object you are looking for, narrow your search by specifying additional search values or more specific search values. If you need to see more objects than the maximum limit allows, ask your administrator to increase the limit.

Not applicable.

If this situation occurs repeatedly, increase the value in the AOPLIMIT, AOPLIMIT_DOCS, or AOPLIMIT_JOBS environment variable. If you increase the limit, you might also need to increase the timeout value in the OutputTimeout directive to prevent the z/OS HTTP Server from timing out before Infoprint Central can display any objects. For information about how to set environment variables in the z/OS HTTP Server environment variables file (httpd.envvars) and the OutputTimeout directive in the z/OS HTTP Server configuration file (httpd.conf), see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You specified a maximum size for the Historical Inventory in the max-historical-inventory-size attribute. However, the Historical Inventory is already larger than the maximum size you specified. Infoprint Server cannot reduce the size of the Historical Inventory, but the Historical Inventory will not grow any larger than its current size. Message AOP121I indicates the current size of the Historical Inventory.

The current size of the Historical Inventory is maintained.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This document is no longer on the JES spool because it finished processing or was deleted. Infoprint Server cannot determine if the document printed successfully. This situation can occur when a document is completed or is deleted while Infoprint Server is not running.

Processing continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This document was deleted from the JES spool.

If IP PrintWay extended mode is running on another system in a sysplex, IP PrintWay might have deleted the print job after it was processed on the other system.

Processing continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This document was held on the JES spool. For example, the operator or job owner might have used Infoprint Central, SDSF, or a JES command to hold the document.

Processing continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This document finished processing and was sent successfully to the printer. If the document was sent to an IBM AFP printer that Print Services Facility™ (PSF) controls, the document has finished printing successfully. If the document was sent to a remote printer that IP PrintWay controls, the document might not have finished printing yet. Although the document was sent successfully to the printer, some errors might have occurred during formatting of the data.

The document remains on the JES spool until all documents in the print job finish processing. IP PrintWay retains the document on the JES spool if a retention time is specified in the printer definition.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The document finished processing. However, errors prevented the document from printing successfully. The error might have occurred while the document was being sent to the printer. In this case, part of the document might have printed.

The document remains on the JES spool until all documents in the print job finish processing. If IP PrintWay processed the document, it retains the document on the JES spool if a retention time is specified in the printer definition.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server could not stop the specified daemon. The daemon did not respond to the normal terminate signal and is in an abnormal state that a system programmer needs to diagnose and fix.

In the message text, daemon is the name of the daemon.

Processing continues. If this error occurred while Infoprint Server daemons are being stopped, this daemon keeps running. If this error occurred while Infoprint Server daemons are being started, other daemons are started, but the functions that the specified daemon supports are not available. Examples: If the daemon is aophinvd, Infoprint Central cannot display historical job information. If the daemon is aopsdbd, Infoprint Central cannot do searches.

Enter the z/OS UNIX aopstop command or run the AOPSTOP procedure to stop all daemons. You might need to use the force option of the aopstop command or AOPSTOP procedure. After you successfully stop all daemons, enter the z/OS UNIX aopstart command or run the AOPSTART procedure to restart Infoprint Server. For more information about how to start and stop daemons, see z/OS Infoprint Server Operation and Administration.

If the error condition persists, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server has started an “abrupt” termination of the specified daemon. When the termination is complete, you see message AOP044I.

In the message text, daemon is the name of the daemon.

Processing continues.

None.

Not applicable.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server has started a potentially “destructive” shutdown of the specified daemon. The daemon stops immediately.

A “destructive” shutdown can cause inconsistent or corrupted Infoprint Server inventory files. If this message has been issued for the aopd, aophinvd, or aopsdbd daemon, the databases the daemons manage might be corrupted.

In the message text, daemon is the name of the daemon.

Infoprint Server stops the specified daemon immediately.

None.

Notify your system programmer. Then use the AOPSTART procedure or z/OS UNIX aopstart command to restart Infoprint Server daemons.

Before the operator starts the Infoprint Server daemons again, set the AOPVALIDATEDB=1 environment variable to request that Infoprint Server check databases for validity. You can set the AOPVALIDATEDB variable in the aopstart EXEC, in the AOPSTART procedure's STDENV data set, or in the environment for the aopstart command. For information about how to edit the aopstart EXEC and the STDENV data set, see z/OS Infoprint Server Operation and Administration.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A required daemon is not running. This error occurs when Infoprint Server daemons are being started.

In the message text, daemon is the name of the daemon.

The other Infoprint Server daemons are started, but the functions that the specified daemon supports are not available. Examples: If the daemon is aophinvd, Infoprint Central cannot display historical job information. If the daemon is aopsdbd, Infoprint Central cannot do searches.

None.

Use the AOPSTOP procedure or the z/OS UNIX aopstop command to stop all Infoprint Server daemons, and notify the system programmer that this error occurred. Then use the AOPSTART procedure or the z/OS UNIX aopstart command to restart Infoprint Server daemons.

Before the operator restarts the Infoprint Server daemons, set the AOPVALIDATEDB=1 environment variable to request that Infoprint Server check databases for validity. You can set the AOPVALIDATEDB variable in the aopstart EXEC, in the AOPSTART procedure's STDENV data set, or in the environment for the aopstart command. For information about how to edit the aopstart EXEC and the AOPSTART procedure, see z/OS Infoprint Server Customization.

If the error condition persists, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

While starting Infoprint Server daemons, Infoprint Server detected that one of its databases contains corrupted data. Before continuing to use Infoprint Server, you must recover this database.

In the message text:

filename

Name of the data base that contains corrupted data.

data

Data that can help IBM solve the problem.

Processing continues, but continued operation of Infoprint Server is likely to produce processing failures and other unexpected results.

None.

Notify your system programmer.

Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Save the file that contains corrupted data and the diagnostic information in this message. Follow the recovery procedures provided by your IBM service representative.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The name of the extended MCS console that Infoprint Central uses to send commands to JES is already in use by another program. The console name must be unique. In a sysplex environment, the console name must be unique on all systems in the sysplex.

In the message text, console is the name of the extended MCS console. This console name was specified in the console-name attribute, or Infoprint Server used a default console name.

The aoplogu command provides more information in fields before the message text. For information about the contents of these fields, see Format of messages in the Infoprint Server common message log.

The Infoprint Server aopssid daemon did not start. Therefore, you cannot use Infoprint Central.

Notify your system programmer that this error occurred.

Notify your system programmer that this error occurred.

If dynamic configuration is enabled, specify a unique name in the console-name attribute in the system configuration definition. Then start Infoprint Server again so that the aopssid daemon attempts to start again. You do not need to first stop any Infoprint Server daemons.

If dynamic configuration is not enabled, specify a unique name in the console-name attribute in the Infoprint Server configuration file (aopd.conf). Then stop all Infoprint Server daemons and restart Infoprint Server.

For information about the console-name attribute, how to edit the system configuration definition, and how to edit the aopd.conf file, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The values in two ISPF fields or two attributes are not compatible. This error can occur when you create or update an object in the Printer Inventory using either the Infoprint Server ISPF panels or the Printer Inventory Definition Utility (pidu command).

In the message text:

• attribute_name1 is the name of the first attribute. The ISPF field has a similar name.
• value1 is the value of the first attribute. If you did not specify the first attribute, this is the existing value or the default value of the attribute.
• attribute_name2 is the name of the second attribute. The ISPF field has a similar name.
• value2 is the value of the second attribute. If you did not specify the second attribute, this is the existing value or the default value of the attribute.

This object is not created or updated in the Printer Inventory.

If you use the ISPF panels, change the value in one of the fields and save the definition. If you used the pidu command, change the value of one of the attributes and resubmit the pidu command to create or update this object.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You requested that Infoprint Central run the traceroute command to trace the connection from z/OS to a TCP/IP-connected printer, but the trace was not completed. You might not have specified enough time for the traceroute command to finish.

Processing continues.

Select a greater number of seconds for the traceroute command and resubmit it so that it has more time to run and you get the information that you need. If it still is not completed, contact your network administrator. There might be a problem with the network.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The required Infoprint Server configuration file was not found. In the message text, filename is the name of the configuration file.

The data was not transformed.

Contact your system programmer.

None.

Make sure that the configuration file exists. If the file exists, make sure the environment variable that indicates the file location is specified correctly in the aopstart EXEC and in the file. If you are using InfoPrint Transform Manager for Linux and need information about the remote configuration file, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A configuration file does not contain the required attributes.

In the message text:

filename

Name of the file that is missing the attribute

attribute

Name of the missing attribute

The data was not transformed.

Contact your system programmer.

None.

Make sure that the configuration file contains the required attributes. For example, the IP address or the port number might be missing. If you are using InfoPrint Transform Manager for Linux and need information about the remote configuration file, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You specified more than one file to be transformed, but only one is allowed.

The data was not transformed.

Resubmit the request with only one input file.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

To migrate to the new release, Infoprint Server temporarily requires more free space in the file system to convert the data from the previous release format to the new release format. The message indicates the number of megabytes of free space that Infoprint Server needs to convert the data. In the message text, directory_path is the name of the directory in the file system that needs the additional free space. The data was not converted.

Processing stops. Infoprint Server ends.

None.

Notify the system programmer.

Make the specified amount of free space available in the file system, and then restart Infoprint Server.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server optional feature is not enabled. Some of the daemons that you requested to start in the start-daemons attribute of the Infoprint Server configuration file (aopd.conf) can be started only if Infoprint Server is enabled.

When the Infoprint Server feature is not enabled, you can only use the Infoprint Server Printer Inventory for PSF function. For information about the Printer Inventory for PSF function, see z/OS Infoprint Server Customization.

Infoprint Server starts only those Infoprint Server daemons that are part of the Infoprint Server Printer Inventory for PSF function.

Not applicable.

Notify your system programmer.

Do one of these:

• If your installation purchased an Infoprint Server license, enable Infoprint Server. Then stop and restart Infoprint Server.
• If your installation did not purchase an Infoprint Server license, no action is required. However, to avoid this message in the future, delete the start-daemons attribute in the Infoprint Server configuration file (aopd.conf). The default location of this file is /etc/Printsrv/aopd.conf.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The Infoprint Server optional feature is not enabled. Infoprint Server supports the function you requested only when Infoprint Server is enabled

When the Infoprint Server feature is not enabled, you can only use the Infoprint Server Printer Inventory for PSF function. For information about the Printer Inventory for PSF function, see z/OS Infoprint Server Customization.

The function is not performed.

Notify your system programmer.

Notify your system programmer.

Do one of these:

• If your installation purchased an Infoprint Server license, enable Infoprint Server. Then stop and restart Infoprint Server.
• If your installation did not purchase an Infoprint Server license, no action is required. However, to avoid this message in the future, delete the start-daemons attribute in the Infoprint Server configuration file (aopd.conf). The default location of this file is /etc/Printsrv/aopd.conf.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server could not reformat the Infoprint Server Printer Inventory because the version in the current Printer Inventory is not supported.

In the message text:

database

The full path name of the Printer Inventory that Infoprint Server is trying to reformat.

version

The version found in the Printer Inventory.

Infoprint Server ends.

Notify your system programmer.

Notify your system programmer.

Collect diagnostic information in the base-directory/aopreformat.log file and any other error messages. The base-directory is usually the /var/Printsrv directory. However, your installation might have specified a different base directory in the base-directory attribute in the Infoprint Server configuration file (aopd.conf).

Then contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server cannot reformat the Printer Inventory because the file system does not contain sufficient space.

In the message text:

base-directory

The directory that contains the Printer Inventory files.

nnn

The number of megabytes of free space that is required to reformat the Printer Inventory.

Infoprint Server ends.

Notify your system programmer.

Notify your system programmer.

Configure the base-directory file system specified in the message to contain the amount of free space indicated in the message. Then start Infoprint Server again. For more information, see z/OS Migration.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The reformat of the Infoprint Server Printer Inventory has completed successfully.

Processing continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The reformat of the Infoprint Server Printer Inventory failed.

Infoprint Server ends.

Notify your system programmer.

Notify your system programmer.

Collect diagnostic information in the base-directory/aopreformat.log file and any other error messages. The base-directory is usually the /var/Printsrv directory. However, your installation might have specified a different base directory in the base-directory attribute in the Infoprint Server configuration file (aopd.conf).

Then contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

When you start Infoprint Server, the Printer Inventory is automatically reformatted to Version 2 format. A problem might have occurred that prevented Infoprint Server from reformatting the Printer Inventory.

Infoprint Server ends.

Notify your system programmer.

Notify your system programmer.

Try to start Infoprint Server again to reformat the Printer Inventory. If the problem persists, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You issued the pidu modify or force-create command to modify or replace the system configuration definition in the Printer Inventory. The pidu command failed because the dynamic configuration function is not enabled in Infoprint Server and these commands are allowed only when dynamic configuration is enabled.

You can receive this message when you import a back-up copy of the Printer Inventory that the pidu export or dump command created on another system where dynamic configuration is enabled. This is because the pidu export and dump commands create a force-create command for the system configuration definition when dynamic configuration is enabled. To import this system configuration definition on a system where dynamic configuration is not enabled, you must first enable dynamic configuration.

The system configuration definition was not modified.

If you want to enable dynamic configuration so that you can modify and replace the system configuration definition, notify your system programmer.

None.

For information about dynamic configuration and how to enable it, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The document has been removed from this print job and is now associated with JES output group output-group. This situation occurs when the operator changes one or more of the JES output-group criteria (such as, class, destination, or forms) for the document while the print job is on the JES spool. JES removes the document from its original print job because all documents in a print job must have the same output-group criteria.

Infoprint Server continues to print the other documents in the print job.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

IP PrintWay tried to acquire the document (output data set) on the JES spool. However, another process has already acquired it.

IP PrintWay processes the print job again after the retry interval expires. When all the retries are attempted, IP PrintWay retains the print job if retention for failed print jobs is requested for the print job. If no retention is requested, IP PrintWay extended mode deletes the print job.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server could not store information about a print job and all its documents in the Historical Inventory because of insufficient space in the Historical Inventory. This situation can occur when a print job contains a very large number of documents. As a result, Infoprint Central cannot display information for this print job in the Infoprint Server Print Job History table.

Consider increasing the maximum size of the Historical Inventory so that it can hold historical information for print jobs with a large number of documents.

In the message text:

job-name

Name of the print job.

job-identifier

Job ID of the print job.

Infoprint Server deleted information about the print job from the Historical Inventory.

None.

None.

Consider increasing the maximum size of the Historical Inventory in the max-historical-inventory-size attribute. For information about this attribute, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A required Printer Inventory file is missing. In the message text:

file-name

Name of the missing file.

Infoprint Server does not start.

None.

Notify the system programmer that this error occurred.

Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A required Printer Inventory file is missing. In the message text:

file-name

Name of the missing file.

version

Version of the missing file.

Infoprint Server does not start.

None.

Notify the system programmer that this error occurred.

Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server created an empty Printer Inventory. The Printer Inventory does not contain any printer definitions or other types of definitions. If this is the first time you have started Infoprint Server, use the Infoprint Server ISPF panels or the Printer Inventory Definition Utility (PIDU) to create printer definitions and other definitions. Otherwise, you should restore a backup copy of the latest Printer Inventory.

In the message text:

inventory-filename

The name of the Printer Inventory file that Infoprint Server created.

inventory-version

The version of the Printer Inventory that Infoprint Server created.

Infoprint Server continues processing.

None.

If this is not the first time you have started Infoprint Server, ask your system programmer to restore a backup copy of the Printer Inventory.

Restore the latest backup copy of the Printer Inventory that you created with the pidu command. The backup copy can contain any version of the Printer Inventory. When you restore the backup copy, Infoprint Server creates definitions in the format that Infoprint Server supports.

For information about how to restore the Printer Inventory, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An error occurred when Infoprint Server tried to add Infoprint Server health checks (IBMINFOPRINT) to the IBM Health Checker for z/OS.

In the message text:

macro

The macro that failed.

retcode

The return code from the macro.

reasoncode

The reason code from the macro.

Infoprint Server continues processing. The IBMINFOPRINT health checks might not run.

None.

Notify your system programmer.

If you do not use the IBM Health Checker, you can ignore this message.

If you use the IBM Health Checker, correct the problem. For information about the return code and reason code in the message text:

• For the HZSCHECK macro, see IBM Health Checker for z/OS: User’s Guide.
• For the CSVDYNEX macro, see z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN.

In addition, look for other messages in the console log that might indicate the reason for the failure.

After you correct the problem, restart Infoprint Server to add the health checks. You can use these MVS commands to stop and restart Infoprint Server:

START AOPSTOP
START AOPSTART

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server could not add Infoprint Server health checks (IBMINFOPRINT) to the IBM Health Checker for z/OS because required Infoprint Server modules are missing.

Infoprint Server continues processing. The IBMINFOPRINT health checks cannot run.

None.

Notify your system programmer.

If you do not use the IBM Health Checker, you can ignore this message.

If you use the IBM Health Checker, enter this command to refresh LNKLIST:

F LLA,REFRESH

After you refresh the LNKLIST, restart Infoprint Server to add the health checks. You can use these MVS commands to stop and restart Infoprint Server:

START AOPSTOP
START AOPSTART

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server could not add Infoprint Server health checks (IBMINFOPRINT) to the IBM Health Checker for z/OS because the Health Checker is not running.

Infoprint Server continues processing. The IBMINFOPRINT health checks cannot run until you start the Health Checker.

None.

Notify your system programmer.

If you do not use the Health Checker, you can ignore this message.

If you use the Health Checker, enter this console command to start it:

START HZSPROC

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server made a call to the JES subsystem interface (SSI), and the SSI returned an unexpected result. This message can occur during normal processing or because a problem exists. This message contains information that can help diagnose a problem if one exists. If a problem exists, the message log usually contains another error message.

In the message text:

nn

The SSI call.

return-code

The return code from the SSI call.

reason-code

The reason code from the SSI call.

additional-information

Additional information from the SSI call.

Infoprint Server continues processing.

None.

Notify your system programmer.

If other messages in the message log indicate a problem, use the information in this message to help diagnose the problem. Otherwise, you can ignore this message.

For information about the return code and reason code in the message, see z/OS MVS Using the Subsystem Interface.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The JES2 secondary subsystem specified in the aopd.conf configuration file is not defined to MVS.

In the message text:

jes-name

Is the name of the JES2 secondary subsystem.

Infoprint Server ends.

None.

Notify your system programmer.

Correct the jes-name attribute in the aopd.conf configuration file. Then restart Infoprint Server. For information about the jes-name attribute and how to edit the aopd.conf file, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The JES2 secondary subsystem specified in the aopd.conf configuration file is defined to MVS but is not active.

In the message text:

jes-name

Is the name of the JES2 secondary subsystem.

Infoprint Server ends.

None.

Notify your system programmer.

Restart the JES2 secondary subsystem specified in the message text. Then restart Infoprint Server.

If the JES2 secondary subsystem is started, make sure that the jes-name attribute in the aopd.conf configuration file is correct. For information about the jes-name attribute and how to edit the aopd.conf file, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server has successfully connected to the JES2 secondary subsystem specified in the jes-name attribute in the aopd.conf configuration file. This message is for information only.

In the message text:

jes-name

Is the name of the JES2 secondary subsystem.

Infoprint Server continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server has been working with a JES2 secondary subsystem. However, the JES2 secondary subsystem is ending and Infoprint Server can no longer continue.

In the message text:

jes-name

Is the name of the JES2 secondary subsystem.

Infoprint Server ends.

None.

Notify your system programmer.

Restart the JES2 secondary subsystem specified in the message text. Then restart Infoprint Server.

If you want to work with the JES2 or JES3 primary subsystem, comment out the jes-name attribute in the aopd.conf configuration file before you restart Infoprint Server.

For information about the jes-name attribute and how to edit the aopd.conf file, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server is connecting to the JES2 secondary subsystem specified in the jes-name attribute in the aopd.conf configuration file. This message is for information only.

In the message text:

jes-name

Is the name of the JES2 secondary subsystem.

Infoprint Server continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The document was removed from the print job. The document might have been moved to another print job or deleted from the JES spool.

Infoprint Server continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

This message contains information that can help diagnose a problem if an error occurs later. It does not indicate that a problem exists.

In the message text:

diagnostic-information

Diagnostic information

Infoprint Server continues.

None.

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server issued the system authorization facility (SAF) RACROUTE REQUEST=FASTAUTH macro to verify that the program trying to access the Printer Inventory has access to the AOP.ADMINISTRATOR profile in the PRINTSRV class. The RACROUTE return code or reason code indicates a problem with RACF configuration.

In the message text:

saf-retcode

SAF return code in hexadecimal format.

racf-retcode

RACF return code in hexadecimal format.

racf-reasoncode

RACF reason code in hexadecimal format.

Infoprint Server does not allow access to the Printer Inventory.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

To fix the problem, look up the RACROUTE REQUEST=FASTAUTH return codes and reason codes in z/OS Security Server RACROUTE Macro Reference.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A program has requested to read or update the Printer Inventory. However, the program is not APF authorized, and the user who started the program is not authorized to access the Printer Inventory. For example, the user might have no access to the Printer Inventory, or the user might have READ access to the Printer Inventory but is requesting to update the Printer Inventory.

In the message text:

type

Type of request made to the Printer Inventory.

nn

Request number.

access

Type of access that is required: READ or UPDATE. READ is required to read the Printer Inventory. UPDATE is required to update the Printer Inventory.

Infoprint Server does not allow the program to access the Printer Inventory.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

To allow the program to access the Printer Inventory, either make the program APF authorized or give the user who starts the program the required access to the AOP.ADMINISTRATOR profile in the PRINTSRV class. For information about the AOP.ADMINISTRATOR profile, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

A program has requested to read or update the system configuration definition in the Printer Inventory. However, the user who started the program is not authorized to access the system configuration definition. For example, the user might have no access to the system configuration definition, or the user might have READ access to the system configuration definition but is requesting to update the system configuration definition.

In the message text:

type

Type of request made.

nn

Request number.

access

Type of access that is required: READ or UPDATE.

Infoprint Server does not allow the program to access the system configuration definition.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

Look for another message that indicates which program attempted to access the system configuration definition. To allow the program to access the system configuration definition, give the user who started the program the required access to the AOP.CONFIGURATION profile in the PRINTSRV class. If the AOP.CONFIGURATION profile does not exist, you can give the user the required access to the AOP.ADMINISTRATOR profile.

For information about the AOP.CONFIGURATION and AOP.ADMINISTRATOR profiles, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

An internal error occurred in an Infoprint Server module. If another error occurs, the information in this message can help IBM diagnose the problem.

In the message text:

source

Name of the module that detected the error.

request

Type of request being processed.

return-code

Internal return code.

reason-code

Internal reason code.

Processing continues.

None.

None.

If another error occurs, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance. Send this message and the subsequent error messages to IBM.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server issued the system authorization facility (SAF) RACROUTE LIST macro to verify that the program trying to access the Printer Inventory has access to the AOP.CONFIGURATION or AOP.ADMINISTRATOR profile in the PRINTSRV class. The RACROUTE return code or reason code indicates a problem with RACF configuration.

In the message text:

class

RACF class name.

saf-retcode

SAF return code in hexadecimal format.

racf-retcode

RACF return code in hexadecimal format.

racf-reasoncode

RACF reason code in hexadecimal format.

Infoprint Server does not allow access to the Printer Inventory.

Notify the system programmer that this error occurred. After the problem is fixed, try to access the Printer Inventory again.

Notify the system programmer that this error occurred.

To diagnose the problem, look up the RACROUTE LIST return code and reason code in z/OS Security Server RACROUTE Macro Reference. After you fix the problem, the user can try to access the Printer Inventory again.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You issued a pidu create, rename, or delete command to create, rename, or delete the system configuration definition in the Printer Inventory. However, these pidu commands are not allowed for the system configuration definition.

If dynamic configuration is enabled, you can use the pidu modify command (or the Infoprint Server ISPF panels) to modify attributes in the system configuration definition, and you can the pidu force-create command to replace the system configuration definition. You can also use the pidu

The pidu command was not accepted.

For information about:

• Editing the system configuration definition using the ISPF panels, see z/OS Infoprint Server Customization
• The pidu command, see z/OS Infoprint Server Operation and Administration

None.

None.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You requested to read or update the Printer Inventory. However, you do not have the required RACF authorization.

In the message text:

access

Type of access that is required: READ or UPDATE.

The request to read or update the Printer Inventory was not accepted.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

Give the user the required access to the AOP.ADMINISTRATOR profile in the PRINTSRV class. For information about the AOP.ADMINISTRATOR profile, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

You requested to read or update the system configuration definition in the Printer Inventory. However, you do not have the required RACF authorization.

In the message text:

access

Type of access that is required: READ or UPDATE.

The request to read or update the system configuration definition was not accepted.

Notify the system programmer that this error occurred. After the problem is corrected, try the request again.

Notify the system programmer that this error occurred.

Give the user the required access to the AOP.CONFIGURATION profile in the PRINTSRV class. If the AOP.CONFIGURATION profile is not defined, you can give the user access to the AOP.ADMINISTRATOR profile instead. For information about the AOP.CONFIGURATION and AOP.ADMINISTRATOR profiles, see z/OS Infoprint Server Customization.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server issued an XCF macro that failed. If macro is:

• IXCJOIN: Infoprint Server requested to join an XCF group.
• IXCQUERY: Infoprint Server requested information about an XCF group.

In the message text:

macro

XCF macro name.

return-code

Return code from the XCF macro, in hexadecimal.

reason-code

Reason code from the XCF macro, in hexadecimal.

group

XCF group name.

member

Usually, the XCF member name of the Infoprint Server daemon or command issuing the request. However, if macro is IXCQUERY, return-code is 8, and reason-code is 10, member is instead the name of the daemon that Infoprint Server is requesting information about.

source-code

A code that identifies where Infoprint Server detected the problem. This code can help IBM diagnose the problem

If macro is:

• XCFJOIN: Infoprint Server ends or the Infoprint Server daemon ends.
• XCFQUERY: Processing continues.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

Look up the return and reason codes for the XCF macro in z/OS MVS Programming: Sysplex Services Reference.

After the problem is corrected, if macro is "XCFJOIN", start Infoprint Server again.

If you cannot correct the problem, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The cross-system coupling facility (XCF) component of z/OS sent a signal or message that Infoprint Server could not interpret. The message from XCF might be useful for diagnostic purposes if a subsequent error occurs.

In the message text:

message

Message from XCF.

Processing continues.

None.

None.

If another error occurs, contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance. Send this message and the subsequent error messages to IBM.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server could not load the system logger exit AOPLCMPL. This error means that Infoprint Server was not installed correctly.

In the message text:

return-code

Hexadecimal return code from the LOAD macro.

reason-code

Hexadecimal reason code from the LOAD macro.

Infoprint Server continues processing. However, if you have set up a system logger log stream for Infoprint Server messages, Infoprint Server cannot write messages to the log stream.

Not applicable.

Notify the system programmer that this error occurred. Restart Infoprint Server after AOPLCMPL is available.

Contact your service representative in the IBM Support Center, or use your electronic link with IBM service for assistance. When AOPLCMPL is available, restart Infoprint Server.

Tip: If you have set up a log stream for Infoprint Server messages, request that Infoprint Server write messages to the z/OS UNIX file system until you fix the problem. Use the Infoprint Server ISPF panels to edit the system configuration definition. Edit these fields and save the panel:

• Clear the log stream name in the Log stream name field.
• Specify a value greater than 0 in the Log retention field.

When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the z/OS UNIX file system. After the problem is fixed, edit these fields again and save the panel:

• Specify the log stream name in the Log stream name field.
• Set the Log retention field to its original value.

When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the log stream.

For information about the LOAD return code and reason code, see z/OS MVS System Codes.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Infoprint Server tried to access the system logger log stream to read or write messages. However, the user did not have the required authorization to the RACF resource profile that protects the log stream:

• The user who starts Infoprint Server must have UPDATE access.
• The user who uses the aoplogu command to read messages must have READ access.

In the message text:

user

ID of the user who is not authorized. If the type of required access is UPDATE, this is the ID of the user who started Infoprint Server.

access

Type of access required to the RACF resource profile: READ or UPDATE.

log-stream

Name of the log stream.

Infoprint Server continues processing, but if the required access is UPDATE, messages are lost until the problem is corrected.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

Look for another message from RACF (for example, message ICH408I) that includes the name of the log stream profile and give the user ID the required access to that profile. When the user has the required access, Infoprint Server automatically starts writing messages to the log stream.

For information about how to set up security for the Infoprint Server log stream, see z/OS Infoprint Server Customization.

Tip: To request that Infoprint Server write messages to the z/OS Unix file system instead of to the system logger while you fix the problem, use the Infoprint Server ISPF panels to edit the system configuration definition. Edit these fields and save the panel:

• Clear the log stream name in the Log stream name field.
• Specify a value greater than 0 in the Log retention field.

When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the z/OS UNIX file system. After the problem is fixed, edit these fields again and save the panel:

• Specify the log stream name in the Log stream name field.
• Set the Log retention field to its original value.

When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the log stream.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

The log stream for Infoprint Server messages that is specified in the system configuration definition is not defined to the system logger. You must define the log stream to the MVS system logger before you specify the log stream name in the system configuration definition.

In the message text:

log-stream

Name of the log stream specified in the system configuration definition.

Infoprint Server continues processing, but messages are lost until the problem is corrected.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

Make sure that the log stream name is spelled correct in the Infoprint Server system configuration definition. Use the Infoprint Server ISPF panels to view the system configuration definition and correct the name in the Log stream name field (logstream-name attribute) if necessary. When you correct the name and save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the specified log stream.

If the log stream name is correct in the message text, make sure that the log stream is defined correctly to the system logger. You can use the MVS DISPLAY LOGGER command to display the status of log stream. For information about the DISPLAY LOGGER command, see z/OS MVS System Commands.

For information about how to define the log stream to the logger, see z/OS Infoprint Server Customization.

When the log stream is defined correctly, Infoprint Server automatically starts writing messages to the log stream.

Tip: To request that Infoprint Server write messages to the z/OS Unix file system instead of to the system logger while you fix the problem, use the Infoprint Server ISPF panels to edit the system configuration definition. Edit these fields and save the panel:

• Clear the log stream name in the Log stream name field.
• Specify a value greater than 0 in the Log retention field.

When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the z/OS UNIX file system. After the problem is fixed, edit these fields again and save the panel:

• Specify the log stream name in the Log stream name field.
• Set the Log retention field to its original value.

When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically starts writing messages to the log stream.

Not applicable.

Infoprint Server

Not applicable.

Not applicable.

Not applicable.

Not applicable.

Another system in the sysplex is using a system logger log stream with the same name. If a log stream is a DASD-only log stream, only one system in a sysplex can write to it.

In the message text:

log-stream

Name of the log stream specified in the system configuration definition.

Infoprint Server continues processing, but messages are lost until the problem is corrected.

Notify the system programmer that this error occurred.

Notify the system programmer that this error occurred.

Do one of these:

• Define a DASD-only log stream only for Infoprint Server messages on this system. Then use the Infoprint Server ISPF panels to edit the system configuration definition. Specify the log stream name in the Log stream name and save the panel. When you save the Infoprint Server System Configuration ISPF panel, Infoprint Server automatically writes messages to the specified log stream.
• Convert the log stream to a CF-structure log stream.

When the problem is corrected, Infoprint Server automatically starts writing messages to the log stream.

For information about how to define a log stream for Infoprint Server messages, see z/OS Infoprint Server Customization.

For information about how to define log streams to the MVS system logger, see z/OS MVS Setting Up a Sysplex.

Tip: To request that Infoprint Server write messages to the z/OS Unix file system instead of to the system logger while you fix the problem, use the Infoprint Server ISPF panels to edit the system configuration definition. Edit these fields and save the panel: