Closed jeff-snyder closed 4 months ago
Hi Jeff,
The CTCE recovery attempts are known to not always end successfully. The DEVINIT 0:0610
attempt may very well fail when the device by then is busy or has an interrupt pending. That in this case it caused a crash was probably due to the Hercules watchdog timer discovering HHC00822S PROCESSOR CP00 APPEARS TO BE HUNG!
. So this crash was probably a case of Works As Desgined ("WAD").
Some years ago numerous efforts were spent on making the CTCE automatic recovery's fail-safe, and progress was made, but no, I was unable to make it work in all cases. As this occurrence was started by an incorrect CTCE configuration, I'd suggest we close this Issue. As some additional help avoiding CTCE configuration errors, I'd suggest to not specify any port numbers at all when the CTCE links are between difference hosts, but just restrict the configuration to just use device (CCUU) numbers, e.g.:
0610 CTCE =Hercules
or if one prefers the device number host-side specific:
0610 CTCE 0601=js01.hostname
0601 CTCE 0610=js10.hostname
Cheers,
Peter
Peter,
Some years ago numerous efforts were spent on making the CTCE automatic recovery's fail-safe, and progress was made, but no, I was unable to make it work in all cases. As this occurrence was started by an incorrect CTCE configuration, I'd suggest we close this Issue.
I'm good with that. I have a work around (i.e. fix your stupid configuration error!).
As some additional help avoiding CTCE configuration errors, I'd suggest to not specify any port numbers at all when the CTCE links are between difference hosts, but just restrict the configuration to just use device (CCUU) numbers, e.g.:
Unfortunately, this doesn't work for me because I run multiple Hercules images on each host and I move them around, so I'm never sure which images will be running on which hosts. It's a good solution for people with fewer images or a more stable environment, theough!
Thanks, Jeff
Hi Peter,
The two systems JS01 and JS10 are configured to talk to each other over a CTC. Unfortunately, a typo was made on the JS01 configuration and instead of 610 as the remote CUU, E20 was entered.
When I bring up Hercules for JS01 and IPL VM/ESA, there are no problems. A "devlist ctca" shows the link defined (among others).
When I then bring up Hercules for JS10, it thinks it successfully connected to this link.
The "devlist" for JS10 shows a connection.
The log for JS01 shows it started an outbound connection, but there was never an inbound connection.
The "devlist" confirms an incomplete link.
When I IPL JS10, errors ensue:
and, eventually, a crash dump.
Note, this happened on Windows 10, running Hercules version 4.8.0.11129-SDL-DEV-g5517d322-modified I retested with version Hercules version 4.8.0.11129-SDL-DEV-g5517d322, i.e. without the changes to ctcadpt.c, and it still happens.
JS01 is VM/ESA 2.4 and JS10 is VM/SP 5.
Here are the associated log and config files.
Unfortunately, due to the 74 MB file size, I cannot upload the dump file. For now, I have put it on my Google drive. Hopefully, you can get it from there or we can find another way to get it to you.
Thanks for looking at this! Jeff