Reason:
Sysouts specified for the selective unload were not found on the View database.
Action:
Delete the unloaded file. Correct the sysout ids specified for selective unload. Rerun the job.
Reason:
Informational message indicating the start of the index file block mapping phase of the database verification process. The verification process involves three phases which are the index file block mapping phase, the index record verification and subfile (SYSOUT data and panel data) mapping phase, and the alternate index and extended index record verification phase.
Action:
None. This is an informational message.
Reason:
This is an informational message indicating the start of the index record verification and subfile (SYSOUT data and panel data) mapping phase of the database verification process. The verification process involves three phases which are the index file block mapping phase, the index record verification and subfile mapping phase, and the alternate index and extended index record verification phase.
Action:
None. This is an informational message.
Reason:
This is an informational message indicating the index record currently being processed in index record verification and subfile mapping phase. This message is written to the operator console on an interim basis depending on the frequency defined in the DBMSGFRQ initialization option.
Action:
None. This is an informational message.
Reason:
The data space occupied by the incomplete REORG function is freed from the database.
Action:
None. This is an informational message.
Reason:
The data space that is occupied by the specified online member (panel, message, or skeleton JCL) is being verified and mapped. If the internal structure of the subfile is incorrect, the online member can be truncated or lost.
Action:
None. This message is informational.
Reason:
The data space that is occupied by the subfile for the specified SYSOUT or page layout RESOURCE is being verified and mapped. If the internal structure of the subfile is incorrect, the archival SYSOUT data can be truncated or lost.
Action:
None. This message is informational.
Reason:
The data space that is occupied by the auxiliary file (SYSOUT indexing mapping data) for the specified SYSOUT or page layout RESOURCE is being verified and mapped. If the internal structure of the subfile is incorrect, the auxiliary data can be truncated or lost.
Action:
None. This message is informational.
Reason:
A master control record (index record which contains initialization parameters and other vital information) cannot be found in the database and is being created.
Action:
After the database verification process is complete, run the SARINIT utility to reinstate all initialization options.
Reason:
SYSOUT groups are found in the database to contain a higher generation number, sequence number, and/or tape sequence number than indicated in the master control record (index record which contains initialization parameters and other vital information). The higher generation number, sequence number, and/or tape sequence number are being placed in the master control record.
Action:
None. This is an informational message.
Reason:
The current generation number and sequence number in the master control record are being changed from a complemented form to a non‑complemented form.
Action:
None. This is an informational message.
Reason:
The data space that is occupied by the specified model banner page member is being verified and mapped. If the internal structure of the subfile is incorrect, the model banner page member can be truncated or lost.
Action:
None. This message is informational.
Reason:
This is an informational message indicating the start of the alternate index and extended index record verification phase of the database verification process. The verification process involves three phases, as follows:
Action:
None. This is an informational message.
Reason:
This message is informational indicating the index record that is being processed in the alternate index and extended index record verification phase. This message is written to the operator console on an interim basis depending on the frequency defined in the DBMSGFRQ initialization option.
Action:
None. This message is informational.
Reason:
The extended index record for the specified key contains invalid data and has been deleted from the database.
Action:
None. This is an informational message.
Reason:
The index record for the specified SYSOUT group contains invalid data and has been deleted from the database.
Action:
None. This is an informational message.
Reason:
Informational message indicates the end of the verification process.
Action:
None. This is an informational message.
Reason:
The SARSTC archival task has been started with Forward Recovery activated. The CA View initialization parameters RCVPRIM=xxxx and RCVUNIT=nnnn activate Forward Recovery.
Action:
None. This is an informational message.
Reason:
An error occurred during the allocation of a forward recovery data set. The hexadecimal error and information codes are provided.
Action:
The allocation error message may not be critical if issued during the recovery process or during the deletion process of the backup cycle. If the message, however, is issued by the archival task during archival of SYSOUT data, forward recovery can be disabled as indicated by the SARDRP99 message. In this case, resolve the error before forward recovery can be restarted. Forward recovery can be restarted by recycling the archival task or by initiating a backup cycle.
Reason:
An error occurred while performing I/O to a forward recovery data set.
Action:
If the I/O error occurred while recording archival data, an attempt is made to recover from the I/O error by allocating a new forward recovery data set and writing the appropriate information to the new data set. If recovery fails, the SARDRP99 message indicates that forward recovery is disabled. In this case, resolve the error before forward recovery can be restarted. Restart forward recovery by recycling the archival task or by initiating a backup cycle.
Reason:
Forward recovery was unable to recover from a previous error.
Action:
See the explanation and action in the previous error message for resolution. When the previous error is resolved, restart forward recovery by recycling the archival task or by initiating a backup cycle.
Reason:
The end-of-file messages are purely informational and rarely issued. The not found/not written messages can indicate possible logic errors. These logic errors arise when there are no forward recovery data sets to read from or write to. The data set not allocated message indicates that the RCVUNIT and/or RCVPRIM initialization parameters were not initialized to activate forward recovery.
Action:
The only messages that can require attention are the not found and not written messages. Normally, these messages are accompanied by previous error messages. See the explanation and action of the previous error messages for resolution.
Reason:
An error occurred opening a forward recovery data set.
Action:
Normally, forward recovery continues processing by allocating a new forward recovery data set. In extreme cases, forward recovery can be disabled as indicated by the SARDRP99 message. In this case, resolve the error before forward recovery can be restarted. Forward recovery can be restarted by recycling the archival task or by initiating a backup cycle.
Reason:
The forward recovery data set does not conform to the data structure of its data records. This condition can occur when foreign data is copied into a forward recovery data set or a foreign data set is renamed to conflict with a current forward recovery data set. This message can also be produced with new releases of the product when the length of database index records has changed.
Action:
None. Forward recovery continues processing with a new forward recovery data set.
Reason:
The residence or location of the forward recovery data set on a DASD device has changed. This condition can occur when a forward recovery data set is moved to a different volume or to a different location in the same volume.
Action:
None. Forward recovery continues processing with a new forward recovery data set.
Reason:
The space allocation for the forward recovery data set was not large enough to contain its internally maintained control records and archival control data.
Action:
Increase the primary and/or secondary space allocation amount for the forward recovery data set that is identified by the RCVPRIM and RCVSEC initialization parameters.
Reason:
The internal control block structure that is used to control the forward recovery data sets has been overlaid or destroyed.
Action:
This error can occur from incorrectly modified user exits or from internal logic errors. Forward recovery is disabled as indicated by the SARDRP99 message. Forward recovery can be restarted by recycling the archival task or by initiating a backup cycle. For assistance, contact Technical Support at http://ca.com/support.
Read functions not permitted during output processing
Write functions not permitted during input processing
Reason:
I/O activity issued against a forward recovery data set is inconsistent with its designed processing features.
Action:
This error identifies a flaw in the internal processing logic. Contact CA Technical Support for resolution.
Reason:
I/O requests to write archived data or auxiliary data to the forward recovery data set are not preceded by an I/O request to write the archival group control that identifies the archival data.
Action:
This error identifies a flaw in the internal processing logic. For assistance, contact Technical Support at http://ca.com/support.
Reason:
Forward recovery was unable to successfully write control data and/or archival data to the forward recovery data set.
Action:
This error is accompanied by the SARDRP12 I/O error message. Processing usually continues with a new forward recovery data set. In extreme cases, forward recovery is disabled as indicated by the SARDRP99 message. Restart forward recovery by recycling the archival task or by initiating a backup cycle.
Reason:
This message indicates that a forward recovery data set has been allocated on the specified volume.
Action:
None. This is an informational message.
Reason:
This message indicates that a forward recovery data set has been deleted. Old forward recovery data sets are deleted as part of the normal processing flow at the end of the backup cycle.
Action:
None. This is an informational message.
Reason:
The SARSTC archival task has stopped the process of capturing SYSOUT and writing a duplex copy of it to the forward recovery data set. This message is normal during shutdown of SARSTC.
Action:
No action is required for normal shutdown. Check for previous error messages indicating I/O errors on the forward recovery data set if this message occurs at a time other than normal shutdown.
Reason:
The index file space allocation is being verified.
Action:
None. This is an informational message.
Reason:
The space allocated for the file overlaps the space allocation of another. The allocation has been corrected.
Important! Some of the data can be lost.
Action:
None. This message is informational.
Reason:
The file contains an invalid block pointer. The pointer has been corrected. Some of the data can be lost.
Action:
None. This message is informational.
Reason:
The database allocation blocks are being rewritten.
Action:
None. This is an informational message.
Reason:
The contents of the index file are being logically verified.
Action:
None. This is an informational message.
Reason:
A logical error is found in the index file. The index entry is deleted.
Action:
None. This is an informational message.
Reason:
A logical error is found in the index file. The index entry is corrected to the high key for the lower block.
Action:
None. This is an informational message.
Reason:
A logical error is found in the index file. Unrecognizable data is found in an index entry. The entry is corrected.
Action:
None. This is an informational message.
Reason:
A logical error is found in the index file. The index data record is deleted.
Action:
None. This is an informational message.
Reason:
A logical error is found in the index file. The number of index entries in an index block is in error and has been corrected.
Action:
None. This is an informational message.
Reason:
A logical error is found in the index file. The used data count is in error and has been corrected.
Action:
None. This is an informational message.
Reason:
The expanded access server for tape and robotics has abended. The system or user abend code is provided.
Action:
Consult the IBM MVS System Messages manual to determine the reason for the abend. If you still cannot determine the problem, contact CA Technical Support.
Reason:
A tape-processing task of the expanded access server for tape and robotics has abended. The system or user abend code, TCB address, process request entry address, process request type, and the job ID of the requestor are provided.
Action:
Consult the IBM MVS System Messages manual to determine the reason for the abend. If you still cannot determine the problem, contact Technical Support at http://ca.com/support.
Note: The task is restarted automatically and processing continues.
Reason:
A tape-processing task of the expanded access server for tape and robotics has abended and is being restarted automatically.
Action:
None. This is an informational message.
Reason:
Dynamic allocation failed for the tape specified by dsname. The hexadecimal error and information codes are provided.
Action:
None. The tape cannot be used. Processing continues.
Reason:
This message is displayed whenever the server is stopped. You can use the information that is provided to adjust the NREQ initialization parameter.
Action:
None. This message is informational.
Reason:
The device type is invalid for the tape specified by dsname. The server can only process 3480/3490 type cartridge tapes.
Action:
None. The tape cannot be used. Processing continues.
Reason:
An attempt is made to read data from a copy of an archival tape that had been created by the SARTCP utility. SARTCP created tapes cannot be used directly. However, the data on the SARTCP created tape can be made available again by compacting the tape to another tape with the SARPAC utility.
Action:
None. The tape cannot be used. Processing continues.
Reason:
The primary server is already active and cannot be started again.
Action:
None. This is an informational message.
Reason:
The server is already active on this system and cannot be started again.
Action:
None. This is an informational message.
Reason:
The specified operator command is invalid.
Action:
Reissue the operator command in its correct form.
Reason:
The specified parameter is invalid. The server uses the default value for the parameter and continues processing.
Action:
Correct the initialization parameter in the start procedure JCL.
Reason:
The specified server type is invalid. The server uses the default value ONLY for the server type and continues processing.
Action:
Correct the initialization parameter in the start procedure JCL.
Reason:
A listing of the parameters that are actually used by the server is provided at startup time.
Action:
None. This message is informational.
Reason:
The specified XCF request failed. The hexadecimal return and reason codes are provided.
Action:
For the return and reason codes to determine the cause of the failure, see the IBM Authorized Assembler Reference Guide. If you still cannot determine the problem, Contact CA Technical Support.
Reason:
The specified L-Serv request failed. The hexadecimal return and reason codes are provided.
Action:
Consult the CA L-Serv System Guide for the return and reason codes to determine the cause of the failure. If you still cannot determine the problem, contact CA Technical Support.
Reason:
The specified communication mechanism is invalid. The server uses the default value LSERV for the communication mechanism and continues processing.
Action:
Correct the initialization parameter in the start procedure JCL.
Reason:
The COMMRESET operator command was successfully executed.
Action:
None. This is an informational message.
Reason:
The UNLOAD operator command is posted to the tape processing threads.
Action:
None. This message is informational.
This message number represents a two line message:
Reason:
SAREAS has processed a modify NTHREADS command request and rejected the new value (nnn) for NTHREADS. xxx is the value that was specified when the task was started, and yyy is the current value for NTHREADS.
Action:
Correct the NTHREADS value.
Reason:
SAREAS has processed a modify NTHREADS command request and accepted the new value (nnn) for NTHREADS.
Action:
None. This is an informational message.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid or missing printer ID.
Action:
Correct the initialization parameter.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid SYSOUT class.
Action:
Correct the initialization parameter.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid destination.
Action:
Correct the initialization parameter.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid forms name.
Action:
Correct the initialization parameter.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid external writer name.
Action:
Correct the initialization parameter.
Reason:
An invalid external print interface is found in the master control record. Only types JESDS and PGM are valid.
Action:
Run SARINIT to correct the external print initialization parameters.
Reason:
Dynamic allocation failed for the JESDS data set. The hexadecimal error and information codes are provided.
Action:
Run SARINIT to correct the external print initialization parameters.
Reason:
Too many distribution identifiers, special instructions, or both are contained in the CA Deliver external print request.
Action:
Reissue the external print request with fewer distribution identifiers, special instructions, or both.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid or missing interface type.
Action:
Correct the initialization parameter.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid or missing program name.
Action:
Correct the initialization parameter.
Reason:
The SARINIT initialization parameter xxxxxxxx contains an invalid program parameter.
Action:
Correct the initialization parameter.
Reason:
The external print interface was unable to load program xxxxxxxx.
Action:
Correct the program name in the corresponding external print initialization parameter. If it is already correct, supply the STEPLIB DD statement for the library that contains the program.
Reason:
The requested function code is invalid. This problem is in the coding of the external print interface product.
Action:
Contact the vendor who supplied the external print interface product for a resolution.
Reason:
The requested initialization token is invalid, probably the result of an improper initialization request. This problem is in the coding of the external print interface product.
Action:
Contact the vendor who supplied the external print interface product for a resolution.
Reason:
The requested access token is invalid, probably the result of an improper access request. This problem is in the coding of the external print interface product.
Action:
Contact the vendor who supplied the external print interface product for a resolution.
Reason:
The external print record is invalid. This problem is in the coding of the external print interface product.
Action:
Contact the vendor that supplied the external print interface product and have them correct the error.
Reason:
The program load modules and the database are not at the same release level. CA View does not execute.
Action:
Correct the problem and retry.
Reason:
The group control record for the archived SYSOUT cannot be found in the database. A user deleting the SYSOUT GROUP between the time it was queued for external printing and the time that the external print actually occurs usually causes this issue.
Action:
None. The SYSOUT group is no longer available.
Reason:
A page range, record range, or both are specified for an external print of a page selection request for a SYSOUT group.
Action:
Resubmit the external print request omitting the page range, record range, or both.
Reason:
The page selection text specification requires a valid logical view.
Action:
Resubmit the external print request with a valid logical view.
Reason:
The SYSOUT group does not currently reside on DISK and its page selection is not available.
Action:
Reload the SYSOUT group to disk and then resubmit the external print request.
Reason:
The SYSOUT group that is requested for the external print cannot be found on any backup tape.
Action:
None. The SYSOUT group is not available on tape.
Reason:
The SYSOUT group that is located on the backup tape for external printing is not the SYSOUT as referenced in the master index.
Action:
Use the SARTCP utility to map and correct the backup tape.
Reason:
The backup tape cannot be found in the master index. This is usually caused by the backup cycle deleting the tape before completion of the load request.
Action:
None. The SYSOUT group is no longer available.
Reason:
Dynamic allocation failed for allocating the backup tape file. The hexadecimal error and information codes are provided.
Action:
Consult the online retrieval HELP facility for a description of the dynamic allocation error code. Take appropriate action to correct the allocation error, and then resubmit the print request.
Reason:
A permanent I/O error occurred attempting to position the archival tape to retrieve the SYSOUT group for external printing.
Action:
Resubmit the request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape.
Reason:
A permanent I/O error occurred attempting to read SYSOUT data from a backup tape.
Action:
Resubmit the request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape.
Note: For more information about recovery methods, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified view does not exist in the master index.
Action:
Verify the existence of the view. If the view number was specified incorrectly, change the parameter specification, and then resubmit the external print request.
Reason:
The external print request specifying the SELECT keyword has failed because no views exist for the SYSOUT.
Action:
Do one of the following actions:
Page indexing occurs only during archival.
Reason:
The external print request specifying the SELECT keyword has failed because an I/O error occurred while opening or reading the page index data from the database. The data is unreadable.
Action:
Do one of the following actions:
Note: The index can be rebuilt only by re-archiving the SYSOUT.
Reason:
The external print request specifying the SELECT keyword has failed because indexing has not been established for the view.
Action:
Establish indexing criteria for the view if it does not exist. Re-archive the SYSOUT. Page indexing occurs only during archival.
Reason:
The external print request specifying the SELECT keyword has failed because the SELECT text ID did not match any index selection.
Action:
Check that the SELECT text and index selection criteria are as intended. Re-archive the SYSOUT if the page indexing criteria is changed. Page indexing occurs only during archival.
Reason:
SARSTC issues this message when a non-zero return code is returned by SARPRTUX.
Action:
This message is informational, no action is required.
Reason:
An internal request is made to position to an invalid record in the report index file.
Action:
The database record for the report contains an invalid starting position for the extracted report index data. This condition is due to database corruption. The positioning information can be reestablished by re-indexing the report.
Reason:
An I/O error occurred while attempting to read index data for the referenced report.
Action:
The I/O error can be corrected by re-indexing the report. If problems persist, restore the database.
Reason:
The identified report is not accessible through the expanded access server, or online viewing of the report is not allowed due to the specification of the VIEWTAPE=NO ERO parameter.
Action:
If the report is accessible through the expanded access server, make the SAREAS task is active. Otherwise, load the report into the database.
Reason:
An I/O error occurred while attempting to read index data for the referenced report.
Action:
The I/O error can be corrected by re‑indexing the report. If problems persist, restore the database.
Reason:
An I/O error occurred while attempting to read index data for the referenced report.
Action:
The I/O error can be corrected by re‑indexing the report. If problems persist, restore the database.
Reason:
The report that you have requested needs a resource to display correctly. This resource cannot be found on the database. (ACIF and Xerox reports have resources.)
Action:
Reload report from tape.
Reason:
The report that you have requested needs a resource to display correctly. This resource cannot be found on the database. (ACIF and Xerox reports have resources.)
Action:
Reload report from tape.
Reason:
An internal request is made to position to an invalid record in the report.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal request is made to position to an invalid page in the report.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The connect request from the FSA to JES failed; the return and reason codes are provided.
Action:
The FSA is terminated.
Reason:
The disconnect request from the FSA to JES failed; the return and reason codes are provided.
Action:
The FSA is terminated.
Reason:
A send request from the FSA to JES failed; the return and reason codes are provided.
Action:
The FSA is terminated.
Reason:
A get data set request from the FSA to JES failed; the return and reason codes are provided.
Action:
The FSA is abnormally terminated.
Reason:
A release data set request from the FSA to JES failed; the return and reason codes are provided.
Action:
The FSA is abnormally terminated.
Reason:
A get record request from the FSA to JES failed; the return and reason codes are provided.
Action:
The FSA is abnormally terminated.
Reason:
A permanent I/O error occurred attempting to get a record from JES.
Action:
Processing for the data set is ended, and execution continues.
Reason:
A logical I/O error occurred attempting to get a record from JES.
Action:
Processing for the data set is ended, and execution continues.
Reason:
An attempt to open the input parameter file for the device failed.
Action:
The FSA is terminated.
Reason:
The first control statement in the input parameter file for the device must be a TYPE= statement.
Action:
The FSA is terminated. Add the TYPE= control statement.
Reason:
An invalid data collector name is specified on the TYPE= statement in the input parameter file for the device.
Action:
The FSA is terminated. Correct the TYPE= control statement.
Reason:
The load module is not found for the FSA.
Action:
The FSA is terminated. Verify that the correct step/job libraries are specified in the FSS startup procedure.
Reason:
An error occurred attempting to retrieve the OUTPUT statements for a data set.
Action:
The data set is placed on hold and not processed.
Reason:
A copy of the input parameter statement is logged.
Action:
None. This is an informational message.
Reason:
The identified report is not accessible through the expanded access server, or online viewing of the report is not allowed due to the specification of the VIEWTAPE=NO ERO parameter.
Action:
If the report is accessible through the expanded access server, make the SAREAS task is active. Otherwise, load the report into the database.
Reason:
An attempt has been made to start the FSS directly with a START operator command, bypassing JES.
Action:
Use the appropriate JES command to start the FSS.
Reason:
An invalid start command is issued for the FSS.
Action:
Use the appropriate JES command to start the FSS.
Reason:
The connect request from the FSS to JES failed.
Action:
Take the appropriate action, based on the return and reason codes provided.
Reason:
The disconnect request from the FSS to JES failed; the return and reason codes are provided.
Action:
Take the appropriate action, based on the return and reason codes provided.
Reason:
A keyword is misspelled in the //PRTnnn statement.
Action:
Correct the keyword, and then resubmit the job.
Reason:
A keyword is assigned an invalid value.
Action:
Correct the keyword, and then resubmit the job.
Reason:
The database name that is specified as the NAME statement was not found.
Action:
Correct the name, and then resubmit the job.
Reason:
Either the index member name is misspelled, or it does not exist.
Action:
Correct the name, and then resubmit the job.
Reason:
A media problem exists.
Action:
Verify that the volume is online and functioning properly.
Reason:
The database is not at the appropriate level.
Action:
Verify that your database level (set with the SARDBASE utility) is correct, and then rerun SARDBASE if necessary.
Reason:
A keyword is misspelled in a SARINDEX member‑name group parameter control statement.
Action:
Correct the keyword, and then resubmit the job.
Reason:
A SARACT DD statement was present in the job stream, but the data set failed to open successfully.
Action:
Verify that the data set is correct, or remove the DD statement to disable accounting.
Reason:
The data set specified by the SARACT DD statement has an invalid logical record length, an invalid block size, or is not a CA View accounting file.
Action:
Verify that the data set is correct, or remove the DD statement to disable accounting.
Reason:
This is an informational message.
Action:
None.
Reason:
The SYSOUT line count exceeds the MAXLINES initialization parameter value of the database.
Action:
None. This message is informational.
Reason:
There is not enough space in the database to perform the archival.
Action:
Reply with either an R to reattempt archival or a T to terminate:
1. Run the SARDBASE program to add more space to the database, or manually delete SYSOUT groups to free up space while the archival task waits. After you make more space available, reply R to have the archival task retry its archival with the additional space.
2. Reply T to terminate the archival task.
This message number represents one of the following:
Reason:
Each unique report id can have up to 65,535 copies per database generation. A 'generation' being the time between Full Backup Cycles. Each unique report id in a generation is assigned sequential numbers from 1 to 65,535. After 65,535, the sequence number will wrap back to zero and date selection problems will occur. This message gives a chance to the user to run a backup cycle so this number can be reset to one.
The second format of SARFVC25 is displayed if a response other than 'R' or 'T' is given to the original message.
Action:
Reply with either an R after a backup cycle has been started or a T to terminate. The SARFVC25 message can be reissued after replying T and re-starting the View FSS Collector.
Reason:
The View Collector user exit (SARFVCUX) requested the display of a message with the specified text.
Action:
This depends on the site's requirements for the message.
Reason:
The program load modules and the database are not at the same version level. This is normally caused by the STEPLIB, JOBLIB, linklist, or LPA pointing to old load modules, or the database has not been converted to the correct version level (new versions of the product can require conversion of the database).
Action:
You can either STEPLIB to the correct load modules or convert the database to the correct release level.
Reason:
During CA Deliver bundle or rerun processing SARGAM failed to open or read the auxiliary file for a dynamic report.
Action:
Review your CA Deliver Dynamic Report definitions.
Reason:
Your print request exceeded the maximum number of lines that are permitted during a batch or on-line print request. The reprint line limit could have been defined in the VTAM Printer Device Definition, the CA Spool Device Definition, or the OUTLIM Initialization Parameter. This message appears at the end of the report which was being printed and the reminder of the report is truncated.
Action:
Do one of the following actions:
Reason:
Your print request exceeded the maximum number of lines that are permitted during CA Spool print processing. This message can also occur on non-VTAM printers simultaneously.
Action:
Do one of the following actions:
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
User does not have access to the requested report.
Action:
Check with your Security Administrator.
Reason:
The distribution ID referenced in the CA View user profile is not defined or has no reports that are defined to it. For EXP mode users, the DISTID and applicable reports are defined in CA Deliver. For SAR mode users, the DISTID and applicable reports are defined in CA View.
Action:
To produce lists of reports for the user, define the reports to the associated DISTID with CA Deliver (for EXP mode users) or CA View (for SAR mode users).
Reason:
The library containing the RMOGAM module is not defined to the DRAS task or is not accessible.
Action:
Add the CA Deliver load library to the STEPLIB or JOBLIB concatenation for the DRAS job or started task. Or, add the CA Deliver load library to the linklist.
|
Copyright © 2013 CA.
All rights reserved.
|
|