In which Programs, application Will wait for user response instead of serving the other users in that Wait-time ?
-
Non-Psuedo Conversational program
-
Psuedo Conversational
-
Reentrant program
-
Quasi-reentrant program
Non-Pseudo Conversational programs hold control and wait for user response, blocking other users from being served during that wait time. In contrast, Pseudo Conversational programs release control back to CICS after sending output and wait for the next input, allowing other users to be served. This makes pseudo-conversational programs more efficient for multi-user environments.
In a Non-Pseudo-Conversational CICS program, the program stays resident and holds its resources (terminal, storage, locks) while waiting for the user's next input — during that wait, it isn't released back to CICS to serve other users, tying up system resources. This contrasts with Pseudo-Conversational design (the standard best practice in CICS), where the program terminates after sending output and CICS re-dispatches a fresh task only when the user responds, freeing resources in between so CICS can serve other users concurrently. Reentrant and quasi-reentrant describe code-sharing/reusability properties, not conversational wait behavior.