HP3000-L Archives

October 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Renz <[log in to unmask]>
Reply To:
Date:
Fri, 16 Oct 1998 14:52:31 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Listers,

I've searched high and low and either I misplaced the info regarding Y2K
windowing using the View intrinsics.  I'm familiar with the VSETNEXTCENTURY
jcw and setting bits 15 & 14 to control View's functionality.  When bit 14
is set on it uses the value of "50" to determine what to set the century.
When it is off what is the value or is one implied?  If we want to override
the window value to some other is there a jcw or var that sets the new
window value?  Is there another View jcw or does the code revert to using
the new HPSPLITYEAR var.

On another topic, it would be nice if this was available and usage of the
HPSPLITYEAR single point var would reduce the number of items that need to
be added in logon udc's to support Y2K on the HP3000.  As I go deeper and
deeper in the Y2K changes I have noticed that multiple vendors have their
own windowing value and their own jcws/vars that need to be set or settings
in the programs.  I have run across values of "50", "49", "10" and so on
for windowing values where the product will assume where the century will
begin/end.  Is there a document somewhere that lists all of the vendor's
window default values, any jcw/var values that need set, etc. so that a
system manager can prepare and set up their system to be consistent across
all software solutions?  For the vendors, Why not use one variable to
establish the windowing point, like HPSPLITYEAR?

Thanks!!

tom renz

ATOM RSS1 RSS2