i'm getting this message in my CICS/ts

[ASIFF AMAHED]

i'm getting this message, any ideas?

CEE0374C CONDITION = CEE3250C TOKEN = 00040CB2 61C3C5C5 00000001

WHILE RUNNING PROGRAM UNKNOWN

AT THE TIME OF INTERRUPT

PSW 00000000 82167B3C

GPR 0-3 0265AC68 0265ADB0 0265C940 000002D0

GPR 4-7 00000097 00000000 02653808 0091F0D0

GPR 8-B 0265AE40 02165028 0265BE40 0216777E

GPR C-F 02164FE8 0265AAC8 82167B3C 00000000

FLT 0-2 2610000000000000 1800000000000000

[David Stuart]

Asiff,

According to the LE/VSE Debugging Guide and Run-Time Messages, for a CEE0374C you need to "Contact your service representative."

Was either a Transaction or System dump taken? Either one might give you a better idea as to what was running at the time.

Also, did you receive a separate CEE3250C message? If so, it should have an abend code that could provide more information as to why the program/transaction was canceled.

Dave

Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
David....@ventura.org

>>> "ASIFF AMAHED" <asif...@gmail.com> 8/4/2011 8:48 AM >>>

[Chris Mason]

Asiff

 

One idea is to use the following URL in order to get an explanation of what the message means:

 

http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat/index.html

 

"IBM LookAt"

 

<quote>

 

1.23 CEE0374C

 

   CEE0374C  CONDITION = condition-id TOKEN = condition-token WHILE RUNNING
             PROGRAM program-name WHICH STARTS AT program-address AT THE TIME
             OF INTERRUPT

 

              PSW
             psw   GPR 0-3 gpr0 gpr1 gpr2 gpr3  GPR 4-7
             gpr4 gpr5 gpr6 gpr7   GPR
             8-B gpr8 gpr9 gprA gprB   GPR C-F gprC
             gprD gprE gprF   FLT 0-2 flt0 flt2  FLT
             4-6 flt4 flt6

 

Explanation: An unrecoverable condition occurred while processing a previous condition. This message is issued with a WTO because Language Environment has encountered a critical error while handling a previous condition. The CONDITION indicates the message representing the condition being handled and the TOKEN is the three word Language Environment Condition Token. The program-name, program-address (starting address of program), psw, and registers are for the condition being handled when the unrecoverable condition occurred. If the CEE0374C message appears several times in sequence, the conditions appear in order of occurrence. Correcting the earliest condition may allow the application to run successfully.
Programmer Response: Attempt to correct the original condition by looking up the condition-token specified in the message.

 

System Action: The thread is terminated abnormally.

 

Symbolic feedback code: CEE0BM

 

</quote>

 

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CEEA91B0/SPTCS00584

 

from "z/OS Language Environment Run-Time Messages, SA22-7566-11".

 

However, as Dave mentioned, that single message does not appear to be the whole story.

 

Chris Mason

[michael...@googlemail.com]

Chris,

It is not a good idea to point a VSE person at a z/OS manual. As you ought to have concluded by now they have some similarities but can be radically different, have a look at the DISP JCL parameter as one classic example.Most folks can find a message, I think what he was asking is what we often tend to do in cases like this:

"What the heck does this really mean is wrong?"

At least, that is what I would be asking for.

Maybe somebody like Garry in Perth will spot the request and handle it outside a PMR.

Mike

[Chris Mason]

Asiff

 

If you follow my initial suggestion and use the URL which I recommended, you will note that, by default, it "bullets" a z/OS version/release but that also VM and VSE versions/releases can be bulleted. So here is the "nappy change" that Mr Poil thinks I should have employed for you:

 

<quote>

 

3.1.18 CEE0374C

 

   CEE0374C CONDITION = condition-id TOKEN = condition-token WHILE PROCESSING
          PROGRAM program-unit WHICH STARTS AT address AT THE TIME OF
          INTERRUPT

 

