IRXJCL is great for 'pure Rexx. Low overhead, lightweight. However, you can't use any function described as 'TSO/E only'. You might be surprised how many common functions require TSO. The Rexx manual has a section on TSO/E-only functions. If you need even one of them, you have to run under IKJTSOxx. I tried using IRXJCL early on and decided that it was too restrictive for regular use. In the end, with today's super-fast processors and DASD, you won't even notice a difference in practice.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Barkow, Eileen Sent: Thursday, March 03, 2016 10:04 AM To: [email protected] Subject: (External):Re: rexx and tso alllocate thanks Lizette. I started out using IKJEFT01 and for some reason switched to IRXJCL. What will run with IRXJCL will also run from ISPF 1.6 but not the other way around. Anyway, the SDSF REXX clists certainly run a lot faster than the cumbersome SDSF BATCH and can accomplish the same thing as far as extracting spool files. ,-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Thursday, March 03, 2016 12:27 PM To: [email protected] Subject: Re: rexx and tso alllocate Have you tried under TSO BATCH with or without ISPF libraries (and I am thinking the ISF libraries may need to be included in the JCL). Lizette -----Original Message----- >From: "Barkow, Eileen" <[email protected]> >Sent: Mar 3, 2016 9:26 AM >To: [email protected] >Subject: Re: rexx and tso alllocate > >I am currently converting some SDSF BATCH routines to SDSF REXX and I >am finding that things do not always work the same when invoking the clist >from ISPF 1.6 and invoking it from batch with IRXJCL. >option 1.6 runs under TSO/E and IRXJCL does not. >so far, I have encountered differences with the ISFOWNER settings, >putting quotes on datasetnames used for ISFPRTDSNAME, and the use of the TSO/E >SYSDSN routine is not allowed with IRXJCL. > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] >On Behalf Of Lizette Koehler >Sent: Thursday, March 03, 2016 11:09 AM >To: [email protected] >Subject: Re: rexx and tso alllocate > >If you search on JES2DISK by John McKown, >https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997 > >This is a very nice example of extracting from SPOOL to DASD or other. > >Lizette > > >-----Original Message----- >>From: Tim Brown <[email protected]> >>Sent: Mar 3, 2016 9:06 AM >>To: [email protected] >>Subject: Re: rexx and tso alllocate >> >> >>No I havent will research >> >>Thanks >> >>-----Original Message----- >>From: IBM Mainframe Discussion List [mailto:[email protected]] >>On Behalf Of Lizette Koehler >>Sent: Thursday, 03 March, 2016 11:04 AM >>To: [email protected] >>Subject: Re: rexx and tso alllocate >> >> >>** THIS IS AN EXTERNAL EMAIL ** Use caution before opening links / >>attachments. Never supply UserID/PASSWORD information. >> >> >>If you are a jes2 shop, have you looked at the ISFEXEC (SDSF REXX) to do some >>of this work? >> >>Lizette >> >> >>-----Original Message----- >>>From: Tim Brown <[email protected]> >>>Sent: Mar 3, 2016 8:31 AM >>>To: [email protected] >>>Subject: Re: rexx and tso alllocate >>> >>>Briefly, I have a home grown process that takes selected output files from >>>the Jes2 spool via an external writer and writes them to a combined dataset >>>with separators. I then read the results via REXX and create individual >>>files that are processed via TXT2PDF to create pdfs. Some of the resulting >>>pdfs were not taking the width of the page and I thought it was related to >>>files whose actual lrecl was quite less than the lrecl of 300 that was used >>>to capture all files originally. That was not the case, it was the zoom >>>parameter on the font statement, by making it 100 it fit the page perfectly. >>> >>>I am ok for now , but since I started this thread, how do others create >>>PDF's from Jes2 spool output? >>> >>>Appreciated as always! >>> >>>Tim >>> >>> >>> >>>-----Original Message----- >>>From: IBM Mainframe Discussion List [mailto:[email protected]] >>>On Behalf Of Bill Woodger >>>Sent: Wednesday, 02 March, 2016 4:16 AM >>>To: [email protected] >>>Subject: rexx and tso alllocate >>> >>> >>>** THIS IS AN EXTERNAL EMAIL ** Use caution before opening links / >>>attachments. Never supply UserID/PASSWORD information. >>> >>> >>>Joel Ewing has made a valid point about programs potentially having LRECL >>>expectations. COBOL is good for that. >>> >>>Tim Brown is silent on what he actually wants to do this for. Until then >>>it's difficult to suggest something concrete. Ditch the blocksize has been >>>said, making the LRECL smaller has no obvious benefit has been said. Just to >>>add that the LRECL can always be "overridden" on the DD for a subsequent >>>reference. >>> >>> >>>On Wednesday, 2 March 2016 08:24:22 UTC, Ted MacNEIL wrote: >>>> Why not just create a VBA file with a very long LRECL and not worry about >>>> it at all? Longer LRECLs don't introduce any more ov‎eReader than short >>>> ones. >>>> >>>> -teD >>>> Original Message >>>> From: Kjell Holmborg >>>> Sent: Wednesday, March 2, 2016 02:54 >>>> To: [email protected] >>>> Reply To: IBM Mainframe Discussion List >>>> Subject: Re: rexx and tso alllocate >>>> >>>> One suggestion might be that your rexx program writes records to a stem >>>> variable and you could keep track of the longest record and then just >>>> before writing the contents of the stem variables to the dataset you do a >>>> TSO Allocate with the longest record as a variable to the ALLOCATE command. >>>> >>>> /Kjell ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
