|
Migration
Consideration
All Information Exchange customers using Expedite/Async
communication interface will have access to the new function.
Private and Organizational Alias Table Support
Previously, when sending EDI data, if any part of an alias
destination was specified on the +SEND command, all three
alias destination values had to be provided and the data
was treated as non-EDI data. If all three alias destination
values are provided on the +SEND command, the data is still
treated as non-EDI data. However, now when an incomplete
alias specification is provided, the missing values will
be determined from the EDI data header, and the data will
be treated as EDI data.
When the alias table type is not specified, it defaults
to G, and the Information Exchange global alias tables
are used.
When the alias table ID is not specified, it is determined
as follows:
For X12 and EDIFACT data, when only the alias table type
is specified, the alias table name is XNN where
X represents the EDI data type and NN is the
EDI receiver ID qualifier. For X12 data, the X value
is X, and for EDIFACT data, the X value is
E. Also, for EDIFACT data, only the first two characters
of the receiver ID qualifier are used for the NN
value. For UCS data, the table ID defaults to UCS.
For UNTDI data, the table ID defaults to UTD.
When an alias name is not specified, up to the first 16
bytes of the EDI receiver ID from the EDI data header is
used as the alias name.
The format of the +SEND command is as follows:
+SEND
{{{ SYSID(sys) } DESTACCT(account) DESTUID(userid) } |
{ LIST(listname) } |
{ ALSTBLTYP(tbltype) ALSTBLID(tblid) ALSNAME(aliasname)}
|
{ ALSTBLTYP(tbltype) ALSTBLID(tblid) } |
{ ALSTBLTYP(tbltype) } |
{ ALSTBLID(tblid) } |
{ ALSNAME(aliasname)}
{USERCLASS(userclass) }
{MSGNAME(msgname) }
{MSGSEQN(msgseqn) }
{MSGCLASS(blank|P|I) }
{MSGCHRG(1|2|3|4|5|6) }
{ACK(blank|R|D|B|A|C|E|F) }
{BINARY(blank|Y|N) }
{PROTOCOL(XMODEM|1KXMODEM|YMODEM|ZMODEM)}
{DELIMITER(blank|CRLF) }
{FILENAME(filename) }
{FILELOC(fileloc) }
;
|
