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

Conference dssdev::tdms

Title:	TDMS comments/questions
Notice:	See note 443.5 for V1.9A netkits
Moderator:	DSSDEV::SYSTEM

Created:	Tue Mar 04 1986
Last Modified:	Wed May 14 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	596
Total number of notes:	1599

595.0. "ACMS error "Cancel results from a TDMS error"" by HGOSPS::MICKWIDLAM () Tue Apr 22 1997 22:48

    I have a customer running TDMS V1.9A-1 and ACMS V4.0-2. Recently he got
    lot of errors from ACMS which is related to TDMS. The ACMS's audit log
    showed lot of these error:
    
    ************************************************************
    Type   : TASK      Time   : 22-APR-1997 15:04:51.11
    Appl   : GSMPROD
    Task   : CUSTOMER_INQUIRY
    User   : T247247SHP
    ID     : A::00CD03CE-0000004B-ED9D74A7-009B2F15
    Sub    : A::00CD03CE-00000000-ED9D74A7-009B2F15
    Text   : Task start failed during initialization
    Cancel results from a TDMS error
    ************************************************************
    
    The users were just enter from ACMS main menu to sub-menu screen (user
    run ACMS/ENTER and chose an option). They were failed to enter to the
    sub-menu screen and the screen prompted "Cancel results from a TDMS
    error".
    
    Anyone seen similar problem? How can I get more information from TDMS?
    I learnt that there is a logical TSS$TRACE_OUTPUT but I don't know how
    exactly it works (or how exact to make it works).
    
    Thanks and regards,
    Mickwid.

T.R	Title	User	Personal Name	Date	Lines
595.1		CLUSTA::HALL	Bill Hall - ACMS Engineering - ZKO2-2	`Wed Apr 23 1997 20:11`	14
	Define TSS$TRACE_OUTPUT to point to a directory and a file spec. It has to be visible to the process doing the TDMS I/O. If it's a menu, then CP has to see it. If it's a non-distributed system, then the EXC has to see it. If it's a distributed system, then it's CP again that has to see it. More than likely it cannot find the request or the form has some non-printable characters. Bill
595.2	possible ACMS problem?	HGOSPS::MICKWIDLAM		`Thu Apr 24 1997 05:45`	14
	re .1 > More than likely it cannot find the request or the form > has some non-printable characters. This is a possible. If we assume this is the non-printable character causing the problem, where does it come from? The user is just enter from ACMS main menu and even the first screen was not seen when the problem happen. In addition, the problem happened intermittenly. Will this a possible ACMS problem, or ACMS tuning problem? I've cross posted this problem on ACMS notes. Thanks and regards, Mickwid.
595.3		2868::HALL	Bill Hall - ACMS Engineering - ZKO2-2	`Thu Apr 24 1997 07:41`	22
	Trace will tell you exactly what when wrong. If it is an unprintable character, it will tell you the field it was trying to display. It sounds like your menu displays OK and then you select a task which presents a menu and this is where the problem occurs. This could happen if someone changed a record definition and used an initial value. The TDB contains the workspaces with the initial values as specified in the CDD. When a task starts, the workspaces are initialized to those values. More than likely, your request contains something like OUTPUT %ALL as the first statement (I think TDMS does all output statements first anyways regardless of the position in the request definition). I'd look at when this problem started and see what has changed since then. Running TRACE all the time will slow the system down and consume disk space. Please keep this discussion here and not in ACMS. I doubt it's an ACMS issue. Bill
595.4		HGOSPS::MICKWIDLAM		`Fri Apr 25 1997 04:57`	39
	re .3 I don't know if it is really not related to ACMS. I post here the ACMSGEN parameters here for reference. The customer usually have 450 tasks active: Parameter Name Current -------------- ------- MAX_LOGINS 500 MAX_TTS_CP 25 PERM_CPS 1 CP_SLOTS 20 MIN_CPIS 2 TSC_USERNAME ACMS$TSC TSC_PRIORITY 4 ACC_USERNAME ACMS$ACC ACC_PRIORITY 4 CP_USERNAME ACMS$CP CP_PRIORITY 4 MAX_APPL 10 MSS_POOLSIZE 2048 MSS_MAXBUF 30000 MSS_MAXOBJ 3000 WS_POOLSIZE 512 WSC_POOLSIZE 128 TWS_POOLSIZE 64000 TWSC_POOLSIZE 1024 NODE_NAME A MSS_PROCESS_POOL 1024 MSS_NET_RETRY_TIMER 10 QTI_USERNAME ACMS$QTI QTI_PRIORITY 4 QTI_SUB_TIMEOUT 7200 QTI_RETRY_TIMER 1800 QTI_POLLING_TIMER 5000 Regards, Mickwid.
595.5		2868::HALL	Bill Hall - ACMS Engineering - ZKO2-2	`Fri Apr 25 1997 08:04`	7
	You will not be able to find the cause of this problem without using TRACE. Since you've filed an IPMT case there will be no further discussion here. Bill