Explanation: An unrecoverable condition has occurred while processing a previously-unhandled condition. The condition-id corresponds to the LE/VSE message number associated with the failure, and condition-token is the internal representation of the event (where the condition-id and condition-token translate to each other). The message is issued to the operator console when nested conditions occur. The message display includes the registers and PSW information relating to the displayed condition token. This is the condition that was being processed when the unrecoverable error occurred. If this message appears more than once, the conditions appear in order of occurrence.

 

   PSW      psw
   GPR      gpr    grp 1   gpr    gpr 3
   0-3      0              2
   GPR      gpr    gpr 5   gpr    gpr 7
   4-7      4              6
   GPR      gpr    gpr 9   gpr    gpr B
   8-B      8              A
   GPR      gpr    gpr D   gpr    gpr F
   C-F      C              E

 

Programmer Response: The earliest condition is the one that should be investigated and corrected. For information on condition tokens and how the CEE0374C message is used to debug errors, refer to the section "Using Condition Information" of "Chapter 1. Preparing Your Routine for Debugging" in the LE/VSE Debugging Guide and Run-Time Messages.

 

System Action: The thread is terminated abnormally.

 

Symbolic Feedback Code: CEE0BM

 

</quote>

 

From IBM Language Environment for z/VSE Debugging Guide and Run-Time Messages Version 1 Release 4 Modification Level 5, SC33-6681-07.

 

I note that the formatting still comes out incorrectly, if differently so!

 

I note also that the "explanation" is essentially the same in both cases - as I would have expected - but that, actually, the z/OS explanation has a bit more meat on it - which may be no bad thing.

 

I'm sorry if this response seems offensive but Mr Poil has a track record of being, as far as I am concerned, a royal PITA so the aggravation spreads. At least his contribution this time was pointless instead of being persistently contrary!

 

Chris Mason

 

----- Original Message -----

From: ASIFF AMAHED

To: VSE Discussion List

Sent: Thursday, August 04, 2011 5:48 PM

Subject: i'm getting this message in my CICS/ts

[Eshu...@aol.com]

Hi Chris:

 

Is there any particular reason for this statement?

 

"I'm sorry if this response seems offensive but Mr Poil has a track record of being, as far as I am concerned, a royal PITA so the aggravation spreads. At least his contribution this time was pointless instead of being persistently contrary!"

 

Granted that I haven't seen all of Mr.Poil's replies on VSE-L but the ones I have seen have been useful and very helpful.

 

Just my $.02.

 

Regards,

Gene

[Richard Verville]

Thursday afternoon before Share in Orlando.... there are only a few of us left on VSE-L, we should try to get along....

[ch...@arneycomputer.com]

Are you trying to say all the VSE people are headed to Share?

 

Chuck Arney

Arney Computer Systems

www.arneycomputer.com

 

 

---

From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf Of Richard Verville
Sent: Thursday, August 04, 2011 2:29 PM
To: VSE Discussion List
Subject: Re: i'm getting this message in my CICS/ts

[Richard Verville]

Along with WAVV, that'd be cool. Richard

[michael...@googlemail.com]

What I was trying to say was that pointing somebody at a z/OS manual was inherently dangerous.

The response was downright rude and offensive. Who moderates the list?

Mike

[michael...@googlemail.com]

Perhaps I should also have mentioned that I work on a product that runs on both z/OS and z/VSE. I have to be technically competent on both, so for instance, I know that VSE LE is not the same as the z/OS LE product, VSE/VSAM is not the same a z/OS VTAM etc..

I am not in the habit of saying things for the sake of it.

Mike

[Eshu...@aol.com]

Hi Mike:

 

I've had similar problems with what you mention on this list as CICS TS for z/OS has some major differences with CICS TS for VSE. So, your point is well taken.

 

Regards,

Gene 

[RJac...@decare.com]

Mike,

Over the years that I have been on this list, I have not seen to many
situations where it has needed moderation, so it is very possible that the
answer is no one.

During the time that Chris Mason has been posting, I have found his
knowledge of VTAM and SNA to be extensive and useful, so I am glad he
contributes. However, unfortunately he does seem to take offense easily
and is seldom inclined to let it pass.

Bob Jacobson
(651) 994-5329

michaelalanpoil@g
ooglemail.com
Sent by: To
owner-vse-l@Lehig "VSE Discussion List"
h.EDU <vs...@Lehigh.EDU>
cc

