> Anyone got a clue why on earth the SWA stuff is in a DSECT and macro
called
> ZB505? I see a bunch of other IEFZBnnn macros, which seem equally badly
> named. I'm quite frankly horrified.
This old version suggests this naming convention goes back to at least
1972. The Poughkeepsie developers of that era are all gone from IBM, so
some of the "why?" answers are lost in the sands of time.
* /* 04/01/72 */
* %GOTO ZB505PLS; /*
MACRO
IEFZB505
ZB505 DSECT
SWBLKPTR DS F POINTER TO BLOCK
SWVAFW DS 0F 4 BYTE SWA VIRTUAL ADDRESS
SWVA DS CL3 3 BYTE SWA VIRTUAL ADDRESS
SWBLKID DS CL1 BLOCK ID OR ZERO
SWLNGTH DS F LENGTH OF SWA BLOCK (NOT INCLUDING
* SWA PREFIX)
SWCHNPTR DS F CHAIN POINTER OR ZERO
MEND */
*%ZB505PLS:;
* DCL
* 1 SWAEPA BASED(SWEPAPTR),
* 2 SWBLKPTR PTR(31), /* POINTER TO BLOCK */
* 2 SWVAFW PTR(32), /* 4 BYTE SWA VIRTUAL ADDRESS */
* 3 SWVA PTR(24) BDY(BYTE), /* 3 BYTE SVA */
* 3 SWBLKID CHAR(1), /* BLOCK ID OR ZERO */
* 2 SWLNGTH FIXED(31), /* LENGTH OF SWA BLOCK (NOT
* INCLUDING SWA PREFIX) */
* 2 SWCHNPTR PTR(31); /* CHAIN POINTER OR ZERO */
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
