Dist. List for SNDNETSPLF

[J.Pluta]

<font color=#602090>On Tuesday, September 29, 1998, 10:52 AM, Lisa Patteson wrote: To send a net spooled file to a remote AS/400, does the sender need to be enrolled in a distribution list directory on the local box? Someone told me that you could override this with a system value so that the sender doesn't have to be on a list, but I can't find one that applies. </font><hr> Well, according to <A > href="http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QBJAGD00/3.4.1.1">IBM (click here)</A> you do. Users have always had to be enrolled as far as I've known, Lisa. Nobody I know of has ever said anything about a magic system value to allow non-enrolled users to send files over the network. Joe

[Guest.Visitor]

I believe the switch user API would enable sending from a user who is not in the distribution directory. I would instead however, implement this as a 'server' job to which the request is added to a monitored data queue -- the server job submitted as a user in the directory. Regards, Chuck Comments provided "as is" with no warranties of any kind whatsoever.

[J.Pluta]

<font color=red>On Tuesday, September 29, 1998, 04:02 PM, Chuck Pence wrote: I believe the switch user API would enable sending from a user who is not in the distribution directory. I would instead however, implement this as a 'server' job to which the request is added to a monitored data queue -- the server job submitted as a user in the directory. </font><hr> Personally, I would avoid the change user API like the plague, at least in client programs. Its legitimate purpose is for servers to change to the client's user ID so as to act appropriately (logging information and so on), not for clients to "mask" their true identity in order to perform actions outside of their purview. Your second option is by far the more secure approach, IMHO. Joe