× 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.



On 2/23/11 8:05 AM, Robert Rogerson wrote:
I've been checking the archives but so far I haven't found the
required information.

Here is the scenario. We have an inhouse distribution utility which
can distribute objects via email, IFS and spool file (to replace
multiple SNDNETSPLFs in a program). In our utility we have the
ability to send to multiple profiles.

My problem is that the SNDNETSPLF command sends to a System
Distribution Directory entry. This may not be equal to the user
profile. For example, my user profile is TROGERSONR and the entry
associated with my profile is TROGERSO.

Is there a way (API?) I can use to get the entry associated with a
profile? If not has anyone else done something similiar?


That request seems to muddle the Distribution Queues [WRKDSTQ] data with the Directory Entries [WRKDIRE] data. There is the QOKSCHD "Search Directory" API for the latter; although I would not recommend coding directly to them, that data is in the files QUSRSYS/QAOK*. For the former, I believe still lacking any API, refer to the files listed in WRKF QUSRSYS/QASN*:

QASNADSA PF SNADS Secondary Node ID Table
QASNADSL LF Logical view of QASNADSQ: SNADS Dst.
QASNADSQ PF SNADS Distribution Queues Table
QASNADSR PF SNADS Destination System Routing Table

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.