08/04/2011 03:37 Subject
PM Re: i'm getting this message in my
CICS/ts

Please respond to
vs...@Lehigh.EDU

[Chris Mason]

Gene

 

> Is there any particular reason for this statement?

 

Yes.

 

But I expect you have a hidden question which is to ask "What is it about?"

 

I'm sorry that I find it impossible to work with the archiving facilities of the VSE-L list. This is no doubt a severe failing of mine but it's peculiar given I have no difficulty with other lists. Thus I can only offer the following:

 

In thread "CICS Web Services" dated in and around 16 December 2010, Mr Poil offered us the following:

 

<quote>

 

In CICS Transaction Server for VSE/ESA Web Support and 3270 Bridge SG24-5997 published in 2000, you will find appendix "A.3 Listing of TCP/IP IPINIT00 with CWS parameters highlighted". And the first one highlighted is actually SET IPADDR.

 

</quote>

 

See if you agree. I don't. And it having been pointed out how disingenuous this statement was, Mr Poil tried to bluff it out!

 

From here you can download the redbook in question:

 

http://www.redbooks.ibm.com/abstracts/sg245997.html

 

The first text highlighted according to the rest of the world's understanding of the technique is GATEWAY, followed by DEFINE NAME, SET DNS1 and DEFINE HPPTD - full stop, period, whatever ...

 

It was the arrogant "first" - you need to know how we got to this point fully to appreciate the enormity of that insult - followed by even more arrogant refusal to accept that the highlighting in the redbook left a great deal to be desired. The highlighting matter was, of course, trivial. It was Mr Poil's attitude that got my goat big time ... So he's not on my Christmas card list!

 

And we see something of the same attitude in this latest response, an attitude shared by some others of the "usual suspects" who just seem not to be able to abide any sort of assistance entering their sacred list from outsiders not currently blessed with the accolade of VSEer! VSE-L seems to operate as a sort of cabal!

[Allan Peterson]

Wow , always want to be in a Cabal
Can now tick that off my bucket list

[michael...@googlemail.com]

It is highlighted with "<-----------", which is what was just described as an inappropriate method of showing that it is significant

It is a well-known technique that when somebody wants to make mischief to prove their own case or point of view, only quote part of what is said, the full post was:

---------------------------------------------------------------------------------------------------------------------
I have come in rather late on this one. I know that CICS TS VSE
general manuals can lack useful techie information. However, IBM do
know that and so Redbooks are often used to help to fill the gap.

In CICS Transaction Server for VSE/ESA Web Support and 3270 Bridge
SG24-5997 published in 2000, you will find appendix "A.3 Listing of
TCP/IP IPINIT00 with CWS parameters highlighted". And the first one
highlighted is actually SET IPADDR.

It is very easy to miss something vital that is written down
somewhere, I wish I could remember to look everywhere that might be
relevant when I am tearing my hair out trying to figure out why
something does not work.

The requirement for OS/390 Unix manuals was due to VSE development
basing their TCP/IP support on the OS/390 product that was available
at the time (as they did for the OS/390 API used by CICS TS), and I
guess that they decided that it was not worth the effort and cost to
duplicate another manual.
----------------------------------------------------------------------------------------------------------------------

I am not sure how you can derive "disingenuous":

1. not straightforward; not candid or frank; insincere
2. slyly deceptive or misleading, typically by means of a pretense of ignorance or unawareness

or "arrogant" from this.

Mike

[michael...@googlemail.com]

Need to get my facts straight, memory is fallible, the "<---------" was noted afterward.

Apologies Asiff, I hope you get an answer that identifies the underlying problem and I will add no more to this thread.

[David Heilman]

That is one of the great things about emails. If I see Chris's name on a
post I just delete it without reading it. Never liked people that try to
make everyone else look like an idiot just to boost their ego.

Sorry list but I've seen this happen on the Z/OS and MVS lists and that
is why I dropped them. To many big egos on them. This has been one of
the greatest self help tools I have used over the past 45 years of my
mainframe career. Would hat4e to see this go much farther.

Dave