| 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
|
|
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.
|