Re: Java->C->HLASM non-XPLINK

2017-03-21 Thread Tony Harminc
Someone anonymous wrote: > I know what my end-game is -- a java class which will call an existing HLASM > module, which is _not_ XPLINK -- I wrote a dummy HLASM program called > JAVAOSLI, which simply does a WTO. But your assembler module *is* LE? > It's my understanding that the only way to c

Re: Java->C->HLASM non-XPLINK

2017-03-21 Thread Charles Mills
6:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Java->C->HLASM non-XPLINK First, more people will see your post if you send to the listserv rather than the newsgroup. -- For IBM-MAIN subscribe / signoff / archive access instruc

Re: Java->C->HLASM non-XPLINK

2017-03-21 Thread Denis
call COBEP*/ On JVM execution you can try the following option to percolate e.g. an 0C4 or S806: -Xsignal:userConditionHandler=percolate Denis. -Original Message- From: Don Poitras To: IBM-MAIN Sent: Tue, Mar 21, 2017 2:43 pm Subject: Re: Java->C->HLASM non-XPLINK First, more

Re: Java->C->HLASM non-XPLINK

2017-03-21 Thread Don Poitras
First, more people will see your post if you send to the listserv rather than the newsgroup. Second, you need to have R13 pointing to a save area when you call the non-XPLINK program. If it has any parms, you need to have R1 pointing to them. If you are in AMODE 64 and calling an AMODE 31 progra