Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp

more options
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content

» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping

Find Support Information and Customer Communities for Presario.
Content starts here
DATATRIEVE DTRVAXECO02072 V7.2 for OpenVMS VAX Systems ECO Summary
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.

Modification Date:  09-AUG-1999
Modification Type:  Updated applicable OpenVMS VAX versions.

PRODUCT:    DEC Datatrieve V7.2 for OpenVMS VAX Systems


COMPONENT:  Report Writer

SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  DTRVAXECO02072
     ECO Kits Superseded by This ECO Kit:  DTRVAXECO01072     
     ECO Kit Approximate Size:  4284 Blocks
     Kit Applies To:  DEC Datatrieve V7.2 for OpenVMS VAX Systems
                      OpenVMS VAX V6.2 and higher
     Rolling Re-boot Supported:  Not Known

     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:


       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:



An ECO kit exists for DEC Datatrieve V7.2 for OpenVMS VAX Systems
on OpenVMS VAX V6.2 and higher.  This kit addresses the following

Problems Addressed in DTRVAXECO02072

  o  The logical DTR$DATE_INPUT did not handle four digit years correctly.
     For example, if the logical was set to "MDY" and a date string was
     input in the following format - 12311999 - a conversion error was
     reported. This problem has now been fixed, and the correct date 
     (i.e. 31-DEC-1999 in the example) will be returned.

  o  DTR supports several formats of date field on its forms. These
     include 2-digit and 4-digit year date formats. DTR validates date
     fields and translates all date fields formats into the standard
     OpenVMS binary date format which is then passed to the application.

     In order to successfully translate 2-digit year date fields into 
     their corresponding binary format, DTR has to supply the missing 2 
     digits of the year (i.e. the century digits). DTR has always used the
     century digits as specified by the system clock. This is entirely
     consistent with the way that incompletely specified dates are
     interpreted in OpenVMS.

     At the turn of the century, the behavior of DTR as described above
     will mean that 2-digit year dates from the screen will be interpreted
     differently. All 2-digit year dates will be processed as being in 
     the 21st century, exactly 100 years later than previously.

     DTR now uses a so-called sliding window capability for the translation 
     of DTR 2-digit year dates.

     This enhancement will allow for the modification of the behavior of
     DTR so that the century digits applied to a 2-digit year date may be
     based on a customer specified value.

     On each occasion DTR is required to expand a 2-digit year date it
     will attempt to translate a logical name called DTR$BASE_YEAR. Valid
     values for this logical name are 4-digit numbers in the range 1859 
     - 9900. DTR will search the PROCESS table followed by the GROUP 
     table and finally the SYSTEM table and will use the first valid value 
     found.  If no valid translation of the DTR$BASE_YEAR logical is found 
     then the behavior of DTR in processing 2-digit year dates will remain
     exactly as in the current version of DTR.

     This 4-digit number resulting from a valid translation of the
     DTR$BASE_YEAR logical name is used by DTR to define the first year
     of a 100 year window in which all 2-digit year dates fall. For
     example a value of 1980 defines a 100 year date window of 01-JAN-1980
     to 31-DEC-2079.

     Customers who wish to have DTR continue to translate 2-digit year
     dates in the 20th century should set the DTR$BASE_YEAR logical to
     the value 1900 while customers who wish to have DTR behave exactly 
     as before should not define the logical name.

Problems Addressed in DTRVAXECO01072

  o  This kit fixes a problem in the Report Writer. When the 
     AT TOP OF REPORT clause was executed, no output for the 
     desired literal occurred.


The images in this kit will not take effect until the system is
rebooted.  If there are other nodes in the VMScluster, they must 
also be rebooted in order to make use of the new image(s).  

All trademarks are the property of their respective owners.

Files on this server are as follows:
privacy statement using this site means you accept its terms