John,
sorry- I did need a second and third pass reading what you said- I did
not get the fact that it is NOT fixed at a later level.
I say YES go for an RFE- this is more than needed.
I could now repeat Garys W. arguments, but ...
Martin
Your *+4 would be incorrect in more than 1 way.
Here's another case where more liberal immediate operands (LLILF
Rx,Q(CEEx)) would come in handy.
sas
On 3/8/2017 10:23, Gary Weinhold wrote:
I think it is worth RFEing. Reentrant baseless code is a desirable
standard and IBM's own code
On Wed, Mar 8, 2017 at 9:29 AM, wrote:
>
> Using ceepccal hlasm , goff, rent & base0
> In code (base 0):
>
> provads 0h
> la 2,ceepcall_w
> larl 15,modulo
> CEEPCALL (15),(END_TIME,START_TIME),VL,MF=(E,(2))
> j dopo
On Wed, Mar 8, 2017 at 9:23 AM, Gary Weinhold wrote:
> I think it is worth RFEing. Reentrant baseless code is a desirable
> standard and IBM's own code should not be thwarting it. And over the years
> my experience has been that LE has on occasion ignored HLASM standards and
Using ceepccal hlasm , goff, rent & base0
In code (base 0):
provads 0h
la 2,ceepcall_w
larl 15,modulo
CEEPCALL (15),(END_TIME,START_TIME),VL,MF=(E,(2))
j dopo
EXTRN modulo
modulo XATTR
I think it is worth RFEing. Reentrant baseless code is a desirable standard
and IBM's own code should not be thwarting it. And over the years my
experience has been that LE has on occasion ignored HLASM standards and trends.
They should be reminded that they should interface nicely with
John,
I would not RFE it- it is there and you could copy the macro to the
older system.
sidenote: I would have done it with r14 (less thinking time at
converting the macro ;-) )
Martin
This is likely not worth the bother, but I have a "problem" with the
CEEPCALL macro. Yes, I write LE enabled HLASM. Mainly so that I can easily
inter-operate with C.
I like to use "baseless" coding techniques. One problem that I had, which
required a base register be used, is that I use the