  Network communications via mailboxes? 
 The Question is:
 
Hallo Wiz,
I have a dbl (Formerly VAX DIBOL) that does
a sys$crembx and thereafter writes to a
mailbox denoted by the logical FRED_MBX
"DEFINE FRED_MBX MBA2:"
 
The above situation works!
 
If i then redefine the logical to ;-
DEFINE FRED AXPZ"USERNAME PASSWORD"::MBA2:
 
I GET Invalid device name!
 
There is no net$server.log created on the target
node. (decnet/osi)
 
I do an open en write with dcl and this works
both locally and remotely.
 
Please could you let me know the following;
a. should this work
b. what am i doing wrong
Thankyou In advance,
Wim
 
Note: A college has made the same program in
DEC C and the result is the same. Please Help
because the functionality is important for a client
 
ps.ps YES i did know that mba2 is for OPCOM but
since this system is for testing i didnt think
it would matter. My colleges use MBA3177 at
the moment with the SAME RESULTS...
Thanyou once again,
Wim.
 
 The Answer is:
 
  You will need to contact the customer support center for assistance
  with programming in DIBOL -- this language is not familiar to the
  OpenVMS Wizard.  Expect to be asked for a copy of the C or DIBOL
  source code for the errant program.
 
  Remote mailbox access as specified uses RMS and the FAL object, and
  the behaviour of RMS and FAL over DECnet does not exactly match the
  behaviour of a local mailbox accessed directly, and may not match a
  local mailbox accessed via RMS.  The Wizard favours accessing local
  mailboxes via sys$qio or sys$qiow calls, and not via RMS.  (The
  sys$crembx call does not support the specification of a node name.
  References to a remote mailbox can only be made via an RMS call,
  either made directly or indirectly, or via a remote application
  server process that acts as an intermediary.)
 
  Use of existing mailboxes associated with unrelated applications and
  unrelated protocols -- such as the MBA2: device -- can and will cause
  problems.  (This is one of the reasons why this MBA2: mailbox is
  protected against non-privileged access.)
 
  Remote access is not normally achieved using mailboxes via RMS FAL,
  the usual approaches for remote communications are ICC (V7.2 or later;
  within the same cluster), DECnet task-to-task, or IP sockets via
  sys$qio or sys$qiow calls to the IP driver or via the socket calls
  in the C library.
 
