TRANSFER Programming Manual

NAME-CONTEXT
The XDIR Server
E–4 069138, Update 1 to 040970 Tandem Computers Incorporated
NAME-CONTEXT NAME-CONTEXT is included in the X400-TO-CORR and CORR-TO-X400 UOWs to
indicate to the XDIR server what type of name is referenced. You can program the
XDIR server to process different types differently; the gateway servers do not interpret
the names that are returned.
DEF NAME-CONTEXT.
05 CONTEXT-CODE type binary 16 unsigned. ! name context
88 P1-ORIGINATOR VALUE 0.
88 P1-RECIP VALUE 1.
88 P2-ORIGINATOR VALUE 2.
88 P2-PRIMARY VALUE 3.
88 P2-CC VALUE 4.
88 P2-BCC VALUE 5.
88 P2-AUTHORIZING VALUE 6.
88 P2-REPLY-TO VALUE 7.
88 REPORT-ORIGINATOR VALUE 8.
88 REPORT-RECIP VALUE 9.
88 REPORT-INTENDED-RECIP VALUE 10.
05 ITEM-ID type ITEM-ID.
05 PDU-ID pic X(10).
05 P1-MSG-ID.
10 LOCAL-ID pic X(32).
10 DOMAIN.
15 COUNTRY-LEN pic 9(4) comp.
15 ADMD-NAME-LEN pic 9(4) comp.
15 PRMD-NAME-LEN pic 9(4) comp.
15 COUNTRY pic X(4).
15 ADMD-NAME pic X(16).
15 PRMD-NAME pic X(16).
15 FLAGS.
20 COUNTRY-IS-X121 pic X(1).
20 ADMD-IS-NUMERIC pic X(1).
20 PRMD-IS-NUMERIC pic X(1).
20 RESERVED-3 pic X(1) value "N".
20 RESERVED-4 pic X(1) value "N".
20 RESERVED-5 pic X(1) value "N".
20 RESERVED-6 pic X(1) value "N".
20 RESERVED-7 pic X(1) value "N".
05 P2-LOCAL-ID pic X(64).
END.
The CONTEXT-CODE field is always defined. The other fields can be undefined (all
zero bytes) if the gateway server has not yet encountered the relevant information.
For example, the P2-LOCAL-ID is unknown when the Importer is translating the P1 of
a message. The Importer processes the P1 before the P2; the Exporter builds the P2
before the P1.