On Thu, 23 Oct 2025 13:44:52 -0400, Mike Shaw wrote: >... To pass an argument to >the exec, you code PARM= as a single BINARY ZERO followed by the argument >for the exec. > <https://www.hyrumslaw.com/>
It's an accident. Programmers knew about it and were exploiting it long before it was documented. They noticed that in the Assembler interface to REXX, if the member is omitted the field defaults to zeroes and the interpreter presumes sequential. >Does anyone else think this is stupid? > I do. Instead of IBM adding code to IRXJCL >so that it checks the SYSEXEC DD to see if it is DSORG=PS and then acting >accordingly if it is, > That may not be the best way. It may not correctly handle: //SYSEXEC DD DSN=DATA.SET(MEMBER). which Using Data Sets calls a "sequential allocation", yet OPEN sets DCBDSORG=PO. > ... the user is supposed to edit their JCL PARM= field >'HEX ON' and type in a binary zero (which displays as a blank under ISPF) >between single quotes to tell IRXJCL to treat SYSEXEC as a sequential file. > Infuriating when I try to edit JCL in a UNIX file. It would be better to use an explicit token which is not considered a valid member name by the JCL converter. That should be a good Idea. >I don't get it... > Simple. Developer indolence. It could have been done better by adding only a CLC and a BC to the code. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
