Conference 2.301::basestar

1559.0. "Problem upgrading V3.3 to V3.4 /AXP" by VNACO1::KARASEK (Thomas KARASEK @AUI) Tue Feb 18 1997 04:23

Hi there !
As just reported by a customer, an upgrade from BASEstar/Classic V3.3 to V3.4
leaves the system unusable after database conversion. (VMS/AXP).

I tried to reproduce it with my own AXP, ( - didn't test it on VAX yet -), and
got the same result: The converion-routine within the IVP fails to pass the
CORE parameter check.
(B.t.w., it also fails to create the object logfile.)
After that a "SHO SYSTEM" fails as well:

BASEstar> sh system
%PLI-F-NOSELECT, No WHEN clause selected and no OTHERWISE specified.

- regards, Tom.
-------------------------------------------------------------------------------
Here is the installation logfile:

2New4u > @sys$update:vmsinstal BCCVA034 DAD1:[BCCVA034.KIT] options i

        OpenVMS AXP Software Product Installation Procedure V6.1


It is 17-FEB-1997 at 16:26.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-ACTIVE, The following processes are still active:
        SLS$TAPMGRRQ
        SLS$OPCOM
        ;-)
        PDP-11 is it
        DECW$TE_012F
        �TOM_2NEW4U_1
        SERVER_0077
        SERVER_0076

The following products will be processed:

  BCCVA V3.4

        Beginning installation of BCCVA V3.4 at 16:26

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

        BASEstar Kernel V3.4 AXP Installation Procedure
        -----------------------------------------------


    BASEstar requires one of these licenses to be registered
    and loaded on all nodes on which BASEstar will run:

             Product
             ---------------
        [1]  BASESTAR
        [2]  BASESTAR-G
        [3]  BASESTAR-RT
        [4]  BASESTAR-RT-G
        [5]  BASESTAR-USER
        [6]  BASESTAR-LTD
        [7]  BASESTAR-RT-LTD
        [8]  BASESTAR-CU
        [9]  BASESTAR-CU-RT

* Which of the above licenses will be used? [1]: 1

        Product:      BASESTAR
        Producer:     DEC
        Version:
        Release Date:


* Does this product have an authorization key registered and loaded? y

Getting data from   $ MCR NCP  LIST EXECUTOR   ...
  ... Done.
SCSNODE and SCSSYSTEMID checks passed.

The DECnet node ID found for this node is:
    49712 (48.560)


    This node is a member of a multi-node VMScluster.

    A single-node installation or a multi-node installation
    can be chosen.   For a multi-node installation, the nodes
    must share a cluster common system disk, and so must all
    be of the same architecture type (AXP or VAX).

* Do you want to install BASEstar on just one node [YES]?

    A single-node installation will be performed.


BASEstar is already installed on this system.
The file SYS$COMMON:[SYSLIB]BCC$SHR.EXE was found.
Its image file identification is:  BCC V3.3-001

         This BASEstar Classic System is being upgraded from V3.3 to V3.4.
         This upgrade will convert the object data bases on each system
          upgraded, which requires that the data global sections be deleted.
          This will cause all BASEstar logical data points to be set to their
          initial value on the first startup after this installation,
          including points that are set PERSISTANT.
         For more information on the data base conversions, please read
          the BASEstar Classic V3.4 release notes before upgrading.

* Do you wish to continue this installation [YES]?

__________________________________
Processing node 2NEW4U::
__________________________________

BASEstar is already installed on this node.  The file
SYS$SPECIFIC:[SYS$STARTUP]BCC$STARTUP.COM  was found.

%BCCVA-I-COREUPGRADE, BASEstar CORE will be upgraded.

%BCCVA-I-DMGTUPGRADE, BASEstar Data Management will be upgraded.

* Do you want to install BASEstar External Data Support [YES]?

* Do you want to install BASEstar List Services Support [YES]?


