🚀 go-pugleaf

>
> I am trying to call a cross memory service using stacking PC and the
call
> fails in S0f8-10. Can anyone in this list give me some insight into
what
> this could be due to

Sure. No problem.

> S0F8-10, according to manual says: "The issuer of a Supervisor Call
(SVC)
> instruction was not in the correct mode to issue the SVC. A
hexadecimal
> reason code in the RTM2CRC field of the RTM2WA data area explains the
> error: and rsncode 10:  10     The issuer was in cross memory mode."
>
> What mode is this about? My etdef in the SP is as follows:
>
> ETD1           ETDEF
TYPE=ENTRY,PROGRAM='PSG0001',SSWITCH=YES,SASN=NEW,X
>                STATE=PROBLEM,AKM=(0:15),EKM=(0:15),EK=8,PKM=REPLACE,
X
>                ARR='PSGARR01'
>
> And I am modesetting to problem mode and key 8 before invoking PC:
>
>                LMH   15,15,SV1PC
>                L     14,SV1PC
> *              DROP  14
>                MODESET MODE=PROB
>                MODESET KEYADDR=KEYADDR1,WORKREG=2
>                PC    0(14)
>
>  And :
>
> KEYADDR1       DC    X'08'

If you defined this PC routine in address space A and then you call it
from address space B, then your PC routine "PSG0001" will get control
with PASN=SASN=A,HASN=B, that is, your PC routine will be running in
cross memory mode. That's what "SSWITCH=YES" means on the entry table.
You wanted the routine to run in your server address space. The hardware
did what you asked it to.

But here's the thing... you can't issue an SVC while running in
cross-memory mode. So if your PC routine issues -any- SVC (GETMAIN,
WAIT, POST,...) that SVC instruction will get a S0F8. You can only avoid
that by avoiding those macros, or by using the forms that tolerate
cross-memory. Often that's a "LINKAGE=SYSTEM" keyword or something
similar.

If you are going to write code that runs in cross-memory mode, you are
going to have to get familiar with the restrictions of that environment
and use the correct forms of the macros. You're getting a lot closer but
you're not there yet.

CC