Conference rocks::dec_edi

The way the DEC/EDI process are created means that they will not benefit
from the raised enqlm even if the DECEDI account enqlm quota is set to
32767.


We will shortly produce a patched DECEDI$STARTUP.EXE that does permit
processes to recieve the new quota.


Note: the most inmportant process to receive the new quota is the Interchange
user - and this will happen just by upgrading to V7.1 and setting enqlm.

For customers that have more than 32767 documents at AVAILABLE and are
getting enqlm quota failures you will need the new startup images.

Mark

This patch is now available in:

EDIENG""::USER2:[DECEDI_V21D_PATCHES}DECEDI$STARTUP.EXE

M

For the moment, don't advise ALPHA customers to upgrade to V7.1.

Oracle RDB V5.1 does not work on OpenVMS V7.1 (it has a privileged image
that needs to be re-linked). 

Stay tuned ...
Mark

OpenVMS V7. requires that certain  privileged images be registered.
It provides a procedure to do this:


SYS$COMMON:[SYSUPD]REGISTER_PRIVILEGED_IMAGE.COM

Find out more: 

$ reg :== @SYS$COMMON:[SYSUPD]REGISTER_PRIVILEGED_IMAGE.COM
$ reg show *

$ make sure the RDB Priv'd images are 'registered' If not
$ reg help 

to find out how to do this.


 registered image: RDMPRV41, ident RDB/VMS V4.1-0
  registered image: RDMPRV42, ident RDB/VMS V4.2-0
  registered image: RDMPRV50, ident DEC RDB V5.0-0
  registered image: RDMPRV60, ident DEC RDB V6.0-0
  registered image: RDMPRV61, ident DEC RDB T6.1-02
  registered image: RDMPRV, ident DEC RDB V5.0-0
  registered image: RDMPRV, ident RDB/VMS V3.1A
  registered image: RDMPRV, ident RDB/VMS V3.1B-0
  registered image: RDMPRV, ident RDB/VMS V4.0-2
  registered image: RDMPRV, ident RDB/VMS V4.0-3
  registered image: RDMPRV, ident RDB/VMS V4.1-0
  registered image: RDMPRV, ident RDB/VMS V4.2-0
  registered image: RDMSHRP41, ident RDB/VMS V4.1-0
  registered image: RDMSHRP42, ident RDB/VMS V4.2-0
  registered image: RDMSHRP50, ident DEC RDB V5.0-0
  registered image: RDMSHRP60, ident DEC RDB V6.0-0
  registered image: RDMSHRP61, ident DEC RDB T6.1-02
  registered image: RDMSHRP, ident DEC RDB V5.0-0
  registered image: RDMSHRP, ident RDB/VMS V3.1A

For ObjectBroker V2.7. This is required for a mixed TCP DECnet system and
it appears to work around a serious problem that affects DEC/EDI:

$ application/broker
$ obb
OBB> show conf

 Configuration  "DECnet-Only Configuration"  (Current)
 -------------------------------------------------------
  Authentication
    AuthrWOAuthn: Enabled
    Package:      Trusted
     Description: Trusted authentication package
  Network
    Package:      DECnet
     Description: DECnet transport package
  Logging Level                  None
  Keep database files            9
  Object Hash Table Size         0

Then issue this command:

OBB> modify configuration "DECnet-Only Configuration"  /ACCEPT_AUTHR_WO_AUTHN

Where the configuration is the string from the current configuration.
Do this whether you have a TCP/IP or DECnet stack.


Although our testing is far from complete, with these changes
OBB V2.7, OpenVMS V7.1, DECnet plus V7.1, TCP/IP V4.1 all look
like a viable proposition.

Mark

DECnet/OSI V7.1 has been tested as well.

It's safe to upgrade to OpenVMS V7.1.

    Hi,
    
    Will EDI V2.1C and OBB V2.5B on Alpha work on VMS 7.1
    or is a upgrade to V2.1D and OBB V2.7 needed?
    
    Sven-Olof

Hi,

I have not tried V2.1C on OpenVMS V7.1 but I would expect it to work
without any problems.

Mark