XCF signaling stopped working.

[sdl-hercules-390]

XCF signaling stopped working.

[Fish-Git]

Hi Göran!

It appears Peter Jansen's latest changes to the CTCE driver that I merged may have reverted my earlier fix.

I need to do some research to see if maybe I can figure out how it broke and how to fix it (which may require me to contact Peter for help).

In the mean time, could you please do us a favor to help us please?

I would like to see a CCW trace on devices E24 and E25 for both commit 9269d74 (without Peter's changes) and commit 6359717 (with Peter's changes).

Make sure you do a CCW trace (t+e24, t+e25) when you run your test on each version. The goal here is to compare how each behaves, both with and without Peter's changes, so I need to see the CCW trace for both test runs (both with and without Peter's changes).

Thanks!

[Peter-J-Jansen]

Hi Fish and Göran, I think I may have found and fixed the “XCF signaling stopped working” problem. First I’d like to thank Fish for merging my previous CTCE fixes into his repository, which I’ve been referring to as “SDL-hyperion” to avoid confusion with the other Hyperion repository. When I browsed the resulting “ctcadpt.c” code, at first I thought it would be OK, but then I realized that the extra logic Fish introduced around “ctce_haltorclear” in the CTCE_Send routine would cause problems on the “send” side. Hence that I regressed that, and tested the result. XCF (and z/VM’s ISFC too) are now working again. The fix is available here: https://github.com/Peter-J-Jansen/SDL-hyperion, and I have already entered a new “pull request” so that Fish may merge it with his SDL-hyperion repository. Any comments are welcome of course. Thanks, Peter

[Peter-J-Jansen]

Oops, sorry for sending the same e-mail twice.

[Fish-Git]

Oops, sorry for sending the same e-mail twice.

No problem. As the repository owner, I can delete any comment I want.

Your duplicate comment has been deleted! Problem solved!   :)

---

FYI: I would personally prefer that everyone not use email when responding/replying to an issue, and instead use GitHub's web based user interface.

Yes, I realize it may be faster and easier to respond via email and slightly more bothersome to use GitHub's web interface instead, but here's the problem: GitHub does not allow me to edit email based replies using markdown (styling). It only allow markdown for comments entered via their web based user interface.

Forgive me, but oftentimes the comments added by others are not well formatted, and I prefer to be able to edit them so they are easier to read and understand (adding italics, inline code, etc) . I cannot do that when you reply via email.

You can continue to reply via email if you want. That's okay. I'm not asking or demanding that you to change your behavior!

I'm simply letting you know about my own personal preference, that's all.

Whether or not you feel my personal preference is important enough to you to change your behavior is entirely up to you.   ;-)

[Fish-Git]

... but then I realized that the extra logic Fish introduced around “ctce_haltorclear” in the CTCE_Send routine would cause problems on the “send” side. [...]

That was going to be my second guess!   ;-)

I wasn't sure whether it was my attempt to the fix the HaltOrClear logic in the various communication device handlers (LCS, CTCI, CTCE and PTP) or whether it was something you did in your original merge request (which was based on a version of my SDL Hyperion without my "fix"). I was hoping Göran could do some tests for us to determine which it was. (I am unable to test CTCE myself.)

I only suspected your code since my code is always perfect and 100% bug free. Only other people make mistakes. I never do.  ;-)
</sarcasm>

Anyway, THANK YOU Peter, for finding and fixing this bug so quickly!

And please accept my apology for temporarily breaking your truly awesome code (and it is truly awesome!!!).

I will merge your fix right away, and close this issue once I do.

Thanks again for everything, Peter.

You are a good friend.   :`)

[Fish-Git]

Resolved by merge "Fixed "XCF signalling stopped working" #16 (commit 1b91101).

Closing this issue as resolved.

Thanks again, Peter!

I will build and upload a new Windows pre-built with this fix in it as soon as I can.