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

Conference ilbbak::ibi_focus

Title:FOCUS, from INFORMATION BUILDERS
Moderator:ZAYIUS::BROUILLETTE
Created:Thu Feb 19 1987
Last Modified:Mon May 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:615
Total number of notes:1779

143.0. "Phantom Focus Loop" by TOLKIN::WELLS () Thu Oct 20 1988 14:24

     I have recently encountered a problem with FOCUS initiating
     an infinite loop that gobbles up CPU like mad.

     I am running FOCUS V5.0 and I discovered FOCUS.EXE running for
     over 24 hrs with incredible system impact. There was no batch 
     job and no users in the account that was running it.

     I have no real clue as to what was going on , but I think it
     has a problem initializing the screen with SET TERM/DEVICE
     set to some types of devices, and somehow detached the process.

     Has anyone run into this or knows a work around ?
T.RTitleUserPersonal
Name
DateLines
143.1Need more infoHEIDI::MACKENZIEFri Oct 21 1988 12:466
    I too have had this 'phenomenom' occur.  I ended up tracing it back
    to the .FEX that was running.  The fex was using CASE logic in update
    mode.  Perhaps if you give a little more info re. the problem, sample
    code, etc., I can be of more help.
    
    Chris
143.2TOLKIN::WELLSMon Oct 24 1988 11:5834
     Here's some more info. on the problem:
    
    This procedure initiated a 30 clock hr/9 hrs of CPU use phantom loop
    
 in a detached process.

 ACCORDING TO THE OPENED FILES IN THE ACCOUNT THAT INITIATED THE LOOP

 THIS (BELIEVE IT OR NOT) WAS WHAT WE FOUND RUNNING :

FILENAME=EX1,SUFFIX=FOC                                                       
SEGNAME=ONE,SEGTYPE=S3                                                        
FIELDNAME=OPERATOR ID,ALIAS=ID,FORMAT=I3,$                                    
FIELDNAME=DATE,ALIAS=DT,FORMAT=I6MDY,$                                        
FIELDNAME=SHIFT,ALIAS=SH,FORMAT=I1,$                                          
FIELDNAME=SYSTEM,ALIAS=SY,FORMAT=A7,$                                         
FIELDNAME=DEVICE,ALIAS=DE,FORMAT=A4,$                                         
FIELDNAME=TEST,ALIAS=TE,FORMAT=A2,$                                           
FIELDNAME=TOTAL TESTED,ALIAS=TT,FORMAT=I6C,$                                  
FIELDNAME=TOTAL GOOD,ALIAS=TG,FORMAT=I6C,$                                    
FIELDNAME=TEST TIME,ALIAS=TI,FORMAT=D5.2,$                                    
FIELDNAME=NON TST TIME,ALIAS=NT,FORMAT=D5.2,$      

                           
TABLE FILE EX1                                                                
PRINT SHIFT AND DATE AND 'OPERATOR ID' AND SYSTEM AND DEVICE AND TEST AND     
'TOTAL TESTED' AND 'TOTAL GOOD' AND 'TEST TIME' AND 'NON TST TIME'            
BY 'OPERATOR ID'   SKIP-LINE                                                  
HEADING CENTER                                                                
"OPERATOR REPORT - VERSION 1"                                                 
END
 
REGARDS,
CHRIS                                                                           
143.3Looks like bad code...!!SCRUZ::PARKER_TYTyrone Parker WR03-2/M13Thu Nov 10 1988 20:0924
	I believe your problem could stem from a foxexec (REPORT) running
	that was coded incorrectly..

	For one, the Master File description looks BOGUS...
FIELDNAME=TOTAL TESTED,ALIAS=TT,FORMAT=I6C,$                                  
FIELDNAME=TOTAL GOOD,ALIAS=TG,FORMAT=I6C,$                                    
FIELDNAME=TEST TIME,ALIAS=TI,FORMAT=D5.2,$                                    
FIELDNAME=NON TST TIME,ALIAS=NT,FORMAT=D5.2,$      

	I don't think you can have fieldnames with embedded blanks...

	This may be why the report has statements like:
PRINT SHIFT AND DATE AND 'OPERATOR ID' AND SYSTEM AND DEVICE AND TEST AND     
'TOTAL TESTED' AND 'TOTAL GOOD' AND 'TEST TIME' AND 'NON TST TIME'            
BY 'OPERATOR ID'   SKIP-LINE                                                  

	This report probably would cause unpredictable results when FOCUS
	was trying to interpret the report and Master file description..

	Hope this helps...

	Tyrone.