        CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 12-SEP-1990 13:48:27.69  To:	MRGATE::"ARISIA::EVERHART" CC:	, Subj:	"almost transparent" DECnet operations  * Received:  by crdgw1.ge.com (5.57/GE 1.73)) 	 id AA05180; Wed, 12 Sep 90 13:30:27 EDT / Message-Id:  <9009121730.AA05180@crdgw1.ge.com> U Received: From CUNYVM.CUNY.EDU by CRVAX.SRI.COM with TCP; Wed, 12 SEP 90 10:10:34 PDT x Received: from DGOGWDG5.BITNET by CUNYVM.CUNY.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 4931; Wed, 12 Sep 90 13:04:18 EDT) Date:    Wed, 12 Sep 1990 19:04:58  +0200 @ From: "GWDGV1::MOELLER"  <U0012%DGOGWDG5.BITNET@CUNYVM.CUNY.EDU> To: info-vax@sri.COM5 Cc: SOMEONE_ELSE@CRVAX.SRI.COM, MOELLER@CRVAX.SRI.COM / Subject: "almost transparent" DECnet operations   ?    I just discovered a sort of undocumented feature relating to   "transparent" DECnet operations.D    According to the manual, you "transparently" accept a DECnet linkE by OPENing `SYS$NET:'. The translation of this logical name contains, B among other things, the connect information (maximum of 16 bytes).N    As it turns out, you can modify this information (and strip the extra bytesK giving object information) and then OPEN - the modified information will be I returned to the requestor in the accept NCB (available only via mailbox). I    Somewhat analogous, connect information may be hidden in the task-spec F when requesting a "transparent" DECnet task-to-task link via RMS, like3         node::"task=name/<2 NULbytes><.ascic info>"   N    This way, it is possible to some extent to mix transparent operation on oneA side with non-transparent operation (e.g. DCL) on the other side. M    In particular, a DCL procedure can mimic MAIL_SERVER to the extent that it I may request and obtain a CC line, and (in principle) even "foreign" MAIL.   J Wolfgang J. Moeller, GWDG, D-3400 Goettingen, F.R.Germany | Disclaimer ...M Bitnet/Earn: U0012@DGOGWDG5         Phone: +49 551 201516 | No claim intended   