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: Program Interrupts (signals)
The HX suppression mod is a bit of a hack which abuses one of the batch flags. It is not a really awful hack but I think we should be able to do better. I'm not sure what exactly HI type behaviour is.
By
Peter Coghlan
·
#1109
·
|
|
Re: Program Interrupts (signals)
After thought, and considering the HX suppression mod posted by Dave, and that intercepting HX would allow BREXX to have HI type behaviour, and that if a divide by zero requires a IPL you can
By
adriansutherland67
·
#1108
·
|
|
Re: memset help
Thank you everyone - to close this subject this is the code I am going to use. I don't use this approach too often but I thought folks might be interested in seeing a non-standard GCC meld of C and
By
adriansutherland67
·
#1107
·
|
|
Re: memset help
Source files
By
adriansutherland67
·
#1106
·
|
|
Re: memset help
Well the results are in - apologies for the long email and not formatting into table - but you know how it is! I declaring *Peter the WINNER* for providing the?MVCL code (although it was suggested by
By
adriansutherland67
·
#1105
·
|
|
Re: Program Interrupts (signals)
My take on this: a long poll wait time is not that bad, important is that the exec can stop without me forcing off the user a short poll time is wasteful, and we are not in the business of using HX
By
[email protected]
·
#1104
·
|
|
Re: Program Interrupts (signals)
Indeed, I abhor polling - but isn't that how CMS itself does HX? I too can poll on an I/O interrupt ... Is the challenge that the flag does not exist - or the worry about polling?
By
adriansutherland67
·
#1103
·
|
|
Re: Program Interrupts (signals)
dave, i didnt mean that CP would abend. i meant that the PIC would be thrown by CP. Sorry for the confusion. Joe
By
Joe Monk
·
#1102
·
|
|
Re: Program Interrupts (signals)
Adrian, I think that would be a challenge and you would either waste lot of time polling the flag, or risk running for a long time before detecting it. I must say CMS is by design, single threaded,
By
Dave Wade
·
#1101
·
|
|
Re: Program Interrupts (signals)
Thanks Dave Great find however. Would this work: Could I use the HX suppression mod to stop HX. But them within GCCLIB poll the HX flag myself (is there a flag?) and if set, exit gracefully. By the
By
adriansutherland67
·
#1100
·
|
|
Re: Program Interrupts (signals)
I think I am very confused :-) What I will do is - Make sure the GCCLIB internals is worked wrt signals (fake signals if you like) - Do a PoC with SPIE?etc. and see what happens with closing files,
By
adriansutherland67
·
#1099
·
|
|
Re: Program Interrupts (signals)
Joe, How can CP ABEND? Really CP is a distraction in this case AND CAN BE IGNORED. Saying CP ABENDS is like saying MVS abends when a program interrupts. Certainly, CP will receive control because CMS
By
Dave Wade
·
#1098
·
|
|
Re: Program Interrupts (signals)
I think you might be slightly confused. Lets take the example of a divide by zero. CMS will not abend that. Rather, CP will because its a hardware abend. You will get a PIC 9. CMS will detect it and
By
Joe Monk
·
#1097
·
|
|
Re: Program Interrupts (signals)
Excuse spelling ... and 3/ like memory closing files is an issue ...
By
adriansutherland67
·
#1096
·
|
|
Re: Program Interrupts (signals)
You see - I have no idea really! I can only follow advice. There are two additional concerns, which are specific if GCCLIB. 1/ If a CMS Abent clears freemen (and I think it doesn't?), we have a bit of
By
adriansutherland67
·
#1095
·
|
|
Re: Program Interrupts (signals)
Doesn¡¯t SPIE cover all of these. Also STAE is available Dave Sent: 23 April 2020 09:58 To: [email protected] Subject: Re: [h390-vm] Program Interrupts (signals) This link is a short (short means
By
Dave Wade
·
#1094
·
|
|
Re: Program Interrupts (signals)
LOL! :-)
By
adriansutherland67
·
#1093
·
|
|
Re: Program Interrupts (signals)
Bob, Well a few reasons for using ¡°C¡±. First is we have a decent ¡°C¡± compiler and when I last used a mainframe the thing that stopped us using ¡°C¡± was the dreadful SAS ¡°C¡± compiler.
By
Dave Wade
·
#1092
·
|
|
Re: Program Interrupts (signals)
This link is a short (short means good for me!) background of what we are trying to achieve https://en.wikipedia.org/wiki/C_signal_handling A
By
adriansutherland67
·
#1091
·
|
|
Re: Program Interrupts (signals)
Thanks for the possibility of assistance. I will pull together details for what I think is needed and why, for discussion, review, refinement, and to see if you think it is feasible and something you
By
adriansutherland67
·
#1090
·
|