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



V5R3. I associated the SMTP name with the directory entry using F19 in the
WRKDIRE screen. I can see it when I use F19, but the DSPDIRE doesn't show
it. It *does* show the ccmail address and stuff. Are you adding SMTP names
to the *SYSTEM or personal directory?

On 1/4/07, Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> wrote:

The field is DFSUID, length of 64.  The domain name is in a separate
field, DFSDR, with a length of 256. What release are you on?  This is
from a V5R3 box, but I can't see it changing from one release to another.

Michael Ryan wrote:
> Hmmm...doesn't seem to be producing the SMTP name. Wonder what I'm doing
> wrong...
>
> On 1/4/07, Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> wrote:
>>
>> Yes it does.  You have to specify *FULL and *TYPE2.  This also gives
you
>> the phone and fax numbers and forms the basis for our internal user
>> phonebook.
>>
>> Michael Ryan wrote:
>> > Does that provide the SMTP name? I've been trying that and it hasn't
>> seemed
>> > to work for me.
>> >
>> > On 1/4/07, Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> wrote:
>> >>
>> >> If you can tolerate having it not entirely up-to-date, display the
>> >> output of the DSPDIRE command to an outfile and retrieve the
>> information
>> >> you need by reading the file.  I run the following job nightly:
>> >>
>> >> DSPDIRE OUTPUT(*OUTFILE) OUTFILE(QGPL/SYSDIR) DETAIL(*FULL)
>> >> OUTFILFMT(*TYPE2)
>> >>
>> >>
>> >>
>> >> Michael Ryan wrote:
>> >> > Anyone know how to programmatically retrieve the SMTP name that's
>> >> > associated
>> >> > with a system distribution directory entry? I saw the API to
search
>> the
>> >> > directory, but I would think there's a CL command or an API that
>> would
>> >> give
>> >> > a result back on a direct hit.
>> >> >
>> >> > Thanks...
>> >> --
>> >> 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.
>>
>>
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.