This document contains special considerations that apply when you are using asynchronous Natural under CICS.
The following topics are covered:
Asynchronous Natural processing is generally discussed in the section Asynchronous Processing in the Operations documentation; however, some additional considerations apply when running under CICS. These are described in the following sections.
Make sure that appropriate
destinations are specified for an asynchronous Natural session; otherwise, any
output (for example, unexpected error messages) will lead to an abnormal
||Any output is ignored.|
||Any output is routed to the operator console.|
By default, the 3270 data stream protocol is used for output of an asynchronous Natural session under CICS.
It is also possible to send Natural output data without any 3270
terminal or printer control information to, for example, a CICS message
destination such as CSSL. This can be accomplished by switching into line mode
'T=' statement or by starting with
Natural output is then sent line by line, with a leading ASA control character
when the Natural profile parameter
EJ is set to
EJ=OFF, no control character is sent at
Recent CICS versions offer a transaction CEDX which enables tracing of asynchronous tasks in CICS. In earlier CICS versions, this functionality did not exist, that is, such debugging was only possible with terminal-bound tasks.
The Natural CICS Interface offers some assistance in this case: You
can test asynchronous Natural sessions by starting that session from a
terminal, but either with
ASYN, as the very first five characters
in the dynamic parameter string, or with the profile parameter
ASYL. The Natural CICS Interface then sets up an asynchronous
Please, note that this emulation is only 100 percent in terms of Natural; CICS keeps on treating the task as terminal bound.