__________________________________
* Do you want to purge files replaced by this installation [YES]?

    The installation procedure  has  no further questions to ask during
    the installation process.  Until the IVP executes, it can continue
    without user assistance.
    IF this is a V3.3 to V3.4 UPGRADE, a data base conversion will execute
    during the IVP.  This conversion requires user input regarding log
    file locations.  The IVP will announce the beginning of the data base
    conversions, before prompting for logging information.
    The installation  time  will  vary  depending on the number of nodes
    selected  for  installation  and  the type of processor on which
    the installation is being done.
    If the data base conversions are required, time will vary depending on
    the size of your BASEstar Classic object data base.

Press <Return> to continue the installation process: :
__________________________________
16:37:03

    This installation creates a VMS rights identifier named BCC$USER,
    which is used to control access to BASEstar.

    After the installation is finished, the VMS Authorize Utility
    must be used to grant this identifier to all accounts that will
    use BASEstar.

    ---------------------------------------------------------------
    A    R E M I N D E R    T O    T H E    I N S T A L L E R

    Each VMS user account that will issue BSTAR commands must be
    granted the BCC$USER rights identifier, as well as having
    certain Authorized privileges set.

    >> Remember to grant the BCC$USER identifier to the SYSTEM account
    >> (and/or any other accounts you will be using to start the BASEstar
    >> system) and to check the Authorized privileges of those accounts
    >> BEFORE YOU ATTEMPT TO START THE BASESTAR SYSTEM.
    ---------------------------------------------------------------


%BCCVA-I-IDENTEXISTS, The BCC$USER identifier already exists

Note: The file SYS$SYSTEM:RIGHTSLIST.DAT will be modified to permit
      access by processes that have been granted the BCC$USER identifier.
      If RIGHTSLIST.DAT does not reside in SYS$SYSTEM, the logical name
      RIGHTSLIST will be translated to access the file for modification.

16:37:05
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
  No MENU installation requested
16:48:16
%VMSINSTAL-I-RESTORE, Restoring product save set E ...

16:48:35
__________________________________
Installing BASEstar on node 2NEW4U:: ...
__________________________________


16:48:39
%BCCVA-I-STARTCORE, BASEstar CORE update beginning on 2NEW4U:: .


    This  installation  places  a  file  named BCC$STARTUP.COM in the
    directory  SYS$SPECIFIC:[SYS$STARTUP]  in  each  system  root  on
    which this installation is being performed.  The SYSTARTUP_VMS.COM
    file should be edited to invoke this startup file when the system
    boots.
16:49:44
BASEstar Data Management installation beginning on 2NEW4U

%VMSINSTAL-I-SYSDIR, This product creates system disk directory 
$3$DKA0:[SYS0.SYSCOMMON.][BCC$COMMON.DMQ_EXAMPLE].
%CREATE-I-EXISTS, $3$DKA0:[SYS0.SYSCOMMON.][BCC$COMMON.DMQ_EXAMPLE] already
exists
16:49:51
BASEstar External Data Support installation beginning on 2NEW4U

16:49:56
BASEstar List Services Support installation beginning on 2NEW4U

16:50:00
%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.BCC].
16:50:13
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Copyright (c) 1996, Digital Equipment Corporation. All rights reserved.

BASEstar Kernel V3.4 Installation Verification Procedure (IVP)

$       DEFINE/NOLOG/PROCESS  BCC$SYSDATA  $3$DKA0:[SYS0.BCC$SPECIFIC]
$       DEFINE/NOLOG/PROCESS  BCC$SYSTEM   $3$DKA0:[SYS0.SYSCOMMON.][BCC$COMMON]
$ set noverify

Beginning BASEstar Classic V3.4 Data Base Conversions
The BASEstar Classic V3.4 Data Base Conversions can be logged
This would provide files with object definitions of the V3.3
 environment being converted.
If requested, these files can be VERY large, and so their
 location should be a scratch disk, that is NOT the BCC$SYSDATA
 disk.  This way, the conversions can complete, even if the log files
 use up the entire disk.
Do you wish to have object log files created? [Y/N]: y
Enter disk:[directory] location for log files: sys$manager:bcc_inst.log




   BASEstar / DCM V3.4 Data Base Conversion Utility

   Copyright (c) 1995, Digital Equipment Corporation





