Re: SYSREXX PDS size
To enhance the information provided. This is under AXR function in the Operating system. This shows some code snippets: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa800/rxxfction.htm System REXX is a z/OS® component that allows REXX execs to be executed outside of conventional TSO/E and Batch environments. REXX has long been considered one of the fastest development languages for system exit and utilities work on z/OS. The possibilities for exploiting REXX code through the use of System REXX are vast, whether to provide operator assists or to provide an easy way to process files and strings. The System REXX environment provides a function package that allows a REXX exec to invoke system commands and to return results back to the invoker in a variety of ways. System REXX execs may be initiated through an assembler macro interface called AXREXX or through an operator command. There are two different System REXX environments supported: TSO=NO TSO=YES In both environments, the exec runs in problem state, key 8, in an APF authorized address space. Any modules that are loaded, linked or attached from the exec, must reside in an APF authorized library; otherwise, a X'306' abend occurs. In both cases, the REXX exec runs under the enclave of the AXREXX invoker when the invoker can be classified; otherwise, the exec runs under the enclave of AXR. There can be up to 64 REXX worker tasks running TSO=NO execs and up to 8 TSO server address spaces running TSO=YES execs. If a worker task is not available for an inbound TSO=NO request, or if a TSO server address space is not available for a TSO=YES request, the request is queued and the requestor is suspended if SYNC=YES is specified. The order in which System REXX processes queued requests may not be in the same order that the requests have been submitted. AXREXX invokers that use SYNC=YES should consider the potentially long wait time. Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Allan Staller > Sent: Friday, August 24, 2018 4:55 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SYSREXX PDS size > > "System Rexx" Came in about z/OS 1.9 IIRC. A set of rexx api's and > environments that allow for things like issuing commands, retrieving command > output, etc. > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Jesse 1 Robinson > Sent: Thursday, August 23, 2018 11:02 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SYSREXX PDS size > > Could I ask what 'SYSREXX' means? At first I thought this referred simply to > the standard common set of REXX execs that users allocate at logon. Is it > something else? > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Beaver > Sent: Thursday, August 23, 2018 8:45 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: SYSREXX PDS size > > It all depends on the concatenation > > Start ISRDDN and see how it reacts > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Carmen Vitullo > Sent: Thursday, August 23, 2018 9:56 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SYSREXX PDS size > > our system rexx library is a library PDS-E, VB 255, I think the guy who set > it up said FB 80 would not work,checking the fine manual he was correct, VB > 255 is required > > > > Carmen Vitullo > > - Original Message - > > From: "Carmen Vitullo" > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Thursday, August 23, 2018 9:53:47 AM > Subject: Re: SYSREXX PDS size > > let me check, from what I recall sysrexx pds must be vb 255 :( > > > Carmen Vitullo > > - Original Message - > > From: "Tony Thigpen" > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Thursday, August 23, 2018 9:42:52 AM > Subject: SYSREXX PDS size > > Our SYSREXX PDS is currently defined as VB 255. We had a system problem this > week that one Sysprog thinks that the the VB 255 aggravated the problem and > is insisting that we change it to FB 80. I disagree, but I thought I would > though it out to the list for views. > > Views? > > -- > Tony Thigpen > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ::DISCLAIMER:
Re: SYSREXX PDS size
"System Rexx" Came in about z/OS 1.9 IIRC. A set of rexx api's and environments that allow for things like issuing commands, retrieving command output, etc. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jesse 1 Robinson Sent: Thursday, August 23, 2018 11:02 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size Could I ask what 'SYSREXX' means? At first I thought this referred simply to the standard common set of REXX execs that users allocate at logon. Is it something else? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, August 23, 2018 8:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size It all depends on the concatenation Start ISRDDN and see how it reacts -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, August 23, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
On Thu, 23 Aug 2018 22:05:33 +, Seymour J Metz wrote: >> (In case you have some sort of irrational attachment to FB.) > >I have an irrational attachment to providing library concatenations that will >work. Concatenating LRECL 80 and LRECL 255 REXX libraries will not work. > >Are you proposing that the installation convert the IBM libraries to FB with a >larger LRECL? If so, how is that better than converting them to VB? > That was supposed to be sarcasm, directed against the view that "FB 80 was good enough for our grandfathers, it should be good enough for us. VB was provided only to economize on storage and that's no longer a concern." o z/OS supports concatenation of FB libraries and UNIX directories. o z/OS supports concatenation of VB libraries and (the same) UNIX directories. o Why not add the third side and complete the triangle? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
> (In case you have some sort of irrational attachment to FB.) I have an irrational attachment to providing library concatenations that will work. Concatenating LRECL 80 and LRECL 255 REXX libraries will not work. Are you proposing that the installation convert the IBM libraries to FB with a larger LRECL? If so, how is that better than converting them to VB? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Thursday, August 23, 2018 5:56:11 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: SYSREXX PDS size On Thu, 23 Aug 2018 19:34:48 +, Seymour J Metz wrote: >It's more than a custom; FB80 doesn't allow long lines. > True. But FB needn't be 80. In fact, FB supports records with 8 more data bytes than the maximum supported by VB. (In case you have some sort of irrational attachment to FB.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
On Thu, 23 Aug 2018 19:34:48 +, Seymour J Metz wrote: >It's more than a custom; FB80 doesn't allow long lines. > True. But FB needn't be 80. In fact, FB supports records with 8 more data bytes than the maximum supported by VB. (In case you have some sort of irrational attachment to FB.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
It's more than a custom; FB80 doesn't allow long lines. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Jesse 1 Robinson Sent: Thursday, August 23, 2018 1:46 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: SYSREXX PDS size (OK, I know my question sounded dumb, but I was afraid I was grossly misinterpreting the thread.) If I were gifted with the luxury of building a new MVS environment from scratch, I would make all REXX and CLIST libraries FB-80. For one thing, that's how virtually all vendors deliver execs. Running with concatenated VB libraries means converting delivered FB objects to VB. Not a huge burden but a task that must be performed periodically to keep up with vendor maintenance. In truth, that chore often gets overlooked--for years at a time! So what's with VB? Every 'mature' shop I've ever been in has used VB libraries. The custom--it's no more than that--goes back decades (think 70s)--to the day when DASD was extraordinarily slow and expensive. Execs are text files that contain lots of trailing blanks. A VB data set can be edited to remove trailing blanks and considerably reduce the space required to store execs and to perform I/O on them. Long before MVS REXX, CLISTs were heavily used. VB reduced the overhead, meaning that VB was more economical. That concern seems pretty trivial these days. But in order to convert existing VB exec libraries to FB, *every single user* in the shop would have to convert at the same moment because, for the all the whizzbang modernization in MVS, data set concatenation still requires all FB or all VB in a single DD. There would be no grace period in the cutover. Just chaos. In the case of system REXX, our SYS1.PARMLIB(AXR00) names only one SYSREXX library, so we could convert that guy to FB with minimal impact. But really, why bother? In 2018 I still get problem calls with mysterious abends resulting from invalid concatenation. A practical suggestion. If your SOP exec libraries are VB, you can get around some concatenation problems like this: ADDRESS ISPEXEC "SELECT CMD(EX 'SYS1.SBLSCLI0(BLSCLIBD)') MODE(FSCR)" This statement in a VB library invokes the real IBM-supplied FB IPCS. No conversion or periodic updates required. Transparent to the user. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Thursday, August 23, 2018 10:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size On 8/23/2018 9:01 AM, Jesse 1 Robinson wrote: > Could I ask what 'SYSREXX' means? At first I thought this referred simply to > the standard common set of REXX execs that users allocate at logon. Is it > something else? System REXX. AXR address space. Scott Fagen's last project before leaving IBM. Where is the real Skip Robinson and what have you done with him? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://secure-web.cisco.com/12n08JKdkdoeomgo8xXmFv4g6kIumZ8SkhGql2MLJw2lqGonfLypVwzvVMtTCdYtPlv-8vlErIP7wBd6HLVgcZ5p8cto6rD-z6eiGDoE6a1SF15JdB5p096tJZI_j8GmR7bGXNxnr_UfTMa6Abl5ZrnXHOiDefGtV9HMOGaor_3eE1uPWSXJ9TletBI_8rrzY2mMfeILwvk3elviE2zqHv74l5aa6rXp9ot8mbDwpzsOiYNtCiTepBF88JuiFyaR57tlbbC7LvwqYz2UzslcRLy-L4NJfeT_DgugRhU-tOQBoCUNXJCsEsJLt4KHc7emS45rdLyUIAZCfQs9QfVTTW6TSaW9WqW7kd6KqUAUFeyuF1eSk-lfs3fSZDD7VW4zlC052rJ-VyNMi2wEB2Zq_I96wBKMfFuZq6MlM4cnFKg8x_-Bhwrg0oe90OkE6Klm7/https%3A%2F%2Fwww.phoenixsoftware.com%2F -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
On Thu, 23 Aug 2018 17:46:43 +, Jesse 1 Robinson wrote: >(OK, I know my question sounded dumb, but I was afraid I was grossly >misinterpreting the thread.) > I wondered, too. Your contributions to some recent threads have not shown the sophistication I had come to expect of you. >If I were gifted with the luxury of building a new MVS environment from >scratch, I would make all REXX and CLIST libraries FB-80. For one thing, >that's how virtually all vendors deliver execs. Running with concatenated VB >libraries means converting delivered FB objects to VB. Not a huge burden but a >task that must be performed periodically to keep up with vendor maintenance. >In truth, that chore often gets overlooked--for years at a time! So what's >with VB? > Ouch! (But things were so simple wnen we could count on all input's coming from an 029.) >Erery 'mature' shop I've ever been in has used VB libraries. The custom--it's >no more than that--goes back decades (think 70s)--to the day when DASD was >extraordinarily slow and expensive. Execs are text files that contain lots of >trailing blanks. A VB data set can be edited to remove trailing blanks and >considerably reduce the space required to store execs and to perform I/O on >them. Long before MVS REXX, CLISTs were heavily used. VB reduced the overhead, >meaning that VB was more economical. > A while back, John Gilmore asserted (implausibly?) that a startling fraction of compiler cycles are spent skipping blanks. So it's not storage, nor even channel bandwidth, but CPU cycles that may now be the concern. I'd expect interpreters to suffer this more than compilers. Aren't there hardware instructions nowadays to skip blanks? (I don't count TRT; it's inefficient.) >That concern seems pretty trivial these days. But in order to convert existing >VB exec libraries to FB, *every single user* in the shop would have to convert >at the same moment because, for the all the whizzbang modernization in MVS, >data set concatenation still requires all FB or all VB in a single DD. There >would be no grace period in the cutover. Just chaos. > It's worse if the coder has used more than 80 colums. I find VB liberating. Never "Oops! I'm at the limit stop; need to figure out how to continue!" And carbon is more expensive than silicon nowadays. I thought there have long been protocols for handling concatenations with unlike attributes. But perhaps that works only for QSAM, not BPAM. >In the case of system REXX, our SYS1.PARMLIB(AXR00) names only one SYSREXX >library, so we could convert that guy to FB with minimal impact. But really, >why bother? In 2018 I still get problem calls with mysterious abends resulting >from invalid concatenation. > CMS does it right. Regardless of RECFM the programmer never sees RDWs. The data go in the programmer-supplied buffer; the length in a separate fullword. For FB80, that word is always loaded with 80. A programmer trusting the data to be FB80 may (imprudently) ignore the length word. Access methods do something similar for UNIX files: they pad records of files allocated FB with blanks unto LRECL. Excessively long records go to SYNAD. This ability ought to be extended to legacy data sets. >A practical suggestion. If your SOP exec libraries are VB, you can get around >some concatenation problems like this: > >ADDRESS ISPEXEC "SELECT CMD(EX 'SYS1.SBLSCLI0(BLSCLIBD)') MODE(FSCR)" > >This statement in a VB library invokes the real IBM-supplied FB IPCS. No >conversion or periodic updates required. Transparent to the user. > Will that user be delighted to make that code change? I'd rather put everything in UNIX directories and let the access method convert on-the-fly. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
(OK, I know my question sounded dumb, but I was afraid I was grossly misinterpreting the thread.) If I were gifted with the luxury of building a new MVS environment from scratch, I would make all REXX and CLIST libraries FB-80. For one thing, that's how virtually all vendors deliver execs. Running with concatenated VB libraries means converting delivered FB objects to VB. Not a huge burden but a task that must be performed periodically to keep up with vendor maintenance. In truth, that chore often gets overlooked--for years at a time! So what's with VB? Every 'mature' shop I've ever been in has used VB libraries. The custom--it's no more than that--goes back decades (think 70s)--to the day when DASD was extraordinarily slow and expensive. Execs are text files that contain lots of trailing blanks. A VB data set can be edited to remove trailing blanks and considerably reduce the space required to store execs and to perform I/O on them. Long before MVS REXX, CLISTs were heavily used. VB reduced the overhead, meaning that VB was more economical. That concern seems pretty trivial these days. But in order to convert existing VB exec libraries to FB, *every single user* in the shop would have to convert at the same moment because, for the all the whizzbang modernization in MVS, data set concatenation still requires all FB or all VB in a single DD. There would be no grace period in the cutover. Just chaos. In the case of system REXX, our SYS1.PARMLIB(AXR00) names only one SYSREXX library, so we could convert that guy to FB with minimal impact. But really, why bother? In 2018 I still get problem calls with mysterious abends resulting from invalid concatenation. A practical suggestion. If your SOP exec libraries are VB, you can get around some concatenation problems like this: ADDRESS ISPEXEC "SELECT CMD(EX 'SYS1.SBLSCLI0(BLSCLIBD)') MODE(FSCR)" This statement in a VB library invokes the real IBM-supplied FB IPCS. No conversion or periodic updates required. Transparent to the user. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Thursday, August 23, 2018 10:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size On 8/23/2018 9:01 AM, Jesse 1 Robinson wrote: > Could I ask what 'SYSREXX' means? At first I thought this referred simply to > the standard common set of REXX execs that users allocate at logon. Is it > something else? System REXX. AXR address space. Scott Fagen's last project before leaving IBM. Where is the real Skip Robinson and what have you done with him? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
On 8/23/2018 9:01 AM, Jesse 1 Robinson wrote: Could I ask what 'SYSREXX' means? At first I thought this referred simply to the standard common set of REXX execs that users allocate at logon. Is it something else? System REXX. AXR address space. Scott Fagen's last project before leaving IBM. Where is the real Skip Robinson and what have you done with him? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
also https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa800/systemrexx.htm Carmen Vitullo - Original Message - From: "Jesse 1 Robinson" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 11:01:47 AM Subject: Re: SYSREXX PDS size Could I ask what 'SYSREXX' means? At first I thought this referred simply to the standard common set of REXX execs that users allocate at logon. Is it something else? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, August 23, 2018 8:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size It all depends on the concatenation Start ISRDDN and see how it reacts -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, August 23, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
On Thu, 23 Aug 2018 12:05:31 -0400, Tony Thigpen wrote: >SYSREXX is rexx code that can be run by the operating system. It allows >for some automation in my shop. > Like, SYSREXX : Rexx :: MetalC : XLC? I was about to sneer, "What century is this!? What of the desigh inntegrity of OS/360!? Can't QSAM deal with it!?" But I can imagine that SYSREXX might reasonably be designed to be independent of access methods as MetalC is independent of LE. The Rexx GIM for the first release of TSO/E recommended RECFM=VB; no line numbers; mixed case for legibility. IBM immediately contravened its own recommendation in its first distributed Rexx EXECs. Bless IBM for choosing RECFM=VB; curse IBM for insisting on LRECL=255, and not merely making it an upper bound. Can I create a SYSREXX library with shorter LRECL and override at allocation to 255? Must all records be padded with blanks (or comments) to 255? I assume the 255 arises from a hard-coded input buffer. >Jesse 1 Robinson wrote on 08/23/2018 12:01 PM: >> Could I ask what 'SYSREXX' means? At first I thought this referred simply to >> the standard common set of REXX execs that users allocate at logon. Is it >> something else? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
ISRDDN would not help I don't think since system rexx is not part if TSO SYSEXEC concatenation an explanation from the fine manual :) https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa800/plsysrexx.htm Carmen Vitullo - Original Message - From: "Jesse 1 Robinson" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 11:01:47 AM Subject: Re: SYSREXX PDS size Could I ask what 'SYSREXX' means? At first I thought this referred simply to the standard common set of REXX execs that users allocate at logon. Is it something else? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, August 23, 2018 8:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size It all depends on the concatenation Start ISRDDN and see how it reacts -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, August 23, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
SYSREXX is rexx code that can be run by the operating system. It allows for some automation in my shop. Tony Thigpen Jesse 1 Robinson wrote on 08/23/2018 12:01 PM: Could I ask what 'SYSREXX' means? At first I thought this referred simply to the standard common set of REXX execs that users allocate at logon. Is it something else? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, August 23, 2018 8:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size It all depends on the concatenation Start ISRDDN and see how it reacts -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, August 23, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
Could I ask what 'SYSREXX' means? At first I thought this referred simply to the standard common set of REXX execs that users allocate at logon. Is it something else? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, August 23, 2018 8:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SYSREXX PDS size It all depends on the concatenation Start ISRDDN and see how it reacts -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, August 23, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
It all depends on the concatenation Start ISRDDN and see how it reacts -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Thursday, August 23, 2018 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYSREXX PDS size our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
our system rexx library is a library PDS-E, VB 255, I think the guy who set it up said FB 80 would not work,checking the fine manual he was correct, VB 255 is required Carmen Vitullo - Original Message - From: "Carmen Vitullo" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:53:47 AM Subject: Re: SYSREXX PDS size let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
Ours is VB 255. The only reference in Init & Tuna Reference: All data sets specified in the REXXLIB concatenation must have the same record type and record length as SYS1.SAXREXEC. The data set must either be a PDS or PDSE. Dana On Thu, 23 Aug 2018 10:42:52 -0400, Tony Thigpen wrote: >Our SYSREXX PDS is currently defined as VB 255. We had a system problem >this week that one Sysprog thinks that the the VB 255 aggravated the >problem and is insisting that we change it to FB 80. I disagree, but I >thought I would though it out to the list for views. > >Views? > >-- >Tony Thigpen > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SYSREXX PDS size
let me check, from what I recall sysrexx pds must be vb 255 :( Carmen Vitullo - Original Message - From: "Tony Thigpen" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, August 23, 2018 9:42:52 AM Subject: SYSREXX PDS size Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SYSREXX PDS size
Our SYSREXX PDS is currently defined as VB 255. We had a system problem this week that one Sysprog thinks that the the VB 255 aggravated the problem and is insisting that we change it to FB 80. I disagree, but I thought I would though it out to the list for views. Views? -- Tony Thigpen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
