RE: Retrieve user output queue name

[craigs@xxxxxxxxx]

Thanks for the responses!
No, SNDTCPSPLF is not an option as these spools are going to users.  No, to
remote outq's too since these are going to specified users and outq's based
on profiles.  We use remote outq's for printing to remote devices.
I am planning on using two API's.  One to get the user profile and another
for the system value.  Use the outq from the profile.  If the profile says
*WRKSTN, it will use the system value for QPRTDEV.  If *DEV, then device on
profile.  If device is special value, get system value.  I think I will go
with that.
Jim asked when SNDNETSPLF is going away?
The release after V5R3 will be the last to support SNA.  IBM is talking
2007, it is confirmed, and they are giving notice.  Basically, you will
need Enterprise Extender to run SNA/APPC apps for a fee.  ANYNET will not
be a workaround since that is going away too.  For the amount of SNA we
use, we have workaround alternatives developed that should get us by.
Search the "midrange" list for "Death of SNA?" for a lengthy discussion.

http://www.mcpressonline.com/mc/.6b24cce2

Claims that the release after V5R3 will be the last to support SNA.

Confirmation from IBM:
http://www-1.ibm.com/servers/eserver/iseries/support/planning/futuresftwr.html


http://www-1.ibm.com/servers/eserver/iseries/support/planning/nav.html

Items affected:
SAVRSTOBJ, SNDDST, SNDNETF, SNDNETMSG, SNDNETSPLF, STRPASTHR, DDM files
using *SNA, etc.

Craig Strong