| Hi,
>>My customer using BASEstar Classic(V3.3) for VAX/VMS(V6.1).
Who is your customer?
Can you please fill out the attached problem report template?
>>They added VAX/VMS(V6.2) workstation on network. I installed B* Classic on
>>workstation.
i assume you also installed V3.3?
Are the systems in the same domain (do they have the same global name servers?)
What is the configuration (what systems are global name servers, what systems
are name dispatchers?)
Do the systems see each other (what is logged to the history file after
a startup of each system, what are the BASEstar parameters BCC$GBLSERVER_NAMES
and BCC$GLOBAL_NAME_SERVER and BCC$QUORUM set to on each system...
what is the output of $ BS SHO SYSTEM *
on each system)
Are either/both systems running DECNET OSI?
>>After entry show point command on workstation.
>>I found following error messages.
were all these messages at the CLI level?
What was in the history file (if anything)?
>> $ show point */full :
>> Any points normal successfull
>> or
>> %system-w-accvio
>> reason mask=!XB, virtual Address=!XL, P=!XL,PSL=!XL
>> or
>> %system-f-exenqlm
>> or
>> %bcc-f-badpntdef
>> bad database definition for point
are you saying that SOMETIMES you get the point info, and SOMETIMES you get an
exceeded enqueue quota message and SOMETIMES it accvios and SOMETIMES you
get the badpntdef error?
are these repeatable as to when you get them (for example, you get an accvio on
every third try?)
have you made sure all the UAF resources for the accounts that start/use B*
are as documented in the install guide... you seem to be running out of
enque quota... is your SYSGEN PQL_MENQLM and PQL_DENQLM set high enough
to allow what is requested inthe UAF record to be given?
>> $ show point */value :
>> Message number 02A29D5a.
this is an ILAN INVDEVICE error, which doesn't make much sense...
>> Workstation have no any B* points, only server have many local and global
>> points.
the sho poi */full will go out to the domain, so i'm assuming it is accessing
the original system... it almost sounds as if you MAY have installed V3.4 on
the workstation, which is not supported to communicate with a V3.3 system,
OR you have some resource problems...
the BCC$SERVER process may also be running out of quota... it does the
remote 'sho point' calls (what happens when you add /SELECT=SCOPE=LOCAL
to the SHO POINT and SHO VALUE calls)?
the bcc$sysdata:bss$system_startup.com could be edited to increase this, but
i'd like to see the information requested from above first (please send the
history file info from startup and when you execute the SHO point commands
from BOTH systems, as well as the parameter ans SHO SYSTEM info from BOTH
systems).
thankx,
sarah johnson
BASEstar Engineering
Customer Contact Information
----------------------------
Customer Contact:
Customer Phone :
Company Name :
Site Location :
Digital Contact :
Customer Support Access Number:
System Information
------------------
Brief Configuration (# systems, system hardware types):
Node Name/address of problem system:
Hardware type of problem system:
System Type (production/development):
Brief description of problem systems' main functionality:
Product Information... please enter version for all products on the system
---------------------------------------------------------------------------
System Software information:
OVMS VAX: OVMS Alpha: Digital UNIX:
WNT Alpha: WNT Intel:
RDB: Oracle: INGRES:
Platform Information:
version support contract part #
--------- -------------------------
BASEstar Classic :
BASEstar Open :
BGE :
CIMfast :
PDAS :
OMNI :
BASEstar DDE :
Device Connect Information:
RS232:
DECNET:
Allen Bradley:
Modicon:
Siemans:
Other:
Priority :
1 - Critical, production down situation.
2 - High Impact
3 - Moderate Impact
4 - Low Impact
5 - No Impact (Informational)
Problem Description (include description of IMPACT for priority 1-3):
---------------------------------------------------------------------
|