.I'm experiencing an issue which I don't understand.
. 
I have a small Stacking Space Switching PC Service Routine,
its Entry Table Definition (ETDEF) has SASN=Old Specified.
.
It is my understanding -                                                
SASN specifies whether the stacking PC routine will execute with SASN   
equal to the caller's PASN (SASN=OLD)
.
PC Service Routine
- issues a STORAGE OBTAIN for some reentrant storage  
- issues a MVCP (Move Characters To Primary) to copy a 
  parameter list into the reentrant storage
- copies a small amount of data (under 100 bytes) back 
  to the secondary address spaces using an MVCS instruction with 
  an address provided in the parameter list.
.
The  parameter list also contains an eye-catcher which is verified
after completion of the MVCP (Move Characters To Primary) instruction.
The are no Access Registers used. 
.
This routine works well as I can see the data returned to the
caller/requester in the secondary address space.
.
I agree - Not much of a PC Service Routine, and Access List may be better
But using AR registers is Not the ISSUE !
.
.
When I modify the Entry Table Definition to use SASN=NEW for this Stacking 
Space Switching PC Service routine, the MVCP instruction does Not produce 
the same results. 
Meaning NO data is copied from the secondary address Space to the Primary 
Address Space. the condition Code is 0.
.
After execution of the MVCP instruction the condition code is 0 and
the structure in the reentrant storage that should occupy the remote 
parameter list does not contain the eye-catcher. The Return address for the 
data is zero. 
.
According to Principal Of Operations, There is no condition code for this 
scenario, .MVCP and MVCS only provide condition code 0 or 3.
.
This anomoly only occurs when I change the ETD Def to use SASN=NEW.
.
Is this Normal Behavior ?, as I have not found this documented clearly
in Extended Addressability. The Program does not change, only the specification
for SASN in the Entry Table Description..Do I need to specify another parameter 
in the ETDEF macro ?
.
.Sorry I can't post code - contractual
Paul D'Angelo...                 .

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

Reply via email to