× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



When is the SNDNETSPLF going away?

Jim

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] 
Sent: Tuesday, June 07, 2005 12:47 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Retrieve user output queue name


I am looking at creating a program to retrieve a user profile's output
queue name.  This would probably use QSYRUSRI or RTVUSRPRF and drill
down for special values like *WRKSTN.  In the cases of not found, it
looks like it would go to the system value QPRTDEV.  I am trying to
create a replacement for SNDNETSPLF to the same system since SNDNETSPLF
will be going away.  SNDNETSPLF to a different system is not so popular
even if at all used and is a different ballgame itself.  We already have
spool duplication in use but not where we specify a user's default
output queue.
What would be the general outline for drilling down to the output queue
name?  Has anyone already done this before?

Thanks in advance!
Craig Strong

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.