IN25UTIL Program Messages › UTIL001—UTIL103

UTIL001—UTIL103

UTIL001

X....X

Reason:

This message is an echo of the input request. The request is indicated by X....X.

Action:

None.

UTIL002

INITIALIZATION COMPLETED

Reason:

The CA InterTest for CICS Symbolic File has been initialized.

Action:

None.

UTIL003

XXXXXXXX DELETED FROM SYMBOLIC FILE

Reason:

Program XXXXXXXX was deleted from the CA InterTest for CICS Symbolic File.

Action:

None.

UTIL004

XXXXXXXX UNLOADED FROM SYMBOLIC FILE

Reason:

Program XXXXXXXX has been unloaded from the CA InterTest for CICS Symbolic File.

Action:

None.

UTIL005

XXXXXXXX RELOADED TO SYMBOLIC FILE

Reason:

Program XXXXXXXX was reloaded to the CA InterTest for CICS Symbolic File.

Action:

None.

UTIL006

XXXXXXXX RELOADED TO SYMBOLIC FILE AND HAS BEEN RENAMED TO YYYYYYYY

Reason:

Program XXXXXXXX was reloaded to the CA InterTest for CICS Symbolic File with the name YYYYYYYY.

Action:

None.

UTIL007

UNLOAD PROCESSING COMPLETED

Reason:

The UNLOAD function completed.

Action:

None.

UTIL008

RELOAD PROCESSING COMPLETED

Reason:

The RELOAD function completed.

Action:

None.

UTIL009

PURGE PROCESSING COMPLETED — XXXXX RECORDS HAVE BEEN FREED

Reason:

The PURGE function completed and freed up the number of records indicated by XXXXX.

Action:

None.

UTIL010

DEVICE NOW CLOSED

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.

UTIL011

INTERTEST BATCH UTILITY RUN COMPLETED SUCCESSFULLY

Reason:

All requested functions have been performed and the CA InterTest for CICS Symbolic File was updated successfully.

Action:

None.

UTIL012

RELOAD PROCESSING STARTED FOR PROGRAM XXXXXXXX

Reason:

The RELOAD function began for program XXXXXXXX.

Action:

None.

UTIL047

XXXXXXXX MUST BE DELETED

Reason:

While processing program XXXXXXXX, a condition occurred that indicated that data for the program was corrupted.

Action:

Delete this program.

UTIL048

XXXXXXXX CANNOT BE UNLOADED

Reason:

Program XXXXXXXX was found to be corrupted and therefore could not be unloaded.

Action:

None.

UTIL049

XXXXXXXX HAS ZERO RECORDS — ENTRY BYPASSED

Reason:

Program XXXXXXXX was found to be corrupted.

Action:

Complete the following steps:

1. Delete the program from the Symbolic file.
2. Run an UNLOAD=ALL UTILity request.
3. Initialize the Symbolic file.
4. Run a RELOAD=ALL UTILity request, using the file created in step 2 as input.

UTIL050

PASSWORD MISSING — REQUEST IGNORED

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.

UTIL051

PASSWORD INCORRECT

Reason:

The password provided on the PASSWORD= parameter card does not match the password that was generated by the SYMPSWD= option of CA InterTest for CICS. The SYMPSWD= gen option is described in the CA InterTest for CICS Installation Guide. 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.

UTIL052

INVALID REQUEST

Reason:

The function requested is not valid. This condition may be caused by a misspelled option or just bad input. The job is terminated.

Action:

Correct the requested function and resubmit the entire job stream.

UTIL053

XXXXXXXX CANNOT FIT ON FILE — PROGRAM IS BYPASSED

Reason:

The CA InterTest for CICS 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:

1. Using the UTILITY job, run an UNLOAD=ALL request.
2. Delete the CA InterTest for CICS Symbolic File using IDCAMS.
3. Run an IDCAMS DEFINE for the CA InterTest for CICS Symbolic File with a larger space allocation. Remember that a secondary space allocation is not permitted.
4. Using the UTILITY job, run an INITIALIZE request.
5. Using the UTILITY job, run a RELOAD=ALL request, using the file created in Step 1 as input.
6. Resubmit the original job.

Or:

1. Using the UTILITY job, run a PURGE= request to free up space.
2. Resubmit the original job.

UTIL054

PURGE INTERVAL INVALID OR MISSING — REQUEST NOT PROCESSED

Reason:

The PURGE= request either 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.

UTIL055

PROGRAM NOT FOUND IN FILE OR WAS NOT USABLE

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.

UTIL056

PROGRAM NAME IS GREATER THAN 8 CHARACTERS LONG — REQUEST IGNORED

Reason:

The program specified for a requested function contained more than 8 characters. This request is ignored.

Action:

Correct the requested function and resubmit the job.

UTIL057

SYMBOLIC FILE IS EMPTY — PLEASE RUN INITIALIZATION AS FIRST STEP

Reason:

