Messages PMS400 through PMS4xx

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

PMS401I PRINTING MISSION STARTED

Explanation: This information message is the normal start message of a Printing Mission.

Corrective Action: No action is required.

PMS402I PRINTING MISSION ENDED

Explanation: This information message is the normal end message of a Printing Mission.

Corrective Action: No action is required.

PMS403E PRINT MISSION HAS NOT STARTED DURING APPROPRIATE TIME FRAME.

Explanation: Highlighted, unrollable message.

The Control-D monitor issued a MODIFY command for a Printing monitor to start processing a Printing Mission. The Printing monitor did not answer during the time frame defined by optional wish WD2344 (whose default is five minutes).

The problem can occur because the Printing monitor has a low priority and the computer is heavily loaded. Therefore, the Printing monitor does not get control during the time allowed for a response.

The Control-D monitor terminates the mission NOT-OK.

Corrective Action: Assign a higher priority and/or change the performance group of the Printing monitor to provide better response time from this address space. In case of a batch printing mission, make sure that enough initiators are available for handling batch printing jobs. If this is impossible or undesirable, define a higher value for the time frame defined by optional wish WD2344 in the IOADFLTS member in the DOC library or specify an appropriate time-out in the Printing Mission Definition screen (screen M.S).

PMS404I SHUTDOWN IN PROGRESS

Explanation: This information message indicates that the Control-D monitor has requested all the subtasks under its control to shut down.

The IOA Log should contain additional messages concerning the reason for the shutdown.

Control-D monitor shuts down.

Corrective Action: No action is required.

PMS405I NO REPORTS ARE WAITING TO BE PRINTED BY THIS PRINTING MISSION

Explanation: This information message indicates that a Printing Mission has executed. However, there are no reports waiting to be printed by the mission.

No reports were found in the Active User Report List file to which all the following apply:

They were decollated by a decollating mission which specified this Printing Mission name in its DO PRINT parameter.
They belong to the users specified in the Printing Mission’s INCLUDE USER parameters.
They are in WAIT (RE)PRINT status.
The decollating mission which has processed them is in the Active Missions file and is not HELD.
They are not currently selected by another Printing Mission.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: No action is required.

PMS406E RECIPIENT recipName IGNORED. RECIPIENT NOT FOUND IN THE TREE

Explanation: The recipient recipName specified in the Printing Mission’s INCLUDE USER parameter is not found in the Recipient Tree; or the Printing Mission tried to select a user (from the Active User Report file) who is not in the tree.

No reports will be printed for this recipient.

Corrective Action: Add the recipient to the Recipient Tree or delete the recipient from the INCLUDE USER parameter of the Printing Mission.

PMS408E PRINTING PLAN FILE ALLOCATION ERROR. RC= rc, ERROR= errCode

Explanation: An error occurred in allocating a Print Plan file for this Printing Mission.

One of the following probably occurred during dynamic allocation of the Print Plan file:

The Printing Mission was restarted, but the Print Plan file was manually erased.
An attempt to allocate a new Print Plan file failed, for a reason such as lack of space, security.
An attempt to delete a Print Plan file failed.

The expressions RC= rc and ERROR= error_code indicate the return and reason codes from the dynamic allocation. For an explanation of these codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

This Printing Mission will not print any reports and will end with a NOTOK status.

Corrective Action: Check the IOA Log, the Control-D monitor syslog, and system log for additional clarification messages.

PMS409E PRINTING PLAN FILE CRITICAL ALLOCATION ERROR

Explanation: Internal error. In attempting to allocate a Print Plan file, an unknown return code was received from the CTDALC Control-D utility module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS40AW SOME REPORTS ARE LOCKED BY ANOTHER PRINT MISSION

Explanation: The current print mission did not place one or more reports in the print plan although these reports have status WAIT PRINT and should be printed by this mission.

Each print mission checks each report to be included into the print plan against print plans of other print missions (excluding missions ended OK/NOTOK). If this report is included into another print plan, the current mission will not print it in order to avoid duplicate printouts.

The print mission continues processing.

Corrective Action: If the skipped reports will be printed by another mission, no action is needed. If these reports should be printed by the current mission, find the other active missions whose print plan includes these reports. Delete the other missions or allow them to terminate.

PMS40BW SOME REPORTS ARE SUPPRESSED BY USER EXIT 20

Explanation: The printing mission did not include some reports in the print plan because user exit CTDX020 suppressed them.

Function PUT is used to call user exit CTDX020. This exit creates the print plan for each report that is eligible for printing. If this exit returns a return code of 4, the report is not included in the print plan.

The printing mission continues.

