SNDDST (Send Distribution)
Purpose
The Send Distribution (SNDDST) command allows a user to send distribution to another user, to a list of users, or to a distribution list.
Restrictions
- A current user of this command working on behalf of another user must be granted authority to work on the behalf of the other user by means of the Grant User Permission (GRTUSRPMN) command.
- Personal distribution cannot be received by a requester working on behalf of another user.
- The DOCD, SUBJECT, and DSTD parameters are not updated from the SNDDST command to the actual mail log when a document (*DOC is specified for the TYPE parameter) is sent.
Required Parameters
- TYPE
- Specifies the type of information sent and the valid values on this command. Dependent parameter codes for this parameter (see syntax diagram) determine which parameters are valid. If the dependent parameter code is listed in the syntax diagram, the parameter is valid when that type is specified.
*LMSG: The text specified on the Long Message prompt (LONGMSG parameter) is sent as an final-form text document (FFTDCA) note. LONGMSG allows up to 5000 characters, which is about one page of text. The "details" parameters (Subject, Reference, Author, Due Date, etc.) are supported with TYPE(*LMSG).
*MSG: Only the message specified in the MSG parameter is sent.
*DOC: The document specified in the DOC or DOCID parameter is sent. The user must have authority for the document before it can be sent.
*FILE: The database file specified in the DOCFILE and DOCMBR parameters is sent. The database file is sent without any changes. The user must have authority for the database file before it can be sent.
*IDP: The interchange document profile (IDP) specified in the IDPFILE and the IDPMBR parameters, or the document profile built from the keywords DOCD, AUTHOR, DOCCLS, KWD, SUBJECT, REFERENCE, STATUS, PROJECT, ACTDATE, CMPDATE, CRTDATE, DOCDATE, FILCAB, CPYLST, and/or EXPDATE is used. The profile can be a profile of a printed document.
*DSTID: The mail entry identified by the distribution ID is distributed. The distribution ID is referred to as the distribution document name.
- TOUSRID
- Specifies the user ID and address of one or more users to whom the distribution is being sent, or the distribution list name of one or more distribution lists containing the user ID and address of one or more users to whom the distribution is being sent. A combination of user IDs and distribution lists can be used on the same command. Up to 300 user IDs and addresses can be specified.
If no user ID and address is specified for the TOUSRID parameter, an internet address must be specified on the TOINTNET parameter.
Element 1: User ID or List ID
user-ID: Specify the user ID of the user to whom the distribution is sent.
list-ID: Specify the distribution list of users to whom the distribution is sent.
Element 2: User Address or List Qualifier
user-address: Specify the user address of the user (specified in element 1) to whom the distribution is sent.
list-qualifier: Specify the distribution list qualifier of users (specified in element 1) to whom the distribution is sent.
Element 3: Recipient Type
*PRI: The user or distribution list is the primary recipient of the distribution.
*CC: The user or distribution list is receiving a copy of the distribution sent to the primary recipient. This copy recipient is identified as a receiver on the distribution.
*BCC: The user or distribution list is receiving a copy of the distribution sent to the primary recipient. However, this copy recipient is not identified as a receiver on the distribution.
- DSTD
- Specifies the description of the distribution. A maximum of 44 characters can be specified.
- TOINTNET
- Specifies the internet address of one or more persons or organizations to whom the distribution is to be sent. If TOINTNET(*NONE) is specified, at least one user ID and address must be specified on the TOUSRID parameter. Up to 300 internet addresses can be specified.
The TOINTNET parameter is not allowed when the TYPE keyword is *MSG.
Single value
*NONE: No internet address is specified.
Element 1: Internet Address
internet-address: Specify the internet address of a person or organization to whom the distribution is being sent. Up to 253 characters can be specified for each address.
Element 2: Recipient Type
*PRI: The internet address is the primary recipient of the distribution.
*CC: The internet address will receive a copy of the distribution sent to the primary recipient.
*BCC: The internet address will receive a copy of the distribution sent to the primary recipient. However, this copy recipient is not identified as a receiver on the distribution.
Optional Parameters
- MSG
- Specifies a short message.
*NONE: No message is sent with the distribution.
*DSTIDMSG: The same message in the distribution document specified on the DSTID parameter is sent with the distribution.
'message-text': Specify the message to send to the users. Up to 256 characters enclosed in apostrophes can be specified.
- LONGMSG
- Specifies the text to send to the recipients as an final-form text document (FFTDCA).
*NONE: No text is sent. This is the default and required when TYPE is not *LMSG.
'long-message-text': Specify the text (5000 characters maximum) to send to the recipients. The text will be put into an final-form text document (FFTDCA) that will be sent as a note.
The text must be formatted by using the following controls within the text:
- :/N - Will cause a new line (Carrier return).
- :/P - Will cause a new paragraph. (New line plus a blank line)
(Carrier return and Required carrier return)
The document is setup with 10 characters to the inch, the font ID is 11, the left margin at position 1, and the right margin at position 75. If :/N is not used to start a new line, the text will continue past the right margin and will not be viewable by some E-mail clients. Blanks are not removed from the text, but left in place for indentation and alignment. No extra text (ie. Recipient List, Date/Time, Subject, or Sender) is put into the document.
Technical note to programmers: Any of the FFTDCA controls (in hexadecimal) can be inserted in the text to provide more control of the format if the controls above are not enough.
- DOC
- Specifies the name of the document being sent.
*DOCID: The document being sent is identified by the library-assigned document name.
document-name: Specify the user-assigned name of the document being sent. Up to 12 characters can be specified.
- FLR
- Specifies the name of the folder that contains the document. This is the user-assigned name given to the folder when it is created. If the DOC parameter is specified, the FLR parameter must also be specified.
*NONE: No folder is specified when the document is identified by the DOCID parameter.
folder-name: Specify the name of the folder that contains the document being sent. A folder name can consist of a series of folder names (FLRA/FLRB/and so on) if the document being sent is located in a folder contained in another folder. Up to 63 characters can be specified.
- DOCID
- Specifies the library-assigned name of the document being sent. This is the name assigned to the document by the system when it was created. The library-assigned document names can be determined by using the Query Document Library (QRYDOCLIB) command or the library-assigned document name is returned in a completion code when using the File Document (FILDOC) command. Library-assigned document names are 24 characters in length with the following format: YYYYMMDDHHMNSSHSSNSNSNSN where:
YYYY = year
MM = month
DD = day
HH = hour
MN = minute
SS = second
HS = hundredth of a second
SNSNSNSN = system name
*NONE: No library-assigned document name is required when the document is identified by the DOC parameter.
'library-assigned-document-name': Specify the library-assigned document name being sent.
- DOCFILE
- Specifies the name of the database file that contains the document data to be sent. The database file is a user-defined file, or it is the output file specified by RCVDST(OUTFILE) or RTVDOC(OUTFILE). If an output file is specified, only the data portion of the document data record is read from the output file and the prefix is removed from the document data record. More information on defining the format of database files (OUTFILES) is in the Database Programming topic in the Information Center.
The name of the database file can be qualified by one of the following library values:
*LIBL: All libraries in the job's library list are searched until the first match is found.
*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.
library-name: Specify the name of the library to be searched.
database-file-name: Specify the name of the database file.
- DOCMBR
- Specifies the document database file member to be sent.
*FIRST: The first member in creation order in the database file is sent.
member-name: Specify the name of the database file member to be sent.
- USRID
- Specifies the user ID and address of the user for whom the request is made.
*CURRENT: The user profile that is currently running is used.
Element 1: User ID
user-ID: Specify the user ID of the user to whom the distribution is sent.
Element 2: User Address
user-address: Specify the user address of the user to whom the distribution is sent.
- DSTID
- Specifies the unique distribution ID of the distribution. The ID is assigned to the distribution by the system that originated it.
Distribution IDs can be found by using the Query Distribution (QRYDST) command. IDs are also returned from the Send Distribution (SNDDST) command.
*NONE: No distribution ID is sent.
'distribution-ID': Specify a distribution ID composed of the second part of the sender's user ID (padded on the right with blanks to 8 characters), the first part of the sender's user ID (padded on the right with blanks to 8 characters), and a 4-digit zoned sequence number with leading zeros. For example, NEWYORK SMITH 0204. The distribution ID is entered this way because a blank character is valid with a user ID address. This parameter is required when TYPE(*DSTID) is specified.
- DSTIDEXN
- Specifies the extension of the distribution ID if one is specified on the DSTID parameter. This extension uniquely identifies a duplicate distribution. This extension is a 2-digit extension ranging from 00 through 99. For incoming distributions, this extension ranges from 01 through 99. For confirmation of delivery distributions, this extension must be 00. For example, if the distribution ID is NEWYORK SMITH 0204 and two copies of this distribution were sent to a user, then the user has two distributions with the same distribution ID. To uniquely distinguish the two distributions, an extension is added to each distribution. For example, one distribution is identified by distribution ID and extension NEWYORK SMITH 020401 and the other one by NEWYORK SMITH 020402. If there are no duplicate IDs, the extension defaults to 01. These extensions map one-to-one with the distribution ID that is specified on the DSTID parameter.
*NONE: There is no duplicate distribution. This value is equivalent to a 01 extension.
distribution-ID-extension: Specify the extension associated with the distribution. This is used to uniquely identify duplicate distributions.
- DOCTYPE
- Specifies the type of document being distributed. This identifier is used by the system to determine whether it can correctly handle the data stream.
*DFT: The system creates the right document type identifier based upon the source of the data.
Document Description 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 fileIf TYPE(*IDP) is specified, the type is 15 (printed document).
If TYPE(*FILE) is specified and the file is an output file created by the RTVDOC command (OUTFILE parameter), then the document type is taken from this file. If this file does not contain a document type or the value in the file for the document type is 0, an error message is sent.
If the file is a user-defined file, the document type is 223 (data file).
If TYPE(*DOC) is specified, the document type of the document sent is used. If TYPE(*DSTID) is specified, the document type is the same document type that is associated with the distribution.
*FFT: The document is a final-form document. This type of document is intended to be shown and printed, but not edited, by the receiver.
*RFT: The document is a revisable-form text. This type of document can be viewed, printed, and edited by the receiver.
document-type-number: Specify a value ranging from 2 through 65535. The numbers ranging from 2 through 32767 are controlled by registering them with the IBM Document Interchange Architecture and are used for IBM-defined document types. The numbers ranging from 32768 through 65535 are not registered with IBM and can be used for non-IBM defined document types. The meaning of these document types must be stated as values of the SYSCOD parameter.
- SNDFMT
- Allows the user to specify the format of the document being sent.
*NOCHG: The document is sent in the current format.
*NOTE: The document is sent in a final form text document content architecture (FFTDCA) data stream as a note.
*FINALFORM: The document is sent in FFTDCA.
- SYSCOD
- Specifies text used with the document type parameter to help identify the type of document being sent. The receiver of the data stream determines the document data stream and processing requirements to edit, view, print or change the document.
*DFT: The system supplies a default system code. If the DOCTYPE value is within the range 2 through 32767, the default is 'IBM iSeries 400 CL'. If the DOCTYPE is within the range 32768 through 65535, a system code must be specified.
'system-code': Specify the text that helps uniquely identify the type of document being sent. Up to 13 characters can be specified.
- SENSITIV
- Specifies the level of sensitivity defined by the X.400 standard. The four levels include normal, personal, private and company confidential. Private distributions cannot be viewed by a user working on behalf of another user.
*NONE: The distribution has no sensitivity restrictions.
*PERSONAL: The distribution is sent to the recipient as an individual.
*PRIVATE: The distribution contains information that should be accessed only by the recipient.
*CONFIDENTIAL: The distribution contains information that should be handled according to company procedures.
- PERSONAL
- Specifies whether the document distribution is private or not. This parameter is replaced by SENSITIV but the PERSONAL parameter can still be used. However, because this parameter may be removed in a later release, whenever possible use the SENSITIV parameter.
If PERSONAL(*YES) is used, the SENSITIV parameter must be omitted or it must be with the value SENSITIV(*NONE). If the command is prompted without this parameter specified, this parameter is not displayed.
*NO: Only the owner and users that have authorization to the distribution document can get access to distributions that are not sensitive. Users authorized to work on behalf of other users who have access to the distribution can access documents that are not sensitive. This value will map to SENSITIV(*NONE).
*YES: Only the owner can get access to private distribution documents. Users authorized to work on behalf of other users who have access to the distribution document cannot get access to the distribution. This value will map to SENSITIV(*PRIVATE).
- IMPORTANCE
- Specify low, normal or high importance. This is an indication to the recipient of the content importance of the distribution. It is different from priority which relates to the speed with which the distribution was sent.
*NORMAL: A distribution of normal importance.
*HIGH: A very important distribution.
*LOW: A low importance distribution.
- PTY
- Specifies whether the distribution is sent using low priority, normal priority or high priority. For distributions to remote receivers, the priority determines which 'SNADS Next System Queue' is used. Normal priority distributions use the normal next system queue. Low priority distributions use the normal next system queue with the lowest priority available within that queue. High priority uses the priority next system queue. The difference between low, high and normal priority depends on information, specified by the user, on the Configuration Distribution Services (CFGDSTSRV) command. The handling of priority distributions by other office system nodes can vary, but generally the high priority distributions take the faster path when there is a choice of paths. For distribution to local receivers, the priority determines whether a message is sent to the receiver's message queue to notify the receiver of the distribution. No message is sent for normal distributions.
*NORMAL: Normal priority is used.
*HIGH: High priority is used.
*LOW: Low priority is used.
- CFMDEL
- Specifies whether the sender wants a confirmation of delivery notification when each receiver receives the distribution. If confirmation of delivery is not requested, the sender is still informed if the distribution is not delivered because of system failures, routing failures, or because it has an invalid user ID. If confirmation of delivery is requested, the sender is informed when the receiver either receives the distribution or deletes the distribution before receiving it. To get this information, the sender must do a Query Distribution (QRYDST) command with the OPTION(*OUT) specified.
*NO: Request for confirmation of delivery is not specified.
*YES: Request for confirmation of delivery is specified.
- IDPFILE
- Specifies the name of a database file that contains the interchange document profile (IDP) data. The interchange document profile is either a user-defined file or the output file specified on the OUTFILE parameter of the Receive Distribution (RCVDST) or Retrieve Document (RTVDOC) commands. If an output file is specified, only the data portion of the document profile record is read from the output file and the prefix is removed from the IDP data.
If this parameter is specified, the remaining parameters on this command are ignored except for the DOCCHRID and CMDCHRID parameters.
*NONE: The interchange document profile is not in a database file. The information is provided by other parameters on this command.
*DSTIDIDP: The interchange document profile (IDP) information associated with the distribution document is used. This is valid only when TYPE(*DSTID) is specified.
*DOCFILE: The interchange document profile is in the same file as the document. A member specified in the IDPMBR parameter is ignored.
The name of the database file can be qualified by one of the following library values:
*LIBL: All libraries in the job's library list are searched until the first match is found.
*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.
library-name: Specify the name of the library to be searched.
database-file-name: Specify the name of the database file that contains the interchange document profile. More information on defining the format of database files (output files) is in the Database Programming topic in the Information Center.
- IDPMBR
- Specifies the interchange document file member name to send. This parameter is valid only when IDPFILE(database-file-name) is specified.
*FIRST: The first member (based on creation date) in the database file is sent.
member-name: Specify the name of the database file member to be sent.
- DOCD
- Specifies a description for the document being distributed. This is the Document Interchange Architecture IDP document name field.
*DFT: The system creates a document description for database files. The default is library-name/file-name/member-name. For a description of a printed document (TYPE(*IDP)), the default is the distribution description. For a description of a distribution document (TYPE(*DSTID)), the default is the document description associated with the distribution.
*DSTD: The distribution description is used for the document name.
'document-description': Specify up to 44 characters for the description of the document.
- AUTHOR
- Specifies the authors of the document.
*NONE: No author is identified for the document.
*USRID: The user ID and address of the user who is requesting the distribution is used as the author's name.
'document-author': Specify the name of the authors. Up to 50 authors can be specified.
- DOCCLS
- Specifies the class associated with this document, such as MEMO, FORM, or SHEET.
*NONE: No class is assigned to the document.
'document-class': Specify the document class. Up to 16 characters can be specified.
- KWD
- Specifies the keywords that can be used to describe the document.
*NONE: No keywords are defined for this document.
'document-keyword': Specify the keywords to use to describe the document. Up to 50 keywords can be specified and each keyword can have up to 60 characters.
- SUBJECT
- Specify the subjects of the document.
*NONE: No subjects are defined for the document.
*DOCD: The document description is used as the subject for the document.
'document-subject': Specify the subjects of the document. Up to 50 subjects can be specified and each subject can have up to 60 characters of text.
- DOCDATE
- Specifies the date the user wants to assign to the document.
*NONE: No date is assigned to the document.
*CURRENT: The current date is used.
document-date: Specify the value used as the document date. The date must be in the format specified by the system value QDATFMT.
- FILCAB
- Specifies the location of the document. This parameter is intended for printed documents. The interchange document profile, which refers to the printed document, is distributed. This parameter is required if TYPE(*IDP) and IDPFILE(*NONE) are specified.
*NONE: No filing cabinet reference is defined for this document.
'filing-cabinet-reference': Specify the text that describes where the printed document is located. Up to 60 characters can be specified.
- CPYLST
- Specifies names of the users who receive this distribution.
*NONE: No copy list is included for this distribution.
'recipient-list': Specify the names of the users who receive the document. Up to 50 names can be specified and each name can have up to 60 characters.
- EXPDATE
- Specifies the date on which the document is no longer needed.
*NONE: No expiration date is specified.
expiration-date: Specify the value to use as the expiration date. The date must be specified in the format specified by the system value QDATFMT.
- CRTDATE
- Specifies the creation date of the object.
*NONE: A document creation date is not specified.
*CURRENT: The current date is used.
create-date: Specify the document creation date. The date must be in the format specified by the system value QDATFMT.
- REFERENCE
- Specifies a reference associated with the document.
*NONE: No reference field is included in the interchange document profile.
'reference': Specify the text that describes the reference associated with the document. Up to 60 characters can be used.
- ACTDATE
- Specifies the due date for the requested action. If no action due date is specified and a reply request date is specified the action due date is set from the reply request date.
*NONE: No action due date is specified.
*CURRENT: The current date is used.
action-due-date: Specify the value used as the action due date. The date must be specified in the format specified by the system value QDATFMT.
- RPYDATE
- Specifies the date and time a reply to the distribution is requested. This applies only to primary recipients.
Element 1: Reply by Date
*NONE: No reply is required.
*CURRENT: The current date is used. The time will default to *ENDOFDAY and will be set to 23:59:59.
*ANY: A reply is requested but no date and time are specified.
reply-by-date: Specify the value used as the reply requested date. The date must be specified in the format specified by the system value QDATFMT.
Element 2: Reply by Time
*ENDOFDAY: A reply is requested by the end of the specified date. The time is set to 23:59:59.
reply-by-time: Specify the value used as the reply requested time.
The time is specified in 24-hour format and can be specified with or without a time separator.
Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where hh=hours, mm=minutes, and ss=seconds. Valid values for hh range from 00 to 23. Valid values for mm and ss range from 00 to 59.
With a time separator, specify a string of 5 or 8 digits (hours and minutes, or hours, minutes, and seconds). The time separator specified by the system value QTIMSEP is used to separate the hours, minutes, and seconds. If the command is entered from the command line, the string must be entered in apostrophes. If a time separator other than the separator used for your job is used, the command fails. Valid values for hh range from 00 to 23. Valid values for mm and ss range from 00 to 59.
- STATUS
- Specifies the user-defined status (In Process, Pending Approval, or Retired).
*NONE: No status is included in the interchange document profile.
'status-of-document': Specify text that describes the status of the document. Up to 20 characters can be specified.
- CMPDATE
- Specifies the completion date for the requested action.
*NONE: No completion date is specified.
*CURRENT: The current date is used.
date-complete: Specify the completion date. The date must be in the format specified by the system value QDATFMT.
- PROJECT
- Specifies the project with which the document is associated.
*NONE: No project field is included in the interchange document profile.
'project': Specify text that describes the project of the document. Up to 10 characters can be specified.
- DOCCHRID
- Specifies the character identifier (graphic character set and code page) for the data being distributed. The character identifier is related to the display device that was used to create the data being distributed. More information about CHRID processing is in the Database Programming topic in the Information Center.
*SYSVAL: The system determines the graphic character set and code page values for the command parameters from the QCHRID system values.
*DEVD: The system determines the graphic character set and code page values for the command parameter from the display device description where the command is entered. This option is valid only when specified from an interactive job. If this value is specified in an interactive CL program or a batch job, an error message is sent.
Element 1: Character Set
graphic-character-set: Specify the graphic character set values to use for creating the data being distributed.
Element 2: Code Page
code-page: Specify the code page value used to create the command parameters. Valid values range from 1 through 999.
- CMDCHRID
- Specifies the character identifier (graphic character set and code page) for data being specified as parameter values on this command. This character identifier (CHRID) is related to the display device used to specify the command. More information about CHRID processing is in the Application Display Programming
book.
Note: The CMDCHRID parameter applies to the following parameters and means in some cases that the data is translated to a code page and character set that is interchangeable with other IBM office products. The interchangeable character set and code page is '697 500' except for USRID, TOUSRID, and DSTID which are '930 500'. In other cases, the code page and character set are attached to the field and sent with it to allow the receiving terminal to correctly print and display the field. Parameter Translate TOUSRID Translated USRID Translated DSTID Translated SYSCOD Translated MSG Translated DOCD Passed DSTD Translated AUTHOR Passed DOCCLS Passed KWD Passed SUBJECT Passed FILCAB Passed CPYLST Passed REFERENCE Passed STATUS Passed PROJECT Passed AUTUSR TranslatedThe value translates the USRID and DSTID parameter to character set and code page of '930 500'. The SNA Distribution Services book contains the character set and code page table for '930 500'.
*SYSVAL: The system determines the graphic character set and code page values for the command parameters from the QCHRID system values.
*DEVD: The system determines the graphic character set and code page values for the command parameter from the display device description where the command is entered. This option is valid only when specified from an interactive job. If this value is specified in an interactive CL program or a batch job, an error message is sent.
Element 1: Character Set
graphic-character-set: Specify the graphic character set values to use for creating the command parameter.
Element 2: Code Page
code-page: Specify the code page. Valid values range from 1 through 9999.
- DOCLANGID
- Specifies the language identifier being placed in this distribution document's interchange document profile (IDP). This parameter is ignored if the IDPFILE parameter is specified.
*JOB: The language identifier specified for the job in which this command is entered is used.
language-identifier: Specify the language identifier. More information on valid language identifiers is in the Globalization topic in the Information Center. More information on this parameter is in commonly used parameters.
- DOCCNTRYID
- Specifies the country or region identifier being placed in this distribution document's interchange document profile (IDP). This parameter is ignored if the IDPFILE parameter is specified.
*JOB: The country or region identifier specified for the job in which this command is entered is used.
country-identifier: Specify an ISO 3166 Alpha-2 code from the country or region code table. More information on this parameter is in commonly used parameters.
- ALWALTRCP
- Specify if the distribution can be delivered to an alternate recipient, determined by the receiving system. This function is used only by X.400 network systems. This function provides the ability to direct certain mail to a specific user.
The default of this field is *YES. However, because the user might change the sensitivity field to private, but might not change the alternate recipient field to no, he may send a private item to an alternate recipient. No error message will be generated for this condition.
*YES: Specifies the distribution can be delivered to an alternate recipient.
*NO: Specifies the distribution cannot be delivered to an alternate recipient.
- DISCLOSE
- Specifies whether or not each recipient gets a list of the other recipients.
*YES: Disclose recipients.
*NO: Do not disclose recipients.
- ALWX400CNV
- Specifies whether an X.400 conversion is allowed on the distribution being submitted. In certain circumstances, the end user knows the capabilities of the recipient and may indicate that the distribution is not to be converted. The system administrator can define whether or not conversion is to take place. This field allows the user to override that setting on a message by message basis. For example, if the gateway allows conversion, the user could specify that conversion is to be prohibited. This will take precedence over the gateway setting. The distribution would then not be converted.
Note: This field is valid only for X.400 support. This field will not affect iSeries 400 data stream transformations, such as RFT to FFTDCA. *YES: Conversion may be performed on the distribution by the receiving system.
*NO: No conversion is permitted on the distribution by the receiving system.
- AUTUSR
- Specifies the user ID and address of the user that authorized the content of this distribution. The authorizing user will receive a copy of the distribution.
*NONE: No authorizing user.
Element 1: User ID
user-ID: Specify the user ID of the user from whom the distribution is authorized.
Element 2: User Address
user-address: Specify the user address of the user from whom the distribution is authorized.
- DSTEXPDATE
- Specifies the date and time at which the distribution is no longer needed in the mail log.
Element 1: Distribution Expiration Date
*NONE: This distribution has no expiration date.
distribution-expiration-date: Specify the value to use as the expiration date. The date must be in the format specified by the system value QDATFMT.
Element 2: Distribution Expiration Time
ENDOFDAY: An expiration time is requested by the end of the specified date. The time will be set to 23:59:59.
distribution-expiration-time: Specify the value as the expiration time.
The time is specified in a 24-hour format and can be specified with or without a time separator.
Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where hh=hours, mm=minutes, and ss=seconds. Valid values for hh range from 00 to 23. Valid values for mm and ss range from 00 to 59.
With a time separator, specify a string of 5 or 8 digits (hours and minutes, or hours, minutes, and seconds). The time separator specified by the system value QTIMSEP is used to separate the hours, minutes, and seconds. If the command is entered from the command line, the string must be enclosed in apostrophes. If a time separator other than the separator used for your job is used, the command will fail. Valid values for hh range from 00 to 23. Valid values for mm and ss range from 00 to 59.
Examples for SNDDST
Example 1: Sending a Distribution on Behalf of Another User
SNDDST TYPE(*FILE) TOUSRID((JACKSON RCH38DB)) DOCTYPE(20000) SYSCOD(BRANDX) DOCFILE(DEPT46ELIB/XTEXT) DOCMBR(GOLD1IPFS) PTY(*HIGH) USRID(JACOBSON RCH38NBS) DSTD('IPFS FOR GOLD1 PROJECT') MSG('review and update section 1.2.4. return for final printing by 2/15/89') CFMDEL(*YES)This command sends a distribution that is being sent by someone (such as a secretary) who is authorized to work on behalf of JACOBSON. The document being sent is a BRANDX text document that is sent to another user who also has the BRANDX text processor.
Example 2: Sending a Mail Log Entry
SNDDST TYPE(*DSTID) DSTID('NEWYORK SMITH 0204') DSTIDEXN(02) TOUSRID((JACKSON RCH38DB)) MSG(*DSTIDMSG) CFMDEL(*YES)This command sends a mail log entry that is identified by the distribution document name NEWYORK SMITH 0204 that is distributed to user JACKSON at address RCH38DB. The message in the distribution document is distributed with the distribution.
Error messages for SNDDST
*ESCAPE Messages
- CPF8A87
- Document name &2 not correct.
- CPF8A97
- Folder name &1 not correct.
- CPF89AA
- *FINALFORM for send format (SNDFMT) valid only for *DOC for type (TYPE).
- CPF89AB
- Specify *IDP or *MSG for type (TYPE) only with *NOCHG for send format (SNDFMT).
- CPF900B
- User ID and address &1 &2 not in System Distribution Directory.
- CPF900C
- Sign on and verify of user failed.
- CPF901A
- Send distribution request failed.
- CPF903D
- Incorrect document identifier specified.
- CPF905C
- Error occurred trying to find a translation table.
- CPF9096
- Cannot use CMDCHRID(*DEVD), DOCCHRID(*DEVD) in batch job.
- CPF9845
- Error occurred while opening file &1.
- CPF9846
- Error while processing file &1 in library &2.
- CPF9847
- Error occurred while closing file &1 in library &2.