Reason:
A database function attempted to access a Sysout which is created with encryption enabled (initialization parameter ENCRYPT set to ICSF) under r11.6 or higher and cannot be processed by CA View r11.5.
Action:
The database must be versioned back to r11.6 or higher, the database must be copied (SARDBASE/COPY) with the initialization parameter ENCRYPT set to NO. Then version the database back to r11.5.
Reason:
A database read function is executed for a database Master Control Record (MCR) and the record is not found in the database.
Identifies the high-level prefix of the database.
Run the initialization utility (SARINIT) to format and add a Master Control Record (MCR) to the database.
Reason:
An I/O error occurred while allocating space on the specified data set. The allocation is attempted on the next data set in the database.
Action:
Probably none; however, verify that the database has no major problem.
Reason:
An I/O error occurred writing a block to the database. The block is marked in error and the data in the block is rewritten to a different location in the database.
Action:
Probably none; however, verify that the database has no major problem.
Reason:
The database has exceeded maximum threshold of utilization; the actual percentage that is used is given.
Action:
None; however, the database must be monitored to see that it does not run out of space. It may be necessary to add more space to the database. Changing the DBTHRESH initialization parameter can alter the maximum threshold setting.
Reason:
A Dynamic De-allocation request is made by CA View to detach its connection to the database. But, the database is still in use by some other function that is associated with the task. This can occur during termination of CA View utilities if the site defines that job to be captured by CA Deliver Pre‑spool, Direct-to-View.
Action:
Save all of the documentation that is associated with the job and notify CA Technical Support.
Note: This message ID represents one of these messages.
Reason:
The specified job cannot obtain an exclusive lock on the lock data set to update data in the specified database. The message is issued in one‑minute intervals until the lock is resolved.
Action:
If the lock is held by a user or job that is no longer executing due to an abend or cancellation, use the UNLOCK control statement of the SARDBASE utility to release the lock. Otherwise, the lock is obtained when available.
Reason:
The specified online library member is being loaded to the database.
Action:
None. This is an informational message.
Reason:
No panels are found in the input OLIB data set.
Action:
Verify that your CA View OLIB data set is correctly named in the STEPLIB, and that it contains panels.
Reason:
An OLOAD control statement is issued to load online members into the CA View database, but the SAROLIB DD statement was not specified. The SAROLIB DD statement references the library containing the online members and is required for the load request.
Action:
Add the SAROLIB DD statement referencing the library containing the online members, and then resubmit the load request.
Reason:
CA View cannot write to the secondary disk.
Action:
Verify your DSK2PARM initialization parameter.
Reason:
The database being copied to has an error.
Action:
Verify that the database has enough allocation (you can increase the allocation with SARDBASE ADDDS) and that the DASD is available to the system.
Reason:
CA View found the end of the SARLOAD file before the database was fully loaded.
Action:
Verify that the SARLOAD data set is complete.
Reason:
The unload file that is referenced by the SARLOAD DD statement contains records that are not consistent with this release of the product.
Action:
Recreate the unload file, recreate the new database, and resubmit the LOAD or MERGE request.
Reason:
An external sort is used to sequence alternate index records for date selection before writing the records to the database. The sort phase ended with the specified nonzero return code resulting in the loss of all or some of the alternate index records.
Action:
The nonzero return code from the sort phase can be caused by a critical error as indicated by a previous message or a sort error as indicated in the sort message data set (SYSOUT). Review the messages to determine the appropriate action. Recreate the new database and resubmit the LOAD or MERGE request.
Reason:
The SARLOAD or SARMERGn DD statement is required for the SARDBASE utility LOAD or MERGE control statement to load or merge the database.
Action:
Add the SARLOAD or SARMERGn DD statement to the JCL, then rerun the job.
Reason:
The SARDBASE utility LOAD or MERGE function was unable to open the SARLOAD or SARMERGn DD statement. The job log must contain messages identifying the error.
Action:
Correct the error and rerun the job.
|
Copyright © 2013 CA.
All rights reserved.
|
|