Now I want to bring my green-screen clients into the E-mail picture, and
I'm having two problems.
Problem 1 - Most of my users have restricted access so they can only
reach the applications, objects, queues they have rightful use of. How
can I give these folks the right to use RCVDST and SNDDST without giving
them access to things they shouldn't have?
Problem 2 - How do I effectively use those commands once they're
accessible? I've tried using them to receive E-mail for profiles with
authorization to the commands. I know I've sent the E-mail and can
receive it by other means (after I've failed with RCVDST), but I'm
stumped as to how to use RCVDST to get at it. I'm also not having much
luck using SNDDST to send a message.
Any help would be greatly appreciated.
--
John Hall
DartE...@worldnet.att.net
The opinions expressed are those of John Hall, and not necessarily
those of Dart Properties, Dart Energy, or any of its subsidiaries.
Without Office Vision, you're essentially pushing a string here.
Giving restricted access users to the xxxDST commands is no big deal - wrap
them in a CL program that runs with a user profile of *OWNER.
The real problem is that SNDDST is quite limited in the length (256 bytes
for a message) and content of information it can convey unless you
essentially write your own version of OfficeVision.
And RCVDST as a way to receive distributions must be preceded by QRYDST to
get the distribution IDs of the messages sent. If you're looking for email
capability without adding Officevision, you might want to consider a third
party product, such as TAO (totally automated office) if they're still
around.
If you've got the OS/400 documentation on CD, I'd suggest you look at OS/400
TCP/IP Configuration and Reference, V3. And try not to puke when you see
the part where, to receive the mail, they suggest:
"5. Use the Display Physical File Member (DSPPFM) command or the Work with
Members Using PDM (WRKMBRPDM) command to view the messages received."
Good luck,
Mike
John Hall wrote in message <68e6fb$6...@bgtnsc03.worldnet.att.net>...