开云体育

Mark, Dave, Rob, Peter et al I am sorry - I was clumsy and irritating. My essay was not a criticism of what was done back in the day on CMS but rather it was a message was that things are kind of

Also, when those of us who’ve dealt with CMS, CP, etc., since the early days speak up, listen! There are those of us who aren’t in the “VM Hall of Fame” and other such categories because we

Wow ... Perfect

TS is Trace Start, and TE is trace end. So basically a trace flag I can also poll. A :-)

I added the trace start, trace end in already. I built the system, so I will test it in the morning. adrian@...> wrote:

All I need is flags at a defined address that I can poll (probs every instruction). I would also reset the flags at REXX start or when acting on them but presumably that won't impact your mod.

If that was there I would definitely plug it into BREXX, thank you. Won't impact GCCLIB which is fine. In fact that would probably represent what the state of play was with CMS when rexx was

So you do not want an HI mod anymore? adrian@...> wrote:

Ok ... I think it is clear that VM/370 does not have the facilities to provide an exit routine, and there is limited support to provide this by the community. As we can't trap HX events it's rather

Bob, Sorry, brain fade, (its my wife’s birthday, not got time to check properly) . DMSFREE … TYPE=NUCLEUS… GC20-1807-4 Page 302… Dave Sent: 25 April 2020 18:13 To: [email protected] Subject:

Dave, Do you recall what storage has to be TYPE=SYSTEM? Bob Bolch

No, its just flagged as such so its not released… Dave Sent: 25 April 2020 17:50 To: [email protected] Subject: Re: [h390-vm] Program Interrupts (signals)

I need to think that through ... Are there any limits to system memory etc.?

Good question ... because it gets to the heart of my concerns. I would want the program to exit but I would not want CMS to execute it's abend logic and in that way ensure that BREXXs memory does not

So REXX needs to allocate system storage… Dave Sent: 25 April 2020 16:58 To: [email protected] Subject: Re: [h390-vm] Program Interrupts (signals) Later editions of the manuals say 'All user storage

A good point and well made!

Noted :-)

Joe, Its older than that. There was a CP40 based on a hacked 360/40 which became CP/67 <https://en.wikipedia.org/wiki/Conversational_Monitor_System>

I think you would need to include a NUCON macro and an FVS macro in an assembly program to get the address of KXFLAG and the bit value of KXWANT. However, I would not suggest going this way because

Correct. After HX, CMS ends whatever is running and returns to the command prompt. It has worked exactly that way for 45 years. Bob Bolch adrian@...> wrote: