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: Possible bug in BREXX parse instruction
Hi Mike, I don't know where the bad code is, but I expect it is probably in the interpre.c piece. There is no code that I could find to handle literals in the parse template. For example, if we have a
By
Bob Bolch
·
#4388
·
|
|
Re: Possible bug in BREXX parse instruction
I have rewritten the test tool: literal delimiters and string_to_parse are supplied as arguments. Usage instructions included. ** ** * davtest CMS bREXX 1.0.1 Jul? 5 2022 CMS COMMAND davtest davtest
By
Martin Scheffler
·
#4387
·
|
|
Re: Three questions about VM/CE (Left, middle, and right field question)
There is no TCP/IP in VM/CE. See VM Interface Program for TCP/IP ( http://bitsavers.trailing-edge.com/pdf/ibm/370/TCP/SH20-6518-1_VM_Interface_Program_for_TCP_IP_Users_Guide_198610.pdf ) - an early
By
Martin Scheffler
·
#4386
·
|
|
Three questions about VM/CE (Left, middle, and right field question)
Hi, I have three questions. As a side note, I'm a ham radio operator (WB8ERT) and use DMR. My left field question would be for fellow ham radio operators. I understand getting a PI-Raspberry to
By
Bertram Moshier
·
#4385
·
|
|
Re: Possible bug in BREXX parse instruction
Hello, I don¡¯t think, the problem is related to template.c In my understanding, this code used by the compiler and will just create the interpreter stack. The Problem may occur in interpre.c. There
By
Mike Gro?mann
·
#4384
·
|
|
Re: Possible bug in BREXX parse instruction
Hello Mark, For MVS there is another version: https://github.com/mvslovers/brexx370 This version is not based on gcclib. The MVS version mentioned by you, is the original multi platform version of
By
Mike Gro?mann
·
#4383
·
|
|
Re: Another Time Zone Question (Sorta)
Hello Mark, Thank you so very much for your reply! I will remove SixPack 1.3 in favor of the more recent VM/CE release. I greatly appreciate knowing this information. I don't know if someone here has
By
Bertram Moshier
·
#4382
·
|
|
Re: Another Time Zone Question (Sorta)
Bertram, you did not read, listen or whatever ... http://www.smrcc.org.uk/members/g4ugm/VM370.htm now tells you to go elsewhere:
By
Martin Scheffler
·
#4381
·
|
|
Re: Possible bug in BREXX parse instruction
There are CMS & MVS versions on GitHub. They are not identical to each other. They both make use of GCCLIB, but I'm not sure if there is an exact, up to date copy of GCCLIB on GitHub for either CMS,
By
Mark A. Stevens
·
#4380
·
|
|
Re: Another Time Zone Question (Sorta)
Sixpack 1.3 preceded all the VM/370 CE releases. MAINT 535, a play on SES, by the way, was added to VM/370 CE V1R1... I forget which exact release. You are missing that minidisk on 1.3, so you won't
By
Mark A. Stevens
·
#4379
·
|
|
Re: Another Time Zone Question (Sorta)
Hello Martin, Thank you for your reply to my questions. by date. *> readme-1_3.txt * was for SixPack 1.3 . I'm not finding anything about VM/CE 1.2 and if it came after SixPack 1.3 or before it.
By
Bertram Moshier
·
#4378
·
|
|
Re: Another Time Zone Question (Sorta)
You can read these files before Hercules is running. This list is sorted by date. *readme-1_3.txt* was for SixPack 1.3? . *E:\Hercules\...\VM370CE.V1.R1.2> dir read* /o-d* ** * Directory of
By
Martin Scheffler
·
#4377
·
|
|
Re: Possible bug in BREXX parse instruction
bREXX is built by *MAINTC* in *VM Community Edition V1 R1.2* : *L MAINTC MAINTC* ** * DASD 190 LINKED R/O; R/W BY MAINT; R/O BY 004 USERS DASD 19D LINKED R/O; R/W BY MAINT; R/O BY 002 USERS DASD 19E
By
Martin Scheffler
·
#4376
·
|
|
Re: Possible bug in BREXX parse instruction
Hello Mark and Bob, I would like to help you (if I can) with diagnosing the problem in BREXX. Maybe we could switch this communication to private. A list of all sources and includes (in C, AFAIK),
By
Bernd Oppolzer
·
#4375
·
|
|
Re: Another Time Zone Question (Sorta)
Hello Dave, So which came first VM/CE 1.2 or SixPack 1.3? I other words, which is the latest SixPack 1.3? Is everything in VM/CE in SixPack 1.3? Finally, I can't find Maint Memo B mentioned earlier.
By
Bertram Moshier
·
#4374
·
|
|
Re: Possible bug in BREXX parse instruction
Thanks, Mark. I never found brexx debug to be very useful. I do remember that you put the BREXXD TEXT on your A-disk, renamed to BREXX TEXT, then IPL CMS. Then the 'trace' statement, in an EXEC ,
By
Bob Bolch
·
#4373
·
|
|
Re: Possible bug in BREXX parse instruction
Welcome back from your surgery. Once again, I'm leaving out thoughts and not writing them down. Sorry. I am referencing Mike's 2nd edition, also the ANSI X3J18-199X document. I will also eat my words
By
Mark A. Stevens
·
#4372
·
|
|
Re: Another Time Zone Question (Sorta)
There are other control files, aux files, and then code which are included when AP is selected for a build. I've forgotten the details, but I used it on our 4381[-P2]?, as it had an attached
By
Mark A. Stevens
·
#4371
·
|
|
Re: Possible bug in BREXX parse instruction
Will check this. Martin Scheffler <San-Lorenzo@...> schrieb am So. 16. Okt. 2022 um 21:28:
By
Mike Gro?mann
·
#4370
·
|
|
Re: Possible bug in BREXX parse instruction
We might look for? TEMPLATE? C? F?? on MAINTC: *q disk* ** * Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total MNT191 191 A?? R/W?? 50 3350?
By
Martin Scheffler
·
#4369
·
|