On Tue, 6 Feb 2024 16:18:16 -0600, Michael Schmitt wrote: >Reason I never knew you could have a sequential SYSEXEC is I'm on z/OS 2.4. >This capability is added in z/OS 2.5. > It has long been possible according to lore. A resourceful programmer looked at the control block description where was documented that if the member was 8x'00' SYSEXEC was treated as sequential and tried forcing that in JCL. IBM learned that programmers were doing that and finally documented it.
>On Mon, 18 Sep 2023 15:25:47 +0000, Schmitt, Michael wrote: > September? Delayed reaction!? >>Huh. I always thought that SYSEXEC had to be a library. >> >>I suppose a sequential SYSEXEC only works for IRXJCL, not IKJEFT01. > Only because TSO syntax regards 8x'00' as an invalid member name, but the JCL reader never bothered to check. What about other unconventional member names that might be created with Assembler STOW? > ...And that if SYSEXEC is sequential, the exec shouldn't call other execs. >> They could reside in SYSPROC. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
