[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference rocks::dec_edi

Title:DEC/EDI
Notice:DEC/EDI V2.1 - see note 2002
Moderator:METSYS::BABER
Created:Wed Jun 06 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3150
Total number of notes:13466

3101.0. "DECEDI$CONFIGURE_ACAS problems with OBB V2.7" by RULLE::KLASSON (Sven-Olof Klasson @GOO) Wed Apr 16 1997 13:00

Hi,

There seems to be a problem with DECEDI$CONFIGURE_ACAS.COM (V2.1D) and 
Objectbroker V2.7 on OpenVMS Alpha. A customer found that DECEDI$CONFIGURE_ACAS
won't run on a system with a _new_ installation of Objectbroker V2.7. 
I see the same problem om my inhouse test system.

Here I have done a new installation of OBB V2.7. TCP/IP + DECnet transport
selected (I have DECnet/OSI on my system).

First time I run DECEDI$CONFIGURE_ACAS I get this error:

  $ @decedi$tools:decedi$configure_acas
  ....
  Configuring DEC ObjectBroker...
  %OBB-E-REG_KEYMODFAIL, Could not modify key `228$DECEDI_IMR_IMPL'. 
  -OBB-E-DB_OBJDBERR, Repository error in 
   		`SYS$COMMON:[OBB]OBB_SOFTWARE_REGISTRY.REG'. 

At subsequent runs I get this:
 
  $ @decedi$tools:decedi$configure_acas
  ....
  Configuring DEC ObjectBroker...
  %OBB-E-DB_OBJNOTFND, Object `ROOT' not found. 


I reinstalled OBB V2.7 (deleted all OBB files first). This time with TCP/IP 
transport only. Error on first run:

  $ @decedi$tools:decedi$configure_acas
  ....
  Configuring DEC ObjectBroker...
  %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=495F524D, PC=8088ECB8, PS=0000001B
  %TRACE-F-TRACEBACK, symbolic stack dump follows
   Image Name   Module Name     Routine Name    Line Number  rel PC      abs PC 
                                                          0 8088ECB8    8088ECB8
                                                          0 809B61AC    809B61AC
   OBB$SHR                                                0 000DE65C    0033C65C
   OBB$SHR                                                0 000D64CC    003344CC
   OBB$SHR                                                0 000E81CC    003461CC
   OBB$CMDSHR                                             0 00049100    0008B100
   OBB$CMDSHR                                             0 00046C48    00088C48
                                                          0 7EF2BC60    7EF2BC60
                                                          0 8002B3F4    8002B3F4
                                                          0 8002B3F4    8002B3F4
   OBB$CMDSHR                                             0 0009B194    000DD194
   OBB$CMDSHR   OTS$CALL_PROC                             0 0000015C    0004215C
   OBB$CMD                                                0 0002040C    0003040C
   OBB$CMD                                                0 00020058    00030058
                                                          0 8AE34170    8AE34170

Subsequent runs:

  $ @decedi$tools:decedi$configure_acas
  ....
  Configuring DEC ObjectBroker...
  %OBB-E-DB_OBJNOTFND, Object `1$Definitions' not found. 


DECEDI$CONFIGURE_ACAS runs fine with OBB V2.6. It also runs fine on
OBB V2.7 if OBB is upgraded from V2.6 like this

 - New installation of OBB V2.6
 - DECEDI$CONFIGURE_ACAS
 - Upgrade OBB to V2.7
 - DECEDI$CONFIGURE_ACAS

I assume the DEC/EDI definitions in OBB is preserved when OBB is upgraded.
The problems is only seen if there is no earlier versions of OBB on the system.

Is this a bug in DECEDI$CONFIGURE_ACAS.COM?

Another problem is that if Objectbroker is not started when I run
DECEDI$CONFIGURE_ACAS I get a errormessage that ACAS$STARTUP.COM is missing.
This is a minor problem, but it could potentially make an unexperienced 
customer think he should install ACAS, wich will lead him into problems.
The easy workaround here is to start Objectbroker.


Sven-Olof Klasson, CSC Sweden
T.RTitleUserPersonal
Name
DateLines
3101.1METSYS::THOMPSONWed Apr 16 1997 14:227
Hi,

this is the second report of this. It didn't happen on our systems.

We need to investigate.

M
3101.2METSYS::THOMPSONWed Apr 16 1997 14:505
My first reaction would be that this is an ObjectBroker bug, did
you report it to them?

Mark
3101.4decedi$configure_acas or obb bug?CSC32::B_ALTMIREWed Apr 16 1997 17:5732
    Mark,
    	I was involved in the call referenced by Lorey in note 3080. I was
    never able to get dialed in to the customers system but he reported the
    same errors:
    
      ....
      Configuring DEC ObjectBroker...
      %OBB-E-DB_OBJNOTFND, Object `ROOT' not found.
      $ @decedi$tools:decedi$configure_acas
      ....
      Configuring DEC ObjectBroker...
      %OBB-E-DB_OBJNOTFND, Object `1$Definitions' not found.
    
    I did get OBB involved and at their request deleted all OBB images and
    files and reinstalled but got the same results when running
    decedi$configure_acas. The final resolution was when Obb dialed in and
    reinstalled OBB and got essentially the same results at first. The
    final resolution was after all implementations had been trashed, including
    the OBB_SOFTWARE_REGISTRY implementation. At that point he deleted all
    copies of OBB_SOFTWARE_REGISTRY.REG from obb$library and reregistered
    the OBB_SOFTWARE_REGISTRY with:
    $ appl/broker import registry /implementation obb_soft_reg.dat
    
    At that point he was able to run decedi$configure_acas sucessfully and
    start DECEDI. Unfortunately I don't know whether DECEDI was up or down
    doing most of this or if it mattered.
    
    By the way there is no note 2986.6 you referenced in 3080.2.
    
    
    Bill
                                                                
3101.5METSYS::THOMPSONWed Apr 16 1997 21:325
Bill,

so are ObjectBroker acknowledging it is their bug?

Mark
3101.6I can reproduce easilyRULLE::KLASSONSven-Olof Klasson @GOOWed Apr 16 1997 22:2133
Hi,

re: .1
> this is the second report of this. It didn't happen on our systems.

I get exactly the same error messages as the customer.

Try this to reproduce:
  Delete the following files
    SYS$SPECIFIC:[OBB...]*.*;* 
    SYS$SPECIFIC:[000000]OBB.DIR;1
    SYS$COMMON:[OBB...]*.*;*
    SYS$COMMON:[000000]OBB.DIR;1
    SYS$MANAGER:OBB*.*;*
    SYS$COMMON:[SYSEXE]DECEDI_OBB_CONTEXT.CO;*
    SYS$COMMON:[SYSEXE]OBB$*.EXE;*
    SYS$COMMON:[SYSLIB]OBB*.*;*
  Install Objectbroker V2.7-10 (this is the kit on the CD's)
  @DECEDI$CONFIGURE_ACAS
It seems like if OBB is upgraded from V2.6 to V2.7 DECEDI$CONFIGURE_ACAS will
run without errors.

Mark, if you want, you can logon to my system and have a look. I only
use DEC/EDI and Objectbroker for testing, so you can do what ever test you like.
Send me a mail if you want to do this, and I'll give you access.

re: .2
> My first reaction would be that this is an ObjectBroker bug, did
> you report it to them?

No, I have not reported this to ObjectBroker engineering.

/Sven-Olof
3101.7MUNICH::WWERNERWhen in doubt, do as the INTs doThu Apr 17 1997 13:324
I have already reported the problem in OBJECTBROKER_DEVELOPMENT note 2466.
Not much reaction up to now. Maybe an IPMT is neccessary...

Wolfgang
3101.8METSYS::THOMPSONThu Apr 17 1997 15:368

All DECEDI$CONFIGURE_ACAS is is dcl script. There is no DEC/EDI code
running in this, all that we supply is the Object References and IDL,MML etc..

This probably should be IPMT's asap.

Mark
3101.9WorkaroundRULLE::KLASSONSven-Olof Klasson @GOOMon Apr 28 1997 13:1926
Hi,

The following workaround seems to work. I have used this on my test system.

Try this if you have done a fresh installation of Objectbroker V2.7. 
If you have uppgraded Objectbroker to V2.7 from a earlier version I don't 
think you'll see this problem.

 1) If DECEDI$CONFIGURE_ACAS.COM has been run and failed, it has left
    corrupted SYS$COMMON:[OBB]OBB_SOFTWARE_REGISTRY.REG files on the system.
    These files are not automatically purged.
    Delete the corrupted files. But leave the older versions.
    (A fresh installation of OBB V2.7 puts two versions of this file on the
    system).

 2) Issue this command
    $ APPL/BROK REG IMPL/REPLACE DECEDI$TOOLS:DECEDI$IMR_REG.DAT

 3) $ @DECEDI$TOOLS:DECEDI$CONFIGURE_ACAS

