It sure would be nice if we had a bit in the VENVCNTL.PUB.SYS file to
control the next century interpretation.
This way we could control it globally without UDC's to set the variable.

John Zoltak
North American Mfg Co

> -----Original Message-----
> From: Keven Miller [SMTP:[log in to unmask]]
> Sent: Friday, February 13, 1998 3:39 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] Feb 29 '00 and VPlus
>
> In my Communicator 3000  MPE/iX express 3 PowerPatch Tape C.55.03
> manaul
> (Does this imply that you need to be on MPE/iX 5.5pp3?)
>
> Page 4-28 (in middle of VPLUS discussion)
>
> Existing 2-digit years can be interpreted differently to handle dates
> in
> the next century.
> Currenlt VPLUS handle year components 00-99 as 1900-1999. This scheme
> of interpretation can be changed. In the new scheme, 00-49 is
> interpreted as
> 2000-2049 and 50-99 is interpreted as 1950-1999. This interpretation
> will be valid
> through all processing done by VPLUS. For example, this scheme will
> allow the user
> to enter 02/29/00 (MDY order) in an existing application and have it
> processed correctly.
>
> To invoke the above method of date interpretation, define a JCW called
> VSETNEXTCENTURY
> and set bit 14 to 1.... This means that 12/11/10 (MDY order) can refer
> to 1910 in one app
> and 2010 in another app.
>
>
> There is a setting for bit 15 to format 4 year dates if the field
> space
> is available.
> See the communicator.
>
> *********************
> * Keven Miller   KC7LYD
> * [log in to unmask]   (Salt Lake City, Utah, USA)
> * ICQ 5721825
> *********************