Pathway/iTS Web Client Programming Manual (G06.24+)

Client Error Messages
Compaq NonStop Pathway/iTS Web Client Programming Manual—520270-001
A-4
Message Descriptions
3020
Cause. The program unit specified in a CALL statement was not found in the
TCLPROG files.
Effect. The operation fails.
Recovery. Isolate and correct the problem within the Java program, using the stack
trace information in error-loc to locate the problem. Alternatively, correct the
problem in the SCREEN COBOL program and reconvert the application.
3022
Cause. The value passed to the gateway requester program for a SCREEN COBOL
SEND statement did not have the format of a valid server-class name.
Effect. The operation fails.
Recovery. Isolate and correct the problem within the Java program, using the stack
trace information in error-loc to locate the problem. Alternatively, correct the
problem in the SCREEN COBOL program and reconvert the application
3027
Cause. The server-class SEND operation did not match the transaction-mode state.
A SEND operation to a server not using the Transaction Management Facility (TMF)
was attempted while the gateway requester thread was in transaction mode.
Effect. The operation fails.
Recovery. Isolate and correct the problem within the Java program, using the stack
trace information in error-loc to locate the problem. Alternatively, correct the
problem in the SCREEN COBOL program and reconvert the application.
3030
Cause. An attempt to use the Transaction Management Facility (TMF) failed because
TMF auditing was not configured in the host NonStop Himalaya system.
Effect. If the ON ERROR clause of the BEGIN-TRANSACTION statement is present
in the SCREEN COBOL source code—that is, if the onTxnErrorMethod method is
present in the Java code—then the ON ERROR branch is taken. Otherwise, the applet
stops.
*3020* CALLED PROGRAM UNIT NOT FOUND error-loc
*3022* SEND: SERVER CLASS NAME INVALID error-loc
*3027* TRANSACTION MODE VIOLATION error-loc
*3030* TMF NOT CONFIGURED error-loc