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


  • Subject: Re: SNDDST Failing with DIA Error 0401
  • From: Sean Porterfield <sporter@xxxxxxxxxxxx>
  • Date: Mon, 16 Oct 2000 16:23:24 -0400
  • Organization: Best Distributing Co.

I am on V4R4 and just found the TOUSRID details a few days ago.  I was able to
send *FILE without a problem.  Today I tried sending *DOC and it also worked.  I
followed directions on an IBM page that someone posted to this list very
recently.  Although the directions said they were for Domino, they worked for
me.

Perhaps you have something set differently?  Here is the command I used:

SNDDST TYPE(*DOC)
   TOUSRID((INTERNET USERS))
   TOINTNET((sporter@bestdist.com))
   DSTD(TEST)
   MSG('This is another test file.  Thanks.')
   DOC(MYSQL.TXT)
   FLR(SEAN)


Is that different from the "Bridge Method"?

I have a DIRE (ADDDIRE) for user INTERNET at address USERS using information
from the following URL.

http://as400service.rochester.ibm.com/s_dir/slkbase.NSF/0cf528a492c9b4a88625680b0002037f/05065e3e8dd15454862565c2007caa52?OpenDocument

HTH

"Coleman, Katherine" wrote:

> Well thanx to all for your input (see attached original email), but it was
> all stuff I had already tried.  And I had already read the "how to" article
> in News/400.  So I broke down and called IBM.  Here was thier solution: Do
> not use the SMTP "Bridge Method" (ie TOUSRID((user MAIL)), use the internet
> address method (the TOINTNET parm).  So my command looks like this and
> works:
>
>  SNDDST TYPE(*DOC)
>         TOINTNET(kcoleman@kmart.com)
>         DSTD(TEST)
>         DOC(HDRFMT.TXT)
>         FLR(KIHTRANS)
>
> The guy I had on the phone had me do some reconfiguring of SMTP and my
> network attributes before I could use his solution, but it works just fine
> and if I want to send to a distribution list, I just set it up on my mail
> server instead of my 400.
>
> However, I was not happy that everyone else in the world (except me and the
> unhappy gentleman in Australia) are able to use TOUSRID.  I pushed the guy
> on the phone and he went to the SMTP Developers (he gets an A for effort!!)
> whose response was "The Bridge Method is not recommended any more - use
> Internet Address.  TOUSRID wont work with documents anyway."  When I showed
> the News/400 article and your emails to the rep and took a wild guess it
> might have to do with release level (I am at V4R4 and the article is from
> '98), he went back to the developers (gotta give him credit here too!) and
> they STILL maintained it wont work with documents - doesnt matter the
> release level.  So since I have a work around, I gave up.
>
> Any IBMers or anyone using the TOUSRID method out there who care to
> comment??
>
> -----Original Message-----
> From: Coleman, Katherine
> Sent: Wednesday, September 27, 2000 2:36 PM
> To: 'RPG400-L@midrange.com'
> Subject: SNDDST Failing with DIA Error 0401
>
> Trying to do a simple SNDDST with a text file attached and am receiving the
> following error.  after a detailed dreview of the SNDDST command, referring
> to several online articles and lots of trial (and continued error), I still
> cant figure out what is wrong.  My command is very simple, and I get the
> same error no matter what I try to send - .TXT, .DOC .XLS - or who I try to
> send it to.  A SNDDST *MSG works fine and lands in our mailbox nicely, but
> now I want to attach a document.
>
> Any advice greatly appreciated.
>
>                       Display Command String
>
>  SNDDST TYPE(*DOC)
>         TOUSRID((DSHRAKE MAIL))
>         DSTD(TEST)
>         DOC(HDRFMT.TXT)
>         FLR(KIHTRANS)
>
>                          Additional Message Information
>
>
>
>  Message ID . . . . . . :   CPI9046       Severity . . . . . . . :   00
>
>  Message type . . . . . :   Information
>
>  Date sent  . . . . . . :   09/27/00      Time sent  . . . . . . :
> 14:06:31
>
>
>  Message . . . . :   Distribution to user identifier DSHRAKE MAIL failed.
>
>  Cause . . . . . :   The distribution was sent by user identifier(ID)
> DSHRAKE
>    SUPRDEV to user ID DSHRAKE MAIL at 06/14/43 14:00:18. The distribution
>
>    failed at System name SUPRDEV System group  with Document Interchange
>
>    Architecture (DIA) notification code X'0401'.  DIA notification codes
> are:
>      0201-System error.
>
>      0301-Invalid recipient.
>
>      0401-Invalid document.
>
>      0502-Distribution purged by system, where recipient user ID may have
> been
>    deleted from the system with unopened mail.
>
>      0601-Maximum number of recipients exceeded.
>
>      0701-Some recipients of a distribution list received the distribution,
>
>
> More...
>  Press Enter to continue.
>
>
>
>  F3=Exit   F6=Print   F9=Display message details   F12=Cancel
>
>  F21=Select assistance level
>
>  Already at top of area.
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.