Messages PTSB00 through PTSBxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PTSB01S SYSOUT ALLOCATION FAILED, RC= rc, ERROR= errCode

Explanation: Dynamic allocation of a sysout during a Printing Mission failed.

RC and error codes are the standard system return codes returned when dynamic allocation of a sysout chunk occurs.

The Printing Mission stops printing and ends NOTOK.

Corrective Action: For information regarding the diagnostics of dynamic allocation error codes, see to the IBM manual MVS Programming: Authorized Assembler Services Guide.

PTSB02E CANNOT PRINT WITH MIXED AFP PARAMETERS WHILE CHUNKSIZE IS SET TO ZERO OR ONE

Explanation: The PAGEDEF and/or FORMDEF printing parameters were specified for reports which are printed with a Printing Mission having a CHUNKSIZE of 0 or 1.

The PAGEDEF and/or FORMDEF printing parameters can only be used in a bundle that uses the chunking mechanism. When CHUNKSIZE is specified with a value of 0 or 1, the chunking mechanism is not active.

Printing continues without processing the PAGEDEF and FORMDEF printing parameters.

Corrective Action: To print reports that require the special printing parameters PAGEDEF and FORMDEF, either change the CHUNKSIZE parameter in the Printing Mission definition to a value other than 0 or 1, or use a different Printing Mission which uses the chunking mechanism.

PTSB03E PRINTING MISSION mission_nam FAILED WHILE TRYING TO LOAD PAGEDEF pagedef OR FORMDEF formdef. DEFAULTS ARE USED INSTEAD

Explanation: An error was encountered while trying to read a PAGEDEF or FORMDEF value from the corresponding library.

Either the PAGEDEF or FORMDEF specified does not exist in the libraries defined for Control-D, or the CHUNKSIZE parameter was specified as 0 or 1. The PAGEDEF and/or FORMDEF printing parameters must print in a bundle using the chunking mechanism. When CHUNKSIZE is specified with a value of 0 or 1, the chunking mechanism is not active.

Printing continues without processing the PAGEDEF and FORMDEF printing parameters.

Corrective Action: To print reports that require the special printing parameters PAGEDEF and FORMDEF, either change the CHUNKSIZE parameter in the Printing Mission definition to a value other than 0 or 1, or use a different Printing Mission which uses the chunking mechanism.

PTSB04E THERE IS NO PC INFORMATION IN THE TREE FOR USER user

Explanation: No PC information was found for the specified user during the process of building PC files.

User PC information must be defined in the Control-D Recipient Tree. If a report was assigned a destination of CTDPC but there is no PC information in the Recipient Tree for this user, it cannot be routed to the PC.

The report is not printed. Processing continues.

Corrective Action: Either define the user PC information in the Control-D Recipient Tree, or do not route the report to the PC.

PTSB05E CTDPC DEST WAS IGNORED FOR USER user (NO PC INFO)

Explanation: Destination CTDPC was specified for the user. The report should be transferred to the PC, but the user definition in the Recipient Tree does not contain PC parameters.

Only a user with PC parameters specified in the tree can receive reports on the PC.

The report will be routed to a mainframe printer instead of a PC.

Corrective Action: Define PC parameters for the user. The user must be authorized to access the CTDPC component.

PTSB06E OUTGRP INFORMATION IS UNAVAILABLE

Explanation: Highlighted, unrollable message.

The OUTGRP parameter is specified in CTDPARM, but the function cannot be performed.

An attempt to get the GROUPID parameter failed due to one of the following:

• The OUTGROUP OUTPUT statement was not specified in the CTDPRINT procedure.
• The corresponding control blocks cannot be found in the current release of MVS.

A special snap is sent to the DADUMP DD name.

Corrective Action: Check that the OUTGROUP OUTPUT statement is specified in the CTDPRINT procedure. If the error persists, contact your INCONTROL administrator and supply the snaps.

PTSB07E OUTGRP COULD NOT BE SET

Explanation: Highlighted, unrollable message.

The GROUPID parameter could not be set for the current chunk according to the OUTGROUP parameter in CTDPARM.

Corrective Action: Notify your INCONTROL administrator.

PTSB08E ERROR ACCESSING BARCODE TRACKING FILE RC= rc

Explanation: A print mission failed to access the Barcode Tracking (BTR) file.

