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

Conference clusta::acms

Title:ACMS comments and questions
Notice:This is not an official software support channel. Kits 5.*
Moderator:CLUSTA::HALLAN
Created:Mon Feb 17 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4179
Total number of notes:15091

4102.0. "more srvnotfound and errnetcre" by CSC32::J_HENSON (Don't get even, get ahead!) Mon Feb 17 1997 16:40

Distributed system
Front End - openvms vax v6.2, acms v4.0-2, tdms 1.9a, no decforms
Back End  - openvms alpha v6.2, acms v4.0-2

A customer (Airtouch Celular) has recently started experiencing problems
with acms.  On the front end, users are getting logged off or dropped.
Once this happens, they log back in and are ok for a while.  However, other
users experience the same problems.

On the backend, the atr log is full of server not found errors occuring
in request steps.  I have the atr log and can provide it if you need
it, but it's about 65k lines and shows 30 minutes worth of logging.

The swlup on the back end reports both the server not found errors, as
well as network partner exited.  In a 30 minute period, there were
about 43 of these errors logged.  Rather than post the entire swlup log,
I will post the first 1000 lines in the first reply.  I have the
entire 35k line file if you want to see it.

While this is being logged on the back end, the front end swlup
logs

%acmsmss-e-errnetcre,...
-system-f-badparam,....

twice during the entire 30 minute interval.  According to the customer,
there is only one fe and one be.  I will post the swlup log for
the entire 30 minute interval in the second reply.

The atr log on the fe doesn't show anything unusual.  There are a
few authentication failures, but not much else.  I have it, though, and can
post it if needed.

Up until Feb. 4th, things were ok.  I have asked the customer to check on
what else happened at that time.  I have also asked them to check out
their network, and they don't show any problems other than some slow ack
times, which they claim are within spec.

A couple of other things are

 - the customer has reported tssshr errors in the fe swlup, as well
   as errors opening NL: reported by the CP process, but I don't see any of 
   this in the swlup logs that I have.

 - the customer claims to be running 4.0-2  (he even analyzed acmshr to
   be sure), but both swlup logs show 4.0-0.  Is this normal?

Please advise.

Thanks,

Jerry
T.RTitleUserPersonal
Name
DateLines
4102.1be swlCSC32::J_HENSONDon't get even, get ahead!Mon Feb 17 1997 16:43997
Out put from SWLUP - backend.

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 1
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)


---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%ACMS-E-SRVNOTFOUND, The server was not found

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 000D8EB0  ENT MASK = 200000FC
PSL = 0000001B  AP = 00000001  FP = 7EE21840  PC = 0016CE30

SR2 = 00000003
SR3 = 00251800
SR4 = 00020184
SR5 = 7EE21AA4
SR6 = 0202000C
SR7 = 00000003
SR29 = 7EE21840

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20002008
PSL = 0000001B  AP = 00000001  FP = 7EE21A50  PC = 8009C664

SR3 = 8D3434D8
SR13 = 00020274
SR29 = 7EE21A50

---------------------------------------------------------------------------
---------------------------------------------------------


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 2
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 7F06F460  ENT MASK = 2000FFFC
PSL = 0000001B  AP = 00000000  FP = 7EE21B80  PC = 80000304

SR2 = 7FFBF818
SR3 = 7FFBF928
SR4 = 7EE72674
SR5 = 00000001
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 7EE62310
SR13 = 7EE63FF0
SR14 = 00000000
SR15 = 009AFCEB
SR29 = 7EE21B80

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 8D31EE60  ENT MASK = 20001FFC
PSL = 0000001B  AP = 00000000  FP = 00000000  PC = 7EEA3EE4

SR2 = 7EE62450
SR3 = 00000001
SR4 = 00000000
SR5 = 7EE72934
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 00000000
SR29 = 00000000

---------------------------------------------------------------------------
---------------------------------------------------------

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 3
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)


Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE48    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%SYSTEM-F-LINKEXIT, network partner exited

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE48    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 000D8EB0  ENT MASK = 200000FC
PSL = 0000001B  AP = 00000001  FP = 7EE21840  PC = 0016CE48

SR2 = 00000003
SR3 = 00251800
SR4 = 00020184
SR5 = 7EE21AA4
SR6 = 0202000C
SR7 = 00000003
SR29 = 7EE21840

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE48    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20002008
PSL = 0000001B  AP = 00000001  FP = 7EE21A50  PC = 8009C664

SR3 = 8D3434D8
SR13 = 00020274
SR29 = 7EE21A50

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 4
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

PID = 21E20CD8    PC = 0016CE48    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 7F06F460  ENT MASK = 2000FFFC
PSL = 0000001B  AP = 00000000  FP = 7EE21B80  PC = 80000304

