Jorge, If this were 30 years ago, I would say that the understanding of the way CICS works would have prevented you from thinking about putting a WAIT into a CICS transaction. Because IBM could reasonably have expected you to know that as someone who had been given the job of writing a CICS transaction, I would say there's no case to answer. Today I just wouldn't know whether CICS had changed enough for that still to be the case. Some of the responders to this thread have speculated that issuing the WAIT might be acceptable - with some rather complex provisions. One interpretation of what Shmuel says is that it is still something a CICS transaction programmer shouldn't even think of doing.
I then tried to think how CICS could "police" the transaction code. If CICS were interpreting the programming statements in some way as is done with REXX or APL code, the code interpreter could spot anything that was "forbidden" - but why have the instruction/statement at all if it was forbidden? <g> In a sense, issuing SVCs is comparable to running with an interpreter so it's possible to imagine there could be an MVS function to filter issuing SVCs, which, if it existed - and I'm so ignorant of MVS these days, maybe such a function does exist - CICS could use for its "policing". It might be more productive to explain what it was you were trying to do. It may also be better to ask in the presence of CICS specialists. I just peeked at the "About Group" for "bit.listserv.cics-l", the "CICS Discussion List", and the activity is very low at the moment. However, last September had more than 400 posts within the month so, unless a small number of subscribers had a "frank exchange of views", there may be quite a few lurking. Chris Mason ----- Original Message ----- From: "Jorge Arueira Campos" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <IBM-MAIN@BAMA.UA.EDU> Sent: Tuesday, 28 March, 2006 8:28 PM Subject: Re: CICS down after transaction exec wait macro. > Hi !!! > > Issuing a wait macro in a CICS transaction, in > the main task, is forbidden. Why no have a protection for not down the CICS > ??? There are a problem if the user coded a macro WAIT in your program and > issue in CICS region and shutdown the entire product. Is necessary open a > call in support IBM for this problem ??? > > Thanks for help me > > Jorge Arueira Campos > > CAIXA ECONOMICA FEDERAL - OSASCO - SP - BRAZIL > > On 3/26/06, Shmuel Metz (Seymour J.) <[EMAIL PROTECTED]> wrote: > > > > In <[EMAIL PROTECTED]>, on 03/25/2006 > > at 06:33 PM, Chris Mason <[EMAIL PROTECTED]> said: > > > > >I'm glad other, sharper "problem vultures" have spotted the two - so > > >far - flaws in the original code. But the matter here is whether > > >issuing a WAIT in a CICS transaction at all is "a good thing" or not. > > > > I'd go farther and say that issuing a wait in a CICS transaction, in > > the main task, is forbidden. > > > > -- > > Shmuel (Seymour J.) Metz, SysProg and JOAT > > ISO position; see <http://patriot.net/~shmuel/resume/brief.html> > > We don't care. We don't have to care, we're Congress. > > (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- 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