The current print mission terminates NOT OK.

Corrective Action: Correct the source of the problem using message IOAF70I or IOAF71I to be found in the JES log. Rerun the mission.

PTSB09E ERROR CREATING PC FILES FOR USER recipName RC= rc

Explanation: An error occurred in the processing of a report to be transferred to Control-D/WebAccess Server for the recipient specified in the message.

An error was encountered while Control-D attempted to create PC packet files for a report whose printing destination is CTDPC.

The report is not made available for transfer to Control-D/WebAccess Server. Certain errors allow the print mission to continue processing with the next report. Most errors, however, cause the print mission to terminate immediately. In both cases, the print mission ends with a NOTOK status.

Corrective Action: If the return code is 28, verify that the recipient is authorized to use Control-D/WebAccess Server. This authorization is defined in the Control-D Recipient Tree. For all other return codes, check the IOA LOG and the MVS system log for previously issued messages describing the error in detail.

PTSB0AE MISSING OUTPUT STATEMENT stmtName

Explanation: Control-D attempted to dynamically allocate a sysout file for printing the report. Allocation failed because the output statement displayed in the message was missing from the JCL of Control-D Print monitor’s started task.

A reference to an output statement name to be used for printing a report is defined in Control-D by one of the following:

• Decollation Mission PRINT/CDAM PARM, subsys parameter in report’s job JCL, or OUTPARMS library member
• Internal output statement references assigned by Control-D, such as CONTROLD, CONTROLF and OUTGROUP

The report is not printed. The Print Mission continues with the next report to be printed, but ends with a NOTOK status.

Corrective Action: Define a JCL output statement for the report in the JCL of all Control-D Print monitors started tasks. Restart Control-D monitor to cause JCL changes to take effect.

PTSB0BE ERROR STORING REPORT IN DATASET. USER usernam, RC= rc

Explanation: Control-D detected an error while processing a printing mission in which the STORE parameter was set to YES.

This message is usually preceded by other messages that describe the problem. These other messages may be issued to the IOA Log file and/or the job log of the Control-D Printers monitor.

The variables in this message are:

• userName - User name
• rc - Printing mission return code

The printing mission ends with the status NOTOK and the return code 56.

Corrective Action: Check the IOA Log file for other printing mission errors. Check the job log in the Control-D Printers Monitor. If you cannot resolve the problem, call BMC Customer Support.

PTSB0CE ERROR IN CTDPRPS RC= rc

Explanation: An internal error occurred during the printing of an AFP report.

In this message, rc is the internal return code of the error.

The printing mission skips the problematic report, and printing continues.

Corrective Action: Do the following:

1. Check the IOA and job logs for any additional messages associated with the error, and try to resolve the problem. Rerun the program.
2. If the problem persists, note the value of rc and contact BMC Customer Support.

PTSB0DE OUTPUT CARD DYNAMIC ALLOCATION FAILED, RC= rc, REASON= rsn, KEY= keycode

Explanation: The dynamic allocation (pursuant to optional wish WD3133) of an output statement during a printing mission failed.

The variables in this message are:

• rc - the return code
• rsn - the reason code
• keycode - the key code

These codes are the standard system return, reason, and key codes that are returned when dynamic allocation of an output statement fails. For more information on these codes, see the description of the OUTADD macro in the IBM manual MVS Programming: Authorized Assembler Services Reference.

The printing mission does not use the dynamic allocation of an output statement for the current report.

Corrective Action: Examine the values of the return, reason, and key codes, and take appropriate corrective action.

PTSB10E "FE" PRINT SUPPORT ERROR. RETURN CODE rc

Explanation: An executing Printing Mission failed to delete an internal Printing Mission record in the Active User Report file.

If the DO PRINT parameter is specified in a Decollation Mission Definition, the Control-D Decollation monitor writes an internal Printing Mission record to indicate that there are reports waiting to be printed by the Printing Mission specified in the DO PRINT parameter.

These records have the following key:

X‘FE’,C‘PRINTMS’,Printing-Mission-Name

In this message, rc is the return code from the CTDXRP routine.

Control-D encountered an error when attempting to delete the record for the current Printing Mission during Printing Mission termination processing.

The Printing Mission continues.

Corrective Action: If the problem persists, report the return code to BMC Customer Support.