SR2 = 7FFBF818
SR3 = 7FFBF928
SR4 = 7EE72674
SR5 = 00000001
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 7EE62310
SR13 = 7EE63FF0
SR14 = 00000000
SR15 = 009AFCEB
SR29 = 7EE21B80

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 0016CE48    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 8D31EE60  ENT MASK = 20001FFC
PSL = 0000001B  AP = 00000000  FP = 00000000  PC = 7EEA3EE4

SR2 = 7EE62450
SR3 = 00000001
SR4 = 00000000
SR5 = 7EE72934
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 00000000
SR29 = 00000000

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 5
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)


PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%ACMSI-I-BUGLOG, Base=7EE62000  Flag=00000000  PC of
Signal/Exception=00062E58
-ACMSI-I-BGLOG1, AP=00000001 FP=7EE21740 SP=7EE21740 PSL=0000001B
-ACMSI-I-BGLOG2, R0=FFFFFFFF R1=00000001 R2=00016628 R3=070448D0
R4=00000001
-ACMSI-I-BGLOG3, R5=07044954 R6=00000000 R7=00FDCA32 R8=00000006
R9=00000001
-ACMSI-I-BGLOG4, R10=00000004 R11=00000000
-ACMSI-I-BGLOG5, R12=02020000 R13=8D3433D8 R14=00000000 R15=00020280
-ACMSI-I-BGLOG6, R16=00FDCA32 R17=00000100 R18=00000003 R19=00000000
-ACMSI-I-BGLOG7, R20=00260170 R21=00000008 R22=00000000 R23=00016628
-ACMSI-I-BGLOG8, R24=000CC6D0 R25=00000001 R26=00062E58 R27=7F006B20
-ACMSI-I-BGLOG9, R28=0000001B R29=7EE21740 R30=7EE21740

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%ACMS-E-SRVNOTFOUND, The server was not found

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20004000
PSL = 0000001B  AP = 00000001  FP = 7EE21280  PC = 7EEA8524

SR14 = 00000000
SR29 = 7EE21280

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 6
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 8D31EE60  ENT MASK = 200003FC
PSL = 0000001B  AP = 00000001  FP = 7EE214D0  PC = 7EEA6BF0

SR2 = 00000918
SR3 = 070448D0
SR4 = 00000001
SR5 = 07044954
SR6 = 00000000
SR7 = 00FDCA32
SR8 = 00000006
SR9 = 00000001
SR29 = 7EE214D0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20000004
PSL = 0000001B  AP = 00000001  FP = 7EE21500  PC = 800071D8

SR2 = 00016628
SR29 = 7EE21500

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20000000
PSL = 0000001B  AP = 00000001  FP = 7EE21740  PC = 990422BC

SR29 = 7EE21740

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 7
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 200001FC
PSL = 0000001B  AP = 00000001  FP = 7EE21790  PC = 00062E58

SR2 = 000CC630
SR3 = 00264AF0
SR4 = 00264F34
SR5 = 00016628
SR6 = 070448D0
SR7 = 00264F34
SR8 = 00264F34
SR29 = 7EE21790

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 200001FC
PSL = 0000001B  AP = 00000001  FP = 7EE21800  PC = 0016FB88

SR2 = 000CBBF0
SR3 = 8D3434D8
SR4 = 00000001
SR5 = 00272028
SR6 = 0202000C
SR7 = 00000001
SR8 = 0022881C
SR29 = 7EE21800

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20000004
PSL = 0000001B  AP = 00000001  FP = 7EE21840  PC = 0016EDC4

SR2 = 00000003
SR29 = 7EE21840

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 8
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)


---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20002008
PSL = 0000001B  AP = 00000001  FP = 7EE21A50  PC = 8009C664

SR3 = 8D3434D8
SR13 = 00020274
SR29 = 7EE21A50

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 7F06F460  ENT MASK = 2000FFFC
PSL = 0000001B  AP = 00000000  FP = 7EE21B80  PC = 80000304

SR2 = 7FFBF818
SR3 = 7FFBF928
SR4 = 7EE72674
SR5 = 00000001
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 7EE62310
SR13 = 7EE63FF0
SR14 = 00000000
SR15 = 009AFCEB
SR29 = 7EE21B80

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.49

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 9
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 8D31EE60  ENT MASK = 20001FFC
PSL = 0000001B  AP = 00000000  FP = 00000000  PC = 7EEA3EE4

SR2 = 7EE62450
SR3 = 00000001
SR4 = 00000000
SR5 = 7EE72934
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 00000000
SR29 = 00000000

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 7EEA8524    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

