Alan Schwartz wrote:
I know that TRUNC(OPT) is preferred. But the lpar that uses OPT is moving
into the lpar that has STD as the default. When a program is recompiled
will it function the same albeit less efficient? My feeling is it will
Not likely. TRUNC(STD) says "truncate to the picture". So if you
have PIC S99 BINARY when you move a constant or a data item with
a value of 200, the defined item will end up with a value of 00
(only 2 9s in the picture, so truncate to two decimal digits to
the left of the decimal point). Not likely what you want.
I appreciate your explanation of INTDATE only impacting calls to LE date
services. We don't have a PL1 compiler but they do use Assembler and
Easytrieve and do a fair amount of inter-language linking of routines. I
don't know how difficult it will be to make the kind of determination
needed especially looking at the implicit functions probably in use.
I've had in reserve the plan to have our Endevor processes pass the
sending lpars parms to their compiles but that won't help compiles done
outside of Endevor.
More analysis to come.
Kind regards,
-Steve Comstock
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
