I have another issue with Hercules: ** Win32 porting error: invalid call .....

[Small]

I'm not sure if this is the right place to post this. If not, please let me know.

I've been geeing these errors on hercules lately, while running the TK system. Once this happens, I cannot recover, and the system is dead until I restart Hercules!

07:37:15 panrate 1000
07:37:15 HHCPN013I EOF reached on SCRIPT file. Processing complete.
07:37:15 HHCAO001I Hercules Automatic Operator thread started;
07:37:15 tid=0000239C, pri=0, pid=5744
07:37:17 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:0010
07:37:23 ipl 0148
07:37:26 HHCCD001I Readahead thread 1 started: tid=00001DE8, pid=5744
07:37:26 HHCCD001I Readahead thread 2 started: tid=0000018C, pid=5744
07:37:26 HHCCD002I Writer thread 1 started: tid=000006EC, pid=5744
07:37:26 HHCCD003I Garbage collector thread started: tid=00000A84, pid=5744
07:37:28 HHCCD002I Writer thread 2 started: tid=000018E8, pid=5744
07:37:32 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C0
07:37:32 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C1
07:37:33 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C2
07:37:33 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C3
07:39:03 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C4
07:39:08 HHCTE007I 3270 device 00C4 client 127.0.0.1 connection closed
07:39:15 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C4
07:39:20 HHCTE007I 3270 device 00C4 client 127.0.0.1 connection closed
07:40:37 console: DBG032: select failed: An operation was attempted on something that is not a socket.
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
07:40:37 console: DBG028: select: No error
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)

[halfmeg]

Post by Small
I'm not sure if this is the right place to post this. If not,
please let me know.

Not sure whether it is a Hercules or a Hercules on Windows issue. Posting in hercules-390 forum would likely be best place for this.

Post by Small
I've been geeing these errors on hercules lately, while running the
TK system. Once this happens, I cannot recover, and the system is
dead until I restart Hercules!
<snip>
07:37:17 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:0010
07:37:23 ipl 0148
<snip>
07:37:32 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C0
07:37:32 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C1
07:37:33 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C2
07:37:33 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C3
07:39:03 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C4
07:39:08 HHCTE007I 3270 device 00C4 client 127.0.0.1 connection closed
07:39:15 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C4
07:39:20 HHCTE007I 3270 device 00C4 client 127.0.0.1 connection closed
07:40:37 console: DBG032: select failed: An operation was attempted on something that is not a socket.
07:40:37 ** Win32 porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
<snip>

There has been a problem ( bug ? ) when numerous 3270 terminals are started all at once. Noted above that 0C4 is delayed 1.5 minutes to connect after 0C1-0C3 connect and then disconnects 5 seconds later. Connects again after 7 seconds and disconnects again 5 seconds later. This may be the cause of the repeated messages and 'hang' you are experiencing.

Believe some have inserted a pause of 1 or 2 seconds or similar in the startup script between start of each terminal.

Phil - YMMV

[Roger W. Suhr]

Thanks so much for this explanation!



Roger



From: turnkey-mvs-***@public.gmane.org [mailto:turnkey-mvs-***@public.gmane.org] On
Behalf Of halfmeg
Sent: Tuesday, September 07, 2010 12:11 PM
To: turnkey-mvs-***@public.gmane.org
Subject: [turnkey-mvs] Re: I have another issue with Hercules: ** Win32
porting error: invalid call ...

I'm not sure if this is the right place to post this. If not,
please let me know.

Not sure whether it is a Hercules or a Hercules on Windows issue. Posting in
hercules-390 forum would likely be best place for this.

I've been geeing these errors on hercules lately, while running the
TK system. Once this happens, I cannot recover, and the system is
dead until I restart Hercules!
<snip>
07:37:17 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:0010
07:37:23 ipl 0148
<snip>
07:37:32 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C0
07:37:32 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C1
07:37:33 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C2
07:37:33 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C3
07:39:03 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C4
07:39:08 HHCTE007I 3270 device 00C4 client 127.0.0.1 connection closed
07:39:15 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C4
07:39:20 HHCTE007I 3270 device 00C4 client 127.0.0.1 connection closed
07:40:37 console: DBG032: select failed: An operation was attempted on

something that is not a socket.

07:40:37 ** Win32 porting error: invalid call to 'w32_select' from

console.c(2129): mixed set(s)

<snip>

There has been a problem ( bug ? ) when numerous 3270 terminals are started
all at once. Noted above that 0C4 is delayed 1.5 minutes to connect after
0C1-0C3 connect and then disconnects 5 seconds later. Connects again after 7
seconds and disconnects again 5 seconds later. This may be the cause of the
repeated messages and 'hang' you are experiencing.

Believe some have inserted a pause of 1 or 2 seconds or similar in the
startup script between start of each terminal.

Phil - YMMV