ACMSEXC   00010000 00090DFF
ACMSHR    00092000 00224C98
DTI$SHARE 001E8000 002220D0
SYS$BASE_ 8D3109A0 8D31D6B0
LIBRTL    7EFFE000 7F04FFFF
LIBOTS    7F05E000 7F08FFFF
SYS$PUBLI 8D302AF8 8D3040E8
EPC$SHR   01622000 016F45B0
DBMMSG    04E2E000 04E39DFF
DBQMSG    04E3A000 04E3A9FF
SYSMSG    04E3C000 04E841FF
PRISMMSGS 04E86000 04E961FF
ACMSMSG   070AA000 070DA1FF
SHRIMGMSG 070DC000 070E29FF

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 10
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)


%ACMSEXC-E-EXCINTERR, Internal EXC error
-ACMS-E-SRVNOTFOUND, The server was not found

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20004000
PSL = 0000001B  AP = 00000001  FP = 7EE21150  PC = 00074E0C

SR14 = 00000000
SR29 = 7EE21150

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 200000FC
PSL = 0000001B  AP = 00000001  FP = 7EE21660  PC = 0004443C

SR2 = 00014388
SR3 = 015F9AFC
SR4 = 015F9C74
SR5 = 00000001
SR6 = 015F9AFC
SR7 = 00000000
SR29 = 7EE21660

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 11
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

Hand = 7F06F440  ENT MASK = 20000FFC
PSL = 0000001B  AP = 00000001  FP = 7EE216D0  PC = 0004EEF0

SR2 = 00014710
SR3 = 015F9AFC
SR4 = 015F9B44
SR5 = 071C6DA8
SR6 = 015F9AFC
SR7 = 00000000
SR8 = 3FFC0000
SR9 = 54030402
SR10 = 00FDCA32
SR11 = 00000000
SR29 = 7EE216D0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20001FFC
PSL = 0000001B  AP = 00000001  FP = 7EE21740  PC = 0004B530

SR2 = 00016628
SR3 = 070448D0
SR4 = 00FDE72A
SR5 = 015F9AFC
SR6 = 00000001
SR7 = 00FDCA32
SR8 = 015F9AFC
SR9 = 00000001
SR10 = 00000004
SR11 = 00000000
SR12 = 02020000
SR29 = 7EE21740

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 200001FC
PSL = 0000001B  AP = 00000001  FP = 7EE21790  PC = 0006300C


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 12
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

SR2 = 000CC630
SR3 = 00264AF0
SR4 = 00264F34
SR5 = 00016628
SR6 = 070448D0
SR7 = 00264F34
SR8 = 00264F34
SR29 = 7EE21790

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 200001FC
PSL = 0000001B  AP = 00000001  FP = 7EE21800  PC = 0016FB88

SR2 = 000CBBF0
SR3 = 8D3434D8
SR4 = 00000001
SR5 = 00272028
SR6 = 0202000C
SR7 = 00000001
SR8 = 0022881C
SR29 = 7EE21800

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20000004
PSL = 0000001B  AP = 00000001  FP = 7EE21840  PC = 0016EDC4

SR2 = 00000003
SR29 = 7EE21840

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 13
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20002008
PSL = 0000001B  AP = 00000001  FP = 7EE21A50  PC = 8009C664

SR3 = 8D3434D8
SR13 = 00020274
SR29 = 7EE21A50

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 7F06F460  ENT MASK = 2000FFFC
PSL = 0000001B  AP = 00000000  FP = 7EE21B80  PC = 80000304

SR2 = 7FFBF818
SR3 = 7FFBF928
SR4 = 7EE72674
SR5 = 00000001
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 7EE62310
SR13 = 7EE63FF0
SR14 = 00000000
SR15 = 009AFCEB
SR29 = 7EE21B80

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00074E0C    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 8D31EE60  ENT MASK = 20001FFC
PSL = 0000001B  AP = 00000000  FP = 00000000  PC = 7EEA3EE4

SR2 = 7EE62450

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 14
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

SR3 = 00000001
SR4 = 00000000
SR5 = 7EE72934
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 00000000
SR29 = 00000000

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00044610    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%ACMSEXC-I-TSKER1, Task name/ID:
DISPLAY_CELL_SERV/PTC20::00020121-00000001-45AE48E6-009AFCEF
-ACMSEXC-I-TSKER2, TP/SP: 02/0E, Flags: 0000/0000, GTB: 002719BC, SBB:
015FD898
-ACMSEXC-I-TSKER3, TIBs */O/P/C/T/P_Q:
015F9AFC/015F9AFC/00000000/00000000/00000000/015F9B3C:015F9B3C
-ACMSEXC-I-TSKER4, EXCPTN-Cur/Pnd FF/FF, Codes: 00000000/00000000/00000000,
 Gen: 00000000, STBs: 00000000/00000000/00000000

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:32:11.50

