So does VESoft now have to pay royalties for using the
(heheheh) "patented" "date-windowing" technology? :-O

> -----Original Message-----
> From: Emerson, Tom (035) El Monte
> Subject: Re: MPEX DATE FORMATTING: Y2K ISSUE?
>
>
> Interestingly enough, VESOFTYEARBASE doesn't appear to be
> documented [still
> searching for it, however]  but I do seem to vaguely recall
> them putting in
> some sort of "quick-fix" type item.  One thing to note on
> these "quick-fix"
> things -- generally, any variable [or JCW] that "has to be
> set to alter how
> some intrinsic feature works" (*) has to be set PRIOR to
> using MPEX.  In
> this case, exit and re-enter MPEX and the test should now
> show 20000106.
>
> (*) this is a speed/efficiency issue -- rather than "look up"
> the contents
> of a SYSTEM variable for each and every evaluation, the
> variable is read
> upon startup and stored within the program.  Thus at
> execution time, the
> "lookup" is from memory rather than a system call.
>
> Tom Emerson
> Sr. Systems Analyst
> NDC | e COMMERCE
> [log in to unmask]
> 626-258-4309
> 626-350-3832 FAX
>
>
>
> > -----Original Message-----
> > From: Scott Lindholm [mailto:[log in to unmask]]
> > Subject: Re: MPEX DATE FORMATTING: Y2K ISSUE?
> >
> > Lee wrote:
> >
> >         MPEX handles two-digit dates after 12/31/99 in a
> > windowing fashion
> > -- you need
> >         to set a JCW, VESOFTYEARBASE to, say, 1950 (the
> > default is 1900) --
> > to have MPEX
> >         treat years 51-99 as 1950-1999, and years 00-49 as
> 2000-2049.
> > Lee,
> >
> > I set the jcw but I still get the same results.
> >
> > 959_sys_%showjcw vesoftyearbase
> > VESOFTYEARBASE = 1950
> > 959_sys_%set date,YMD
> > 959_sys_%SETVAR DATE TODAY + 7
> > 959_sys_%SHOWVAR DATE
> > DATE = 00/01/06
> > 959_sys_%setvar date2 strwrite(!date:'%4Y%0M%0D')
> > 959_sys_%SHOWVAR DATE2
> > DATE2 = 19000106