Is there a kill command within TTY? 1

[dabble]

Somehow I have a complete system DNB listing scrolling on my TTY via Procomm that I can't stop. I have tried typing in **** and hitting enter - nothing. I have tried typing in END - nothing. How can I stop this? I have a CS1000M at rls 4.5.

Even when I disconnect from procomm then re-connect it just picks up where I left off.

Thank you.

 

[dabble]

It finished, but now when at the NACT I start to type in * and it comes back with REQ: I try * again - it comes back with REQ PRT. It's almost like the only command it will recognize is enter, no matter what keys I press. I will try a reboot in case it is my PC, although I am typing in this forum without any problems! Weird!

 

[GHTROUT]

In LD20/22 DNBs a single star does not do what it does for every other overlay. I'm not sure why 4 stars would not work, although it sometimes has to do with the system buffering so much of the DNB before it accepts your stars.

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[dabble]

Did the reboot of my PC - just started back where I left off.

So I logged in on our technician's TTY port (TTY04) and I still see my previous session - is there a way I can kill the TTY01 session?


OVL111 IDLE 0
OVL111 TTY 01 20 COLLIER
.
TTY #04 LOGGED IN COLLIER 15:16 19/5/2009

 

[GHTROUT]

From the Level 2 password, you can log in, then at >

>FORC 1



[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[dabble]

I don't have the level 2 password. I guess I will place a repair call.

 

[Johnthephoneguy]

Isnt the FORC command an option that can be set on each LAPW? You would have to be set up that way before now to use it though.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[GHTROUT]

I'd just wait for it to time out. It won't stay logged in.

I'd also make sure you have your systems level 2 password.

If that isn't possible, ask them to create an LAPW for you, with OPT FORCA MONA (Force and Monitor)

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[dabble]

OK Thanks. I will try logging in later tonight and see what I get.

 

[GHTROUT]

@Johnthephoneguy: FORC can be used from PWD2 also. But fer sure, I prefer LAPWs for even myself - they do more. You can also X1 (block overlay 1) so you never LD 1 by accident

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[SpelingChampeon]

The only 'kill' command in the LD's are either END or ****'s, and they work for just about every LD you are in. Even though you hit ****, you might still see some printing, but that may only be what has been dumped to the buffer on your terminal at that point. NOTE: You should not stop LD 1 TEMPLATE AUDITS or LD 43 EDD.

First thing I would do is check the settings on the PBX for whatever TTY port you are having an issue with. Then check the settings on your PCP terminal to see if they are a match. It seems to me that the (*) key is not being recognized by either PCP or the TTY. Next I would swap the TTY port that your 'technician' uses with the TTY port you use, and see if the problem continues.

If you call in a repair, and the problem is with your PCP setup or COM PORT setup, you might get billed for it.

 

[GHTROUT]

Could it be LON or LOF?

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[dabble]

I tried to connect last evening thinking it would timeout. But now when I connect, it doesn't do the scrolling of the DNB anymore, but it also doesn't recognize any key I type in - it thinks everything I type in is an enter command. This is what I get:

TTY 01 SCH MTC 19:17
OVL111 IDLE 0
>Procomm Plus Ready!


TTY 01 SCH MTC 19:19
OVL111 IDLE 0
>

TTY 01 SCH MTC 19:19
OVL111 IDLE 0
>

Then when I type in LOGI and hit enter I just get the TTY01 SCH MTC line.

I tried creating another Procomm dial up just in case, but same thing happened.

The LON / LOF - how would that get changed?

Perhaps my TTY01 port is corrupt? May have to do a sysload.

 

[GHTROUT]

Set CAPS LOCK on your keyboard if it isn't.

Disable and Re-enable of the TTY port will cure many TTY problems.

An INI also solves many. That will also log everyone out.

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[dabble]

I tried the disable / enable of the TTY port and a modem reset. No luck. I guess an INI is the fix - will have to do that after hours....

 

[TimAbney]

You could also connect a pc or terminal directly to the tty port to make sure it isn't a communcation issue before you ini.