NOTE: This tool converts all BASEstar Classic V3.3   Data Base Configuration

files to the V3.4 format.  Once converted, the  Data Base files CAN work

on either the VAX or Alpha VMS platform, but   CAN NOT work on pre V3.4

BASEstar Classic systems





The log files will be BCC$LOGDATA:DB_object_type.LOG



BCC$LOGDATA currently translates to:
   "BCC$LOGDATA" [user] = "SYS$MANAGER:BCC_INST.LOG" (LNM$PROCESS_TABLE)







SAVING Device File





Unable to open the device change log file
BASEstar V3.4 Data Base Conversions done...
3.4 conversions checked/done...
%BCCIVP-I-CORESTART, CORE verification starting on node 2NEW4U.

%BCCIVP-I-PASS, CORE data files check passed.
%BCCIVP-I-PASS, CORE command files check passed.
%BCCIVP-I-PASS, CORE executable files check passed.
%BCCIVP-I-PASS, CORE support files check passed.
%BCCIVP-I-PASS, CORE system files check passed.
%BCCIVP-I-PASS, CORE installed image check passed.

%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_SECTION_SIZE not found.
%BCCIVP-E-NOPARAM, Parameter BCC$GLOBAL_NAME_SERVER not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_CIRCUITS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_CIRCUIT_CLUSTERS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_LINKS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_NAMES_CACHED not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_POINTS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_PORTS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_SYSTEMS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$QUORUM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$SAVE_SECTION not found.
%BCCIVP-E-NOPARAM, Parameter BCC$SYSTEM_SECTION_SIZE not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_PORT_QUOTA not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MSG_SECTION_SIZE not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_INSTALLED not found.
%BCCIVP-E-NOPARAM, Parameter BCC$UI_INSTALLED not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_SYNC_ELEMENTS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_SYNC_QUEUE not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_EXPR_QUEUED not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MSG_TIMEOUT not found.
%BCCIVP-E-NOPARAM, Parameter BCC$NAME_TIMEOUT not found.
%BCCIVP-E-NOPARAM, Parameter BCC$LOG_TO_OPCOM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$ENABLE_START_PROC not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_STATUS_BLOCKS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_GBLSECTIONS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_GBLPAGES not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_MAXPROCESSCNT not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_VIRTUALPAGECNT not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_ASTLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_BIOLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_BYTLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_DIOLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_ENQLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_FILLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_PGFLQUO not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_PRCLM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_TQELM not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_WSDEF not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_WSQUO not found.
%BCCIVP-E-NOPARAM, Parameter BCC$Q_WSEXTENT not found.
%BCCIVP-E-NOPARAM, Parameter BCC$CHECKQUOTAS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$VMS_VERSION not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_DATA_SECTION_SIZE not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_RESOURCE_LOCKS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$VERIFY_DMGT_SECTIONS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MSG_SECTION_THRESH not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MSG_XON_TIMER not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MSG_XOFF_RETRY not found.
%BCCIVP-E-NOPARAM, Parameter BCC$GBLSERVER_NAMES not found.
%BCCIVP-E-NOPARAM, Parameter BCC$LOG_OPCOM_TARGETS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_LOGGER_DISTR not found.
%BCCIVP-E-NOPARAM, Parameter BCC$ENABLE_LOGGER_DISTR not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_EVAL_PORT_QUOTA not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_EXTDATA_PORT_QUOTA not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_EXTDATA_SECTION_SIZE not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_EXTDATA_TIME_INTERVAL not found.
%BCCIVP-E-NOPARAM, Parameter BCC$DMGT_MAX_REQUESTS not found.
%BCCIVP-E-NOPARAM, Parameter BCC$EXTMAP_INSTALLED not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MAX_STRUCTURES not found.
%BCCIVP-E-NOPARAM, Parameter BCC$MIN_ACCESS_TIME not found.
%BCCIVP-E-FAIL, CORE parameter check failed.