PID = 21E20CD8    PC = 00044874    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%ACMSEXC-I-TSKER5, WP-Cur/W_Q: 00000000/015F9B34:015F9B34, TID:
--transaction not active--
-ACMSEXC-I-TSKER6, SBB-Flags/STB/CTL/Up: 0700/00272CE0/00272D38/015FD878

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:33:33.84

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

%ACMS-E-SRVNOTFOUND, The server was not found

---------------------------------------------------------------------------
---------------------------------------------------------

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 15
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)


Event logged at: 13-FEB-1997 07:33:33.84

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 000D8EB0  ENT MASK = 200000FC
PSL = 0000001B  AP = 00000001  FP = 7EE21840  PC = 0016CE30

SR2 = 00000003
SR3 = 00251800
SR4 = 00020184
SR5 = 7EE21AA4
SR6 = 0202000C
SR7 = 00000003
SR29 = 7EE21840

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:33:33.84

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 00000000  ENT MASK = 20002008
PSL = 0000001B  AP = 00000001  FP = 7EE21A50  PC = 8009C664

SR3 = 8D3434D8
SR13 = 00020274
SR29 = 7EE21A50

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:33:33.84

PID = 21E20CD8    PC = 0016CE30    PSL = 0000001B

Process UIC  : [126,301]
Process name : ACMS01EXC001000
Username     : PRISMLAP_701
Image file   : DSA1364:[SYS0.SYSCOMMON.][SYSEXE]ACMSEXC.EXE

Hand = 7F06F460  ENT MASK = 2000FFFC
PSL = 0000001B  AP = 00000000  FP = 7EE21B80  PC = 80000304

SR2 = 7FFBF818
SR3 = 7FFBF928
SR4 = 7EE72674

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:57:31    ACMS SWLUP V4.0-0                   Page 16
Event Log                                                       14-FEB-1997
 14:57:31    _FTA22:[].COM; (1)

SR5 = 00000001
SR6 = 00000000
SR7 = 00000001
SR8 = 00000000
SR9 = 00000068
SR10 = 7EE62310
SR11 = 7FF0E1A2
SR12 = 7EE62310
SR13 = 7EE63FF0
SR14 = 00000000
SR15 = 009AFCEB
SR29 = 7EE21B80

---------------------------------------------------------
4102.2fe swlCSC32::J_HENSONDon't get even, get ahead!Mon Feb 17 1997 16:45275
Output from SWLUP front end

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:53:39    ACMS SWLUP V4.0-0                   Page 1
Event Log                                                       14-FEB-1997
 14:53:39    _FTA4:[].COM; (1)


---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:31:54.26

PID = 2120EA2E    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP041000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

%ACMSMSS-E-ERRNETCRE, Error creating DECnet object
-SYSTEM-F-BADPARAM, bad parameter value

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:31:54.26

PID = 2120EA2E    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP041000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 000A2DD5  ENT MASK = 000C
PSW = 0000  AP = 7FE65B94  FP = 7FE65B80  PC = 000A02B9

SR2 = 80004BA0
SR3 = A02087D0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:31:54.26

PID = 2120EA2E    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP041000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 00000000  ENT MASK = 0000
PSW = 0000  AP = 7FE65BD4  FP = 7FE65BAC  PC = 9C468003


---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:31:54.26

PID = 2120EA2E    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP041000
Username     : ACMS_SYS_CP

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:53:39    ACMS SWLUP V4.0-0                   Page 2
Event Log                                                       14-FEB-1997
 14:53:39    _FTA4:[].COM; (1)

Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 00000000  ENT MASK = 007C
PSW = 0000  AP = 7FE65C00  FP = 7FE65BDC  PC = 00072FCA

SR2 = 00000000
SR3 = 000031B0
SR4 = 0007307A
SR5 = 00061C04
SR6 = 000032E0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:31:54.26

PID = 2120EA2E    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP041000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 00000000  ENT MASK = 003C
PSW = 0000  AP = 7FE65DA4  FP = 7FE65D68  PC = 00009ADF

SR2 = 00000000
SR3 = 00001035
SR4 = 00000001
SR5 = 000382F0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:31:54.26

PID = 2120EA2E    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP041000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 0000AD3A  ENT MASK = 0FFC
PSW = 0000  AP = 7FE65DFC  FP = 7FE65DC0  PC = 7FEAA5F3

SR2 = 00000001
SR3 = 7FFE5E0C
SR4 = 7FFE5ECC
SR5 = 00000000
SR6 = 7FEA5250
SR7 = 7FEA55A4
SR8 = 00000001
SR9 = 7FFE5E0C
SR10 = 7FEA5B48
SR11 = 7FEACE48

