Conference azur::mcc

3022.0. "TSAM T1.2.7 VMS BUG CHECKS ON ^Y" by CLARID::PATEL (We'll get it right on the night) Tue May 19 1992 05:02

    VS3100 MDL76, 36 Meg memory loads a disk space,  VMS V A5.5-4X6 DECmcc
    T1.2.7, ELM t1.2.7 and TSAM T1.2.7
    
    The following command seems to hang.  It was issued in a com file on a
    batch que some 14 hrs ago and is still there....  When I issued the
    command interactivly I was able to get output if I hit ^C.  
    
    **IF I HIT ^Y I GET A MESSAGE (IMAGE ABORTED BY ^Y) THEN THE SYSTEM BUG
    CHECKS, IF I KILL THE BATCH JOB WHERE THE COMMAND WAS RUNNING THE
    SYSTEM BUG CHECKS AS WELL**
    
    $ mana/e
    DECmcc (T1.2.7)
    
    MCC> show terminal_server local_NS:.e111s1 port * number
    
    PANPAN::SYSTEM 09:14:13 MCC_MAIN  CPU=00:00:08.31 PF=3828 IO=2767 MEM=6426
    PANPAN::SYSTEM 09:35:05 MCC_MAIN  CPU=00:00:08.47 PF=3830 IO=2768 MEM=6428
    PANPAN::SYSTEM 09:35:06 MCC_MAIN  CPU=00:00:08.48 PF=3830 IO=2769 MEM=6428
    
    NOW I hit ^C
    
    [this is the output]
    
    
    Terminal_Server LOCAL_NS:.e111s1 Port 1
    AT 19-MAY-1992 09:12:00 Identifiers
    
    The requested operation cannot be completed
                          VMS Routine Error = %NONAME-F-NOMSG, Message
    number
                                              00000004
    
    Terminal_Server LOCAL_NS:.e111s1 Port 2
    AT 19-MAY-1992 09:38:00 Identifiers
    
                                     Number = 2
    
    Terminal_Server LOCAL_NS:.e111s1 Port 3
    AT 19-MAY-1992 09:38:01 Identifiers
    
                                     Number = 3
    
    Terminal_Server LOCAL_NS:.e111s1 Port 4
    AT 19-MAY-1992 09:38:01 Identifiers
    
                                     Number = 4
    
    Terminal_Server LOCAL_NS:.e111s1 Port 5
    AT 19-MAY-1992 09:38:01 Identifiers
    
                                     Number = 5
    
    Terminal_Server LOCAL_NS:.e111s1 Port 6
    AT 19-MAY-1992 09:38:01 Identifiers
    
                                     Number = 6
    
    Terminal_Server LOCAL_NS:.e111s1 Port 7
    AT 19-MAY-1992 09:38:01 Identifiers
    
                                     Number = 7
    Terminal_Server LOCAL_NS:.e111s1 Port 8
    AT 19-MAY-1992 09:38:01 Identifiers
    
                                     Number = 8
    MCC>
    

From the exchange of mail I found this morning in my mailbox,
after getting back from two days of training, I gather this
problem has been solved?

I've encountered the symptoms you describe, and have not been able to
reliably reproduce the problem.  Your best bet is to disable and re-enable
TSAM, the easiest way to do this is to execute @SYS$STARTUP:MCC_TS_AM_STARTUP
at DCL level.

As for TSAM crashing or bug-checking VMS, since TSAM has no inner-mode code,
it could not directly cause a crash to occur.

-Dave

    The problem was oly seen on a FT 5.5 (A5.5-4X6), It could not be
    reproduced on the SSB A5.5 release.
    
    Thanks Amrit

Unfortunately, even after the upgrade to 5.5, I am having the same problem. 
I am testing some software on two machines and on one machine, the command

MCC>SHOW TERMINAL_SERVER e123s4 port * 

hangs.
When I than press ctrl-C, I get:

MCC> show terminal_server e111s1 port *
Using default ALL IDENTIFIERS
<---hangs.press cntrl-c

Terminal_Server LOCAL_NS:.e111s1 Port 1
AT 30-JUN-1992 11:56:02 Identifiers

Examination of attributes shows:
                                 Number = -- Attribute Not Available
%MCC-S-CANCELED, serviced cancel request calls


On the other machine I get:

MCC> show terminal_server e111s1 port *
Using default ALL IDENTIFIERS

Terminal_Server SSPVBI_NS:.e111s1 Port 1
AT  1-JUL-1992 11:52:18 Identifiers

Examination of attributes shows:
                                 Number = 1

Terminal_Server SSPVBI_NS:.e111s1 Port 2
AT  1-JUL-1992 11:52:22 Identifiers

Examination of attributes shows:
.
..
MCC>exi


Both machines have :VMS 5.5, 32 Mb, DECmcc 1.2.7, TS 1.0.7, the same accounts
with the same quotas. The only difference is that one is a microVAX 3800
(works ok) and the other is a VAXstation 3100 (hangs).

I restarted the TS AM but with the same result.

Any other ideas?

I'll try to investigate this further.

Timo

I've made a new kit with the bug-fix to this problem to tide folks over
until TSAM V1.0 comes out.  It is located on TOOK::TSAM$KITS:.

-Dave