|
|
Reason:
This message is an echo of the input request. The request is indicated by x....x.
Action:
None.
Reason:
The symbolic file has been initialized.
Action:
None.
Reason:
Program xxxxxxxx was deleted from the symbolic file.
Action:
None.
Reason:
Program xxxxxxxx has been unloaded from the symbolic file.
Action:
None.
Reason:
Program xxxxxxxx was reloaded to the symbolic file.
Action:
None.
Reason:
Program xxxxxxxx was reloaded to the symbolic file with the name yyyyyyyy.
Action:
None.
Reason:
The UNLOAD function completed.
Action:
None.
Reason:
The RELOAD function completed.
Action:
None.
Reason:
The PURGE function completed and freed up the number of records indicated by xxxxx.
Action:
None.
Reason:
The device, specified by a CLOSE function, closed. Any subsequent requests for this device cause that device to open at load point.
Action:
None.
Reason:
All requested functions have been performed and the symbolic file was updated successfully.
Action:
None.
Reason:
The RELOAD function began for program xxxxxxxx.
Action:
None.
Reason:
While processing program xxxxxxxx, a condition occurred that indicated that data for the program was corrupted.
Action:
Delete this program.
Reason:
Program xxxxxxxx was found to be corrupted and could not be unloaded.
Action:
None.
Reason:
Program xxxxxxxx was found to be corrupted.
Action:
Complete the following steps:
Reason:
The function requested requires a PASSWORD parameter card. Only this request is ignored.
Action:
Add a PASSWORD parameter card as the first parameter card in the job stream and resubmit the job.
Reason:
The password provided on the PASSWORD parameter card does not match the password that was generated by the SYMPSWD parameter in IN25SOPT. The job is terminated.
Action:
Change the password specified by the PASSWORD parameter card to match the generated password and resubmit the entire job stream.
Reason:
The function requested is invalid. This condition may be caused by a misspelled option or invalid input. The job is terminated.
Action:
Correct the requested function and resubmit the entire job stream.
Reason:
The symbolic file did not contain enough free space to handle a RELOAD function for program xxxxxxxx. The program is bypassed.
Action:
Complete the following steps:
Or:
Reason:
The PURGE request did not specify a number of days or the number of days specified was not within the range of 1 through 365. This request is ignored.
Action:
Correct the PURGE request and resubmit the job.
Reason:
The program specified for a requested function was not found in the symbolic file or was unusable. This request is ignored.
Action:
Run a REPORT function. If the program is found, delete it and resubmit the original job.
Reason:
The program specified for a requested function contained more than eight characters. This request is ignored.
Action:
Correct the requested function and resubmit the job.
Reason:
The symbolic file did not contain the required control records. The job is terminated.
Action:
Using the UTILITY job, run an INITIALIZE request.
Reason:
The symbolic file was created with a wrong record size. The job is terminated.
Action:
Follow the instructions in the chapter "Creating a PROTSYM File" for creating a PROTSYM file.
Reason:
The program specified by the PRINT request did not contain any saved source. This request is ignored.
Action:
None.
Reason:
The request for GETMAIN or GETVIS storage failed. The job is terminated.
Action:
Resubmit the entire job stream, using a bigger region size or run the job in a larger partition.
Reason:
The open request for the device to be used for an UNLOAD function failed.
Action:
Correct the JCL and resubmit the job.
Reason:
The open request for the device to be used for a RELOAD function failed.
Action:
Correct the JCL and resubmit the job.
Reason:
An UNLOAD request has been made after an UNLOAD=ALL request. This request is ignored.
Action:
Resubmit the UNLOAD request which was rejected in a separate job stream.
Reason:
Data being retrieved for a RELOAD request was not in the correct format. This condition may be caused by invalid JCL or by data that was overlaid since its creation by the UNLOAD request. This request is ignored.
Action:
If invalid JCL caused the error, correct the JCL and resubmit the request. If invalid data caused the error, the problem is not correctable.
Reason:
An end-of-file condition occurred on the first read from the RELOAD device. This condition occurs when the file is empty. This request is ignored.
Action:
If invalid JCL caused the error, correct the JCL and resubmit the request; otherwise, the problem is not correctable.
Reason:
The program to be reloaded already exists on the file. This request is ignored.
Action:
Delete the program, using a DELETE request, and resubmit the RELOAD request.
Reason:
A VSAM error occurred while running the UTILITY program. The message contains the following information:
The job may or may not be terminated, depending on the function requested and when the error occurred.
Action:
Using the information from the message, find the explanation of the error in the VSAM guide that contains the error messages. Handle the error as described in your guide.
Reason:
While processing a request, an internal record key was not found. This condition indicates a corrupted file.
Action:
Delete the program that caused the problem.
Reason:
An internal check of the file has failed. This condition indicates a corrupted file. The job is terminated with a dump.
Action:
For assistance, contact Technical Support.
Reason:
A CLOSE request was made but did not specify UNLOAD or RELOAD. The job is terminated.
Action:
Correct the CLOSE request and resubmit the entire job stream.
Reason:
The system detected an error condition while reading a record from the device pointed to by SYS005. The job is terminated.
Action:
Determine the cause of the error, correct the problem, and resubmit the entire job stream.
Reason:
The system detected an error condition while writing a record to the device pointed to by SYS005. The job is terminated.
Action:
Determine the cause of the error, correct the problem, and resubmit the entire job stream.
Reason:
The system detected an error condition while reading a control card. The job is terminated.
Action:
Determine the cause of the error, correct the problem, and resubmit the entire job stream.
Reason:
An error occurred while issuing a SVC 63 (lock) request. The job is terminated.
Action:
For assistance, contact Technical Support.
Reason:
The symbolic file has been defined with a size that exceeds its capacity. The maximum size of this file is about 4,000,000 2 KB records. The job is terminated.
Action:
This error is usually caused by defining the file with a secondary space allocation. If this is the case, redefine the file without a secondary allocation and initialize it.
Reason:
This message is produced on any error condition that terminates the job. If this message is produced, all requested functions, even if they were correct, are backed out.
Action:
After the error condition is corrected, you must resubmit the entire job stream.
Reason:
This message is produced when an error condition, which is not serious, has occurred. If this message is produced, only the requests that were in error are ignored and all valid requests were performed.
Action:
Review the output for any previous error messages, resolve those errors, and try again.
Reason:
The program specified by a RELOAD request was not found in the reload file.
Action:
None.
Reason:
The symbolic file was created with the wrong CI size.
Action:
Recreate the symbolic file with the correct CI size.
Reason:
Messages UTIL095 through UTIL099 are produced by the special checkout procedure. This procedure checks for a corrupted symbolic file.
If a corrupted file is found at the start of the job, one of the above messages displays. If a corrupted file is found at the end of the job, one of the above messages displays, an attempt is made to back out all updates, and the IN25UTIL program abends.
Action:
In response to these messages, try the following procedures before contacting CA Technical Support:
At this point, the symbolic file should be repaired. If the problem still exists, Contact Technical Support.
Reason:
You are attempting to use an r5.4 symbolic file with an earlier CA InterTest release. The new, larger symbolic files can only be used with r5.4 and higher; they are not downward compatible with earlier CA InterTest releases.
Action:
For CA InterTest releases prior to r5.4, only use symbolic files created with a pre-5.4 release.
Reason:
An invalid record has been encountered on the PROTSYM during a utility function.
Action:
Reorganize your PROTSYM by doing an UNLOAD=ALL followed by a RELOAD=ALL to remove the bad record.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |