|
wdsci-l-request@xxxxxxxxxxxx wrote:
7. Re: More on WDSC Problem (Jon Paris) date: Mon, 24 Jul 2006 23:44:22 -0400 Just to let you folks know that one of my two problems has been cured thanks to IBM's Don Yantzi. It seems that somebody who shall remain nameless installed a new security product on the System i - and attached it to the DDM server. The message that I was getting i.e. blank text from the server was occurring because the exit program was simply rejecting my connection with no error message.
Jon: First, glad to know you got a piece working. However, there seems to be an implication that IBM believes that a DDM exit program can send messages that the server will report to the client. I don't work directly on our exit programs, but I haven't seen where that's documented in the interface. AFAIK, the only interface action is the 'Accept/Reject' parm indicator. You reference System i. V5R4, then? I'd like to track this down. *ESCAPE messages, for example, have not been good ideas in the past. They are documented to result in *INQ messages being sent to the system operator. The exit program, and therefore the client request, waits until a response is supplied. But maybe there are enhanced capabilities nowadays.
Sadly CODE is still screwed up. It will do everything except verify. Absolutely refuses to connect to the host for file descriptions. Everything else works fine. Anyone got any ideas on that one?
I can't offer much help there unfortunately. Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.