> 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 <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
07/30/2009 09:29 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
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 <[email protected]> 
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" <[email protected]>
>
>Sent by: "The IBM z/VM Operating System" <[email protected]>
>07/29/2009 03:03 PM
>Please respond to
>"The IBM z/VM Operating System" <[email protected]>
>
>
>
>To
>[email protected]
>cc
>
>Subject
>Re: REXX DATE - Julian and Centry
>
>
>
>
>
>
>> -----Original Message-----
>> From: The IBM z/VM Operating System
>> [mailto:[email protected]] On Behalf Of Frank M. Ramaekers
>> Sent: Wednesday, July 29, 2009 2:47 PM
>> To: [email protected]
>> 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
>[email protected] * 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. 

Reply via email to