On Tue, 4 Apr 2023 14:06:37 -0400, Steve Thompson wrote:
>A similar issue happened with BPXWDYN. COBOL can't set R0. So a
>new entry point in BPXWDYN was created that handled that problem.
>
Why does BPXWDYN require R0 to be set? I've done TSO CALL BPXWDYN
never worrying about R0, so perhaps the TMP sets R0 as needed.
Why did designers provide an alternate entry point rather than simply
removing the restriction? Did that necessarily introduce a new,
undocumented restriction?
I read:
BPXWDYN can be called through an alternate entry point, BPXWDY2.
BPXWDY2 accepts the same parameter list but does not require R0
to be set to 0. This entry point will also preserve the program mask.
Thia is the first mention of "preserv[ing] the program mask." Is it normal
for CALL or LINK to preserve the program mask? Should modifying
the program mask be mentioned as a behavior of BPXWDYN?
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