Corrective Action: If the suppressed report should have been added to the print plan, determine why the report was suppressed.

PMS40CW SOME REPORTS ARE NOT SET FOR THE CURRENT PRINTING MISSION

Explanation: The printing mission found some reports originally set for the current mission. However, they were later reset for another mission.

This can occur if the user manually changes the printing mission name in the report entry in the U screen.

The printing mission continues normal work flow. Invalid reports are skipped.

Corrective Action: No action is required.

PMS40DW SOME REPORTS ARE NOT SET FOR CONTROL-D/PC

Explanation: DEST=CTDPC was specified for the printing mission. However, some reports were found to be ineligible for this mission.

The reports were not eligible because they did not specify either DEST=CTDPC[PRT] or a corresponding recipient authorized to use Control-D/PC.

When DEST=CTDPC is specified for a printing mission, all reports selected by this mission must specify DEST=CTDPC or DEST=CTDPCPRT. Recipients for these reports must be authorized to use Control-D/PC by means of the recipient tree.

The printing mission continues normal work flow. Reports that are not eligible are skipped.

Corrective Action: For reports to be transferred to Control-D/PC, do the following:

Specify DEST=CTDPC or DEST=CTDPCPRT during decollation. See the section on specifying report destinations in the Control-D and Control-V User Guide.
Verify that report recipients are authorized to use Control-D/PC.

PMS40EW INDEX REPORT IS NOT SET FOR STORE=YES MISSION

Explanation: A printing mission specifying STORE=YES did not select Control-V index report setting for Deferred printing. Printing missions specifying STORE=YES select only whole reports. Control-V index reports are not selected by a printing mission with parameter STORE=YES.

Corrective Action: Do not specify a name of a printing mission when STORE=YES is specified in the PRINT statement in DO INDEX.

PMS40GW REPARTITION COPY STAGE IS IN PROCCESS

Explanation: This warning message indicates that the repartition utility CTDUFMPR is running with the COPY function when print mission tries to print a migrated report. The print mission continues normal work flow but the migrated reports are not printed and remain in WAIT PRINT status.

Corrective Action: Submit the CTDBLXRP utility after the CTDUFMPR repartition utility with the COPY function ends. Then rerun the Print mission.

PMS40HW CTDBLXRP WAS NOT SUBMITTED AFTER REPARTITION COPY STAGE ENDED

Explanation: This warning message is issued when a print mission printing migrated reports is started after the CTDUFMPR with COPY function is ended, but the CTDBLXRP utility was not submitted previously. The print mission continues normal work flow but the migrated reports are not printed and remain in WAIT PRINT status.

Corrective Action: Submit the CTDBLXRP utility and then rerun the print mission.

PMS40IW MIGRATED REPORTS ARE NOT PRINTED

Explanation: This warning message follows the PMS40GW and PMS40HW messages and indicates that the migrated reports are not printed.

Corrective Action: Perform actions described for the previous message.

PMS410E OPEN OF PRINTING PLAN FILE FAILED

Explanation: Internal error. The open of the Print Plan file failed.

The dynamic allocation of the Print Plan file was successful, but the open of the file failed.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS411E PRINTING PLAN FILE - WRITE ERROR

Explanation: Internal error. An error occurred in writing to the Print Plan file.

The dynamic allocation and open of the Print Plan file were successful, but an error occurred while writing to the file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS412E INTERNAL ERROR - INVALID RC FROM CTDWTF

Explanation: Internal error. Invalid return code from the internal program CTDWTF while writing the Print Plan file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS413E SYSOUT ALLOCATION ERROR (INVALID DEST) PRINTING STOPPED

Explanation: The DEST (destination) parameter for this Printing Mission is incorrect (meaning, not recognized by MVS/JES).

The DEST parameter specifies the JES destination for printing the report. See also remarks about JES3 in the PRINTER parameter in the Control-D and Control-V User Guide, and in “Set Control-D Installation Parameters” in the Control-D chapter in the INCONTROL for z/OS Installation Guide. If this parameter is omitted, the DEST is assumed to be the main computer printer. Specify the DEST parameter in one of the following ways:

User Report List screen - refer to “User Reports - Report List” in the Control-D and Control-V User Guide.
Report Decollating Definition screen - refer to “Report Decollating Parameters” in the Control-D and Control-V User Guide. Additional details are in Chapter 3, “Report Decollating Mission Parameters”.
Printing Mission Definition screen - refer to “Specific Mission Parameters, PRINTER (DEST)” in the Control-D and Control-V User Guide.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Correct the DEST parameter, and rerun the Printing Mission.