/Sven-Olof


Ps There is a IPMT on this case opened by MUNICH::WWERNER
   The IPMT case number is CFS.50543 / MGO102787 (prio 3)

3101.10METSYS::THOMPSONMon Apr 28 1997 14:227
Ah ha! That's why it's not getting much airtime. 

This is a "system down" situation until they get your
workaround. I would have put that at P1. 

Mark
3101.11DECEDI$CONFIGURE_OBB.COMMETSYS::THOMPSONWed May 07 1997 19:2228
In EDIENG""::user2:[decedi_v21d_patches] there is a new 
procedure: DECEDI$CONFIGURE_OBB.COM.

For V2.1D systems, place this in DECEDI$TOOLS: and it can be used
as a replacement for DECEDI$CONFIGURE_ACAS.COM.

It incorporates a "workaround" from BEA Systems Inc.. This procedure
should *avoid* the problems reported in .0. If the User has already
been affected by this then contact the CSC for details as to how to
recover. 



Note: this only seems to be an OpenVMS Alpha problem. BEA Systems have
not determined the casue yet but it appears that the changes in
DECEDI$CONFIGURE_OBB.COM will avoid the problem.


We have never seen this on our internal systems (in Reading). It has been
stated that if a Clean install is performed for V2.7 then problems will
result. However we have a least one customer who did a clean install
and found no problems.

It is possible this problem is quota/sysgen related, which may explain why
some see it and others do not.

Mark