I'm not sure why there is confusion. MVCP and MVCS deal with current primary and current secondary. When you have SASN=NEW on a space-switch PC, then the PC target gets control with both primary and secondary the same -- the new primary. MVCP and MVCS are no different functionally than MVCK in that case.
It should not be a surprise that you get different results from MVCP/MVCS when you change SASN=OLD to SASN=NEW. In the former, you are referencing your space and your caller's space. In the latter you are referencing only your space. You should not expect to be able to reference your caller's space from a SS-PC target that was SASN=NEW. (In specific cases if your caller was known to have PRIMARY=HOME you would have alternatives, but in general a caller might have primary not equal to home). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