The Symbolic File did not contain the required control records. The job is terminated.

Action:

Using the UTILITY job, run an INITIALIZE request.

UTIL058

VSAM RECORD LENGTH NOT = 2040

Reason:

The Symbolic File was created with a wrong record size. The job is terminated.

Action:

Follow the instructions in the CA InterTest for CICS Installation Guide for the creation of the CA InterTest for CICS Symbolic File.

UTIL059

NO LISTER INFORMATION FOR THIS PROGRAM — PRINT= REQUEST IGNORED

Reason:

The program specified by the PRINT= request did not contain any saved source. This request is ignored.

Action:

None.

UTIL060

REQUEST FOR VIRTUAL STORAGE FAILED

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.

UTIL061

OPEN FAILURE FOR UNLOAD DEVICE

Reason:

The open request for the device to be used for an UNLOAD= function failed.

Action:

Correct the JCL and resubmit the job.

UTIL062

OPEN FAILURE FOR RELOAD DEVICE

Reason:

The open request for the device to be used for a RELOAD= function failed.

Action:

Correct the JCL and resubmit the job.

UTIL063

UNLOAD=ALL HAS BEEN RUN — ALL OTHER UNLOAD REQUESTS ARE IGNORED

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.

UTIL064

INPUT FROM RELOAD FILE IS INVALID

Reason:

Data being retrieved for a RELOAD= request was not in the correct format. This condition may be caused by incorrect JCL or by data that was overlaid since its creation by the UNLOAD= request. This request is ignored.

Action:

If a bad JCL caused the error, correct the JCL and resubmit the request. If bad data caused the error, the problem is not correctable.

UTIL065

RELOAD FILE IS EMPTY

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 a bad JCL caused the error, correct the JCL and resubmit the request; otherwise, the problem is not correctable.

UTIL066

XXXXXXXX ALREADY EXISTS IN FILE: RELOAD FOR THIS PROGRAM IGNORED

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.

UTIL067

xxxxxxx yyyy ERROR R15 = X'rr' ERROR CODE = X'ee'

Reason:

The VSAM error has occurred while running the UTILITY program. The message contains the following information:

• xxxxxxx is the name of the CA InterTest for CICS Symbolic File
• yyyy is the type of request (OPEN, GET, or PUT)
• rr is the return code, in hexadecimal
• ee is the error code, in hexadecimal

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 manual that contains the error messages. Handle the error as described in your manual.

UTIL068

SEQUENCE NUMBER NOT FOUND

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.

UTIL070

RECORD COUNT ERROR AT ENDREQ

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 CA technical support.

UTIL071

UNLOAD OR RELOAD NOT SPECIFIED

Reason:

A CLOSE= request has been made but did not specify UNLOAD or RELOAD. The job is terminated.

Action:

Correct the CLOSE= request and resubmit the entire job stream.

UTIL072

ERROR OCCURRED WHILE READING RELOAD DEVICE (DOS)

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.

UTIL073

ERROR OCCURRED WHILE WRITING TO UNLOAD DEVICE (DOS)

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.

UTIL074

ERROR OCCURRED WHILE READING PARAMETER CARDS (DOS)

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.

UTIL075

ENQ ERROR: CODE = X'yy' (DOS)

Reason:

An error occurred while issuing a SVC 63 (lock) request. The job is terminated.

Action:

For assistance, contact CA technical support.

UTIL076

REQUESTED DATA SPACE EXCEEDS MAXIMUM FOR FILE

Reason:

The CA InterTest for CICS Symbolic File has been defined with a size that exceeds its capacity. The maximum size of this file is about 4,000,000 2K records. The job is terminated.

Action:

This error would normally be caused by defining the file with a secondary space allocation. If this is the case, then redefine the file without a secondary allocation and then initialize it.

UTIL077

BATCH UTILITY RUN UNSUCCESSFUL — ALL UPDATES HAVE BEEN BACKED‑OUT

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, the entire job stream must be resubmitted.

UTIL079

PROGRAM NOT FOUND IN RELOAD FILE — REQUEST IGNORED

Reason:

The program specified by a RELOAD= request was not found in the reload file.

Action:

None.

UTIL080

VSAM CI SIZE NOT = 2048

Reason:

The Symbolic File was created with the wrong CI size.

Action:

Recreate the Symbolic File with the correct CI size.

UTIL101

INVALID RECORD ON FILE. UNLOAD AND RELOAD OF FILE RECOMMENDED

Reason:

An invalid DATE/TIME field is found in a Program Master Index Record.

Action:

Unload and Reload of the PROTSYM file is recommended.

UTIL102

x22 CANCEL, ABEND PERCOLATED

Reason:

A system cancel event occurred while IN25UTIL was executing.

Action:

Capture the dump if needed.

UTIL103

RECOVERY FAILURE, S0C1 GENERATED

Reason:

A VSAM request failed.

Action:

Capture and save the S0C1 dump and contact CA technical support for assistance.