%BCCIVP-I-DMGTSTART, DMGT verification starting on node 2NEW4U.

%BCCIVP-I-PASS, DMGT file check passed.

%BCCIVP-I-EXTMAPSTART, External Data Server verification starting
   on node 2NEW4U.

%BCCIVP-I-PASS, External Data Server file check passed.


BASEstar V3.4 IVP completed with errors.

%VMSINSTAL-E-IVPFAIL, The IVP for BCCVA V3.4 has failed.

    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

    Creating installation data file: VMI$ROOT:[SYSUPD]BCCVA034.VMI_DATA

        VMSINSTAL procedure done at 17:13


2New4u > bs
BASEstar V3.4 for VMS
Copyright (c) 1994, Digital Equipment Corporation.  All Rights Reserved.

BASEstar> sh sys
%PLI-F-NOSELECT, No WHEN clause selected and no OTHERWISE specified.
BASEstar>

>>BASEstar> sh system
>>%PLI-F-NOSELECT, No WHEN clause selected and no OTHERWISE specified.
  this means the conversion did not run...

>>Beginning BASEstar Classic V3.4 Data Base Conversions
>>The BASEstar Classic V3.4 Data Base Conversions can be logged
>>This would provide files with object definitions of the V3.3
>> environment being converted.
>>If requested, these files can be VERY large, and so their
>> location should be a scratch disk, that is NOT the BCC$SYSDATA
>> disk.  This way, the conversions can complete, even if the log files
>> use up the entire disk.
>>Do you wish to have object log files created? [Y/N]: y
>>Enter disk:[directory] location for log files: sys$manager:bcc_inst.log
  i don't see how much space was on your system disk, but you should REALLY
take the suggestion to pick a scratch disk for the conversion logs...
the DB conversion asked for a disk:[directory] only... each conversion
has a file name...
this should be smarter (ie it should parse the disk/directory out)... 
i'll look at fixing that now...

>>BCC$LOGDATA currently translates to:
>>   "BCC$LOGDATA" [user] = "SYS$MANAGER:BCC_INST.LOG" (LNM$PROCESS_TABLE)

>>Unable to open the device change log file
>>BASEstar V3.4 Data Base Conversions done...
>>3.4 conversions checked/done...
the conversions did NOT run... due to the invalid location entered above...

you need to set you default to the [.bcc] directory off of you SYS$TEST.
as the SYSTEM account, @execute_v34_db_conversions

and give only a disk:[directory] location...

please use a scratch disk as requested, or you may run out of space
on your system disk.

thankx,
sarah

i have made the parser of the user input for the log area smarter,
so that any file name/type/version info is stripped off, and just the
valid disk:[directory] info is left...

i have re-kitted the .A savesets on cam::bcc$v34_kits_axp and 
				bcc$v34_kits_vax
with this fix...

Hi Sarah, thanks so far.
Meanwhile the customer did a new V3.4-installation and added some of his points
manually. When trying to delete one of them,  he got the following:

Event 5.10.2 occurred at 20-FEB-1997 12:55:52.14
BCC$$DELETE_POINT (9) - Internal Error:  Multiple deallocate attempted on block.

It looks like the point is defined in the point-file, but not in the section.
So he took his original (V3.3) contents ob BCC$SYSDATA and did the conversion
as stated in your previous reply. This worked fine so far, except that the
points still cannot be deleted. He did send me the whole contents of BCC$SYSDATA
for investigation. 
The history-file contains the following:

Event 10.1.1 occurred at 20-FEB-1997 12:48:34.86
ILAN$DEVSRV - DCM Device Server Starting.

Event 10.1.3 occurred at 20-FEB-1997 12:48:35.18
ILAN$DEVSRV - DCM Device Server Initializing.

Event 10.86.3 occurred at 20-FEB-1997 12:48:35.68
ILAN$DEVSRV - Section files recreated: ungraceful shutdown or missing files.

Event 10.1.2 occurred at 20-FEB-1997 12:48:36.56
ILAN$DEVSRV - DCM Device Server Running.

