ACHA
Explanation
The remote server transaction, CEHS, is not at a compatible level to operate with the CICS/CMS system. This usually indicates that the service levels of CICS/CMS and the remote server are different.
System action
CICS terminates the remote server transaction abnormally with a dump.
User response
If you need further assistance from IBM to resolve this problem, see for guidance on how to proceed.
Problem determination
To diagnose a problem with the remote server, it is generally helpful to obtain a trace of the remote server's activity up to the point of failure.
A remote server trace is obtained by invoking the remote server with the TRACE option, (type CEHS TRACE). The remote server operates as normal but causes entries to be written to a trace log in temporary storage. Note that main storage, not auxiliary, is used for this queue hence large amounts of memory can be used up if this trace is left on for long.
The trace is found in a queue whose name is 'CEHSxxxx', where 'xxxx' is the four-character terminal identifier. The queue can be browsed in text form or in hexadecimal form using CEBR. To find the terminal identifier, invoke CEBR on the terminal that has run CEHS, without giving a queue name. The queue name will default to 'CEBRxxxx', where 'xxxx' is the terminal identifier.
Note: CEBR requires the queue name to be in UPPER CASE.
For a description of the remote server and its trace entries and abend codes, see the (LC33-0438).