<div>
This is done in the application program, not in CICS itself. &nbsp;Pseudoconversational (or non-conversational) mode means that the application transaction returns to CICS after displaying a screen. &nbsp;When the user responds, a new transaction is begun to process the user input. &nbsp;There are several ways to implement a pseudoconversational transaction.<br />
<br />
A conversational transaction displays a screen and then the program waits for a response with a RECEIVE command. &nbsp;This means that the transaction is active while the user is reading the display and (hopefully) entering the response data.
</div>


This is done in the application program, not in CICS itself.  Pseudoconversational (or non-conversational) mode means that the application transaction returns to CICS after displaying a screen.  When the user responds, a new transaction is begun to process the user input.  There are several ways to implement a pseudoconversational transaction.

A conversational transaction displays a screen and then the program waits for a response with a RECEIVE command.  This means that the transaction is active while the user is reading the display and (hopefully) entering the response data.

<div>
Hello<br />
<br />
Could you give an example on how to programatically configure this feature ?
</div>


Hello

Could you give an example on how to programatically configure this feature ?

<div>
Now it's up to me to follow the links and deep knowlege
</div>


Now it's up to me to follow the links and deep knowlege

<div>
<div class="content wysiwyg-content">
Hi Experts<br />
<br />
How to configure CICS to act as conversational or no-conversational modes ?<br />
Is it inside the program or at OS itself ?<br />
<br />
Thanks in advance
</div>
</div>


Hi Experts

How to configure CICS to act as conversational or no-conversational modes ?
Is it inside the program or at OS itself ?

Thanks in advance

How to configure CICS to act as conversational or no-conversational modes ?

A mainframe operating system is networking software infrastructure that allows a mainframe computer to run programs, connect linked machines, and process complex numerical and data-driven tasks. Modern mainframe design is generally defined by redundant internal engineering, extensive input-output facilities, strict backward compatibility with older software, high hardware and computational utilization rates and high stability and reliability. Well-known operating systems include IBM z/OS, z/VM, zTPF, z/VSE, OS/390, and their predecessors, along with MCP for Unisys ClearPath, and NonStop OS/Guardian on HP/Tandem, and questions regarding the IBM midrange operating system called IBM i, OS/400, and i5/OS.

Mainframe OS

There are many computer languages, and they have been evolving from machine language into a more natural way of writing. Languages are generally classified into machine language (direct machine code); assembly (using mnemonics to present the instructions to be translated later into machine language by an assembly program); procedural languages, also known as high-level languages (HLL) (Pascal, FORTRAN, Algol, JCL, COBOL, REXX, PL/I, Basic, and C are common), along with several other types. Mainframe programming is largely done in the procedural languages.