Event 1.98.0 occurred at 20-FEB-1997 12:48:37.54
BCC$RPCR - Process up, 0 outstanding requests.

Event 1.98.0 occurred at 20-FEB-1997 12:48:47.11
BCC$MONITOR - No site specific command file present.

Event 1.99.0 occurred at 20-FEB-1997 12:49:29.21
Multiple deallocate attempted on block.

Event 5.10.2 occurred at 20-FEB-1997 12:49:29.32
The following message pertains to point APMSS_FOX                       .

Event 5.10.2 occurred at 20-FEB-1997 12:49:29.32
BCC$$DELETE_POINT (9) - Internal Error:  Multiple deallocate attempted on block.

Event 2.2.5 occurred at 20-FEB-1997 12:49:29.48
Point APMSS_FOX not fully deleted.
 Multiple deallocate attempted on block.

Event 2.1.5 occurred at 20-FEB-1997 12:55:19.23
User ABFS02::APMSDEV created point APMSS_XXX.

Event 1.99.0 occurred at 20-FEB-1997 12:55:52.00
Multiple deallocate attempted on block.

Event 5.10.2 occurred at 20-FEB-1997 12:55:52.08
The following message pertains to point APMSS_XXX                       .

Event 5.10.2 occurred at 20-FEB-1997 12:55:52.14
BCC$$DELETE_POINT (9) - Internal Error:  Multiple deallocate attempted on block.

Event 2.2.5 occurred at 20-FEB-1997 12:55:52.25
Point APMSS_XXX not fully deleted.
 Multiple deallocate attempted on block
...

As you can see, he did delete the section-files before starting BASEstar again.
There's no DAS currently running, and the points he created have were just
/WRITEABLE /FORMAT=WORD.

Since he got the same problem either with converting his old database or
creating points after a brand-new installation, I'm quite lost.

 - regards, -Tom.

Hi,

>>Meanwhile the customer did a new V3.4-installation and added some of his points
>>manually. When trying to delete one of them,  he got the following:
  was this another V3.3 upgrade, or a new install on a new system?
if a new install, was it a stand-alone system, or part of a domain, and if a
domain, what is the gns/nd configuration?

>>Event 5.10.2 occurred at 20-FEB-1997 12:55:52.14
>>BCC$$DELETE_POINT (9) - Internal Error:  
>>Multiple deallocate attempted on block.
this is a problem with the name, not the point object itself...

>>It looks like the point is defined in the point-file, but not in the section.
what make you say this... did you search bcc$sysdata:*.dat for the name?
if so, what do you get?

>>So he took his original (V3.3) contents ob BCC$SYSDATA and did the conversion
>>as stated in your previous reply. This worked fine so far, except that the
>>points still cannot be deleted. He did send me the whole contents of BCC$SYSDATA
>>for investigation. 
now i'm confused... 

- how was the V3.4 installation done (clean install/upgrade/etc)
- what is the configuration
- how/when was the point created (during V3.3, then upgraded, after
	a v3.4 upgrade, after a clean v3.4 install)
- what command is used to create the point
- what does a BS SET NAME/READ/TYPE=5/scope=3 POINT_NAME give you
- VERY IMPORTANT>>> are these points defined as global names??

Event 1.99.0 occurred at 20-FEB-1997 12:49:29.21
Multiple deallocate attempted on block.
Event 5.10.2 occurred at 20-FEB-1997 12:49:29.32
The following message pertains to point APMSS_FOX                       .
Event 5.10.2 occurred at 20-FEB-1997 12:49:29.32
BCC$$DELETE_POINT (9) - Internal Error:  Multiple deallocate attempted on block.
Event 2.2.5 occurred at 20-FEB-1997 12:49:29.48
Point APMSS_FOX not fully deleted.
 Multiple deallocate attempted on block.

