Previous Topic

Next Topic

Book Contents

Book Index

Messages KSLA00 through KSLAxx

This group includes messages for the IOA (infrastructure) product.

KSLA60I EXCEPTIONAL CONDITION RC=rc, ERROR=err, FEEDBACK=feedback, APPLID= applId

Explanation: This information message indicates that an exceptional VTAM condition was encountered during the execution of a KOA communication command.

This informational message is issued by the KOA Facility. Return code, error and feedback information are detailed in the KeyStroke Language (KSL) User Guide.

The KOA script continues processing. If an ON SCREENERROR statement was specified, the processing resumes at the label specified in the ON statement.

Corrective Action: Analyze the specific VTAM error, and take the corresponding corrective actions. Make sure that the error is handled correctly by the KOA script.

KSLA61E SCREEN COMMAND EXECUTED WITH NO SCREEN AVAILABLE

Explanation: A screen command was executed; however, no screen was available to the KOA script.

Either a screen command was executed before a KOA session was established by means of a LOGON command, or the KOA session was lost due to communication errors.

The KOA script is terminated.

Corrective Action: Check previous error messages. If necessary, correct the error handling inside the KOA script.

KSLA62E CONTROL-O IS NOT ACTIVE. GLOBAL VARIABLES CANNOT BE USED

Explanation: A SETOGLB KOA statement was executed while the Control-O monitor was not active.

Control-O Global variables may be set by a KOA script only while Control-O is active.

The KOA script is terminated.

Corrective Action: Correct the KOA script, or start the Control-O monitor.

KSLA63E SPECIFIED SESSION ID IS NOT ACTIVE

Explanation: A SETSESS KOA statement specified the ID of a session which is not active.

Either the session was not established through a LOGON command, or the session was lost due to communication errors.

The KOA script is terminated.

Corrective Action: Check for previous error messages. Correct the KOA script accordingly, and resubmit.

KSLA64E KEYSTROKE UTILITY DETECTED INTERNAL ABEND abCode

Explanation: An internal abend was intercepted by the KeyStroke utility.

The KSL/KOA script is terminated.

Corrective Action: Check the associated error messages. Correct the KOA script accordingly, and resubmit.

KSLA65E ALLOC OF DDNAME ddName FAILED, RC = rc, ERROR= err, DSN= dsn

Explanation: An ALLOC statement failed due to a dynamic allocation error.

The KSL/KOA script is terminated.

Corrective Action: Check the return code and error information. Correct the KSL/KOA script accordingly, and resubmit.

KSLA66E FREE OF DDNAME ddName FAILED

Explanation: A FREE statement failed due to a dynamic deallocation error.

The KSL/KOA script is terminated.

Corrective Action: Correct the KSL/KOA script accordingly, and resubmit.

KSLA67E OPEN OF DDNAME ddName FAILED

Explanation: An OPENFILE statement failed.

The KSL/KOA script is terminated.

Corrective Action: Check the preceding KSL or MVS error messages. Correct the KSL/KOA script accordingly, and resubmit.

KSLA68E CLOSE OF DDNAME ddName FAILED

Explanation: A CLOSEFILE statement failed.

The KSL/KOA script is terminated.

Corrective Action: Check the preceding KSL or MVS error messages. Correct the KSL/KOA script accordingly, and resubmit.

KSLA69E I/O ERROR WHEN READING FROM DDNAME ddName

Explanation: A GETFILE statement failed due to an I/O error.

The KSL/KOA script is terminated.

Corrective Action: Check the preceding KSL or MVS error messages. If necessary, check that the DCB characteristics of the file are correct. Correct the KSL/KOA script accordingly, and resubmit.

KSLA6AE I/O ERROR WHEN WRITING TO DDNAME ddName

Explanation: A PUTFILE statement failed due to an I/O error.

The KSL/KOA script is terminated.

Corrective Action: Check the DCB characteristics of the file. Make sure it is a fixed length record data set. Correct the KSL/KOA script accordingly, and resubmit.

KSLA6BE UNSUPPORTED DCB CHARACTERISTICS FOR DDNAME ddName

Explanation: The KeyStroke utility handles only fixed length record data sets. An OPENFILE statement failed because the record format of the specified data set is not fixed or the record length exceeds 150 characters.

The KSL/KOA script is terminated.

Corrective Action: Check the DCB characteristics of the file. Make sure the file is a fixed length record data set with a record length that does not exceed 150 characters. Correct the KSL/KOA script accordingly and resubmit.

KSLA6CE ENQ ERR RC= rc, Q= queueName, R= resourceName

Explanation: The execution of the KSL OPEN statement issued an Enqueue request which failed.

The request is terminated.

Corrective Action: Check the return code of the Enqueue failure and proceed accordingly.

KSLA6DE RSV ERR RC= rc, Q= queueName, R= resourceName

Explanation: The execution of the KSL OPEN statement issued a Reserve request which failed.

The request is terminated.

Corrective Action: Check the return code of the Reserve failure and proceed accordingly.

KSLA6EE DDNAME ddName NOT FOUND

Explanation: Control-O was unable to locate the specified data set while executing an OPENFILE request.

The OPENFILE request fails.

Corrective Action: Check why ddName is not allocated. Correct the KOA/KSL script or the JCL, and rerun.

KSLA6FE SETOLOC/SETOGLB ERROR CODE = rc REASON = rsn, TEXT=AutoEdit_expression

Explanation: An error was detected while trying to resolve a SETOGLB or SETOLOC KSL/KOA statement.

The KSL/KOA program is terminated.

Corrective Action:

  1. Ensure that the AutoEdit expression in the SETOLOC or SETOGLB statement is correctly written.
  2. For an explanation of the return code and reason code included in this message, see the table in the explanation of message WTO283E.

KSLA70E THERE IS AN ERROR IN IOAKPRM MEMBER. PLEASE CHECK THE SMFID FIELD.

Explanation: The SMFID of the CPU to which the KSL job was submitted does not appear in the IOAKPRM member in the IOA PARM library.

The KSL stops running.

Corrective Action: Add the SMFID by making the appropriate entry in the IOAKPRM member. The best way of doing this is by means of the INCONTROL Installation and Customization Engine (ICE). For more information on ICE, see the ICE chapter in the INCONTROL for z/OS Installation Guide.

Parent Topic

KSL messages