Wasn't there a REXXTRY available to interactively work with REXX? (Can't seem
to find it on my z/VM 5.4 system.)
Frank M. Ramaekers Jr.
Systems Programmer MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co. Phone: (254)761-6649
1200 Wooded Acres Dr. Fax: (254)741-5777
Waco, Texas 76710
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Schuh, Richard
Sent: Friday, July 31, 2009 10:24 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: REXX DATE - Julian and Centry
I am sure that if we keep trying, we can come up with some pretty bizarre
looking Rexx statements.
Regards,
Richard Schuh
> -----Original Message-----
> From: The IBM z/VM Operating System
> [mailto:ib...@listserv.uark.edu] On Behalf Of P S
> Sent: Friday, July 31, 2009 8:21 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: REXX DATE - Julian and Centry
>
> On Thu, Jul 30, 2009 at 10:30 PM, Bob
> Woodside<ibm...@woodsway.com> wrote:
> > Oh, my. Well, if we must explore it fully, I have to excerpt a
> > snippet from a Rexx course I recently taught, illustrating
> how the use
> > of "not quite reserved" keywords as variable names *can*
> trip you up.
> > It typically happens when one is dynamically building a
> string to be
> > interpreted.
>
> Beat me to it, I saw this after tinkering with:
>
> /**/
> if = 1
> then = 'TYPE PROFILE EXEC A 1 1'
> if if then then
>
> which doesn't quite work, but this does:
>
> /**/
> if = 1
> then = 'TYPE PROFILE EXEC A 1 1'
> if if then (then)
>
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
privacy...@ailife.com.
