RE: MQ Client abend (Solved)

[van Sleeuwen, Berry]

Hi All,

I had opened an PMR at IBM and we have now solved the issue.

Indeed, as Ingo mentioned, the issue was in the EXECKEY. The client programs are with EXECKEY USER. However, program IESMQCTM is in EXECKEY CICS. The effect was that $EDCTCPV sometimes was loaded in EXECKEY USER and sometimes in EXECKEY CICS. When it was loaded in EXECKEY CICS the MQ client transaction abended.

Should you plan a migration to MQ Client then be aware that the EXECKEY must be configured correctly. All programs using MQ Client code must be in EXECKEY CICS, especially when TCPIPservices are in use. $EDCTCPV is loaded in EXECKEY CICS when TCPIP services are started. In our case, since we don’t use TCPIP services, $EDCTCPV was loaded depending on what program would reference the phase first, hence sometimes it ran correctly when in EXECKEY USER and sometimes abended when in EXECKEY CICS.

Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen


-----Original Message-----
From: VSE-L [mailto:vse-l-bounces+berry.vansleeuwen=atos...@lists.lehigh.edu] On Behalf Of Ingo Franzki via VSE-L
Sent: Tuesday, March 22, 2016 1:54 PM
To: vs...@lehigh.edu
Subject: Re: MQ Client abend

I don't see the start of this thread, but CICS programs using the MQ Client must be defined with EXECKEY=CICS. This is because the MQ client performs socket calls which require to run in CICS key, not in user key.

Kind regards, Ingo

On Tuesday, March 22, 2016 at 1:43:48 PM UTC+1, Mick Poil wrote:
> That looks like the function that failed. I guess it is C code, and VSE use C a lot. I wonder if Ingo will comment?

_______________________________________________
VSE-L mailing list
VS...@lists.lehigh.edu
https://lists.lehigh.edu/mailman/listinfo/vse-l
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
_______________________________________________
VSE-L mailing list
VS...@lists.lehigh.edu
https://lists.lehigh.edu/mailman/listinfo/vse-l

[Tony Thigpen]

Just a FWIW:

When using the BSI IPv6/VSE product, the EXECKEY CICS is *not* required
when using our $EDCTCPV phase, or any of our TCP services. We handle
this dynamically within our code.

Tony Thigpen

[Martin Truebner]

(about user-key vs CICS-key)

>> We handle this dynamically within our code.

This had been (watch the "past tense" used here) my pet peeve for a
long time- but I got tired of repeating that it can be done (with a
little extra code - but no big deal) without molesting end-users.

I am very happy that it is now handled in products coming from BSI or
TE.

Martin Trübner; everything around "PoOps of z/arch"

[Tony Thigpen]

Been that way for 10+ years. :-)

Tony Thigpen