|
|
|
|
|
This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.
Explanation: Control-D or Control-V failed to open the (sequential) index file.
The data set dsn cannot be accessed for reading.
Reports will be downloaded to the Control-D/WebAccess Server without index information.
Corrective Action: Record the data set name and return code. Contact your system administrator.
Explanation: A sequential index file failed to close.
The data set dsn did not close successfully.
Reports will be downloaded to the Control-D/WebAccess Server without index information.
Corrective Action: Record the data set name and return code. Contact your system administrator.
Explanation: Control-D or Control-V encountered a problem when attempting to dynamically allocate the dsn index file.
Reports will be downloaded to the Control-D/WebAccess Server without index information.
Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the data set name, internal rc and reason code rsn. Contact BMC Customer Support.
Explanation: Control-D or Control-V failed to dynamically deallocate index file data set name.
Reports will be downloaded to the Control-D/WebAccess Server without index information.
Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the data set name, internal rc and rsn. Contact BMC Customer Support.
Explanation: There is insufficient memory to download index information to the PC.
The Printing Mission that downloads reports to the PC terminates.
Corrective Action: Increase the REGION size of the Control-D Print monitor.
Explanation: An internal error was encountered during the execution of a FREEMAIN macro.
The Printing Mission that downloads reports to the PC terminates.
Corrective Action: Record the return code and contact BMC Customer Support.
Explanation: Index index was not found in the dsn file due to an internal error.
Reports will be downloaded to the Control-D/WebAccess Server without index information.
Corrective Action: Record the index name and data set name. Contact BMC Customer Support.
Explanation: Incorrect parameters were passed from the printing module to the routine creating Control-V indexes for the D/WebAccess Server viewer.
The current print mission terminates NOT-OK.
Corrective Action: Supply BMC Customer Support with the sysout of the Control-D print monitor.
Explanation: Control-V was unable to create an index file for the printed report.
If the error is in the CTVIXC program, look at message REPG01E for a complete explanation of all return codes.
If the error is in the IOATAE program, possible causes are:
rc |
Explanation |
|---|---|
4 |
Member with translation table from ASCII to EBCDIC was not read. A default translation table was used. |
8 |
Not enough storage available. Increase region size. |
12 |
Data is invalid. Check and correct the translation table data. |
16 |
Too many data lines in the translation table. Check and correct the translation table data. |
20 |
Not enough data lines in the translation table. Check and correct the translation table data. |
The translation tables are found in the IOA PARM library referenced by the DACMDLIB DD statement.
The TRNA2E member translates from ASCII to EBCDIC. The TRNE2A member translates from EBCDIC to ASCII.
The Control-V index is not created.
Corrective Action: Take appropriate action to correct the problem based on the return code.
Explanation: Data set name dsn could not be created.
The data set for the Control-V index could not be allocated.
The Control-V index is not created.
Corrective Action: Record the data set name and contact your system administrator.
Explanation: The ACIF process split one or more pages of the report.
If an original report page is split into more than one AFP page during the ACIF process, the original Control-V index for the report cannot be converted to fit the AFP report.
In this message, num is the number of resource pages.
The Control-V indexes are not created.
Corrective Action: Change the ACIF parameters so that no report page will be split by the ACIF process.
Explanation: An internal error occurred while creating Control-V indexes for a STORE=Y report.
In this message, pagenum is the page number of the page that is missing from the report page table.
Control-V indexes are not created.
Corrective Action: Provide the following information to the INCONTROL Administrator:
Explanation: Control-V attempted to convert indexes to fit a new STORE=Y report. However, the existing indexes were created in a non-supported version, and cannot be converted to fit a new STORE=Y report.
The Control-V indexes are not created.
Corrective Action: Redecollate the report using a supported version of Control-V.
Explanation: The printing mission attempted to access a continuation record that did not exist in the Active User Report file.
Control-V indexes are not created.
Corrective Action: Contact your INCONTROL administrator.
Explanation: An internal error occurred during the creation of Control-V indexes for a report created by a Print Mission with STORE set to Y.
A level of the problematic Control-V index is changed.
Corrective Action: Contact BMC Customer Support.
Explanation: During the rendering to PDF, if an original report page is split into more than one PDF page, the original Control-V index for the report cannot be converted to fit the PDF report.
Corrective Action: If possible, change the rendering parameters (for example, CLIQUE, resources) so that no report page will be split by the rendering process.
Explanation: This information message indicates that the current print mission cannot be processed because the print monitor is already processing the maximum number of missions as defined in optional Wish WD2375. The print mission is delayed until one of the missions being processed terminates.
Corrective Action: If this message appears frequently, it is recommended to increase the maximum number of print missions the print monitor can process concurrently.
Explanation: This information message indicates that the print monitor resumed processing a mission that was postponed (see the PTSG9GW message).
Corrective Action: No action is required.
Parent Topic |