Re: Problems

--- In hercules-390@..., Gerhard Postpischil <gerhard@...> wrote:
>
> ** Win32 porting error: invalid call to 'w32_select' from
> console.c(2076): mixed set(s)
> console: DBG028: select: No error
>
> Both problems have occurred on earlier releases, also.

Yeah, I have that problem too (this one just now):

DBG028: select: No error
porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
DBG028: select: No error
porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
DBG028: select: No error
porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)
DBG028: select: No error
porting error: invalid call to 'w32_select' from console.c(2129): mixed set(s)

When I go through a sequence of something along the lines
of:

"startmvs autoipl"

and let it start up properly and fully.

Run "startterm" in c:\mvs380\conf

which starts 5 terminals really quickly.

Close them all down.

startterm again.

Close them all down again.  Last one triggers off
the select errors ...

21:38:07 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C0
21:38:18 HHCTE007I 3270 device 00C0 client 127.0.0.1 connection closed
21:38:31 console: DBG022: recv: An existing connection was forcibly closed by t
21:39:21 console: DBG022: recv: An existing connection was forcibly closed by t
21:39:21 console: DBG021: send: An existing connection was forcibly closed by t
21:39:21 console: DBG021: send: An existing connection was forcibly closed by t
21:39:21 console: DBG021: send: An existing connection was forcibly closed by t
21:39:21 console: DBG021: send: An existing connection was forcibly closed by t
21:39:21 console: DBG021: send: An existing connection was forcibly closed by t
21:39:43 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:00C0
21:40:05 console: DBG021: send: A request to send or receive data was disallowe
21:40:05 console: DBG021: send: A request to send or receive data was disallowe
21:40:05 console: DBG032: select failed: An operation was attempted on somethin
21:40:05 ** Win32 porting error: invalid call to 'w32_select' from console.c(21
21:40:05 console: DBG028: select: No error
21:40:05 console: DBG021: send: A request to send or receive data was disallowe
21:40:05 console: DBG021: send: A request to send or receive data was disallowe
21:40:05 ** Win32 porting error: invalid call to 'w32_select' from console.c(21
21:40:05 console: DBG028: select: No error
21:40:05 ** Win32 porting error: invalid call to 'w32_select' from console.c(21
21:40:05 console: DBG028: select: No error
21:40:05 ** Win32 porting error: invalid call to 'w32_select' from console.c(21
21:40:05 console: DBG028: select: No error
21:40:05 ** Win32 porting error: invalid call to 'w32_select' from console.c(21
21:40:05 console: DBG028: select: No error


I just tried again, more controlled, and this time
the problem only occurred at the end of the 3rd set
of startterm closures.

I previously debugged it to this point:

http://tech.groups.yahoo.com/group/hercules-390/message/58060

http://tech.groups.yahoo.com/group/hercules-390/message/58062

http://tech.groups.yahoo.com/group/hercules-390/message/58065

where I found code that looked wrong and asked for
some guidance, which I didn't get, possibly because
of all the other commotion due to other bugs I
discovered at the same time.

If I can get answers to those questions, I can possibly
debug it further.

Maybe it's time to put an exit into the code that
returns -1 for a file handle (which the caller is
meant to check, but doesn't) so that at least the
"internal error" is detected and exits instead of
giving silly messages in a loop?

BFN.  Paul.