---------------------------------------------------------------------------
---------------------------------------------------------

SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:53:39    ACMS SWLUP V4.0-0                   Page 3
Event Log                                                       14-FEB-1997
 14:53:39    _FTA4:[].COM; (1)


Event logged at: 13-FEB-1997 07:47:46.05

PID = 2120E63F    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP050000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

%ACMSMSS-E-ERRNETCRE, Error creating DECnet object
-SYSTEM-F-BADPARAM, bad parameter value

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:47:46.05

PID = 2120E63F    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP050000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 000A2DD5  ENT MASK = 000C
PSW = 0000  AP = 7FE65B94  FP = 7FE65B80  PC = 000A02B9

SR2 = 80004BA0
SR3 = A02BD890

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:47:46.05

PID = 2120E63F    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP050000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 00000000  ENT MASK = 0000
PSW = 0000  AP = 7FE65BD4  FP = 7FE65BAC  PC = 9C468003


---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:47:46.05

PID = 2120E63F    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP050000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:53:39    ACMS SWLUP V4.0-0                   Page 4
Event Log                                                       14-FEB-1997
 14:53:39    _FTA4:[].COM; (1)

Hand = 00000000  ENT MASK = 007C
PSW = 0000  AP = 7FE65C00  FP = 7FE65BDC  PC = 00072FCA

SR2 = 00000000
SR3 = 000031B0
SR4 = 0007307A
SR5 = 00061C04
SR6 = 000032E0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:47:46.05

PID = 2120E63F    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP050000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 00000000  ENT MASK = 003C
PSW = 0000  AP = 7FE65DA4  FP = 7FE65D68  PC = 00009ADF

SR2 = 00000000
SR3 = 00001035
SR4 = 00000001
SR5 = 000382F0

---------------------------------------------------------------------------
---------------------------------------------------------

Event logged at: 13-FEB-1997 07:47:46.05

PID = 2120E63F    PC = 000A02B9    PSL = 03C00000

Process UIC  : [001,004]
Process name : ACMS01CP050000
Username     : ACMS_SYS_CP
Image file   : DSA1126:[SYS3.SYSCOMMON.][SYSEXE]ACMSCP.EXE

Hand = 0000AD3A  ENT MASK = 0FFC
PSW = 0000  AP = 7FE65DFC  FP = 7FE65DC0  PC = 7FEAA5F3

SR2 = 00000001
SR3 = 7FFE5E0C
SR4 = 7FFE5ECC
SR5 = 00000000
SR6 = 7FEA5250
SR7 = 7FEA55A4
SR8 = 00000001
SR9 = 7FFE5E0C
SR10 = 7FEA5B48
SR11 = 7FEACE48


---------------------------------------------------------------------------
---------------------------------------------------------


SWLUP           SWLUP Event Log Output Listing                  14-FEB-1997
 14:53:39    ACMS SWLUP V4.0-0                   Page 5
Event Log                                                       14-FEB-1997
 14:53:39    _FTA4:[].COM; (1)


          Total of 12 events in report


---------------------------------------------------------------------------
---------------------------------------------------------

4102.3OHMARY::HALLBill Hall - ACMS Engineering - ZKO2-2Mon Feb 17 1997 17:2011
    
    	The messages indicate that the CP and the EXC are having problems
    creating links to the corresponding processes.  The customer should
    check the various line and circuit counters in NCP (assuming this
    is DECnet Phase IV).
    
    	Is this something that just happened or has the environment
    changed (like adding new applications or a number of new users?)
    
    
    	Bill
4102.4CSC32::J_HENSONDon't get even, get ahead!Tue Feb 18 1997 09:1419
>>   <<< Note 4102.3 by OHMARY::HALL "Bill Hall - ACMS Engineering - ZKO2-2" >>>

>>    
>>    	The messages indicate that the CP and the EXC are having problems
>>    creating links to the corresponding processes.  The customer should
>>    check the various line and circuit counters in NCP (assuming this
>>    is DECnet Phase IV).

It's Phase IV.  One of the things I checked was exec counters.  During
a period during which a lot of these errors were logged, there were
no response timeouts.  Nothing else looked out of the ordinary, either.
    
>>    	Is this something that just happened or has the environment
>>    changed (like adding new applications or a number of new users?)

The customer still owes me this information.  I'm hoping that we'll
see some reason for the recent problems once we get this.

