ORDER, and ORNAME X488. 2.$ PMDF TEST/X400/X484 X400> ... X400> EXIT This example shows how to invoke the PMDF TEST/X400 utility for testing X.400-1988 address transformations, and then exit the utility with the EXIT command. Specifying the /X484 qualifier will cause use of the following defaults: DATABASE X400, RHS_ ORDER, and ORNAME X484. 3.$ PMDF TEST/X400/MB400 X400> ... X400> EXIT This example shows how to invoke the PMDF TEST/X400 utility for testing Mailbus 400 (X.400-1988) address transformations using PMDF-MB400's own special TO_MB400 and FROM_MB400 databases, and then exit the utility with the EXIT command. Specifying the /MB400 qualifier will cause use of the following defaults: DATABASE X400 (but using the TO_MB400 and FROM_MB400 databases rather than the default TO_X400 and FROM_X400 databases), RHS_ ORDER, and ORNAME X488. 4.$ PMDF TEST/X400/MR X400> ... X400> EXIT This example shows how to invoke the PMDF TEST/X400 utility for testing Message Router address transformations, and then exit the utility with the EXIT command. Specifying the /MR qualifier will cause use of the following defaults: DATABASE MR, LHS_ ORDER, and ORNAME MR. 5.$ PMDF TEST/X400/MRIF X400> ... X400> EXIT This example shows how to invoke the PMDF TEST/X400 utility for testing Message Router address transformations using PMDF-MR's MRIF channel special TO_MRIF and FROM_MRIF databases, and then exit the utility with the EXIT command. Specifying the /MRIF qualifier will cause use of the following defaults: DATABASE MR (but using the TO_MRIF and FROM_MRIF databases rather than the default TO_MR and FROM_MR databases), LHS_ORDER, and ORNAME MR. 4 Interactive_Commands 5 DECODE 6 DDRFC822 Decode X.400 DD.RFC822Cn attributes into a DD.RFC-822 attribute. Syntax DECODE DDRFC822 dd.rfc-822c-avpl Command Qualifiers Defaults None. None. 7 Parameters dd.rfc-822-avpl A DD.RFC-822 and DD.RFC822Cn attribute value pair list. 7 Description X.400 Domain Defined Attribute values are limited to a maximum of 128 characters. Internet addresses are normally "embedded" into an X.400 address by representing the Internet address using the X.400 DD.RFC-822 attribute; but since Internet addresses may be longer than the X.400 DDA value limit, a single DD.RFC- 822 attribute value may not be able to contain an entire long Internet address. To handle this case, three additional "continuation" DDA's have been defined, DD.RFC822C1, DD.RFC822C2, and DDRFC822C3. A single Internet address may be split among these four DDA's, thus allowing Internet addresses of up to 512 characters to be embedded into an X.400 address. The DECODE DDRFC822 command decodes an AVPL of X.400 DD.RFC-822 plus continuation DD.RFC822Cn attributes into a single DD.RFC-822 attribute. 7 Examples $ PMDF TEST/X400 X400> DECODE DDRFC822 "/DD.RFC- 822=amy.adams(a)example/DD.RFC822C1=.com/" Result: /DD.RFC-822=amy.adams(a)example.com/ This example shows decoding a DD.RFC-822 and a DD.RFC822C1 attribute into a single DD.RFC-822 attribute. 6 PERSONAL Decode an X.400 Personal Name (PN) value into individual component attributes. Syntax DECODE PERSONAL pn-value Command Qualifiers Defaults None. None. 7 Parameters pn-value A Personal Name (PN) value. 7 Description Decode an X.400 Personal Name (PN) value into corresponding individual component attributes. 7 Examples This example shows decoding a Personal Name value into its constituent Surname, Initials, and Given name attribute value pairs. $ PMDF TEST/X400 X400> DECODE PERSONAL "Amy.B.Carlson" Result: /S=Carlson/I=B/G=Amy/ 5 DUMP 6 BER Dump (decode) an X.400 BER-encoded message file. Syntax DUMP BER p1-file-spec Command Qualifiers Defaults None. None. 7 Parameters p1-file-spec The X.400 P1 file to be dumped. 7 Description Dump (decode) an X.400 BER-encoded message file. 7 Examples The following example shows dumping the contents of an outgoing X.400 message file. $ PMDF TEST/X400 X400> DUMP BER PMDF_QUEUE:[X400_LOCAL]ZZ01INYJFBUHWY94G5ZD.P1 CONTEXT CONSTRUCTOR 0 (indefinite length) UNIVERSAL CONSTRUCTOR SET (indefinite length) APPLICATION CONSTRUCTOR 4 57 APPLICATION CONSTRUCTOR 3 21 APPLICATION CONSTRUCTOR 1 4 UNIVERSAL PRIMITIVE PRINTABLESTRING 2 7375 us 0000 APPLICATION CONSTRUCTOR 2 5 UNIVERSAL PRIMITIVE PRINTABLESTRING 3 696969 iii 0000 UNIVERSAL PRIMITIVE PRINTABLESTRING 6 6569 6277656e newbie 0000 UNIVERSAL PRIMITIVE IA5STRING 32 30303047 5845575a 51304a4f 4931303c <01IOJ0QZWEXG000 0000 534f4e4e 492e4549 4257454e 4039564d MV9@NEWBIE.INNOS 0010 APPLICATION CONSTRUCTOR 0 36 ... 6 FILE Dump (decode) a binary file. Syntax DUMP FILE file-spec Command Qualifiers Defaults /DECIMAL /HEXADECIMAL /HEXADECIMAL /HEXADECIMAL /OCTAL /HEXADECIMAL 7 Parameters file-spec The file to dump. 7 Description Dump the bytes of a file. 7 Command_Qualifiers /DECIMAL /DECIMAL /HEXADECIMAL (default) /OCTAL By default, DUMP FILE's output is displayed in hexadecimal. The /OCTAL qualifier may be used to cause the output to be displayed in octal; the /DECIMAL qualifier may be used to cause the output to be displayed as base 10 (decimal) integer values. 7 Examples This example shows dumping the bytes of a sample WordPerfect document. $ PMDF TEST/X400 X400> DUMP FILE SAMPLE.WPC 00000000 01000a01 000000d7 435057ff .WPC............ 0000 00000010 00060000 00000032 0005fffb ....2........... 0010 00110000 00520000 005a000c 00000042 B.....Z...R..... 0020 00d50000 00020008 000000ac 00000029 )............... 0030 00000000 00020000 0078007c 23080000 ...#|.x......... 0040 00000000 00005350 33524553 414c0000 ..LASER3PS...... 0050 00000000 00000000 00000000 00000000 ................ 0060 2e303252 50555449 44000000 00000000 .......DITUPR20. 0070 00000a8c 170c1e14 007801db 00535250 PRS...x......... 0080 01680168 00010001 cf8700c9 40110400 ...@........h.h. 0090 ffffffff 40025852 bc1b12f0 01680168 h.h.....RX.@.... 00a0 3a524944 31355254 50245052 4f435057 WPCORP$PTR51DIR: 00b0 5352445f 31355254 505f5052 4f435057 WPCORP_PTR51_DRS 00c0 61207369 20736968 54000000 5352442e .DRS...This is a 00d0 66726550 64726f57 20656c70 6d617320 sample WordPerf 00e0 746e656d 75636f64 20312e35 20746365 ect 5.1 document 00f0 0258003f 00890600 000c01d4 0a0a0a2e ............?.X. 0100 746e6573 20736968 54c30cc3 d401000c .......This sent 0110 c42e6465 646c6f62 20736920 65636e65 ence is bolded.. 0120 746e6573 20736968 54c30ec3 0a0ac40c .......This sent 0130 6e696c72 65646e75 20736920 65636e65 ence is underlin 0140 00890600 000c01d4 0a0ac40e c42e6465 ed.............. 0150 20736968 54c308c3 d401000c 0578003f ?.x........This 0160 6c617469 20736920 65636e65 746e6573 sentence is ital 0170 0a0ac408 c42e6465 7a696369 icized...... 0180 6 NBS Dump (decode) a Message Router NBS message file. Syntax DUMP NBS nbs-file-spec Command Qualifiers Defaults None. None. 7 Parameters nbs-file-spec The NBS file to be dumped. 7 Description Dump (decode) a Message Router NBS message file. 7 Examples The following example shows dumping the contents of an NBS message file. $ PMDF TEST/X400 X400> DUMP NBS MR$NBS:MR1234.NBS message (qualifier 20) (length 24b) field (qualifier message-id) (length 1d) ascii (length 1b) Block number 0 (00000000), 27 (001b) bytes 312f3139 39373130 31333133 30373430 04703131017991/1 0000 445255 47495340 38333432 2438@NAPLES 0010 field (qualifier posted-date) (length 12) date (length 10) ascii (length 0e) Block number 0 (00000000), 14 (000e) bytes 3034 37303331 33313031 37393931 19971013130740 0000 ... 5 ENCODE 6 DDRFC822 Encode a long X.400 DD.RFC-822 attribute into continuation attributes. Syntax ENCODE DDRFC822 dd.rfc-822-attribute-value-pair Command Qualifiers Defaults None. None. 7 Parameters dd.rfc-822-attribute-value-pair A DD.RFC-822 attribute value pair. 7 Description X.400 Domain Defined Attribute values are limited to a maximum of 128 characters. Internet addresses are normally "embedded" into an X.400 address by representing the Internet address using the X.400 DD.RFC-822 attribute; but since Internet addresses may be longer than the X.400 DDA value limit, a single DD.RFC- 822 attribute value may not be able to contain an entire long Internet address. To handle this case, three additional "continuation" DDA's have been defined, DD.RFC822C1, DD.RFC822C2, and DDRFC822C3. A single Internet address may be split among these four DDA's, thus allowing Internet addresses of up to 512 characters to be embedded into an X.400 address. The ENCODE DDRFC822 command encode a "long" X.400 DD.RFC-822 attribute value-one with more than 128 characters into the value-into a DD.RFC-822 attribute plus continuation DD.RFC822Cn attributes. 6 PERSONAL Encode X.400 attributes into X.400 Personal Name (PN), Free Form name (FFN), and Telephone Number (TN) values. Syntax ENCODE PERSONAL avpl Command Qualifiers Defaults None. None. 7 Parameters avpl An attribute value pair list. 7 Description Encode an X.400 Attribute Value Pair List into Personal Name (PN), Free Form Name (FFN), and Telephone Number (TN) values. 7 Examples This example shows encoding X.400 Surname, Given name, Initials, Telephone Number, and Free Form Name attributes. $ PMDF TEST/X400 X400> ENCODE PERSONAL "/S=Last/I=I/G=First/TN=123-4567/FFN=nick name" Result: First.I.Last Free form: nick name Telephone number: 123-4567 5 EXIT Exit the PMDF TEST/X400 utility. Syntax EXIT Command Qualifiers Defaults None. None. 6 Parameters None. 6 Description The EXIT and QUIT commands exit the PMDF TEST/X400 utility. 5 HELP Obtain help on the use of PMDF TEST/X400. Syntax HELP Command Qualifiers Defaults None. None. 6 Parameters None. 6 Description The HELP command may be used to display a list of the available commands in PMDF TEST/X400. 5 QUIT Exit the PMDF TEST/X400 utility. Syntax QUIT Command Qualifiers Defaults None. None. 6 Parameters None. 6 Description The EXIT and QUIT commands exit the PMDF TEST/X400 utility. 5 SET 6 DATABASE Specify the sort of databases to use for address transformations. Syntax SET DATABASE keyword Command Qualifiers Defaults None. None. 7 Parameters keyword Required value of either MR, specifying Message Router databases, or X400, specifying X.400 databases. 7 Description The SET DATABASE command sets which sort of databases to use for address transformations. SET DATABASE MR specifies that PMDF-MR databases will be used; namely, the TO_MR and FROM_MR databases will be used, unless PMDF TEST/X400 was invoked with the /MRIF qualifier in which case TO_MRIF and FROM_MRIF databases will preferentially be used. SET DATABASE X400 specifies that PMDF-X400/PMDF-MB400 databases will be used; namely, the TO_X400 and FROM_X400 databases will be used, unless PMDF TEST/X400 was invoked with the /MB400 qualifier in which case TO_MB400 and FROM_MB400 databases will preferentially be used. Note that invoking PMDF TEST/X400 with a qualifier such as /MR, /MRIF, /X484, /X488, or /MB400, sets other defaults appropriately, in addition to the databases. Thus it is simpler to invoke PMDF TEST/X400 with appropriate qualifiers from the beginning, rather than manually setting the database from within PMDF TEST/X400. 6 DEBUG Control display of debug output. Syntax SET DEBUG SET NODEBUG Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description The SET DEBUG and SET NODEBUG commands may be used to enable and disable, respectively, detailed debug output regarding the operation of PMDF TEST/X400's other commands. 7 Examples This example shows enabling debugging to see details of an address transformation. $ PMDF TEST/X400/X488 X400> TRANSLATE AVPL "/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Widgets /S=Borg/G=Bob/ Result: Bob.Borg@x400.example.com X400> SET DEBUG X400> TRANSLATE AVPL "/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Widgets /S=Borg/G=Bob/ 15:38:55.13: Rewrite: "$I" - $I$&0$W$&1$M$&2$M$&3$H$&4$X$&5$X$&6$X$TINI|" [OK] 15:38:55.13: Rewrite: "INI|/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Wi dgets/S=Borg/G=Bob/" - failed 15:38:55.13: Rewrite: "INI|/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Wi dgets/S=Borg/G=*/" - failed 15:38:55.13: Rewrite: "INI|/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Wi dgets/S=Borg" - failed 15:38:55.13: Rewrite: "INI|/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Wi dgets/S=*/G=*/" - failed 15:38:55.13: Rewrite: "INI|/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Wi dgets/S=*" - failed 15:38:55.13: Rewrite: "INI|/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Wi dgets" - $N$O$&3example.com$TLOC|" [OK] 15:38:55.13: Rewrite: "LOC|/S=Borg/G=Bob/" - failed 15:38:55.13: Rewrite: "LOC|/S=Borg/G=*/" - failed 15:38:55.14: Rewrite: "LOC|/S=Borg" - failed 15:38:55.14: Rewrite: "LOC|/S=*/G=*/" - failed 15:38:55.14: Rewrite: "LOC|/S=*" - failed 15:38:55.14: Material remaining after rules: /S=Borg/G=Bob/ 15:38:55.14: Attempting to rewrite as personal name. 15:38:55.14: Rewrite: "LOC|$N" - $&1$U$TFFN|" [OK] Result: Bob.Borg@example.com 6 ENVELOPE Treat addresses as envelope addresses. Syntax SET ENVELOPE SET HEADER Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description Note that some PMDF-X400 and PMDF-MR address transformations are envelope or header specific. The SET ENVELOPE and SET HEADER commands may be used to control whether address transformations assume addresses are envelope addresses or header addresses. Header addresses are assumed by default. See also SET HEADER. 6 FORWARD Treat addresses as forward pointing addresses. Syntax SET FORWARD SET REVERSE Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description Note that some PMDF-X400 and PMDF-MR address transformations are specific to either forward pointing or backward point addresses. The SET FORWARD and SET REVERSE commands may be used to control whether address transformations assume addresses are forwarding point or reverse pointing. Reverse pointing addresses are assumed by default. See also SET REVERSE. 6 HEADER Treat addresses as header addresses. Syntax SET HEADER SET ENVELOPE Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description Note that some PMDF-X400 and PMDF-MR address transformations are envelope or header specific. The SET ENVELOPE and SET HEADER commands may be used to control whether address transformations assume addresses are envelope addresses or header addresses. Header addresses are assumed by default. See also SET ENVELOPE. 6 LHS_ORDER Interpret local mailbox parts in left-to-right order. Syntax SET LHS_ORDER SET RHS_ORDER Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description The order in which to interpret attributes in the local mailbox portion of an RFC 822 address may be controlled with the SET LHS_ ORDER and SET RHS_ORDER commands. The proper interpretation order is dependent upon the sort of address under consideration; RHS_ ORDER is usually proper for X.400 addresses, whereas LHS_ORDER is usually proper for Message Router addresses. The qualifiers with which PMDF TEST/X400 was invoked may set a default ordering. See also SET RHS_ORDER. 6 LOCALHOST Syntax SET LOCALHOST host-name Command Qualifiers Defaults None. None. 7 Parameters host-name The local host name as far as address transformations are concerned; e.g., the name of the PMDF system itself. 7 Description If it is made known to the PMDF TEST/X400 utility, the utility will use the local host name for certain address transformation purposes, such as "fixing up" bare usernames presented as putative RFC 822 addresses. 7 Examples The following example illustrates how setting LOCALHOST can allow PMDF TEST/X400 to "fix up" bare usernames and thereby allow address transformation. The example assumes a PMDF-MR configuration where MILAN is the PMDF-MR node, and PMDF is the PMDF MRMAN mailbox name. $ PMDF TEST/X400/MR X400> TRANSLATE 822_TO_AVPL system Syntax error. X400> SET LOCALHOST example.com X400> TRANSLATE 822_TO_AVPL system Result: R 0 MILAN R 0 PMDF R 0 example.com U 0 system FFN 0 system 6 ORNAME Specify the set of valid attribute names to use for address transformations. Syntax SET ORNAME keyword Command Qualifiers Defaults None. None. 7 Parameters keyword Required value of one of DOC, FAX, MHS, MR, X484, or X488. 7 Description The SET ORNAME command sets which set of attribute names will be valid for address transformations. SET ORNAME MR specifies that Message Router attribute names will be used. SET ORNAME X484 specifies that X.400-1984 attribute names will be used. SET ORNAME X488 specifies that X.400-1988 attribute names will be used. Note that invoking PMDF TEST/X400 with a qualifier such as /MR, /MRIF, /X484, /X488, or /MB400, sets other defaults appropriately, in addition to the ORNAME set. Thus it is simpler to invoke PMDF TEST/X400 with appropriate qualifiers from the beginning, rather than manually setting the ORNAME set from within PMDF TEST/X400. 6 REVERSE Treat addresses as reverse pointing addresses. Syntax SET REVERSE SET FORWARD Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description Note that some PMDF-X400 and PMDF-MR address transformations are specific to either forward pointing or backward point addresses. The SET FORWARD and SET REVERSE commands may be used to control whether address transformations assume addresses are forwarding point or reverse pointing. Reverse pointing addresses are assumed by default. See also SET FORWARD. 6 RHS_ORDER Interpret local mailbox parts in right-to-left order. Syntax SET RHS_ORDER SET LHS_ORDER Command Qualifiers Defaults None. None. 7 Parameters None. 7 Description The order in which to interpret attributes in the local mailbox portion of an RFC 822 address may be controlled with the SET LHS_ ORDER and SET RHS_ORDER commands. The proper interpretation order is dependent upon the sort of address under consideration; RHS_ ORDER is usually proper for X.400 addresses, whereas LHS_ORDER is usually proper for Message Router addresses. The qualifiers with which PMDF TEST/X400 was invoked may set a default ordering. See also SET LHS_ORDER. 6 STYLE Set command line style. Syntax SET STYLE keyword Command Qualifiers Defaults None. None. 7 Parameters keyword Required value of one of DEFAULT, UNIX, VMS. 7 Description The SET STYLE command sets the command line style; i.e., whether command qualifiers are specified with slashes or dashes. 5 TEST 6 NUMERIC Test whether all characters in a string are decimal digits. Syntax TEST NUMERIC string Command Qualifiers Defaults None. None. 7 Parameters string String whose characters to test. 7 Description The TEST NUMERIC command checks whether or not the characters in a string are decimal digits. Test whether all characters in a string are printable-string characters. Syntax TEST PRINTABLE string Command Qualifiers Defaults None. None. 7 Parameters string String whose characters to test. 7 Description The TEST PRINTABLE command checks whether or not the characters in a string are all printable-string characters. 7 Examples This example shows checking one string that does consist entirely of printable string characters, "abc", and another string that does not, "ab@". $ PMDF TEST/X400 X400> TEST PRINTABLE abc Yes X400> TEST PRINTABLE ab@ No 6 TRACE Test whether an X.400-Received: header value contains properly formatted X.400 trace information. Syntax TEST TRACE string Command Qualifiers Defaults None. None. 7 Parameters string String to try interpreting as the value of an X.400-Received: header line. 7 Description The TEST TRACE command checks whether the supplied string, interpreted as an X400-Received: header value, contains properly formatted X.400 trace information. 7 Examples This example shows checking that the header X400-Received: by /PRMD=PROCESS/ADMD=III/C=US/; Relayed; Fri, 15 Nov 2012 15:01:44 -0700 indeed contains syntactically valid X.400 trace information. $ PMDF TEST/X400 X400> TEST TRACE " by /PRMD=PROCESS/ADMD=III/C=US/; Relayed; Fri, 15Nov 2012 15:01:44 -0700" Result after decode/encode: by /PRMD=PROCESS/ADMD=III/C=US/; Relayed; Fri, 15 Nov 2012 15:01:44 -0700 5 TRANSLATE 6 822_TO_AVPL Translate an RFC 822 address to AVPL form. Syntax TRANSLATE 822_TO_AVPL rfc822-address Command Qualifiers Defaults None. None. 7 Parameters rfc822-address RFC 822 (Internet) address. 7 Description The TRANSLATE 822_TO_AVPL command translates a specified RFC 822 address into AVPL form, using the address transformation database currently in effect and the LHS_ORDER/RHS_ORDER ordering currently in effect. 7 Examples This example illustrates the transformation of an RFC 822 address to X.400 format, assuming that PMDF-X400 is configured with x400.example.com as its pseudodomain name. $ PMDF TEST/X400/X488 X400> SET ENVELOPE X400> SET FORWARD X400> TRANSLATE 822_TO_AVPL """/C=US/ADMD=TELCO/PRMD=Big Corp/S=Adamson/ G=Bob/""@x400.example.com" Result: C 0 US ADMD 0 TELCO PRMD 0 Big Corp S 0 Adamson G 0 Bob 6 ASCII_TO_PRINTABLESTRING Translate an ASCII string to a printable-string encoding of the string. Syntax TRANSLATE ASCII_TO_PRINTABLESTRING string Command Qualifiers Defaults None. None. 7 Parameters string An ASCII string. 7 Description The TRANSLATE ASCII_TO_PRINTABLESTRING command translates an ASCII string to a printable-string, using the multi-character substitutions specified in RFC 2156 for ASCII characters that have no printable-string equivalent. 7 Examples This example illustrates the transformation of the ASCII string "First Last"@example..com to a printable-string version of the string. Note that ASCII string corresponds to a rather common form of Internet address. But such a string cannot be literally represented in an X.400 address (if for instance one wants to embed this address using the DD.RFC-822 X.400 attribute), since the quote character and at character are not printable-string characters-such characters have to be encoded, as with the RFC 2156 multi- character substitutions. $ PMDF TEST/X400/X488 X400> TRANSLATE ASCII_TO_PRINTABLE """First Last""@example.com" Result: (q)First Last(q)(a)example.com 6 AVPL_TO_822 Translate an AVPL to an RFC 822 address. Syntax TRANSLATE AVPL_TO_822 avpl Command Qualifiers Defaults None. None. 7 Parameters avpl An Attribute Value Pair List (AVPL). 7 Description The TRANSLATE AVPL_TO_822 command translates an AVPL representation of an address to an RFC 822 (Internet) address, using the address transformation database currently in effect, and the LHS_ORDER/RHS_ORDER currently in effect. 7 Examples This example illustrates transforming a Message Router address of Ann Adams@A1@MILAN to an RFC 822 equivalent, assuming PMDF-MR has been configured to associate the A1 Message Router mailbox on the node MILAN with the pseudodomain name a1.example.com. $ PMDF TEST/X400/MR X400> set envelope X400> set forward X400> TRANSLATE AVPL_TO_822 "/R=MILAN/R=A1/U=Ann Adams" Result: "Ann Adams"@a1.example.com 6 OID Translate an OID to a descriptive sequence. Syntax TRANSLATE OID oid Command Qualifiers Defaults None. None. 7 Parameters oid An OID. 7 Description The TRANSLATE OID command converts an OID-dot separated sequence of integers - into descriptive text. 7 Examples This example shows obtaining a description of the OID for an X.400 File Transfer Body Part containing a PostScript attachment. $ PMDF TEST/X400 X400> TRANSLATE OID 1.3.6.1.7.1.2.1.2 Result: iso(1) identified-organization(3) dod(6) iana(1) mail(7) mixer(1) bodies (2) bp-data(1) postscript(2) 6 PRESENTATION_TO_AVPL Translate an X.400 presentation address to AVPL form. Syntax TRANSLATE PRESENTATION_TO_AVPL presentation-address 7 Parameters presentation-address An X.400 presentation address, e.g., "c=us; admd=teleco; prmd=Example; o=Engineering; ou=Widgets; S=Brown; G=Bob;". 7 Description The TRANSLATE PRESENTATION_TO_AVPL command transforms an X.400 presentation address-the sort that may be seen on a business card, for instance-into a canonical AVPL form. 7 Examples The following example shows transforming an X.400 presentation address into AVPL form, and then transforming the AVPL form into RFC 822 form (assuming a PMDF-X400 configuration as shown in the example in the appropriate edition of the PMDF Installation Guide). X400> TRANSLATE PRES "C=US; ADMD=GALACTIMAIL; PRMD=Example Corp; O=R and D; OU=Widg ets; S=Borg; G=Bob; Result: /C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Widgets/S=Borg/G=Bob/ X400> TRANSLATE AVPL "/C=US/ADMD=GALACTIMAIL/PRMD=Example Corp/O=R and D/OU=Widgets /S=Borg/G=Bob/ Result: Bob.Borg@x400.example.com 2 VERSION Print PMDF version number. Syntax PMDF VERSION Command Qualifiers Defaults None. None. 3 Restrictions None. 3 Parameters None. 3 Description VERSION prints out the PMDF installed version number, and displays the system's architecture type and operating system version number. 3 Examples To check what version of PMDF you are running, issue the command: $ PMDF VERSION %PMDF-I-VERSION, PMDF version is PMDF V6.6 AlphaServer 4X00 5/466 4MB running OpenVMS Alpha V8.3 PMDF_SHARE_LIBRARY version V6.6; linked 13:06:23, Feb 4 2012 2 convert_cache.com Perform a CONVERT/RECLAIM operation on the queue cache database. Syntax @PMDF_COM:convert_cache.com 3 Description The CONVERT_CACHE.COM utility performs a CONVERT/RECLAIM operation on the queue cache database. If you encounter difficulties with the queue cache database which a CACHE/SYNCHRONIZE command does not resolve, using this utility should be your next step. 3 Examples To convert the queue cache database issue the command $ @PMDF_COM:convert_cache.com 2 migrate UNIX-style command utility to copy folders of messages from one system running an IMAP server to another system running an IMAP server. See the PMDF User's Guide for details.