开云体育

Yeah I will do that. Please work in feature/fnnnn branches off develop. If you handle the source/brexx itself, I will handle the build process automation, and release management - OK? :-) I don't care

One More Thing: other people (Peter Jacob, Mike Grossmann ) are working on BREXX for OS/VS 3.8 (MVS) TK4- which runs quite nice - their repo is at https://github.com/mgrossmann/brexx370 They have

Or, Adrian, you can just add me as collaborator so I can work directly on the CMS brexx code in there, and use your build system, for speed.

Yes, I have a fork of Bill Vlachoudis’s repository at rvjansen/brexx, because I use that for pull requests for macos. Maybe it’s best if you also fork from the main brexx repository, than I can

There are substantial changes because original assumes ASCII. Some where we have a separate licence. Dave adrian@...> wrote:

So I made a repository - https://github.com/adesutherland/CMS-370-BREXX - (and guessed licenses - wrongly) - but then noticed this https://github.com/vlachoudis/brexx (

And then there was the Romulan Cloaking Device (RLD) which created a second directory on the disk.?? Rather dangerous actually, as hidden files would get clobbered if the directory they were hidden

Well, yes.? Consider I used DDR to dump the raw tracks of the MVS master catalog for its password a couple of weeks ago. And of course, all those clear text passwords in the USER DIRECT ... -ahd-

It worked (thank you) ... f.y.i this is the shell script that does the install: #!/bin/sh # Install YATA on CMS # Exit if there is an error set -e # IPL herccontrol -v herccontrol "ipl 141" -w "USER

I will create a CMS BREXX project directly and ping the link Yes lets get the source / issues logged. My backlog is like this: - Update the VM/370 docker image to include YATA so I can move

This is also reproducible: type say exec /* */ INTERPRET 'SAY' ARG(1) Ready; T=0.01/0.01 13:04:22 say 21000/365 583.333333ABCDEFGHIJKLMNOPQRSTUVWXYZ0123 (brexx on other platforms gives

Bob, I don’t think we ever implied that modes 1 and 2 on the “S” and “Y” disk were anything other than for convenience. However, for Mode 0 the CMS user guide for VM/370 says “a filemode

The ability to make only certain filemode number files visible, like filemode 2 files on the S and Y disks, was not a security mechanism. It was a way to save storage by making only necessary files

Those were more innocent times, well in terms of IT security at least ...

Well that sure would explain this awful headache that I've not been able to shake. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

Hello! Actually that's what I asked. It is too good for IBM to write it. ---- Strange that glowing green spill in PA is getting worse. It's creeping to a museum across the street. It seems Dave you

Le mar. 11 févr. 2020 à 19:41, Gregg Levine <gregg.drwho8@...> a écrit : And was this a user created mod? Or was it something that IBM created I can see CPWATCH on the WATERLOO tape, with a

Hello! After updating Docker, its suggestion not mine, I promptly tried again Adrian's Docker container for Hercules and the VM Six Pack and found that yes indeed CPWatch was there. I checked on the

Back in the day, as an ordinary VM user, that was quite beyond my capability. Instead I uses an easier but more sledgehammer to crack a nut approach. I defined a temporary disk the same size as the

Adrian There will be a document somewhere that describes the file modes. (CMS user guide) Mode “0” files are only visible if you have write access to the disk, Unless you patched the access