Jerry
4102.5CLUSTA::HALLBill Hall - ACMS Engineering - ZKO2-2Tue Feb 18 1997 11:0814
    
    	When ACMS V4.0-1 and V4.0-2 were released as ECO's it meant we
    couldn't bump up the version number.  The only real way to check is
    to do an ANA/IMAGE SYS$LIBRARY:ACMSHR.EXE and you'll see the real
    version number there.
    
    	BTW - ACMS V4.1 is the only version certified to run on OpenVMS
    V6.2 according to the SPD.  While the older versions may run on higher
    versions of OpenVMS, there is no testing involved.  It also means
    that we are under no obligation to fix any problems they encounter
    although even that is not a hard and fast rule.
    
    Bill
    
4102.6NCP statsCSC32::J_HENSONDon&#039;t get even, get ahead!Wed Feb 19 1997 09:54149
Here are NCP statistics for lines and circuits for both the FE and BE.  The
only thing that looks bad to me are some user buffer unavailable counts
and adjacency down counts.  Other than that, everything looks ok.

Can anyone tell me whether or not the network looks sound from the
following?

Thanks,

Jerry

==============================================================================


On front end - node PTC20.

Known Line Volatile Summary as of 18-FEB-1997 13:48:57

   Line             State

  MNA-0             on


Line Counters as of 18-FEB-1997 13:49:04

Line = MNA-0

       42348  Seconds since last zeroed
     2846850  Data blocks received
      147296  Multicast blocks received
           0  Receive failure
   404525080  Bytes received
    26232265  Multicast bytes received
           0  Data overrun
     1507829  Data blocks sent
        3697  Multicast blocks sent
        1862  Blocks sent, multiple collisions
        7433  Blocks sent, single collision
       13703  Blocks sent, initially deferred
   276711710  Bytes sent
      217892  Multicast bytes sent
           0  Send failure
           0  Collision detect check failure
           0  Unrecognized frame destination
           0  System buffer unavailable
          15  User buffer unavailable





Known Circuit Volatile Summary as of 18-FEB-1997 13:49:15

   Circuit          State                   Loopback     Adjacent
                                              Name      Routing Node

  MNA-0             on                               56.1022 (DC7000)


Circuit Counters as of 18-FEB-1997 13:49:33

Circuit = MNA-0

       42377  Seconds since last zeroed
     1703095  Terminating packets received
      684110  Originating packets sent
           0  Terminating congestion loss
           0  Transit packets received
           0  Transit packets sent
           0  Transit congestion loss
           0  Circuit down
           0  Initialization failure
           0  Adjacency down
           1  Peak adjacencies
      686936  Data blocks sent
   142532026  Bytes sent
     1705920  Data blocks received
   322816586  Bytes received
           0  Unrecognized frame destination
          15  User buffer unavailable


 On backend - node DOMINO

Known Line Volatile Summary as of 18-FEB-1997 13:51:21

   Line             State

  MNA-0             on


Line Counters as of 18-FEB-1997 13:51:41

Line = MNA-0

      >65534  Seconds since last zeroed
   115503311  Data blocks received
     5109341  Multicast blocks received
           0  Receive failure
 >4294967294  Bytes received
   841595635  Multicast bytes received
           0  Data overrun
   121383692  Data blocks sent
      105701  Multicast blocks sent
      927576  Blocks sent, multiple collisions
     3135236  Blocks sent, single collision
      663872  Blocks sent, initially deferred
 >4294967294  Bytes sent
     6982734  Multicast bytes sent
           0  Send failure
      >65534  Collision detect check failure
           0  Unrecognized frame destination
           0  System buffer unavailable
        1170  User buffer unavailable





Known Circuit Volatile Summary as of 18-FEB-1997 13:51:52

   Circuit          State                   Loopback     Adjacent
                                              Name      Routing Node

  MNA-0             on                               56.1022 (DC7000)


Circuit Counters as of 18-FEB-1997 13:52:22

Circuit = MNA-0

      >65534  Seconds since last zeroed
    99627498  Terminating packets received
   110235401  Originating packets sent
           0  Terminating congestion loss
           0  Transit packets received
           0  Transit packets sent
           0  Transit congestion loss
           0  Circuit down
           0  Initialization failure
          33  Adjacency down
           1  Peak adjacencies
   110313142  Data blocks sent
 >4294967294  Bytes sent
    99705112  Data blocks received
 >4294967294  Bytes received
           0  Unrecognized frame destination
        1170  User buffer unavailable

4102.7?CSC32::J_HENSONDon&#039;t get even, get ahead!Fri Feb 21 1997 09:458
Can someone give me some direction on this?  My customer is pushing me for
an answer.  Should I spr this or tell them to upgrade?

Thanks,

Jerry


