> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Ted MacNEIL
>
> >Strictly verbotten in every shop I've ever been in, but there are
> >always exceptions.
>
> If you can get the wait off of the main TCB (TCA?), it's not
> as bad, but IBM (and almost every CICS sysprog I know) still
> strongly recommends against it.
For the past few releases of CICS (since TS 1.3; possibly earlier) the
EXEC CICS WAIT EVENT and EXEC CICS WAIT ECBLIST commands have been
available for the kinds of processing for which the WAIT macro is
intended.
With CICS TS 3.1 (and presumably follow-on releases) and appropriate
exploitation of the enhanced Open Transaction Environment (OTE), use of
traditionally "frowned-upon" MVS services within CICS tasks will become
moot as long as those tasks are running on their own TCBs rather than
the CICS QR TCB. The basis for "frowning upon" invoking MVS services
that could cause a WAIT was that such a WAIT would effectively "stall"
the CICS address space: The CICS (sub-)dispatcher would be unable to
dispatch other work while WAITing for whatever because it ran on the
same TCB.
-jc-
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
