1. That's the text that started this discussion. It doesn't explain why,
after what has already been written here, you believe it.
2. Quoting the text again doesn't answer the question "What does that mean?".
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe
Monk [joemon...@gmail.com]
Sent: Thursday, June 4, 2020 9:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: What is GRXBIMG
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ikja300/tsorun.htm
"You can invoke a REXX exec in the TSO/E address space in several ways. To
invoke an exec in TSO/E foreground, use the TSO/E EXEC command processor to
either implicitly or explicitly invoke the exec and you must have ddname
GRXBIMG allocated."
Joe
On Thu, Jun 4, 2020 at 7:54 AM Seymour J Metz <sme...@gmu.edu> wrote:
> What does that mean and why do you say so? It's not a DD that you need to
> use REXX in TSO, because IKJEFT01 works fine without it. It's not SYSPROC
> or SYSECEC, which would make sense. And it has a prefix not associated with
> REXX or any other z/OS component.
>
> If it were indeed a DD statement that the authors believed to be necessary
> to run REXX in TSO, wouldn't they have explained what to code on it or at
> least used it in sample JCL?
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ________________________________________
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Joe Monk [joemon...@gmail.com]
> Sent: Thursday, June 4, 2020 8:46 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: What is GRXBIMG
>
> Its some REXX DD that has to be allocated before you can run in TSO.
>
> Joe
>
> On Thu, Jun 4, 2020 at 7:25 AM Seymour J Metz <sme...@gmu.edu> wrote:
>
> > Idle speculation: it's the file name of s bit map meant to go into the
> > manual and the text was supposed to say SYSPROC.
> >
> >
> > --
> > Shmuel (Seymour J.) Metz
> > http://mason.gmu.edu/~smetz3
> >
> > ________________________________________
> > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> > of Charles Mills [charl...@mcn.org]
> > Sent: Wednesday, June 3, 2020 6:36 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: What is GRXBIMG
> >
> > A more interesting question might be "what happens if I do allocate it?"
> > and at least for a simple test with ALLOC FI(GRXBIMG) DA(*) the answer
> > seems to be "nothing special."
> >
> > What might this be a relic of? GRX does not seem to be a component
> prefix.
> > I could be wrong.
> >
> > Here's my theory: a developer whose initials were GR added some sort of
> > debug output: GRXBIMG = George Rothwell's Extended Byte Image or
> something
> > like that. It somehow made it into the product documentation. Astounding
> > that it has hidden there in plain sight for over twenty years.
> >
> > I do not see the reference in the 1991 MVS/REXX Reference:
> >
> >
> http://secure-web.cisco.com/1msRUVNTCVPM6al9HyShyRDCsU6ONoAtBXbZbF7GJI59Gj89EEVWxcw_sygtcmoro-Imjk1U0ivgPs56TezTZL7Ba2WK1xNb6Yt-8QhSSHtfKcjpi4120Lk2HeTC2GP_IBVSjpDZ2aER63S8t_e86YAeMWGEkxm-0kO-Skka5_F7n-9WQmSxHedXSSqNjPMCsTlIWQCC56yaSIKzebhds42QUBcHC9zlx-UMb5yTFa2oIWvz0WrXbUGm2BF2bLLjlEhdCanddWLM-oXiVALYstYbU2hWeGN7BMRxMcJFPaMNmBxidchg_eoJCTNNqeCY_q74Di2uFtY4YQx2Y89PNJ8tAou1-jxWUZ1teZbByjfqzH8hUIH2VQUbpBvenpMTw1T4CneetfQe7qvCqp5o2OSE52nYpPrr4XGXLb1VNGnwTSrzLKz3fW4A6bNBpdw-r/http%3A%2F%2Fwww.bitsavers.org%2Fpdf%2Fibm%2F370%2FTSO_Extensions%2FSC28-1883-4_TSO_Extensions_Version_2_Procedures_Langage_MVS_REXX_Reference_Aug1991.pdf
> >
> > Charles
> >
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of Paul Gilmartin
> > Sent: Wednesday, June 3, 2020 9:16 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: What is GRXBIMG
> >
> > On Wed, 3 Jun 2020 07:00:19 -0700, Charles Mills wrote:
> >
> > >I must have time on my hands. I just dragged out the OS/390 V2R8 CDs
> from
> > 1999, and the sentence is there verbatim.
> > >
> > >It's the only hit on GRXBIMG on CD #1.
> > >
> > >-----Original Message-----
> > >From: Steve Smith
> > >Sent: Wednesday, June 3, 2020 6:37 AM
> > >
> > >It's still there in V2R4... and I am appalled that I've been running
> REXX
> > >incorrectly for decades now.
> > >
> > I submitted a (slightly snarky) RCF on this:
> >
> > Hello, MHVRCFs,
> >
> > In:
> >
> https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ikja300/tsorun.htm
> > • /OS 2.2.0
> > • z/OS TSO/E
> > • z/OS TSO/E REXX Reference
> > • Using REXX in different address spaces
> >
> > I read: "... you must have ddname GRXBIMG allocated."
> >
> > I'm curious. Does:
> > //GRXBIMG DD DUMMY
> > suffice, or must it be a PDS(E)?
> >
> > What error is reported if the programmer fails to
> > allocate GRXBIMG?
> >
> > Is this covered in M&C?
> >
> > Thanks,
> > 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
> >
> > ----------------------------------------------------------------------
> > 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
