开云体育

  1. H390-Vm
  2. Topics

How to distribute Rexx helpfiles?

 

As part of the bREXX update effort, I sat down and wrote a full set of HELP files for it, similar to the existing set of HELPEXC for EXEC.? What's the best way to distribute these?? I could certainly add them to the bREXX release packages, but they'd still need to be moved to the MAINT 19D disk somehow.? Or would folks rather I get them into the HELP collection at?, from whence I expect they'd wind up in the next VM/CE release?

Or other ideas?

Thanks,
Ross
 

I will have the same question when the NEW EE is mature enough for a broader release.
I think these help files should be included in the product distribution to encourage people to give the new stuff a try.
?
I see the VM/CE distribution as targeted to new users, this will not help existing users to update their carefully configured system.
?
In the case of the NEW EE I expect that people want to have it immediately, once convinced. They do not want to wait for the next release of VM/CE .
?
Something personal: I am preparing for a hospital stay, there will be no fixes and bleeding edge releases of EE until I have returned and recovered.
?
Martin?
?
 

i, Ross,
?
How are you packaging and delivering the actual code for distribution currently?
?
I would create a VMARC archive file that contains all of those help files that need to go on the MAINT 19D minidisk, with instructions so anyone can sign-on as MAINT, access 19D as R/W, and then VMARC UNPACK them to that disk.? You (or someone) could upload this VMARC file to the "Files" area of this H390-VM list group.
?
I would also add them to that github.
?
All the best,
?
Mark S. Waterbury
 

On Mon, Nov 4, 2024 at 4:18?PM Mark Waterbury via <mark.s.waterbury=gmail.com@groups.io> wrote:
How are you packaging and delivering the actual code for distribution currently?

bREXX has an established practice for distribution, which I have repeated for the upcoming release.? The code is built completely on GitHub (including launching VM/370 under Docker to compile it!), then packaged in three forms:
  1. A pair of "binary" and "source" AWS tape files.
  2. A pair of "binary" and "source" VMARC files.
  3. A replacement for the GCCBRX DASD file of VM/370 CE.
The AWS tapes and VMARC files contain the exact same set of CMS files.? The DASD file is, of course, somewhat different,?but the minidisks on it contain the files that were dumped for the first two formats.

?I would create a VMARC archive file that contains all of those help files that need to go on the MAINT 19D minidisk, with instructions so anyone can sign-on as MAINT, access 19D as R/W, and then VMARC UNPACK them to that disk.

Thanks, that's a good option.

? You (or someone) could upload this VMARC file to the "Files" area of this H390-VM list group.

I'd probably distribute it from GitHub along with the rest of bREXX, so at least it could be versioned.

?I would also add them to that github.

Makes sense.

Thanks!

Ross
 

On Mon, Nov 4, 2024 at 6:10?PM Ross Patterson <ross.patterson@...> wrote:
On Mon, Nov 4, 2024 at 4:18?PM Mark Waterbury via <mark.s.waterbury=gmail.com@groups.io> wrote:
I would create a VMARC archive file that contains all of those help files that need to go on the MAINT 19D minidisk, with instructions so anyone can sign-on as MAINT, access 19D as R/W, and then VMARC UNPACK them to that disk.

Thanks, that's a good option.

So I did that, and the second and third bREXX betas have a BRXHELP VMARC file embedded inside the BREXXSRC?VMARC file, and the bREXX installation tool (NEWBREXX EXEC) will unpack that onto the MAINT 19D HELP disk.

I'm going to also add them all to the HELP collection at?.? I'll try my best to keep both collections in sync, so nobody has to worry which to install.

Ross

1 - 5 of 5