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

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

开云体育

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,

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.

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?

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

开云体育

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 . . .

开云体育

great work, I’ll be sure to check it over the weekend!

Automatic build done ... added to latest docker image.

I'll try and actually do some debugging now!

开云体育

yes, that is fine with me, I’ll start on the testsuite and the errors that remain when the gcc runtime gets better

On Fri, Feb 21, 2020 at 06:25 PM, rvjansen@... wrote:

let’s use the issue system to avoid doing duplicate work

I think you can assign people to issues.?

I would like to concentrate on reentrancy, residency, and gcclib issues if that works for you?

On Fri, Feb 21, 2020 at 06:25 PM, rvjansen@... wrote:

can herccontrol address a non-console session?

No ... I disconnect and logon the user to the console as needed. However if you are using a real mainframe that won't work :-(

开云体育

On Tue, Feb 18, 2020 at 03:44 PM, rvjansen@... wrote:

I checked in the current source, will add some of the VM modules also. I started with the .corig sources and checked them in as.c, and then checked in the current .c modules, so we can track them with git diff. As a result, some of the files are empty now (and are not part of the build procedure - hmm).

Added some missing files (just headers I think - also separated the .horig files following your approach) and made all the files lower case (sorry!!).

Added some very rough instructions.txt for release management. Basically make a feature/f000n (or hotfix/h0001) and work there until you are happy with it and then we both can stage it to a release.

BREXX built and ran manually (good!) - so I am just going to automate that (feature f0001). I have the template from GCCLIB so should not take long. Then we will have each check-in building and running whatever tests we have automatically on GITHUB servers. And it can feed the upstream VM/370 image build. Quick turnaround for bugs (well assuming we can work out how to fix the bugs!)

I can't (well wont!!) use any s3270 scripts myself - happy with driving the console via my herccontrol thingy. And it is bedded-in for the github builds.?

Cheers

Adrian

GLOBAL TXTLIB GCCLIB?is definitely needed in SYSPROF (for both GCCLIB and BREXX) however I don't understand the logic of what is included in the TEXT file being loaded high, and what can be left out to be fixed up from the TXTLIB

Any clues welcome - although I am just leaving it alone for now ... it works as is ...

A

Thanks Rene

Rebuilt the BREXX module - I found I needed to issue a GLOBAL TXTLIB GCCLIB first for it to be happy (it had a few standard library missing symbols otherwise).

btw - PDPCLIB is not what we want ..

Anyway Say/Interpret seemed a bit more happy with life ... you may want to test

On Fri, Feb 21, 2020 at 02:06 PM, Dave Wade wrote:

I loaded the statically linked versions of EE and FSLIST etc because of the instabilities with the dynamic library.

Just as well! :-)

开云体育

This GCLIB version of 0.7.1 is almost identical to the last version available (i.e. I have not materially edited it ... yet!)?


Interestingly both EE, FSLIST etc. and BREXX seem to work without changes/rebuilding. Which tells me that they are statically linked (perhaps).

Anyway I will look at BREXX now.

Adrian

For info.

TXTLIB did not work when run from sysprof exec when "installed globally" (it wa ok for a local install on cmsuser). Perhaps a disk is missing at that ipl stage? Anyway I have left it as a text concat.

A