CA InterTest for CICS Online Help Messages › CAIN1701—CAIN2000

CAIN1701—CAIN2000

CAIN1701

ENTER THE SQL COMMAND TO BE EXECUTED.

Reason:

Instructional message.

Action:

Enter the SQL command to be executed on the FILE screen. Refer to the CA InterTest for CICS User Guide for a list of valid commands.

CAIN1702

(*) INVALID SQLTYPE.

Reason:

The SQL type that you entered was invalid.

Action:

Refer to the CA InterTest for CICS User Guide for a list of valid SQL types and commands.

CAIN1703

LOC MUST BE NUMERIC FROM 1 ‑ 9999

Reason:

You entered a character other than 1 to 99999, which is not considered numeric.

Action:

Specify data in hexadecimal format (for example X'F1F2F3') or as data without quotes (for example, 1234).

CAIN1704

(*) EXECUTED SUCCESSFULLY.

Reason:

The command you specified executed successfully.

Action:

None.

CAIN1705

(*) COMMAND NOT SUPPORTED.

Reason:

The command that you entered is not supported by CA InterTest for CICS.

Action:

Refer to the CA InterTest for CICS User Guide for a list of valid commands.

CAIN1706

NO SAVED COMMANDS.

Reason:

You either did not specify a valid save command, or you cleared the screen and did not save your commands.

Action:

Enter the correct save command.

CAIN1707

TRANSMIT ERROR.

Reason:

When you pressed ENTER or one of the PF keys, it did not take effect.

Action:

Press the proper PF key.

CAIN1708

MODIFY COMMAND OR PRESS ENTER TO EXECUTE.

Reason:

Instructional message.

Action:

Modify the command or press ENTER to execute it.

CAIN1709

(*) ROWS SELECTED.

Reason:

The rows that you specified were selected.

Action:

None.

CAIN1710

NO ROWS SELECTED

Reason:

The number of rows you specified was not selected.

Action:

Re‑enter the number of rows.

CAIN1711

SQL/DS NOT ACTIVE.

Reason:

A DB2 request received an "AEYA" abend, which usually means SQL/DS is not active.

Action:

Ensure that SQL/DS is correctly defined in your CICS region.

CAIN1712

DSNC NOT ACTIVE OR DB2 NOT AVAILABLE.

Reason:

A DB2 request received an "AEYA" abend, which usually means DB2 is not active.

Action:

Ensure that SQL/DS is correctly defined in your CICS region.

CAIN1714

ENTER C TO COMMIT, R TO ROLLBACK.

Reason:

You must commit your previous changes or roll them back.

Action:

Enter C or R.

CAIN1713

(*) ABEND HAS OCCURRED.

Reason:

A DB2 request received a CICS abend other than "AEYA".

Action:

Refer to your CICS MESSAGES and CODES manual.

CAIN1715

ERROR HAS OCCURRED

Reason:

A CICS transient data write error has occurred. The EIBRCODE field identifies the error code, which can be found in your CICS Application Programming Reference book.

Action:

Correct the error, and resubmit the request.

CAIN1716

ENTER X TO RE‑EXECUTE OR M TO MODIFY A COMMAND

Reason:

Informational message.

Action:

None.

CAIN1717

(*) RECORDS INSERTED

Reason:

During the FILE transaction, you added the number of records indicated in the message.

Action:

None.

CAIN1718

(*) RECORDS DELETED

Reason:

The DEL function executed successfully.

Action:

None.

CAIN1719

(*) RECORDS UPDATED

Reason:

You have successfully updated the number of records indicated in the message.

Action:

None.

CAIN1720

DATA TABLE ROW > 65K

Reason:

The Data Table Row is greater than 65K.

Action:

Examine your program; reduce the Data Table Row to less than 65K.

CAIN1901

(*) FUNCTION IS NOT AVAILABLE ON THIS TERMINAL.

Reason:

On this type of terminal, the function you specified is invalid.

Action:

See the CA InterTest for CICS Installation Guide for a list of valid functions for your terminal.

CAIN1902

(*) FUNCTION TERMINATED.

Reason:

A Clear or PF3 key was entered, and the HELP transaction was terminated.

Action:

None.

CAIN1903

(*) FUNCTION ‑ VSAM ERROR ON CA InterTest HELP FILE

Reason:

A VSAM error occurred on the Help File.

Action:

Contact the systems programmer. Determine the problem with the file.

CAIN1904

(*) FUNCTION ‑ END OF FILE.

Reason:

While you were browsing a file, an end of file condition occurred.

Action:

Either enter 'PREV' or a previous code, or browse using a different key, or end this file function.

CAIN1905

(*) FUNCTION ‑ INCORRECT FCT ENTRY FOR CA InterTest HELP FILE.

Reason:

The HELP file was incorrectly defined to your system.

Action:

Contact the system programmer.

CAIN1906

(*) FUNCTION ‑ HELP FILE COULD NOT BE OPENED.

Reason:

Information about the requested function could not be obtained, because the Help File could not be opened.

Action:

Ensure that the Help File is properly defined to the region and is not disabled.

CAIN1908

(*) FUNCTION ‑ HELP FILE IS NOT OPEN.

Reason:

Information on the requested function could not be obtained because the Help File is not open.

Action:

Open the Help File and re‑enter your request.

CAIN1909

(*) FUNCTION ‑ HELP FILE INCOMPLETE.

Reason:

Information on the requested function could not be obtained because the Help File cannot be accessed.

Action:

Check the status of the Help File to ensure that it is enabled. Re‑run the IDCAMS repro to recreate the Help File, if necessary.

CAIN1910

(*) FUNCTION ‑ NO MAIN STORAGE AVAILABLE.

Reason:

There is not enough space available in main storage to complete your request.

Action:

When storage becomes available, re‑enter your request.

CAIN1911

INVALID TRANSACTION

Reason:

The transaction that you entered was not a valid CA InterTest for CICS transaction.

Action:

Correct your error and re‑enter the proper transaction code.

CAIN1912

INTERTEST RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)

Reason:

The version of CA InterTest for CICS that you are running is not supported by the installed version of CICS.

Action:

Install the correct version of CA InterTest for CICS.

CAIN1913

NOTAUTH CONDITION ‑ RESOURCE LEVEL SECURITY FAILED FOR "(*)"

Reason:

The resource that you named failed the resource level security check.

Action:

Determine the reason for the failure, and change the security parameters if necessary.