[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference evms::y2k

Title:OpenVMS Year 2000
Moderator:EVMS::MARIONN
Created:Mon Aug 26 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:82
Total number of notes:427

65.0. "ANSI TApe labels - handled properly?" by KAPTIN::BLEI (Larry Bleiweiss 237-6080 SHR3-2/X17) Wed Apr 02 1997 13:24

Just a note to request a reply if anyone is working on ANSI Tape labels for Y2K.

The label has a six character date field. The first character of which specify's
the most significant two digits of the year, i.e.- SPACE for 19 and 0 for 20.

Does anyone know if VMS and UNIX handle this properly?

Thanks
T.RTitleUserPersonal
Name		DateLines
65.1Fixed Ten Years Ago...XDELTA::HOFFMANSteve, OpenVMS EngineeringWed Apr 02 1997 14:358
    See 38.1 for OpenVMS -- the magtape ACP was checked -- the ANSI
    tape label changes are already present in OpenVMS.  (This zero
    in the first position -- rather than a space -- fix was added to
    OpenVMS back on 18-Dec-1986.)

    As for UNIX, you'll want to check with the UNIX engineers.
65.2Fixed, but that doesn't stop calls being loggedGIDDAY::GILLINGSa crucible of informative mistakesWed Apr 02 1997 22:4336
  re .1:

    I had a customer report a tape error while performing Y2K testing.
  Unfortunately I can't find the call notes, but, from memory, the scenario
  was attempting to re INITIALIZE a tape after year 2000 yielded a FILNOTEXP
  error. I have failed to reproduce this on OpenVMS/Alpha V6.2 and OpenVMS/VAX
  V5.5-2H4 today, and I now suspect the customer was trying to re init a tape
  which he had initialized while the clock was past 2000 after setting the
  time back.

$ init MUA0: y2ktst
$ set time="+2000-0"
$ show time
  24-SEP-2002 12:30:47
$ init MUA0: y2ktst
$ set time="-2000-0"
$ show time
   3-APR-1997 12:31:17
$ init MUA0: y2ktst
%INIT-F-FILNOTEXP, file is not expired	! This is correct since the expiry
$					! date is in the future
$ init/override=expiration MUA0: y2ktst
$

  When a tape is initialized, the system first checks for an expiry date
  in any existing header. If there is none, or that time is past, the new
  expiry date is set to the current time. Otherwise a FILNOTEXP error is
  issued.

  So, if the INIT command were not Y2K compliant, an expiry date in 1997 
  could be interpreted as 2097 after 2000 and hence an incorrect FILNOTEXP
  error be issued. My testing shows that this DOES NOT happen. However, even
  if it did, the condition is trivial to workaround using the
  /OVERRIDE=EXPIRATION qualifier as shown above.

						John Gillings, Sydney CSC