This group is for all folks running the original IBM VM/370 Release 6 operating system (or later (e.g. VMTCE (Community Edition)) on Hercules. Like the other early IBM operating systems this version has always been in the public domain and so can be freely distributed. The base version as supplied by IBM is lacking in many facilities. IBM solved this by providing additional extension products which were licensed and so are not available. There are however many user enhancements available which can be installed. In addition, in order to get users up and running quickly updated "releases" of VM/370 included the most popular updates are available for download, so novices can start to learn VM without having to delve into the system internals. It is intended that this wiki will provide information on the base release and these updates.
The available versions are here :-
?
?
|
Re: How to distribute Rexx helpfiles?
<mark.s.waterbury@...> wrote: bREXX has an established practice for distribution, which I have repeated for the upcoming release. The code is built completely on GitHub (including
By
Ross Patterson
·
#6279
·
|
|
Re: How to distribute Rexx helpfiles?
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
By
Mark Waterbury
·
#6278
·
|
|
Re: How to distribute Rexx helpfiles?
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
By
Martin Scheffler
·
#6277
·
|
|
Re: First beta of bREXX 1.1.0 now available
I have installed the binary distribution via VMARC on the MECAFF user. There is a change how REXX tracing works which is disturbing EENEW's internal machinery. My workaround is to begin all REXX
By
Martin Scheffler
·
#6276
·
|
|
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
By
Ross Patterson
·
#6275
·
|
|
Re: Possible Diag 8C Issue
Hi William, It is true that DIAG8C does not return row/column values based on the RPQ result, but mostly because it doesn't need to.? CP was already built around having fixed model numbers for 3270
By
Bob Polmanter
·
#6274
·
|
|
Re: Possible Diag 8C Issue
[email protected]> wrote: Back when I worked for VM Software/Systems Center/Sterling Software (whew! I'll never write that again!), we had a lot of CMS application code written in C. We had our own
By
Ross Patterson
·
#6273
·
|
|
Re: Possible Diag 8C Issue
Seeing as "C" code cannot have sequence numbers in 73-80 you can't use UPDATE to maintain it. There are copies of "DIFF" and "PATCH" on the CE edition which can be used in the same way, but I suspect
By
Dave Wade
·
#6272
·
|
|
Re: Possible Diag 8C Issue
Bob.. Thanks for pointing out to me that the update for mod 5 also bumped the Diag8C return values. I guess my point was that the current Diag8C implementation does not return values based on the RPQ
By
William Denton
·
#6271
·
|
|
First beta of bREXX 1.1.0 now available
The first beta release of bREXX v1.1.0 for CMS on VM/370 is now available at https://github.com/RossPatterson/CMS-370-BREXX/releases/download/v1.1.0-beta-01/BREXX.zip . I have been testing this update
By
Ross Patterson
·
#6270
·
|
|
Re: Possible Diag 8C Issue
The original Diagnose 8C code only supported 3270 models 2, 3, and 4 because at the time that was all that was supported in the VM/370 code that we had.? Later, when model 5 support was added to the
By
Bob Polmanter
·
#6269
·
|
|
Possible Diag 8C Issue
I am working on an update to CP that would allow pretty much arbitrary display screen sizes. One thing I noticed in the current Diagnose 8C code is that the returned column count is being hardwired at
By
William Denton
·
#6268
·
|
|
Re: Let's Talk About RSCS
FYI, RJE from VM works with MVT 21.8F as well, in case either of you use that OS. Jeff
By
Jeff Snyder
·
#6267
·
|
|
Re: Let's Talk About RSCS
Somone informed me off list that their "MVS expert" states the actual buffer size is 520. I've been experimenting with that today and it is working well.
By
Daniel L. Srebnick
·
#6266
·
|
|
Re: VM Guest Printing
Dan, From the first level's operator's console, you'd be closing the operator's virtual printer.? To close the VM hosting the second level machine from the operator's console, you'd have to "send"
By
Ganino, James (PERATON)
·
#6265
·
|
|
Re: VM Guest Printing
OK folks, I solved it! I was doing the CP CLOSE PRT from the 1st level operator console. ?That did not work but when I tried it from the 2nd level operator console as #CP CLOSE PRT, that did it. I
By
Daniel L. Srebnick
·
#6264
·
|
|
Re: VM Guest Printing
I used to do it the other way around. I'd change the guest machine's first-level LINEND character to something other than #. That way, when I habitually typed #CP something on the 2nd level machine, I
By
Jeff Henry
·
#6263
·
|
|
Re: VM Guest Printing
[email protected]> wrote: Sure, that'll work fine. You sound like you generally know what you're doing on VM, so I hesitate to ask, but have you changed the LINEND character on your second-level
By
Ross Patterson
·
#6262
·
|
|
Re: VM Guest Printing
Hi Bob: That did not work either. ?The spooled file is there at level 2 as long as the printer is drained. ?Starting it and the output vanishes. So I tried something else. ?I attached 00F to the
By
Daniel L. Srebnick
·
#6261
·
|
|
Re: VM Guest Printing
Daniel, You have to issue the CP CLOSE PRT from the virtual machine console (first level) userid that is hosting the 2nd level VM system. At that point, if your first level system printers are stopped
By
Bob Polmanter
·
#6260
·
|