On Sun, 17 Aug 2025 14:06:12 -0500, Paul Gilmartin <[email protected]> wrote: >Is it then the target's responsibility to dual-path and >*assume* PLIST8 for an AMODE64 caller, and >*assume* PLIST4 for other AMODE callers?
Like IBM services, it is up to you to write the restrictions for your services. If these are your restrictions, then you can assume them. Knowledge is power and knowing the caller's amode can make you powerful but it's up to you to create its power. You can't assume PLIST8 for AMODE64. Using SETFRR as the example, AMODE64 is supported but not RMODE64. PLIST4 is required. You can use caller AMODE as you wish. SETFRR SDWALOC31=NO is ignored for AMODE64 but honored for AMODE31. Someone calls your service using LINKX and your service returns some data. You can choose where to allocate the data depending upon the callers AMODE. You're not going to storage obtain loc=64 when the caller is running AMODE31 but you could choose LOC=24, 31 or ANY. You specifically asked about dual-path logic which requires knowing the caller's AMODE. Do you need need dual-path based on AMODE? Knowing the AMODE is a tool but it is up to you to implement the solution. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
