RE: Retrieving System Distribution Directory details...

Rather than code directly to them, why not use embedded SQL to limit the exposure?


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Wednesday, February 23, 2011 9:45 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Retrieving System Distribution Directory details...

Hi Robert,

Using the API should ensure your software is future-proof; if you do want to
use the QAOK* files directly, be prepared for possible changes to the tables
(and therefore level checks) when you move to a new release etc.

Chuck said: "I would not recommend coding directly to them" and I second
that.

Richard

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: 23 February 2011 17:21
To: Midrange Systems Technical Discussion
Subject: Re: Retrieving System Distribution Directory details...

Thanks all,

Searching on the QOKSCHD API lead me to learn that the System Directory
Entries are stored in QUSRSYS/QAOK* files. Specifically the file QAOKL02A
is keyed by user profile. So by Chaining to this file I can get the entry
(TROGERSO).

My question is if this is a safe thing to do? I don't really know anything
about these files.

Thanks,

Robert Rogerson

On Wed, Feb 23, 2011 at 11:41 AM, Richard Thomas <
richard_matthew_thomas@xxxxxxxxxxx> wrote:

Hi Robert,

I haven't checked for certain, but the Search System Directory (QOKSCHD)
API
might do what you're looking for.

Richard

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: 23 February 2011 16:06
To: midrange-l@xxxxxxxxxxxx
Subject: Retrieving System Distribution Directory details...

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?

Thanks,

Robert Rogerson
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.