That is part of the UDP design. If an error occurs the data is silently
discarded.
RPN01 wrote:
I was going to ask what I was doing wrong... But I figured that out just
a moment ago.
My question now is what is the logic behind requiring a user to be in
TCPIP’s Obey list to allow it to use certain TCP/IP ports and protocols.
It isn’t everything, because things like FTP work, and I think you can
play fairly fast and loose with higher numbered ports. But trying to
connect to port 514 on another virtual machine wasn’t allowed until I
put the user in the Obey list in the PROFILE TCPIP file.
Also: If I violate this using Pipe and the UDP stage, why don’t I get a
non-zero return code? The UDP stage quietly accepts records, and the
pipe returns a zero return code, but no data is actually sent. There’s
no errors in the TCPIP console log either; the data is just ignored and
not sent anywhere. Shouldn’t there be an indication somewhere that the
data wasn’t sent? Or (and I confess I haven’t tried to decode anything
in the output string yet) is there something in the output of the UDP
stage that would indicate that the message failed to send?
--
Robert P. Nix Mayo Foundation .~.
RO-OE-5-55 200 First Street SW /V\
507-284-0844 Rochester, MN 55905 /( )\
----- ^^-^^
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us
