[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

4171.0. "Share image corruption when accessing MDB" by CSC32::D_BUTLER () Tue May 20 1997 20:34

More front-end problems are becoming apparent at Pacificare. This is the
latest. They would appreciate feedback if the problem is a known one but
as documented in this note they are not yet prepared to upgrade their
software. Your comments are as usual appreciated in anticipation.
-------------------------------------------------------------------------------
Dave Butler


at time of ACMS/ENTER/NORETURN

SWLUP DATA IS:

forms-f-fatinterr, fatal internal error
forms-f-intdatcor , internal data corruped at 5 in forms$wmg_open_display
forms-f-mgrciobase, form$manager = 00142800, forms$cioshr = 001d0400
lib-f-badbdloadr, bad block address

TERMINAL DATA IS:
acmstu-i-cpi or user thread died

reported from front-end image 

	SYS$SHARE:ACMS_MENU.EXE

This occurs as the system is trying to display the menu (standard MDB)
and the terminal locks. A reset clears the terminal and the user
can get on the system with another ACMS/ENTER. It appears to be related 
to a single CP.

Not able to stop terminal subsystem controller there are 1000 people logged 
on at present. TSC will be recycled along with rest of system at 6 pm this 
evening. So hopefully this rogue CP problem will go away.

-------------------------------------------------------------------------------
Current versions are ACMS v4.0-2 and Decforms 1.4-5.

I raised the issue of upgrading to v4.2 of ACMS as requested by engineering
in order to trace these front-end problems but the technical staff are having
some difficulty getting an OK on that upgrade.
-------------------------------------------------------------------------------
Dave Butler

T.R Title User Personal
Name Date Lines

4171.1 GEM02::GASS Wed May 21 1997 16:40 29

T.R	Title	User	Personal Name	Date	Lines
4171.1		GEM02::GASS		`Wed May 21 1997 16:40`	29
	Is this the same node that is having the DECNET problems? The customer should think of upgrading to DECforms V2.2 along with ACMS 4.2. Since, they are receiving DECforms errors, this should be cross posted in the DECforms notes file. You might also check in the DECforms notes files for pointers to all the patches to 1.4-5, this should bring them to either 1.4-12 or 1.4-13. Are there any other problems in the SWL file? How is this related to a single CP? Do they see a lot of data set hanups on the effected CP? Do all users within the "bad" CP become effected? What happens when another user is assigned to the "bad" CP? You could do a stop-id on the effected CP, of course this would logout any of the other users within a CP. Gail


     Is this the same node that is having the DECNET problems?

     The customer should think of upgrading to DECforms V2.2
     along with ACMS 4.2.

     Since, they are receiving DECforms errors, this should be
     cross posted in the DECforms notes file.  You might also
     check in the DECforms notes files for pointers to all the
     patches to 1.4-5, this should bring them to either 1.4-12
     or 1.4-13.

     Are there any other problems in the SWL file?

     How is this related to a single CP?

     Do they see a lot of data set hanups on the effected CP?

     Do all users within the "bad" CP become effected?

     What happens when another user is assigned to the "bad" CP?

     You could do a stop-id on the effected CP, of course this would
     logout any of the other users within a CP.

     Gail