RMODE(64)When neither binder options RMODE=64 nor RMODEX are specified,
RMODE(64) ESD are treated as RMODE(ANY) for module loading and execution,
with the exception of data class C_WSA64, which can be loaded above the
2-gigabyte bar. In this case, the map in the binder listing and ESD records
obtained from program objects through the binder API (for example, by the
AMBLIST service aid) will show the original RMODE. However, for load
modules, the ESD records are permanently modified.
Joe

On Mon, Dec 21, 2020 at 9:45 AM Joseph Reichman <[email protected]>
wrote:

> I personally wanted to know I’m not sure if RMODE64 was available on 2.3
>
> I looked up the CDE and it had an extension ihacdx so did xtentlist to
> take into account 64 bit address
>
> > On Dec 21, 2020, at 10:38 AM, R.S. <[email protected]>
> wrote:
> >
> > W dniu 21.12.2020 o 16:19, Ed Jaffe pisze:
> >>> On 12/21/2020 6:27 AM, Paul Gilmartin wrote:
> >>>
> >>>> On Sun, 20 Dec 2020 21:14:21 -0800, Ed Jaffe wrote:
> >>>
> >>>>
> >>>> There are many, Many, MANY restrictions!
> >>>>
> >>> Are these listed anywhere?  For code or for data?  Services calls?
> Citation needed.
> >>
> >>
> >> I was referring primarily to services. Our approach has been to invoke
> those that don't support RMODE(64) from GLUE code running below the bar.
> Many services still don't support AMODE(64). For those, even the
> inout/output parameters must be below the bar.
> >
> > (my humble question)
> > Out of curiosity: why did you choose RMODE(64)?
> > I understand AMODE(64) - more memory for data, but RMODE64 seems to me
> good solutions for really large programs or maybe multi-program address
> space like CICS.
> >
> > --
> > Radoslaw Skorupka
> > Lodz, Poland
> >
> >
> >
> >
> >
> > ======================================================================
> >
> > Jeśli nie jesteś adresatem tej wiadomości:
> >
> > - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> > - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> > Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
> >
> > mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,
> www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, NIP:
> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2020 r. wynosi 169.401.468 złotych.
> >
> > If you are not the addressee of this message:
> >
> > - let us know by replying to this e-mail (thank you!),
> > - delete this message permanently (including all the copies which you
> have printed out or saved).
> > This message may contain legally protected information, which may be
> used exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar
> action, violates the law and may be penalised.
> >
> > mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850
> Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the
> Capital City of Warsaw, 12th Commercial Division of the National Court
> Register, KRS 0000025237, NIP: 526-021-50-88. Fully paid-up share capital
> amounting to PLN 169.401.468 as at 1 January 2020.
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to