That solution is ugly. It is better to avoid using keywords as variable names 
regardless of whether you can do it. You can disembowel yourself, too, but it 
would not be advisable.

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers
> Sent: Thursday, July 30, 2009 10:39 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: REXX DATE - Julian and Centry
> 
> I don't think that any of the Rexx functions commands are 
> reserved, but you have to be careful if you use any of them.  
> For instance:
> 
> When=Date('B')-1
> 
> Will cause problems for the following
> 
> Select
>   When g=1 then
>      nop
>   Otherwise
>     nop
> End
> 
> To fix this, you have to put the keywords within quotes 
> (apostrophes) to prevent substitution:
> 
> Select
>   'When' g=1 then
>      nop
>   Otherwise
>     nop
> End
> 
> 
> 
> 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 Mike Walter
> Sent: Thursday, July 30, 2009 11:11 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: REXX DATE - Julian and Centry
> 
> Ah... part of a Select/When/End statement.  Completely 
> slipped my mind. 
> Yep... it's a reserved keyword. 
> 
> And I agree.  I don't think that I've ever used it as a 
> variable in actual code, just that example.  I'll change my 
> copy of the example.
> 
> You are correct, and I do avoid using reserved keywords.  
> This one was an aberration.  Thanks for pointing it out so 
> that everyone benefits.
> 
> Mike Walter
> Hewitt Associates
> Any opinions expressed herein are mine alone and do not 
> necessarily represent the opinions or policies of Hewitt Associates.
> 
> 
> 
> 
> 
> Brian Nielsen <bniel...@sco.idaho.gov> 
> 
> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
> 07/30/2009 10:32 AM
> Please respond to
> "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
> 
> 
> 
> To
> IBMVM@LISTSERV.UARK.EDU
> cc
> 
> Subject
> Re: REXX DATE - Julian and Centry
> 
> 
> 
> 
> 
> 
> 'when' is used as a variable in:
> 
>    when=date('B')-1
> 
> Brian Nielsen
> 
> On Thu, 30 Jul 2009 10:27:54 -0500, Mike Walter 
> <mike.wal...@hewitt.com>
> 
> wrote:
> 
> >> I hate to see a keyword used as a variable name
> >
> >I must be blind today... which rexx keyword is being used as 
> a variable
> >name in the following posts?
> >
> >Mike Walter
> >Hewitt Associates
> >Any opinions expressed herein are mine alone and do not necessarily
> >represent the opinions or policies of Hewitt Associates.
> >
> >
> >
> >
> >Brian Nielsen <bniel...@sco.idaho.gov>
> >
> >Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
> >07/30/2009 09:29 AM
> >Please respond to
> >"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
> >
> >
> >
> >To
> >IBMVM@LISTSERV.UARK.EDU
> >cc
> >
> >Subject
> >Re: REXX DATE - Julian and Centry
> >
> >
> >
> >
> >
> >
> ><wince>
> >
> >While legal, I hate to see a keyword used as a variable name.
> >
> ></wince>
> >
> >Brian Nielsen
> >
> >
> >On Wed, 29 Jul 2009 15:13:44 -0500, Mike Walter
> <mike.wal...@hewitt.com>
> >wrote:
> >
> >>To add to John's suggestions, a slightly different flavor:
> >>
> >>when=date('B')-1                              /* Yesterday       */
> >>prevjdate=left(date('O',when,'B'),2)||right(date('D',when,'B'),3,0)
> >>
> >>when=date('B')+1                              /* Tomorrow       */
> >>nextjdate=left(date('O',when,'B'),2)||right(date('D',when,'B'),3,0)
> >>
> >>Executive summary:  when performing date math, rexx's 
> "Base" date can
> be
> >>your friend.
> >>
> >>Mike Walter
> >>Hewitt Associates
> >>Any opinions expressed herein are mine alone and do not necessarily
> >>represent the opinions or policies of Hewitt Associates.
> >>
> >>
> >>
> >>"McKown, John" <jmck...@healthmarkets.com>
> >>
> >>Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
> >>07/29/2009 03:03 PM
> >>Please respond to
> >>"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
> >>
> >>
> >>
> >>To
> >>IBMVM@LISTSERV.UARK.EDU
> >>cc
> >>
> >>Subject
> >>Re: REXX DATE - Julian and Centry
> >>
> >>
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: The IBM z/VM Operating System
> >>> [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers
> >>> Sent: Wednesday, July 29, 2009 2:47 PM
> >>> To: IBMVM@LISTSERV.UARK.EDU
> >>> Subject: REXX DATE - Julian and Centry
> >>>
> >>> I don't understand why there is the following restriction on
> >>> the Date()
> >>> function:
> >>>
> >>> NOTE:
> >>>
> >>> (1)  If the Century or Julian format is specified, then no
> >>> other options
> >>>
> >>>      are permitted. These two formats are provided for 
> compatibility
> >>> with
> >>>      programs written for releases prior to VM/ESA(R) version
> >>> 2 release
> >>>
> >>>      1.1. It is recommended that they not be used for new 
> programs.
> >>>
> >>>
> >>> There are still some programs/systems that use Julian.  For
> instance,
> >>> EREP requires DATE input in Julian.
> >>>
> >>> Having said that, how can I compute a day 90 days in the
> >>> past, specified
> >>> in Julian (in REXX)?
> >>>
> >>> Frank M. Ramaekers Jr.
> >>
> >>/* REXX */
> >>TODAY1 = DATE('B')
> >>MINUS90 = TODAY1 - 90
> >>DDD = DATE('D',MINUS90,'B') /* DAY IN YEAR */
> >>YY=LEFT(DATE('O',MINUS90,'B'),2)
> >>YYDDD=YY||DDD
> >>
> >>--
> >>John McKown
> >>Systems Engineer IV
> >>IT
> >>
> >>Administrative Services Group
> >>
> >>HealthMarkets(r)
> >>
> >>9151 Boulevard 26 * N. Richland Hills * TX 76010
> >>(817) 255-3225 phone * (817)-961-6183 cell
> >>john.mck...@healthmarkets.com * www.HealthMarkets.com
> >>
> >>Confidentiality Notice: This e-mail message may contain confidential
> or
> >>proprietary information. If you are not the intended 
> recipient, please
> >>contact the sender by reply e-mail and destroy all copies of the 
> original
> >>message. HealthMarkets(r) is the brand name for products 
> underwritten 
> and
> >>issued by the insurance subsidiaries of HealthMarkets, Inc. -The
> >>Chesapeake Life Insurance Company(r), Mid-West National 
> Life Insurance
> >>Company of TennesseeSM and The MEGA Life and Health Insurance
> Company.SM
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>The information contained in this e-mail and any accompanying
> documents
> >may contain information that is confidential or otherwise protected
> from
> >disclosure. If you are not the intended recipient of this message, or
> if
> >this message has been addressed to you in error, please immediately
> alert
> >the sender by reply e-mail and then delete this message, 
> including any
> >attachments. Any dissemination, distribution or other use of the
> contents
> >of this message by anyone other than the intended recipient 
> is strictly
> >prohibited. All messages sent to and from this e-mail address may be
> >monitored as permitted by applicable law and regulations to ensure
> >compliance with our internal policies and to protect our business. 
> E-mails
> >
> >are not secure and cannot be guaranteed to be error free as 
> they can be
> >intercepted, amended, lost or destroyed, or contain viruses. You are
> >deemed to have accepted these risks if you communicate with us by
> e-mail.
> >>============================================================
> ==========
> ===
> >
> >
> >
> >
> >
> >
> >The information contained in this e-mail and any 
> accompanying documents
> 
> may contain information that is confidential or otherwise 
> protected from
> 
> disclosure. If you are not the intended recipient of this 
> message, or if
> 
> this message has been addressed to you in error, please immediately
> alert 
> the sender by reply e-mail and then delete this message, 
> including any 
> attachments. Any dissemination, distribution or other use of the
> contents 
> of this message by anyone other than the intended recipient 
> is strictly 
> prohibited. All messages sent to and from this e-mail address may be 
> monitored as permitted by applicable law and regulations to ensure 
> compliance with our internal policies and to protect our business.
> E-mails 
> 
> are not secure and cannot be guaranteed to be error free as 
> they can be 
> intercepted, amended, lost or destroyed, or contain viruses. You are 
> deemed to have accepted these risks if you communicate with us by
> e-mail.
> >=============================================================
> ==========
> ==
> 
> 
> 
> 
> 
> 
> The information contained in this e-mail and any accompanying 
> documents
> may contain information that is confidential or otherwise 
> protected from
> disclosure. If you are not the intended recipient of this 
> message, or if
> this message has been addressed to you in error, please immediately
> alert the sender by reply e-mail and then delete this 
> message, including
> any attachments. Any dissemination, distribution or other use of the
> contents of this message by anyone other than the intended 
> recipient is
> strictly prohibited. All messages sent to and from this e-mail address
> may be monitored as permitted by applicable law and regulations to
> ensure compliance with our internal policies and to protect our
> business. E-mails are not secure and cannot be guaranteed to be error
> free as they can be intercepted, amended, lost or destroyed, 
> or contain
> viruses. You are deemed to have accepted these risks if you 
> communicate
> with us by e-mail. 
> 
> _____________________________________________________ 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.
> 

Reply via email to