More appropriately, since my ALLOC of SYSEXEC to a PATH specified FILETYPE(TEXT), it seems to me that should signal to the system (whoever creates and opens the SYSEXEC DCB) that the data in that file are presumptively RECFM=V,LRECL=(some reasonable maximum like 4096).
Hindsight is always 20/20. I will try out both LRECL on the existing ALLOC and the BPXWDYN method and see which works. Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Thursday, September 15, 2022 7:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to use LISTDSI from Rexx under Unix shell? On Thu, 15 Sep 2022 22:19:40 +0000, Farley, Peter x23353 <peter.far...@broadridge.com> wrote: >Follow-up: Unexpected and dumb restriction found. > >While using the knowledge I built during this investigation to write a >real-world use of the process, I found that the "address TSO" process from a >starting Rexx in a Unix directory has a record-length restriction on SYSEXEC >of 80 bytes. > >In other words, ALLOC of a Unix directory as the SYSEXEC DD makes TSO (and/or >Rexx itself) "AssUMe" that the LRECL for the directory is 80. > >In JCL you may be able overcome this using a dummy first PDS with a longer or >variable-length RECFM/LRECL, but as far as I can tell ALLOC has no way to >CONCAT a PDS (dummy or otherwise) with a Unix directory. BPXWDYN may be able >to do better, I really need to research that. > ADDRESS TSO "call bpxwdyn 'concat(SYSEXEC,...)'" >Anyway, if any line in the second Unix directory Rexx script (the one you >really want to run) that is executed under "address TSO" is > 80 bytes, you >get a "WRONG.LENGTH.RECORD" error and I/O abend from BPAM. > Can't you specify LRECL on ALLOCATE (or BPXWDYN) PATH ...? Many years ago I encountered a similar (I felt it was worse) problem because a PATH hasn't a DSORG acceptable for REXX. Has that been fixed? DYNALOC should supply PO or PS as suitable, or at least make DSORG not mutually exclusive with PATH in JCL. I circumvented with CONCAT. And I got an ABEND from FREEMAIN (I guess) at exec termination (storage key conflict, I guess.) I ignored it because it occurred at completion and no data were lost. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