Event 2.1.5 occurred at 20-FEB-1997 12:55:19.23
User ABFS02::APMSDEV created point APMSS_XXX.
Event 1.99.0 occurred at 20-FEB-1997 12:55:52.00
Multiple deallocate attempted on block.
Event 5.10.2 occurred at 20-FEB-1997 12:55:52.08
The following message pertains to point APMSS_XXX                       .
Event 5.10.2 occurred at 20-FEB-1997 12:55:52.14
BCC$$DELETE_POINT (9) - Internal Error:  Multiple deallocate attempted on block.
Event 2.2.5 occurred at 20-FEB-1997 12:55:52.25
Point APMSS_XXX not fully deleted.
 Multiple deallocate attempted on block

>>As you can see, he did delete the section-files before starting BASEstar again.
>>There's no DAS currently running, and the points he created have were just
>>/WRITEABLE /FORMAT=WORD.
  definitely not /scope=global??

>>Since he got the same problem either with converting his old database or
>>creating points after a brand-new installation, I'm quite lost.
so he did a clean install AND a data base conversion??

i DO believe there is a bug in basestar, and i am looking at fixing it now...
i'll have to get you a new BCC$SHR to try... i'll re-read these notes,
but if it doesn't say, is this VAX or Alpha??

please have them do a BS DUMP NAMC/FU/OUT=namc.dat
and send me namc.dat... i am especially curious as to the decnet id of the
system...

in the future, can you please submit customer problems to cam::bstar_mail,
along with the template that was sent to all the basestar_support members?
(if you need a new tempate, just let me know)

hi again...

i'm having trouble reproducing, so i'm going thru the debugger to
see if i can verify what i think the problem is...

i THINK they can temporarily solve this by doing the following
(please do this AFTER you did the namc dump i asked for in the last note/mail)

BS SET PARAM BCC$MAX_NAMES_CACHED 0

restart basestar

try and delete the point again...

if this works, it will save others a great deal of agony until we get a fix
out.

please let me know how this goes as soon as you can.

thankx,
sarah

here i am back again...

quite the obscure problem your customer has found...

setting the bcc$max_names_cached to 0 will definitely solve the problem
for now... there may be a slight performance degradation, as all name
functions will take a file i/o hit, but it shouldn't be too bad...
i will be fixing this and releasing a new bcc$shr for both vax and alpha in the
next few days... 

we will also write a STARS article on this... but i still need to verify
with you that the problem is as 'controlled' as i think it is...
this should happen ONLY on a system whose SYSGEN SCSSYSTEMID has a hex
value where the low-order byte = 2

please do post the scssystemid of the customer system... 

i want to verify that i have a handle on the full problem before 
implementing the fix.

thankx,
sarah

Hi Sarah !

Thanks so far (though I didn't post it the official way).
First of all:
	- yes you are right, SCSSYSTEMID = 40962 (Hex = 0000A002)
	- BS SET PARAM BCC$MAX_NAMES_CACHED 0 resolves that issue for
	  any points created afterwards. However, you still cannot delete
	  any of the previously created points.

	- NAMC.DAT is on the way, I'll send it per mail asap.

>> - how was the V3.4 installation done (clean install/upgrade/etc)
	Both - 	After a 'clean install' and manually creating the points
	the problem was discovered. Thereafter we did restore BCC$SYSDATA with
	the previously saved V3.3-files, and called the conversion-routine
	EXECUTE_V34_DB_CONVERSIONS.COM - with the same symtom.

>> - what is the configuration
	Only about 50 logical points, 2 of them being structures, the rest	
	should be format:word.

>> - how/when was the point created (during V3.3, then upgraded, after
>>		a v3.4 upgrade, after a clean v3.4 install)

	$ BS CREAT POINT /WRITE /FORMAT=WORD <pointname>
	both after a clean V3.4-install, as well as after upgrading the 
	V3.3-database again.
>> - what does a BS SET NAME/READ/TYPE=5/scope=3 POINT_NAME give you

 SYSID SYSNAM TYPE             SCOPE       OBJECT ID OBJECT NAME
------ ------ ---------------- --------- ----------- ------------
-24574 ABFS02 ( 5)Point        (1)Local     43409792 GUE_TEST

>> - VERY IMPORTANT>>> are these points defined as global names??

	No !

- Thanks & regards, Tom.