Skip to main content

Hi guys,

yesterday i put a question on  Micro Focus Visual COBOL Discussions, (look at end of this post **) Blair Mcdonald suggest asking here...

let me summarize: installed Object Cobol on debian, never used since purchase (2002). 

all is working, but in accept i have bell and 'That keystroke has no meaning here'.

Seems the program gets some strange input.. Then it stops regularly for user data, bua the same thing happens on any accept...

using PuTty in telnet with TERM=ansi from the PC side it does not happen?!

With out Terminal emulator (Ericom) we have this problem.

I have checked the dialog with tcpdump (see listing) with a small program...

Please have a look and tell me why the cobol program send the error message, without receiving any input...

I know that the product is old etc etc, but where should be a way to exlain the thing and fix it..

Let me know any needed info.

Thanks in advance.

Dario

The enviroment: 

Linux debian 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux

root@debian:/a/tio# cob -v
cob -C nolist -Bdynamic=c -Bdynamic=oops -Bdynamic=stdc++ -v
I see no work
root@debian:/a/tio# cobrun -v
/opt/lib/cobol/rts32
V4.1 revision 40 build 10/10/2 G; 24801. Run Time System OXCTY/AA0/00000H

the test program:


root@debian:/a/tio# cat test.cbl
IDENTIFICATION DIVISION.
PROGRAM-ID. TEST.
AUTHOR. STUDIO-3C.
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
SPECIAL-NAMES.
DECIMAL-POINT IS COMMA
CONSOLE IS CRT.
DATA DIVISION.
WORKING-STORAGE SECTION.
77 campo1 pic x(10).
77 campo2 pic x(10).
77 campo3 pic x.
PROCEDURE DIVISION.
MAIN SECTION.
PRELIMINARI.
DISPLAY SPACE AT 0101.
move space to campo1 campo2 campo3.
move "bb" to campo1.
ll.
display "campo1:" at 0301.
display "campo2:" at 0501.
accept campo1 at 0315.
move campo1 to campo2.
accept campo2 at 0515.
display "ok" at 0701.
accept campo3 at 0704.
display " " at 0701.
go ll.

heare find the packet dump, just breaking program after first accept:

from Ericom terminal emulator:

