开云体育

On spinhawk, is this the correct configuration to connect two systems on the same host??

The example uses unique IP addresses and same port numbers.

veronica/veronica.conf: 08C0???? CTCE??? 2216 localhost 2316
veronica/veronica.conf: 08C1???? CTCE??? 2218 localhost 2318

viola/viola.conf:       0e44???? CTCE??? 2316 localhost 2216
viola/viola.conf:       0e45???? CTCE??? 2318 localhost 2218

Thanks in advance,
-ahd-

-- 
Drew Derbyshire

 I'm back in the saddle again . . .

Yes Drew, this is a correct configuration, not only on spinhawk, but also on? where my newest CTCE v2 is already committed (and which still supports that format as well).

By the way, I intend to backport the same CTCE v2 corrections and improvements on spinhawk as well. I have just started the testing of that backport.

Cheers,

Peter

Drew,

My earlier reply has not yet been approved by the moderators, which is good because it was wrong.

No, the configuration statement for all 3088 type devices on spinhawk still requires the keyword 3088 following the device number (CCUU address), i.e. :

veronica/veronica.conf: 08C0???? 3088 CTCE??? 2216 localhost 2316

and so on.? In? this *3088" keyword is no longer allowed.?

By the way, SDL-hyperion already has my latest CTCE v2 corrections and improvements, which I'm in the process of backporting to spinhawk as well.

Cheers,

Peter?

开云体育

Drew,

My earlier reply has not yet been approved by the moderators, which is good because it was wrong.

No, the configuration statement for all 3088 type devices on spinhawk still requires the keyword 3088 following the device number (CCUU address), i.e. :

veronica/veronica.conf: 08C0???? 3088 CTCE??? 2216 localhost 2316

It's not needed in my copy, which was pulled from Github January 6.?

veronica.conf:08C0???? CTCE??? 2216 localhost 2316
veronica.conf:08C1???? CTCE??? 2218 localhost 2318

log/veronica.log:22:28:14 HHCCT063I 08C0 CTCE: Awaiting inbound connection :2217 <- 127.0.0.1:2316
log/veronica.log:22:28:14 HHCCT063I 08C1 CTCE: Awaiting inbound connection :2219 <- 127.0.0.1:2318
log/veronica.log:22:28:19 HHCCT070I 08C0 CTCE: Accepted inbound connection :2217 <- 127.0.0.1:2316 (bufsize=61592,12)
log/veronica.log:22:28:19 HHCCT070I 08C1 CTCE: Accepted inbound connection :2219 <- 127.0.0.1:2318 (bufsize=61592,12)

viola-network-io.conf:0e44???? CTCE??? 2316 localhost 2216
viola-network-io.conf:0e45???? CTCE??? 2318 localhost 2218

log/viola.log:22:28:02 HHCCT063I 0E44 CTCE: Awaiting inbound connection :2317 <- 127.0.0.1:2216
log/viola.log:22:28:02 HHCCT063I 0E45 CTCE: Awaiting inbound connection :2319 <- 127.0.0.1:2218
log/viola.log:22:28:19 HHCCT054I 0E44 CTCE: Started outbound connection :2316 -> 127.0.0.1:2217
log/viola.log:22:28:19 HHCCT072S 0E44 CTCE: Not all sockets connected: send=62, receive=-1
log/viola.log:22:28:19 HHCCT054I 0E45 CTCE: Started outbound connection :2318 -> 127.0.0.1:2219
log/viola.log:22:28:19 HHCCT072S 0E45 CTCE: Not all sockets connected: send=64, receive=-1
log/viola.log:22:29:39 HHCCT072S 0E44 CTCE: Not all sockets connected: send=62, receive=-1
log/viola.log:22:29:39 HHCCT072S 0E44 CTCE: Not all sockets connected: send=62, receive=-1
log/viola.log:22:29:41 HHCCT072S 0E44 CTCE: Not all sockets connected: send=62, receive=-1

--

Drew Derbyshire

 Vidi, vici, veni.

开云体育

BTW, please print the full status of the CTCE; this is not useful when debugging half open links:

0:0E44 3088 .:....=127.0.0.1:2216 open????????????????????????????????????????????????????????????????????????????
0:0E45 3088 .:....=127.0.0.1:2218 open

-- 
Drew Derbyshire

"It may sound absurd . . . but don't be naive
 Even Heroes have the right to bleed
 I may be disturbed . . . but won't you concede
 Even Heroes have the right to dream
 It's not easy to be me"
                        -- Five for Fighting, "Superman (It's Not Easy)"

Drew, yes, you're right, it appears that keyword "3088" in the current spinhawk CTCE is optional. Thanks for making me aware of this.

Cheers,

Peter

Drew, the upcoming backport of my CTCE v2 corrections and improvements will have an improved output from the DEVLIST <devnum> command which I thus hope will address this. The existing command CTC DEBUG … will then also support CTCE devices to assist debugging this even better.

Cheers,

Peter

On 2/24/20 12:44 AM, Peter Jansen via Groups.Io wrote:

Drew, the upcoming backport of my CTCE v2 corrections and improvements will have an improved output from the DEVLIST <devnum> command which I thus hope will address this. The existing command CTC DEBUG … will then also support CTCE devices to assist debugging this even better.

If you point me at your next CTCE Spinhawk version when it's public (github?), I'll beta test.? :-)

--
Drew Derbyshire

"A hobbit will get you through times of no bagels better than bagels
will get you through times of no hobbit." -- The Grey-eyed Elf

Please note that my? of the? is available for anyone who wishes to beta test my CTCE v2 corrections and improvements (as well as some older changes). The code is not finalized yet, some problems are known to exist, but as a successful CTCE connection was made yesterday (a VTAM non-MPC CTCA link to a? Hercules system), I'd appreciate testing feedback. The new CTCE support for the CTC DEBUG ON <devnum> command may be helpful.

When this spinhawk CTCE v2 work has been sufficiently tested, I will make a pull request for it, but cannot guarantee that these will be actually carried out.?

Feedback welcome !

Cheers,

Peter?