Keyboard Shortcuts
Likes
- H390-Vm
- Messages
Search
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: building BREXX
¿ªÔÆÌåÓýyes, that is fine with me, I¡¯ll start on the testsuite and the errors that remain when the gcc runtime gets better
|
Re: building BREXX
¿ªÔÆÌåÓý
yes, forgot about the .h files, noticed that just now when trying to compile on z/VM. lower case, fine. I prefer that too.
yes, that would also be good for the wiki.
let¡¯s use the issue system to avoid doing duplicate work. I¡¯ll assign to myself if I start on some issue (assuming github can do that, did not look yet)
can herccontrol address a non-console session? best regards, ¸é±ð²Ô¨¦.
|
Re: building BREXX
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 |
Re: GCCLIB Advice
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 |
Re: BREXX Login
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 |
Re: Docker image (1.4.1/latest) with GCCLIB 0.7.1
¿ªÔÆÌåÓýAdrian, You tell me there is no BREXX module so its no linked at all. BREXX is re-linked? with the dynamic library from the Profile EXEC I loaded the statically linked versions of EE and FSLIST etc because of the instabilities with the dynamic library. Dave ? From: [email protected] <[email protected]> On Behalf Of adriansutherland67
Sent: 21 February 2020 13:34 To: [email protected] Subject: [h390-vm] Docker image (1.4.1/latest) with GCCLIB 0.7.1 ? This GCLIB version of 0.7.1 is almost identical to the last version available (i.e. I have not materially edited it ... yet!)? docker pull adriansutherland/vm370:latest
|
Docker image (1.4.1/latest) with GCCLIB 0.7.1
This GCLIB version of 0.7.1 is almost identical to the last version available (i.e. I have not materially edited it ... yet!)?
docker pull adriansutherland/vm370:latest
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 |
Re: BREXX Login
toggle quoted message
Show quoted text
|
Re: BREXX Login
¿ªÔÆÌåÓýHi Adrian,that is correct, the BREXX user is just a placeholder to attach a disk volume to, so it cannot ipl cms. From another user, do ¡°gimme brexx 191 mr¡±, give the MULT password, and then you can access it. To compile successfully, you need to do a small change to mkbrexx exec, as indicated in the git version. best regards, ¸é±ð²Ô¨¦.
|
Re: SNAP Macro
Steven,
toggle quoted message
Show quoted text
As others have said sometimes you need to include OSMACRO and use OS Macros. The supported macros are listed in the CMS User Guide. Rather than SNAP , you might want to use the PER. The CMS in the six-packs has the PER command included (Program Event Recording) which is extremely powerful and very useful for de-bugging programs. For seeing what is going on the LINEDIT macro is pretty useful. Its documented in the CMS Command Reference manual. Dave -----Original Message----- |
Re: SNAP Macro
On 2/20/20 4:43 PM, Steven Fosdick wrote:
I have been reading Sharon Tuggle's book "Assembler LanguageThe SNAP macro is in the OSMACRO MACLIB S -- Drew Derbyshire How would the Lone Ranger have handled this? |
Re: SNAP Macro
George Shedlock
The SNAP macro is simply a wrapper for the PDUMP macro. IIRC the parameters given to the SNAP macro are labels in the program whereas the PDUMP macro expects addresses in storage. On Thu, Feb 20, 2020, 8:15 PM Gregg Levine <gregg.drwho8@...> wrote: Hello! |
Re: SNAP Macro
Hello!
toggle quoted message
Show quoted text
That's an excellent question. I don't know. Dave W might,. There are other books on the subject, two of them were written by Jeff Savit. He's an old friend of VM, and wrote those two whilst actually managing the OS for one of the victims of the Great Recession. I can list them, but I can rather do that in a completely different thread. The other was written by Phil Smith III and Gabe Goldberg. It's on VM/ESA but should provide some good ideas. If you're running DOS under VM then the book written by the Professors Yarnish concerning Assembly programming on OS and DOS for S/360 and S/370 will work. I seem to recall that many good libraries have books stacked up on the subject. --- Uh oh, the Blob has fully covered a museum in PA. No one can get in, and no one is getting out. However an adventurous something else has started trying to remove it by eat it. We'll know more in six weeks. ----- Gregg C Levine gregg.drwho8@... "This signature fought the Time Wars, time and again." On Thu, Feb 20, 2020 at 7:43 PM Steven Fosdick <stevenfosdick@...> wrote:
|
SNAP Macro
I have been reading Sharon Tuggle's book "Assembler Language
Programming: Systems/360 and 370" and it makes use of a macro SNAP on OS (MVS etc) which, from what I can tell, produces some kind of dump output of the program state. This does not seem to be defined while assembling on CMS. Is there an equivalent? Or do I need to do something to include a specific macro library? |