4102.8CLUSTA::HALLBill Hall - ACMS Engineering - ZKO2-2Fri Feb 21 1997 17:3912
    
    
    	I'd say that anything that states 'failure' or 'unavailable'
    	indicates a problem with the network.  ACMS is just trying to
    	open and use a link and if it can't do that, then don't expect
    	ACMS to work properly.
    
    	What was the outcome of 'what has changed in this environment'
    	question?
    
    	Bill
    
4102.9CSC32::J_HENSONDon&#039;t get even, get ahead!Fri Feb 21 1997 17:509
>>   <<< Note 4102.8 by CLUSTA::HALL "Bill Hall - ACMS Engineering - ZKO2-2" >>>

    
>>    	What was the outcome of 'what has changed in this environment'
>>    	question?
    
Still waiting.

Jerry
4102.10more infoCSC32::J_HENSONDon&#039;t get even, get ahead!Fri Feb 21 1997 18:0426
This still in.  Does it help?  Also, I've posted the line/circuit counter
info to note 5872 in bulean::decnetvax to see if anyone can tell me
more about what these numbers indicate.

Jerry

===========================================================================


On the night of 2/1, morning of 2/2 the following firmware was upgraded on
this cluster according to our Field Service Engineer:

CPU         from 4.0 to 4.3
DEMNA   from 8.3 to 9.4 (VAXen only)
CI             from 7.1 to 7.2
Console  from 4.0 to 4.1

The CPU's on DOMINO (the alpha backend system) were upgraded from 300 MHz
to 440 MHz.

In talking with our Help Desk folks, this only happens to users who are
connecting to PTC20 (view only VAX front end), not on CMB (on line VAX
front end).  The problem started occurring (or at least the PN was opened)
on 2/4.

Ryan
4102.11...KERNEL::PULLEYCome! while living waters flowWed Feb 26 1997 06:5847
    Hi Jerry,
    
    For what it's worth we've a customer here who maybe having similar
    problems.
    Some differences like ACMS v4.1 and DECforms rather than TDMS.
    There's been some stuff in this conference & a couple of IPMT's.
    Both IPMTs pointed things back to DECnet, or at least asked for more
    monitoring on the systems involved.
    Ours is looking into acms$monitor, VMS monitoring using PS I think but
    probably most helpfully DECnet, with a network sniffer.
    
    I'm not a DECnetist, but just had a chat with someone who is and they
    reckon your number of collisions is nothing to be worried about.
    Apparently you should start getting worried if it's > 10% of the total
    E.g., single blocks sent > a million, collisions 7433.
    Also the user buffer unavailable, 15 in that time, isn't that bad.
    (We can't tell about the back end as we don't know when the counts
    were last 0ed).
    User buffer unavailable seems that DECnet had to retry sending a
    message to the application.
    
    One thin he did say is that there was some problems with object
    databases in VMS v6.0/6.1, but all the DECnet fixes were rolled into
    VMS v6.2.
    
    One of the IPMTs talked about dangling objects--those not attached to
    processes, because they hadn't been deleted.
    In the case I was involved in, we don't think there were danglinig
    objects as ACMS had come down OK the night before.
    Wonder if anyone's seen this where ACMS isn't brought down each night?
    
    I've asked in a level 5 IPMT if ACMS could be changed to log further
    info when it gets a system-f-badparam.
    If we knew what parameters it called the system service with, we might
    be able to tell DECnet whether they were really good or not.
    At the moment, we can only rely on catching anything networky with the
    sniffer.
    If the sniffer squeeks before ACMS says it can't create the object,
    then perhaps it's DECnet--if not then it could be ACMS upsetting
    DECnet.
    
    Incidently, my customer has seen the problem between VAX & VAX, though
    it most often seems to arise between VAX to Alpha.
    
    Cheers,
    Steve.
    
