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



Thanx for you quik response, but already tried that.  That parm is not
allowed with TYPE(*DOC).

                      Display Command String      
                                                  
 SNDDST TYPE(*DOC)                                
        TOUSRID((DSHRAKE MAIL))                   
        DSTD(TEST)                                
        MSG(TEST)                                 
        DOCTYPE(11)                               
        DOC(HDRFMT.TXT)                           
        FLR(KIHTRANS)                             
    
                         Additional Message Information

 

 Message ID . . . . . . :   CPF904C       Severity . . . . . . . :   40

 Message type . . . . . :   Diagnostic

 Date sent  . . . . . . :   09/27/00      Time sent  . . . . . . :
17:25:26   
 

 Message . . . . :   Error occurred when TYPE(*DOC) was specified.

 Cause . . . . . :   When TYPE(*DOC) is specified, DOCFILE, DOCMBR, DOCTYPE,

   SYSCOD, DOCCHRID, DSTID and DSTIDEXN must not be specified.

 Recovery  . . . :   If any of the parameters listed above are specified,

   remove the value from the prompt, and then try the request again.

 

 

 


-----Original Message-----
From: Jodi_Walker@ccmail.columbia.com
[mailto:Jodi_Walker@ccmail.columbia.com]
Sent: Wednesday, September 27, 2000 4:21 PM
To: Coleman; Katherine
Subject: Re: SNDDST Failing with DIA Error 0401


     
you might want to try using the DOCTYPE (document type) parm in addition to
the 
type(*doc) that you already have.  DOCTYPE is used to identify what type of
doc 
is being used & allows the system to determine whether it can handle the
data 
stream or not.

here are some of the type codes and their meaning

       Type 

       2           Final form text document 
       3           5520 revisable form text document 
       4           Word processing EBCDIC 
       5           Word processing information file 
       6           Image-data subset document 
       7           3730 text data stream 
       8           DIA document library descriptor 
                   document 
       9           3732 display document data stream 
       10          DIA display document data stream 
       11          Revisable form text document 
       12          1403 compatible data stream with 
                   variable length, unblocked records 
       13          Digitized ADS audio 
       14          IBM PC data file 
       15          Hard copy of document 
       223         Data file 
 
 
 jw
 ______________________________ Reply Separator 
 _________________________________
 Subject: SNDDST Failing with DIA Error 0401
 Author:  "Coleman; Katherine" <KColeman@kmart.com> at Internet
 Date:    09/27/2000 2:35 PM
 
 
 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 ...


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.