| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1347.1 | | SNOFS1::ELLISS | Are you all sitting too comfybold square on your botty? - Then we'll begin | Tue Jul 30 1996 00:03 | 4 |
| It's probably because Kermit is sticking to VT100, or ANSI, controls.
I think PCM expects a minimum of VT200 series (there I may be wrong)
Shaun
|
| 1347.2 | | COMICS::MILLSS | Ivanova is God ! | Tue Jul 30 1996 09:36 | 10 |
| Re .1
I asked him about this and his Kermit terminal emulator thinks its a VT320. It
works OK with other apps that do screen things, i.e. MONITOR, TPU, etc.
The version of Kermit is V3.14, if that's of any use...
Thanks
Simon.
|
| 1347.3 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue Jul 30 1996 13:36 | 13 |
| >I have a customer who's using KERMIT to dial in to his PCM V1.6 system
>and then
>CONNECT to hosts, etc. Under VCS V1.4 this worked perfectly, but now
>PCM writes
>stuff to the screen as soon as you CONNECT where VCS didn't. This
>"screws up"
>their terminal emulator.
I don't understand how "writing stuff to the screen" is screwing up the
terminal emulator. Could you give me some more detail?
Regs,
Dan
|
| 1347.4 | | COMICS::MILLSS | Ivanova is God ! | Thu Aug 01 1996 03:10 | 30 |
| Hi Dan,
Here is the customer's latest thoughts on the subject. I think it describes the
behaviour he is seeing -
> I have now spent some time examining a dump of the screen output produced
> from the PCM Console Connect command. An extract is included below which
> I have annotated with the control character descriptions. I can honestly
> say I am not impressed.
> At the start of the output there is a lot of unnecessary screen controls.
> Why erase the screen 7 times? The output data is carefully presented a screen
> at a time, then immediately erased and the second screen output and so on.
> Making it impossible to read the display at normal terminal speeds of 9600
> and above, before it is erased (looks good at 300b, you must buy your
> programmers faster screens!). It would be better to output the data and
> allow the entire screen to scroll, since most modern terminals and emulators
> allow display scroll back of a mumber of pages. It is also interesting to note
> that large numbers of DCS (Device Control String) which are output without any
> parameters. What are these for? These are what cause the backwards question
> marks on DECterm displays.
I haven't included his extract and notes but I can make them available if you
want to see them.
I have also asked him to clarify exactly what he means by "screws up" his
emulator.
Thanks and regards,
Simon.
|
| 1347.5 | And the problem is ... | COMICS::MILLSS | Ivanova is God ! | Thu Aug 01 1996 04:45 | 22 |
| In the customer's own words, this is what he means by "screws up" his terminal -
> Symptoms appear to vary depending upon how data is output
> by PCM. The most common is that cursor is left some way
> down the screen after the line 'Type CTRL/E to exit or
> CTRL/G to escape to monitor' is output. At the same time
> the previously output data is still displayed both before
> and after the cursor position.
> The above is also sometimes accompanied with the symptom
> that it is not possible to enter commands to the target
> system or to enter CTRL/E to exit from the connect.
> CTRL/Y will take you back to the dollar prompt. After
> which commands which expect a VT300 terminal do not
> display output or fail to run. A SHOW TERMINAL command
> still indicates that the terminal is VT300_Series with
> all the correct attributes. The only way out of this is
> to terminate the session and login again.
Thanks and regards,
Simon.
|
| 1347.6 | Sorry, but... | COMICS::MILLSS | Quality bloke time and lager space | Mon Aug 05 1996 05:02 | 5 |
| Sorry to be a pest, but can anyone help me out here ?
Many thanks,
Simon.
|
| 1347.7 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Mon Aug 05 1996 14:54 | 15 |
| Simon,
I reread the info from the customer about the esc codes etc. I have
to wonder if he's really using the SELECT command from the
Monitor interface. Whenever your in MONITOR the terminal is
"controlled" using SMG routines. When your using the CONNECT
interface SMG is not being used. This business about the
screen repainting 7 times would only happen in Monitor. If you issue
the CONSOLE CONNECT command the screen will initially paint ala MONITOR
because MONITOR/CONNECT are the same image and you always run the
MONITOR initialization routines. Also, does the customer
have ECO 2? Their is a known hang in Monitor that was fixed by ECO 2.
There is actually a bug in SMG that had to be worked around.
Regards,
Dan
|
| 1347.8 | | COMICS::MILLSS | Quality bloke time and lager space | Thu Aug 08 1996 05:37 | 19 |
| Sorry, Dan, he *is* using a CONSOLE CONNECT from the DCL prompt...
> Below is a dump of a CONSOLE CONNECT session after installing ECO3. It can be
> clearly seen from this that the entire screen is cleared 7 times (records 7,
> 11, 13, 15, 17, 19 and 21). Also the cursor is moved to the same screen
> position 7 times (records 6, 10, 12, 14, 16, 18 and 20). Since ECO3 was
> applied the number of Device Control Strings (DCS) output appear to have
> reduced. However, they are still present (records 30, 34, 38 and 42) and
> display as a large backwards question mark. These are not in the original
> OPCOM message.
I think he means ECO2 in the above. There hasn't been an ECO3 yet, has there ?
The dump he mentions is available for viewing if you require it, but the
formatting seems to have been messed up by his DSN mail.
Thanks and regards,
Simon.
|
| 1347.9 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Aug 08 1996 14:39 | 12 |
| Simon,
Okay, but the dump he showing has to be the initial screen-paint
put up by the SMG routines used by Monitor. Whenever CONSOLE CONNECT
is issued you *always* enter MONITOR first and it goes through all the
screen gyrations. It's kinda silly actually and it really needs to be
changed.
Now, why this screws up his terminal emulator is interesting. If
it's a good emulator then it should handle it.
Regs,
dan
|