I'm using the Metal option to build a program to be called from APL2 without the LE runtime environment. I have the entry and exit linkage stuff working, but I'm having trouble getting the metal C environment to work. When I call __cinit, I'm getting an abend. APl2 is trapping the abend and taking a snap dump, but I'm too rusty with mainframe stuff to make sense of the dump.
Can anyone think of something obvious I might be doing wrong to make __cinit abend?
(I copied the code to call __cinit directly from the Metal C programming Guide and Reference.)
Thanks in advance.
IBM APL Products and Services
This topic has been locked.
Pinned topic Is __cinit supposed to crash?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-11-18T14:03:45Z at 2010-11-18T14:03:45Z by SystemAdmin
Visda 060001SUB122 PostsACCEPTED ANSWER
Re: Is __cinit supposed to crash?2010-11-18T12:04:53Z in response to SystemAdminHi David,
mysysenv.__csesubpool = 127;
If that didn't solve the abend, can you please post the Abend and Reason codes here, it would help if you post your CPARMs/compile options as well.