PMS414E PRINTING PLAN FILE - CANNOT BE OPENED BY THE PRINTERS CONTROL MONITOR

Explanation: Internal error. The Printers Control monitor could not open the Print Plan file.

The Print Plan file was successfully created by the Control-D monitor, and passed the name of the Print Plan file to the Printers Control monitor. However, the Printers Control monitor was unable to open the file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS415E OPEN OF SYSOUT FOR PRINT FAILED

Explanation: Internal error. The Printers Control monitor could not open the sysout file for printing.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Look for additional messages on the system log. If you cannot find the problem, have your system programmer call BMC Customer Support for assistance.

PMS416E PRINT - UNKNOWN INTERNAL ERROR

Explanation: Internal error in Printers Control monitor. An unknown return code was received from the CTDPRT module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS417E MEMORY SHORTAGE OR INTERNAL ERROR MAY CAUSE DUPLICATE PRINT OF SOME REPORTS

Explanation: An error occurred in main memory during the building of the Print Plan List.

The Print Plan List is checked during the building of a Print Plan file to verify that the same report is not included for printing by other Printing Missions that may be processing in parallel.

The Printing Mission continues processing; however, another Printing Mission may possibly process the same reports.

Corrective Action: Enlarge the REGION size for the Control-D monitor. If this does not solve the problem, contact BMC Customer Support.

PMS418S PRINT - INTERNAL ERROR WHILE READING ACTIVE REPORTS FILE INDEX

Explanation: Internal error in the CTDCLS module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS419S INTERNAL ERROR WHILE PREPARING USER LIST FOR THE PRINT PLAN

Explanation: Internal error in the CTDPM2 module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS420S INSUFFICIENT STORAGE TO BUILD PRINTING PLAN

Explanation: There is insufficient storage to build the Print Plan file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Increase the REGION size of the Control-D monitor, and rerun this Printing Mission.

PMS421S PRINT - INTERNAL ERROR IN CTDPM1

Explanation: Internal error in the CTDPM1 module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS422I START COMMAND HAS BEEN ISSUED FOR PROCEDURE procName, COM number

Explanation: This information message indicates that a batch print mission has been started as a started task.