4102.12Dangling objects is DECnet issue, not ACMSCSC32::D_CAREWWed Feb 26 1997 23:3750
    
    |>
    |>One of the IPMTs talked about dangling objects--those not attached
    |>to processes, because they hadn't been deleted.
    |>In the case I was involved in, we don't think there were danglinig
    |>objects as ACMS had come down OK the night before.
    |>
    	That IPMT may have been one I was involved in.  In my experience, 
        ACMS comes down fine the night before (or whenever).  However,
        after it is gone, you can still see ACMS task-to-task objects
        named ACM$xxxxxxxx  where xxxxxxx is some number.  DECnet P4
        NCP show known links command will show these.
    
        These objects are dangling, and they seem to cause trouble for
        the next incarnation of ACMS on the FE where they persist.  It
        seems that *any* CP which gives the FE errnetcre error when it
        connects to a BE EXC will then cause task cancellation and 
        SRVNOTFOUND errors whenever it submits tasks to that EXC.  
        Frustrated users will logout and back in and eventually get to 
        a good CP.  
    
        It might be that stop/id on the 'bad' CP's would work around it
        (never tried in the case I recall).  New perm CP's might establish
        new objects which do not 'clash' with the dangling ones, or
        whatever...
    
        What *did* work was adding a check for ACM$xxxxxx task objects
        in DECnet after ACMS was brought down nightly (and before the
        new ACMS was run up on the FE).  If any dangling objects of
        that name were found, then the command proc actually re-started
        DECnet on the FE node before bringing up ACMS.  This is a 
        pretty drastic workaround -- any network-based sessions outside
        of ACMS are obviously affected, etc.  But it seemed to work.
    
        DECnet legend (notes conf notes regarding dangling objects in
        non-ACMS cases) has it that there is some NCP command with is
        supposed to take out links--- but that when a link persists
        beyond its owning process, the command is useless.  It might be
        worth looking up and attempting to use it in this ACMS case.
    
    For my money, this is a DECnet problem, pure and simple.  Maybe if
    enough people IPMT it, they will come out of denial (not reproducible)
    and chase this bug down and shoot it.
    
    Dave Carew
    
    PS -- It does seem to be the case that popping ACMS up/down daily
          gives this bug more chance to happen-- but the sites which
          do this generally have good reasons for doing it!
          
4102.13KERNEL::PULLEYCome! while living waters flowThu Feb 27 1997 05:2326
    Dave,
    
    I thought it was the NCP> show known object
    that would show the dangling objects--but having written that I'm not
    so sure.
    As for the shooting down the CP's that are broken, we've not tryed this
    as yet, but whether it works or not, probably depends on the algorithm
    for the CP choosing it's object name--particularly with a dangling
    object.
    All a bit speculative.
    One way of getting a badparam is by trying to create the same object
    twice, so if you've an object left there, you might eventually clash.
    My customer has basically assured me that they don't have objects left
    from the previous ACMS shutdown, so it should be a name clash that's
    not quite so straight forward, or something completely different.
    I've checked the audit, for around the time they got the problems, and
    if there is any corrolation between remote requests to when they get
    errnetcre, it's very loose.
    I.e., five out of six of the times they got the errors, there were two
    or three attempted connections from this front end to the same back end
    plus application.
    But that doesn't prove anything name wise or not.
    
    Cheers,
    Steve.
    
4102.14?CSC32::J_HENSONDon&#039;t get even, get ahead!Fri Mar 07 1997 09:3511
I need to do something with this.  Once again, should I tell them to upgrade
their version of acms, spr this, or ask for more information?  If
the answer is to ask for more information, what information to you need?

This problem is occurring on a rather frequent basis, although the
customer isn't pushing hard at this time.  As we all know, though,
this is subject to change without notice.

Please advise.

Jerry
4102.15OHMARY::HALLBill Hall - ACMS Engineering - ZKO2-2Fri Mar 07 1997 10:116
    
    	Upgrading ACMS will not correct the problem.  SPR the problem
    against DECnet not ACMS.
    
    Bill
    
4102.16okCSC32::J_HENSONDon&#039;t get even, get ahead!Fri Mar 07 1997 16:2012
>>  <<< Note 4102.15 by OHMARY::HALL "Bill Hall - ACMS Engineering - ZKO2-2" >>>

    
>>    	Upgrading ACMS will not correct the problem.  SPR the problem
>>    against DECnet not ACMS.
    
Will do.

Thanks,

Jerry    

4102.17?KERNEL::PULLEYCome! while living waters flowMon Apr 21 1997 12:0825
    Recently, my customer's been having the similar problems again.
    We first looked in swlup on the front end--(star8)--and found the
    errnetcre, and badparam, errors for CP 30 & 48.
    So, we did, again on the front end NCP> show known object char
    There were many acm$00010%%% objects E.g., for CP's 1 & 2 acm$0001017a
    and acm$0001017d.
    It looked almost like by following more of the CP's and their
    associated
    object names, that an object name is like acm$<number> where number is
    C+(<number of CPs> -1)*k.
    (C and K are not quite constant, but it works most of teh time).
    So, E.g., for our CP 30 & 48 we should have had acm$0001017a+29*3=
    acm$000101d1 and acm$0001017a+47*3=acm$00010207.
    Now those objects were indeed there.
    But they were attached to pids that were not showing up in show system,
    or analy/system, or accounting since last reboot.
    
    There were a couple of nonfatal bugchecks in
    analy/error/include=bugcheck/since=... but I can't tell what processes
    they were--the pids don't match up with the one's on those objects, but
    I think they are in a completely different format.
    
    If an ACMS process wnet over in exec mode, would it have chance to run
    the exit handler to clear it's network object?