Conference iosg::all-in-1_v30

4178.0. "Problems with TRaining while tracing" by GIDDAY::BURT (Scythe my dandelions down, sport) Thu May 19 1994 02:45

Hello and Greetings.

Customer running ALL-IN-1 IOS V3.0

Doing TRaining while tracing causes looping and other nasties.

The customer trace argument form was invoked from the MAIN menu, and looked 
like this:


                            Trace Flag Argument Form

     1  FLOW (calls to OAFRM or OAFLO)   1  SCRIPT
     1  SCRINP (script input)            1  SYMBOL
     1  IO (file access)                 1  FORM
     1  ALL (all flow processing)        1  FUNCTION
     1  INPUT (terminal input)           1  FIELD
     0  DCL (verify)                     1  PUT
     1  STACK (form-stack dump)          1  COMMAND
     0  HELP (help calls)                1  BLP
     1  IVP (ivp commands)               1  IMAGE
     1  MESS (messages to line 24)
     0  A1LOG (ALL-IN-1 logging)
     0  DPEINI (DPE init commands)
     0  MAIL (generic mail information)
     0  LOG (trace to logfile)           a1_trace.log
     0  TERM (trace to terminal)         0  APPEND (append log to above file)

He then invoked the TR option for training, and selected TR3 for user 
training.
Things then started to get weird. The training prompts did not match on the
screen, causing a multitude of errors and eventually a loop occurred which
could only be stopped by doing a control C, then turning tracing off. If
tracing was left ON, no terminal input was seen as valid.
With tracing OFF, the training options seem to work just fine. I get the same
behaviour on our non-customised, mup'd v3 system. I've not tried any other 
menu options, this seemed sufficiently ghastly.

The loop included some VERY fast pasrt the eyes something about EXIT F10, and
something VT100 - the trace did not capture it. The trace can be found at
RIPPER::USER$TSC:[BURT]Q51816.LOG_T3;1

Thanks & regards,

Chele