# cat ericom.lst
16:05:03.079627 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [P.], seq 1409536325:1409536327, ack 340490048, win 1023,
length 2
0x0000: 4500 002a 665e 0000 7f06 b2d9 c0a8 5044 E..*f^........PD
0x0010: c0a8 5101 dd9f 0017 5403 d145 144b 7740 ..Q.....T..E.Kw@
0x0020: 5018 03ff eda9 0000 0d00 0000 0000 P.............
16:05:03.081418 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.56735: Flags [P.], seq 1:13, ack 2, win 502, length 12
0x0000: 4500 0034 d0c4 4000 4006 4769 c0a8 5101 E..4..@.@.Gi..Q.
0x0010: c0a8 5044 0017 dd9f 144b 7740 5403 d147 ..PD.....Kw@T..G
0x0020: 5018 01f6 2373 0000 0d0a 1b5b 3f32 3030 P...#s.....[?200
0x0030: 346c 0d00 4l..
16:05:03.136148 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [.], ack 13, win 1023, length 0
0x0000: 4500 0028 665f 0000 7f06 b2da c0a8 5044 E..(f_........PD
0x0010: c0a8 5101 dd9f 0017 5403 d147 144b 774c ..Q.....T..G.KwL
0x0020: 5010 03ff faa5 0000 0000 0000 0000 P.............
16:05:03.136261 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.56735: Flags [P.], seq 13:103, ack 2, win 502, length 90
0x0000: 4500 0082 d0c5 4000 4006 471a c0a8 5101 E.....@.@.G...Q.
0x0010: c0a8 5044 0017 dd9f 144b 774c 5403 d147 ..PD.....KwLT..G
0x0020: 5018 01f6 3b66 0000 1b5b 6d1b 5b31 306d P...;f...[m.[10m
0x0030: 1b5b 3337 3b34 306d 1b5b 6d1b 5b33 373b .[37;40m.[m.[37;
0x0040: 3430 6d1b 5b32 4a1b 5b48 1b5b 324a 1b5b 40m.[2J.[H.[2J.[
0x0050: 481b 5b32 4263 616d 706f 313a 1b5b 353b H.[2Bcampo1:.[5;
0x0060: 3148 6361 6d70 6f32 3a1b 5b33 3b31 3548 1Hcampo2:.[3;15H
0x0070: 6262 1b5b 353b 3848 1b5b 4a1b 5b33 3b31 bb.[5;8H.[J.[3;1
0x0080: 3548 5H
16:05:03.183082 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [.], ack 103, win 1023, length 0
0x0000: 4500 0028 6660 0000 7f06 b2d9 c0a8 5044 E..(f`........PD
0x0010: c0a8 5101 dd9f 0017 5403 d147 144b 77a6 ..Q.....T..G.Kw.
0x0020: 5010 03ff fa4b 0000 0000 0000 0000 P....K........
16:05:03.312441 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.56735: Flags [P.], seq 103:152, ack 2, win 502, length 49
0x0000: 4500 0059 d0c6 4000 4006 4742 c0a8 5101 E..Y..@.@.GB..Q.
0x0010: c0a8 5044 0017 dd9f 144b 77a6 5403 d147 ..PD.....Kw.T..G
0x0020: 5018 01f6 52dd 0000 071b 5b32 353b 3148 P...R.....[25;1H
0x0030: 5468 6174 206b 6579 7374 726f 6b65 2068 That.keystroke.h
0x0040: 6173 206e 6f20 6d65 616e 696e 6720 6865 as.no.meaning.he
0x0050: 7265 1b5b 333b 3135 48 re.[3;15H
16:05:03.355181 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [.], ack 152, win 1023, length 0
0x0000: 4500 0028 6661 0000 7f06 b2d8 c0a8 5044 E..(fa........PD
0x0010: c0a8 5101 dd9f 0017 5403 d147 144b 77d7 ..Q.....T..G.Kw.
0x0020: 5010 03ff fa1a 0000 0000 0000 0000 P.............

from Ericom terminal emulator:

# cat putty2.lst
16:36:16.155881 enp1s0 In IP 192.168.80.68.64119 > 192.168.81.1.23: Flags [P.], seq 791560031:791560032, ack 2010174593, win 1020,
length 1
0x0000: 4500 0029 6901 0000 7f06 b037 c0a8 5044 E..)i......7..PD
0x0010: c0a8 5101 fa77 0017 2f2e 3f5f 77d0 d481 ..Q..w../.?_w...
0x0020: 5018 03fc c6ca 0000 0d00 0000 0000 P.............
16:36:16.156806 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.64119: Flags [P.], seq 1:13, ack 1, win 502, length 12
0x0000: 4500 0034 e8e6 4000 4006 2f47 c0a8 5101 E..4..@.@./G..Q.
0x0010: c0a8 5044 0017 fa77 77d0 d481 2f2e 3f60 ..PD...ww.../.?`
0x0020: 5018 01f6 fc90 0000 0d0a 1b5b 3f32 3030 P..........[?200
0x0030: 346c 0d00 4l..
16:36:16.205310 enp1s0 In IP 192.168.80.68.64119 > 192.168.81.1.23: Flags [.], ack 13, win 1020, length 0
0x0000: 4500 0028 6902 0000 7f06 b037 c0a8 5044 E..(i......7..PD
0x0010: c0a8 5101 fa77 0017 2f2e 3f60 77d0 d48d ..Q..w../.?`w...
0x0020: 5010 03fc d3c6 0000 0000 0000 0000 P.............
16:36:16.205425 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.64119: Flags [P.], seq 13:103, ack 1, win 502, length 90
0x0000: 4500 0082 e8e7 4000 4006 2ef8 c0a8 5101 E.....@.@.....Q.
0x0010: c0a8 5044 0017 fa77 77d0 d48d 2f2e 3f60 ..PD...ww.../.?`
0x0020: 5018 01f6 1484 0000 1b5b 6d1b 5b31 306d P........[m.[10m
0x0030: 1b5b 3337 3b34 306d 1b5b 6d1b 5b33 373b .[37;40m.[m.[37;
0x0040: 3430 6d1b 5b32 4a1b 5b48 1b5b 324a 1b5b 40m.[2J.[H.[2J.[
0x0050: 481b 5b32 4263 616d 706f 313a 1b5b 353b H.[2Bcampo1:.[5;
0x0060: 3148 6361 6d70 6f32 3a1b 5b33 3b31 3548 1Hcampo2:.[3;15H
0x0070: 6262 1b5b 353b 3848 1b5b 4a1b 5b33 3b31 bb.[5;8H.[J.[3;1
0x0080: 3548 5H
16:36:16.252043 enp1s0 In IP 192.168.80.68.64119 > 192.168.81.1.23: Flags [.], ack 103, win 1026, length 0
0x0000: 4500 0028 6903 0000 7f06 b036 c0a8 5044 E..(i......6..PD
0x0010: c0a8 5101 fa77 0017 2f2e 3f60 77d0 d4e7 ..Q..w../.?`w...
0x0020: 5010 0402 d366 0000 0000 0000 0000 P....f........

---

**  yesterday post

--

ok, is not visual cobol related, but the previous object cobol product.

since 1987 we developed application for aix, then with the version for msdos we successfullly ported some application..

we used very basic part of the product, no screen section, accept/display standard.

in lan and wan using terminal emulator (ericom) we never had problems.

In 2002 we purchased the linux version of the product, but it went asleep till now...

Installed a debian 64bit (last version) with some struggle with os library x32, we get the cobol run on linux.   

using the same emulator seems all ok, except for this strange behaviour: the accept sound the bell, and claims 'That keystroke has no meaning here'.

Obviously no data was typed... after the message the data accept is normally done, but every field the bell and the message are replied.

I am looking for some help, any guy out there is available?

Online    

Hello Dario Cinquetti,

 

Welcome to the Micro Focus Visual COBOL community site. As you mentioned, Object COBOL Developer Suite is a very old product. It is no longer actively supported. I did a quick search in our database of old Support Cases, and didn't find anything matching the symptoms you've described.

 

It seems that you might be using an operating system that was not supported or tested with Object COBOL. You might want to contact your Rocket Software Account Manager, and look into moving your application to Visual COBOL on a supported platform. Here is a link to a page showing the supported Unix/Linux platforms for Visual COBOL.

 

One last thought - you might stand a slightly better chance of getting a reply by posting this in the forum for the Server Express product, as Server Express was the successor to Object COBOL. Someone who has used this older product might have encountered your issue and offer a suggestion.

Hi guys,

yesterday i put a question on  Micro Focus Visual COBOL Discussions, (look at end of this post **) Blair Mcdonald suggest asking here...

let me summarize: installed Object Cobol on debian, never used since purchase (2002). 

all is working, but in accept i have bell and 'That keystroke has no meaning here'.

Seems the program gets some strange input.. Then it stops regularly for user data, bua the same thing happens on any accept...

using PuTty in telnet with TERM=ansi from the PC side it does not happen?!

With out Terminal emulator (Ericom) we have this problem.

I have checked the dialog with tcpdump (see listing) with a small program...

Please have a look and tell me why the cobol program send the error message, without receiving any input...

I know that the product is old etc etc, but where should be a way to exlain the thing and fix it..

Let me know any needed info.

Thanks in advance.

Dario

The enviroment: 

Linux debian 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux

root@debian:/a/tio# cob -v
cob -C nolist -Bdynamic=c -Bdynamic=oops -Bdynamic=stdc++ -v
I see no work
root@debian:/a/tio# cobrun -v
/opt/lib/cobol/rts32
V4.1 revision 40 build 10/10/2 G; 24801. Run Time System OXCTY/AA0/00000H

the test program:


root@debian:/a/tio# cat test.cbl
IDENTIFICATION DIVISION.
PROGRAM-ID. TEST.
AUTHOR. STUDIO-3C.
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
SPECIAL-NAMES.
DECIMAL-POINT IS COMMA
CONSOLE IS CRT.
DATA DIVISION.
WORKING-STORAGE SECTION.
77 campo1 pic x(10).
77 campo2 pic x(10).
77 campo3 pic x.
PROCEDURE DIVISION.
MAIN SECTION.
PRELIMINARI.
DISPLAY SPACE AT 0101.
move space to campo1 campo2 campo3.
move "bb" to campo1.
ll.
display "campo1:" at 0301.
display "campo2:" at 0501.
accept campo1 at 0315.
move campo1 to campo2.
accept campo2 at 0515.
display "ok" at 0701.
accept campo3 at 0704.
display " " at 0701.
go ll.

heare find the packet dump, just breaking program after first accept:

from Ericom terminal emulator:

# cat ericom.lst
16:05:03.079627 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [P.], seq 1409536325:1409536327, ack 340490048, win 1023,
length 2
0x0000: 4500 002a 665e 0000 7f06 b2d9 c0a8 5044 E..*f^........PD
0x0010: c0a8 5101 dd9f 0017 5403 d145 144b 7740 ..Q.....T..E.Kw@
0x0020: 5018 03ff eda9 0000 0d00 0000 0000 P.............
16:05:03.081418 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.56735: Flags [P.], seq 1:13, ack 2, win 502, length 12
0x0000: 4500 0034 d0c4 4000 4006 4769 c0a8 5101 E..4..@.@.Gi..Q.
0x0010: c0a8 5044 0017 dd9f 144b 7740 5403 d147 ..PD.....Kw@T..G
0x0020: 5018 01f6 2373 0000 0d0a 1b5b 3f32 3030 P...#s.....[?200
0x0030: 346c 0d00 4l..
16:05:03.136148 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [.], ack 13, win 1023, length 0
0x0000: 4500 0028 665f 0000 7f06 b2da c0a8 5044 E..(f_........PD
0x0010: c0a8 5101 dd9f 0017 5403 d147 144b 774c ..Q.....T..G.KwL
0x0020: 5010 03ff faa5 0000 0000 0000 0000 P.............
16:05:03.136261 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.56735: Flags [P.], seq 13:103, ack 2, win 502, length 90
0x0000: 4500 0082 d0c5 4000 4006 471a c0a8 5101 E.....@.@.G...Q.
0x0010: c0a8 5044 0017 dd9f 144b 774c 5403 d147 ..PD.....KwLT..G
0x0020: 5018 01f6 3b66 0000 1b5b 6d1b 5b31 306d P...;f...[m.[10m
0x0030: 1b5b 3337 3b34 306d 1b5b 6d1b 5b33 373b .[37;40m.[m.[37;
0x0040: 3430 6d1b 5b32 4a1b 5b48 1b5b 324a 1b5b 40m.[2J.[H.[2J.[
0x0050: 481b 5b32 4263 616d 706f 313a 1b5b 353b H.[2Bcampo1:.[5;
0x0060: 3148 6361 6d70 6f32 3a1b 5b33 3b31 3548 1Hcampo2:.[3;15H
0x0070: 6262 1b5b 353b 3848 1b5b 4a1b 5b33 3b31 bb.[5;8H.[J.[3;1
0x0080: 3548 5H
16:05:03.183082 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [.], ack 103, win 1023, length 0
0x0000: 4500 0028 6660 0000 7f06 b2d9 c0a8 5044 E..(f`........PD
0x0010: c0a8 5101 dd9f 0017 5403 d147 144b 77a6 ..Q.....T..G.Kw.
0x0020: 5010 03ff fa4b 0000 0000 0000 0000 P....K........
16:05:03.312441 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.56735: Flags [P.], seq 103:152, ack 2, win 502, length 49
0x0000: 4500 0059 d0c6 4000 4006 4742 c0a8 5101 E..Y..@.@.GB..Q.
0x0010: c0a8 5044 0017 dd9f 144b 77a6 5403 d147 ..PD.....Kw.T..G
0x0020: 5018 01f6 52dd 0000 071b 5b32 353b 3148 P...R.....[25;1H
0x0030: 5468 6174 206b 6579 7374 726f 6b65 2068 That.keystroke.h
0x0040: 6173 206e 6f20 6d65 616e 696e 6720 6865 as.no.meaning.he
0x0050: 7265 1b5b 333b 3135 48 re.[3;15H
16:05:03.355181 enp1s0 In IP 192.168.80.68.56735 > 192.168.81.1.23: Flags [.], ack 152, win 1023, length 0
0x0000: 4500 0028 6661 0000 7f06 b2d8 c0a8 5044 E..(fa........PD
0x0010: c0a8 5101 dd9f 0017 5403 d147 144b 77d7 ..Q.....T..G.Kw.
0x0020: 5010 03ff fa1a 0000 0000 0000 0000 P.............

from Ericom terminal emulator:

# cat putty2.lst
16:36:16.155881 enp1s0 In IP 192.168.80.68.64119 > 192.168.81.1.23: Flags [P.], seq 791560031:791560032, ack 2010174593, win 1020,
length 1
0x0000: 4500 0029 6901 0000 7f06 b037 c0a8 5044 E..)i......7..PD
0x0010: c0a8 5101 fa77 0017 2f2e 3f5f 77d0 d481 ..Q..w../.?_w...
0x0020: 5018 03fc c6ca 0000 0d00 0000 0000 P.............
16:36:16.156806 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.64119: Flags [P.], seq 1:13, ack 1, win 502, length 12
0x0000: 4500 0034 e8e6 4000 4006 2f47 c0a8 5101 E..4..@.@./G..Q.
0x0010: c0a8 5044 0017 fa77 77d0 d481 2f2e 3f60 ..PD...ww.../.?`
0x0020: 5018 01f6 fc90 0000 0d0a 1b5b 3f32 3030 P..........[?200
0x0030: 346c 0d00 4l..
16:36:16.205310 enp1s0 In IP 192.168.80.68.64119 > 192.168.81.1.23: Flags [.], ack 13, win 1020, length 0
0x0000: 4500 0028 6902 0000 7f06 b037 c0a8 5044 E..(i......7..PD
0x0010: c0a8 5101 fa77 0017 2f2e 3f60 77d0 d48d ..Q..w../.?`w...
0x0020: 5010 03fc d3c6 0000 0000 0000 0000 P.............
16:36:16.205425 enp1s0 Out IP 192.168.81.1.23 > 192.168.80.68.64119: Flags [P.], seq 13:103, ack 1, win 502, length 90
0x0000: 4500 0082 e8e7 4000 4006 2ef8 c0a8 5101 E.....@.@.....Q.
0x0010: c0a8 5044 0017 fa77 77d0 d48d 2f2e 3f60 ..PD...ww.../.?`
0x0020: 5018 01f6 1484 0000 1b5b 6d1b 5b31 306d P........[m.[10m
0x0030: 1b5b 3337 3b34 306d 1b5b 6d1b 5b33 373b .[37;40m.[m.[37;
0x0040: 3430 6d1b 5b32 4a1b 5b48 1b5b 324a 1b5b 40m.[2J.[H.[2J.[
0x0050: 481b 5b32 4263 616d 706f 313a 1b5b 353b H.[2Bcampo1:.[5;
0x0060: 3148 6361 6d70 6f32 3a1b 5b33 3b31 3548 1Hcampo2:.[3;15H
0x0070: 6262 1b5b 353b 3848 1b5b 4a1b 5b33 3b31 bb.[5;8H.[J.[3;1
0x0080: 3548 5H
16:36:16.252043 enp1s0 In IP 192.168.80.68.64119 > 192.168.81.1.23: Flags [.], ack 103, win 1026, length 0
0x0000: 4500 0028 6903 0000 7f06 b036 c0a8 5044 E..(i......6..PD
0x0010: c0a8 5101 fa77 0017 2f2e 3f60 77d0 d4e7 ..Q..w../.?`w...
0x0020: 5010 0402 d366 0000 0000 0000 0000 P....f........

---

**  yesterday post

--

ok, is not visual cobol related, but the previous object cobol product.

since 1987 we developed application for aix, then with the version for msdos we successfullly ported some application..

we used very basic part of the product, no screen section, accept/display standard.

in lan and wan using terminal emulator (ericom) we never had problems.

In 2002 we purchased the linux version of the product, but it went asleep till now...

Installed a debian 64bit (last version) with some struggle with os library x32, we get the cobol run on linux.   

using the same emulator seems all ok, except for this strange behaviour: the accept sound the bell, and claims 'That keystroke has no meaning here'.

Obviously no data was typed... after the message the data accept is normally done, but every field the bell and the message are replied.

I am looking for some help, any guy out there is available?

Online    

Hello Dario Cinquetti,

 

Welcome to the Micro Focus Visual COBOL community site. As you mentioned, Object COBOL Developer Suite is a very old product. It is no longer actively supported. I did a quick search in our database of old Support Cases, and didn't find anything matching the symptoms you've described.

 

It seems that you might be using an operating system that was not supported or tested with Object COBOL. You might want to contact your Rocket Software Account Manager, and look into moving your application to Visual COBOL on a supported platform. Here is a link to a page showing the supported Unix/Linux platforms for Visual COBOL.

 

One last thought - you might stand a slightly better chance of getting a reply by posting this in the forum for the Server Express product, as Server Express was the successor to Object COBOL. Someone who has used this older product might have encountered your issue and offer a suggestion.

Hello Dario Cinquetti,

 

Thanks for posting on the forum related to Server Express, and for sharing some additional information. Hopefully this might get more attention from other users of the older COBOL products, who may have hit a similar issue.

 

It sounds like your test program works correctly with Putty, that your program is only having this issue with the Ericom terminal emulator?

 

You mentioned Ericom, what is the name of the actual terminal emulator you are using? This might help me search for information about supporting this terminal emulator in old Support Cases.

 

Have you checked with the vendor of the Ericom terminal emulator to see if they can recommend a particular TERM setting for use with their product on your O/S and platform?

 

If you change your example program so that the DISPLAY and ACCEPT statements do not use the AT option , does the ACCEPT work correctly? For example, instead of:

accept campo1 at 0315.

If you just have

accept campo1

 

Then, does that accept statement still get the error?

 

What TERM setting are you trying to use with the Ericom terminal emulator?

 

You might try experimenting with instead setting TERM to some of the following terminal types, to see if you get better behavior:

at386

at386-m

ansi

att605

xterm

qvt102

tty5420

vt100

vt100-w

vt220

wy50

wy60

wy60-w

wy75

wy85

wy120

wy120-25

-- end of list --

Terms & ConditionsAccessibility statement