开云体育

I am happy to try this ... but I clearly need more hints / examples! Where should I start? Can you help? A

Useful thanks

Is there an example assembler doing this?

Not sure what you mean ... how can I use os interrupt handlers without os macros?

Indeed, VM/SP does not clean up: q cmslevel VM/SP Release 5, Service Level 521 Ready; T=0.12/0.50 13:29:06 type divzero exec /* check divide by zero */ 'DMSIBM' 'q n' Ready; T=0.01/0.04 13:29:14

Since this version of Fortran came from the OS world, it almost certainly uses SPIE to get control on a program check. Bob

The point is that I am trying to make gcclib avoid the need for a IPL if a client program happens to cause an abend ...

Exactly. But I need a hint about how to catch it! How does the Fortran runtime do it?

If I must I must ... I will just have to use infinite monkeys!

PrincOps. You can find it on bitsavers.. http://www.bitsavers.org/pdf/ibm/370/princops Joe adrian@...> wrote:

Dave, Thats my point. Just as fortran catches the divide by zero, so Adrian should have a C runtime that does the same thing, no? Joe

Have you a link ... I can't think what pops means!

Considering a shared GCCLIB and BREXX, and thinking of a REXX program calling something like EXECIO also leveraging GCCLIB. Well I need a way to know that a program (say EXECIO) had bought a farm and

Joe, Yes you can take control, but the question I would ask is do you want to? What are you going to do if a program does a divide by zero,. For example FORTRAN already catches divide by zero…. So

The VM/370 System Programmers Guide, page 238: "The program interruption handler, DMSITP, receives control when a program interruption occurs. When DMSITP gets control, it stores the Program old PSW

That is exactly as Bob wrote. I've checked POPS for System/370 - on page 72 you have all serviceable exceptions wit old and new PSW what probably cover all cases. And this is as in Unix world - the

I don’t think there is an issue with the OS interrupt handlers, the problem with OS macros is that if you are using OS storage the chains get cleaned at program termination time. Provided you are

STAE is an OS macro as well.?? I can't recall for sure but if memory serves this macro provides almost nothing in CMS.? I seem to recall it being a no-op. Bob

Adrian, Divide-by-zero does indeed cause a program check interruption 9.? If you are concerned about this possibility, mitigate it in your C code by checking the divisor first to see if it is zero.?

Can’t we use STAE? Or is that also one of those ’tainted’ OS macro’s?