Don, you know that Pipes has tcpclient and tcpserver stages, right?
Use TRACE EXT 4000 to see if you're getting IUCV interrupts. And use CMSIUCV
to CONNECT and SEVER.
Alan
Sent from my iPhone using IBM Verse
On Sep 2, 2017, 6:41:00 AM, [email protected] wrote:
From: [email protected]
To: [email protected]
Cc:
Date: Sep 2, 2017, 6:41:00 AM
Subject: [CMS-PIPELINES] using IUCV sockets in a pipe stage
I'm writing an assembler pipe stage to use IUCV sockets...
Things are going south very quickly... :-(
I establish the hndiucv interrupt handler, and do the iucv connect
Both of those complete ok... but the iucv connect is asynchronous, I'm
supposed to get an interrupt showing "connection complete" or "connection
severed"... but I'm not getting any interrupt at all. :-(
I know I don't get an interrupt because I CP TRACE I RANGE ... covering the
interrupt handler code ... if it got there, I'd be in trace...
I must be missing something basic at this point, but think I'm doing
everything correctly based on the TCP/IP Programmer's Reference.
Are there any Redbooks or coding samples of how to do this?.... it doesn't
seem that complicated, yet ... it's not working right out the gate. :-)
It does properly detect when the TCPIP ID is logged off... IUCV SEND fails
with iprcode 11 as expected... but when it is logged on (and TCPIP is
running) I get the expected 0...
After IUCV SEND, I use pipwecb to wait for the interrupt handler to post
the ecb... but it doesn't even get to the interrupt handler. Did pipwecb do
something like mask external interrupts? I wouldn't think so....
I was going to pipcommt 0 after the IUCV connection was established, but
thought maybe I had some order of events wrong, so tried pipcommt 0
earlier... no difference.
Same results on both VM 6.3 and 6.4
Any suggestions?
Thank you
Donald Russell
Visa Inc.