A batch print mission runs as a started task when its skeleton member does not contain a JCL statement (starts with //) but an operator command.

Corrective Action: No action is required.

PMS423S PRINT - INTERNAL ERROR IN CTDCOL

Explanation: Internal error in the CTDCOL module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS424S ERROR WHILE READING THE ACTIVE USER FILE FOR PRINTING PARAMETERS

Explanation: An error occurred while accessing the Active User file during a print mission run.

Message CTD908S preceding this message contains the reason code of the error and other information.

The current print mission terminates NOT-OK.

Corrective Action: Using the information in message CTD908S, correct the problem, and reprint the corresponding reports.

PMS425S SYSOUT ALLOCATION ERROR - PRINTING STOPPED

Explanation: Internal error in the Printers Control monitor.

The CTDSYS module was unable to allocate a sysout file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Look for additional messages on the System Log. If you cannot find the problem, have your system programmer call BMC Customer Support for assistance.

PMS426E OPEN OF DAINTRDR FAILED

Explanation: An error occurred during the dynamic allocation of the INTRDR internal reader while a batch printing mission was starting a batch print job as a started task.

No reports are printed by this batch printing mission. The mission ends with the status NOT OK.

Corrective Action: Examine the system log for further error messages that may help identify the problem. If the problem persists, ask your system programmer to contact BMC Customer Support.

PMS427S PRINTING PLAN FILE CANNOT BE ALLOCATED - NO SPACE ON DISK

Explanation: There is no disk space for allocating the Print Plan file.

The Installation Parameters WRKUNIT and WRKVOL, described in “Set Control-D Installation Parameters” in the Control-D chapter of the INCONTROL for z/OS Installation Guide, specify the unit and volume serial number for the printing plan file. The WRKVOL disk does not have disk space for allocating the printing plan file.

This Printing Mission does not print any reports, and ends with a NOTOK status.

Corrective Action:

Delete unneeded files from the WRKVOL disk, or change the WRKUNIT/WRKVOL parameters on CTDPARM.
Bring Control-D down.
Start the Control-D monitor.
The Printing Mission can then be rerun.

PMS428S INSUFFICIENT STORAGE FOR INCLUDE/EXCLUDE LIST

Explanation: There is insufficient storage for Control-D to handle all the INCLUDE/EXCLUDE USER statements in the Printing Missions Definition.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action:

Remove some INCLUDE/EXCLUDE USER statements from this Printing Mission Definition and create new Printing Missions to put them in, or (preferably)
Increase the REGION size of the Control-D monitor.
Bring Control-D down, then up.
The Printing Mission can then be rerun.

PMS429S ABEND IN THE PRINTERS CONTROL MONITOR

Explanation: Print mission failed with an abend. A detailed description of the failure appears in the preceding message.

The current print mission ends NOT-OK.

Corrective Action: Check the dump and any relevant messages in the system log. For an explanation of the abend code, refer to the relevant IBM manual. Correct the problem and restart the problematic PRINT mission.

PMS42AE PRINT JOB IS NOT SUBMITTED DUE TO ERROR

Explanation: Print mission failed to submit print job.

A detailed description of the failure appears in the preceding message.

The current print mission ends NOT-OK

Corrective Action: Proceed according to the description of the failure in the preceding message.

PMS42BE ERROR READING SKELETON. CTMMEM RC= rc

Explanation: Print mission skeleton cannot be read from the SKL library.

The current print mission ends NOT-OK.

Corrective Action: Proceed according to the CTMMEM return code identified in the message. A description of the CTMMEM return codes can be found in the DOCIMEM member in the IOA DOC library.

Rerun the print mission.

PMS42CE MESSAGE=MEMBER memName IS NOT FOUND IN THE SKELETON LIBRARY

Explanation: The SKELETON parameter specified in the Print mission definition does not exist in the SKL library.

The current print mission ends NOT-OK.

Corrective Action: Correct the SKELETON parameter in the print mission definition, or if it is correct, add it to the SKL library. Rerun the print mission.

PMS42DE CTDX009 REJECTED PRINT JOB SUBMISSION

Explanation: Exit 9 (CTDX009) rejected submitting a print job.

The current print mission ends NOT-OK.

Corrective Action: If it is required that the job be submitted, check Exit 9 for a return code of 8 and modify the exit accordingly. Rerun the print mission.

PMS42EI PRINT JOB name / jobId HAS BEEN SUBMITTED

Explanation: This information message indicates that the print job name has been successfully submitted.

Corrective Action: No action is required.

PMS42FE PRINT MISSION CANNOT BE STARTED. PRTMON#=0 IS DEFINED IN CTDPARM

Explanation: No print monitors are defined in CTDPARM.

The PRTMON# field must be defined in CTDPARM so that a print mission can be executed as a subtask of the print monitor.

The current print mission terminates NOT-OK.

Corrective Action: Specify PRTMON# parameter in CTDPARM, or define the SKELETON field in the print mission definition to run the mission as a batch job.

PMS430S PRINT - INTERNAL ERROR IN CTDCIO

Explanation: An error occurred in the CTDCIO Control-D communication file I/O module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Bring down Control-D, then follow these steps:

Check the DACOM DD statement in the Control-D monitor and Printers Control monitor JCL, and correct the JCL if required.
Check the COMSIZE Installation Parameter. For more information, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.
If this parameter is modified, then the CTDFRCOM Control-D utility will have to be run in order to create a new communications file.
Bring up Control-D, and rerun this Printing Mission.

If following the steps specified above does not solve the problem, have your system programmer call BMC Customer Support for assistance.

PMS431S INTERNAL SYNCHRONIZATION ERROR - SHUTTING DOWN

Explanation: An internal error has occurred in the Printers Control monitor.

An error occurred in the CTDPMS module--the synchronization with the Printers Control monitor failed.

Control-D monitor shuts down.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS432I NOTHING LEFT TO PRINT (THERE ARE USERS, BUT COP=0 OR REPORTS DELETED)

Explanation: This information message indicates that there are no reports for this Printing Mission to print.

There are a few possibilities:

All the SYSDATA entries to be printed were deleted.
All the CDAM files to be printed were deleted.
The copy count of all reports to be printed was set to 0 in the Active User Reports file.
The relevant decollation entries in the Active Missions file were deleted or are in HOLD status.

The Printing Mission will not print any reports, and will end up with a NOTOK status.

Corrective Action: Change the copy count to a value other then zero and/or free the Active Missions file report entries and/or rerun the Report decollating mission if the reports were accidentally deleted. The Printing Mission can then be rerun.

PMS433S ALLOC OF dd_stmt FAILED ON rsn

Explanation: An internal error has occurred in the Control-D monitor.

An error occurred in the CTDPSR utility module that sorts the printing plan file. The dynamic allocation of dd_stmt failed because of the reason identified in the message.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS434S FREE OF dd_stmt FAILED ON rsn

Explanation: An internal error has occurred in the Control-D monitor.

An error occurred in the CTDPSR utility module that sorts the printing plan file. The dynamic allocation and read/write to dd_stmt was successful. However, the attempt to free dd_stmt failed because of the reason identified in the message.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS435S SORT OF BUNDLE FAILED. RC= rc

Explanation: An internal error has occurred in the Control-D monitor.

An error occurred in the CTDPSR utility module that sorts the printing plan file. The installation sort routine returned a condition code of rc to the CTDPSR module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Check the system log and the Control-D monitor sysout in order to determine why the installation sort routine returned a condition code of rc. RC is the SORT RC, so check it in the SORT manual. If you cannot resolve the problem, have your system programmer call BMC Customer Support for assistance.

PMS437E SORT OF BUNDLE FAILED. PRINTING MISSION ENDED NOTOK

Explanation: The sort of the Printing Plan file failed.

Corrective Action: Check the IOA Log for additional clarification messages.

PMS438E RESTART OF PRINTING MISSION FAILED. COMMUNICATION FILE WAS FORMATTED

Explanation: Restart of Printing Mission failed.

The Control-D Communication file was formatted, making automatic restart impossible.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Rerun the Printing Mission without rebuilding the Printing Plan file.

PMS439I ONLY (number) FREE ENTRIES ARE LEFT ON THE COMMUNICATION FILE - PLEASE INCREASE ITS SIZE

Explanation: The Control-D Communication file is almost full.

This is an informational message only.

The printing of the reports will continue.

Corrective Action: At the earliest possible time, bring down Control-D, then follow these steps:

Increase the COMSIZE Installation Parameter. For more information, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.
Run the CTDFRCOM utility in order to create a new communication file.
Bring up Control-D.

PMS43AE NO FREE RECORDS IN COM FILE. PRINT MISSION TERMINATES ABNORMALLY

Explanation: The current print mission cannot obtain a free record in the communications file.

Each print mission requires one record in the COM file for communicating between the Control-D monitor and the print task. A free record is obtained before the print task is started released when it ends.

The print mission terminates NOTOK.

Corrective Action: Increase the size of the COM file by increasing the value of the COMSIZE parameter in CTDPARM. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 2, Control-D Dataset Parameters.
Increase the size of the COMSIZE parameter.
Return to the Minor Steps Selection screen, and select Minor Step 3, Save Parameters into Product Libraries.
Select Minor Step 5, Format the Communication File.

You can now rerun the print mission.

PMS43BE ERROR STORING REPORTS IN DATASETS

Explanation: Control-D detected an error while processing a printing mission with the STORE parameter 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 printing mission ends with a status of NOTOK and a reason code of 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.

PMS440I MISSION RESTARTED. PRINTING WILL START FROM NEXT REPORT

Explanation: A stopped Printing Mission has been restarted

The user has previously put this Printing Mission on HOLD (while printing), and has now FREEd this mission.

Printing will start again from the next report.

Corrective Action: No action is required.

PMS441I MISSION RESTARTED (FROM START OF PRINT PLAN)

Explanation: This information message indicates that a stopped Printing Mission was restarted using the printing plan built during the previous run of the mission

Corrective Action: No action is required.

PMS442I PRINTING MISSION RESTARTED

Explanation: Normal message when a stopped Printing Mission has been restarted.

The user had previously put this Printing Mission on HOLD (while printing), and has now freed this mission.

The printing of the reports continues.

Corrective Action: No action is required.

PMS443E SOME REPORTS WERE NOT PRINTED

Explanation: The print mission processed all the reports in the print plan, but some of them were not successfully printed.

Detailed messages appear during this print mission execution.

The problematic reports are marked as NOT-PRINTED in the Active User File.

Corrective Action:

Correct the cause of the problem that prevented the printing of the reports, using the messages that appear during the execution of the print mission.
Reprint the reports by ordering Deferred Print in the User Reports screen (U Screen).
Rerun the print mission with a rebuild of the print plan.

PMS443S INSUFFICIENT STORAGE TO LOAD PRINT PLAN MODULE

Explanation: There is insufficient storage to load the CTDPLN print plan module.

The Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Increase the REGION size for the Control-D monitor.

PMS444S DELIVERY ERROR - PRINTING STOPPED

Explanation: Delivery error in the Printers Control monitor.

An error was encountered while attempting to connect to the Control-D/Delivery Server. Printing to the CTDS destination failed, because the Control-D printing monitor did not manage to establish a connection to the Control-D/Delivery Server.

This Printing Mission will not continue distribution reports and will end with status NOTOK.

Corrective Action: Look for additional messages on the System and IOA Logs. Fix the problem and restart the PRINT mission.

Parent Topic

PMS messages