Jump to content
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

Transition Impacts

HP-UX Software Transition Kit
» 

DSPP Home

» HP STK home
HP-UX STK
» Home
» Overview
» Tools
» Documentation
» Transition impacts
» Identifier types
» Impact list
» Qualifying on HP-UX
» Porting to HP-UX
» FAQ
» Glossary
» Help
» Send us feedback
Site maps
» HP-UX STK
» DSPP
Content starts here

date impacts summary

 

Date Impacts Summary

Now that the Year 2000 transition has passed, it is important to continue to handle dates properly in software development. Other date transitions are coming. Software which was quickly patched to survive the Year 2000 transition should be properly repaired. And software shelved during the transition time and later brought back to development may still need to be scanned for problems.

To help you locate date-related problems in your software, the STK may include the following types of impacts:

  • Impacts for APIs that are date-related. These interfaces indicate that the software is performing date processing, which could cause date-related problems:
    • For C and C++, asctime, ctime, daylight, difftime, ftime, gettimeofday, gmtime, localtime, mktime, settimeofday, stime, strftime, time, time_t, timeb, timeval, timezone, tm, tzname, tzset, execl, execlp, execve, execle, execv, execvp, popen, system
    • For Fortran, CTIME, FDATE, DATE_AND_TIME, IDATE, GMTIME, LTIME, TIME
    • For COBOL, CURRENT-DATE, DATE-OF-INTEGER, WHEN-COMPILED, INTEGER-OF-DATE, INTEGER-OF-DAY, DAY-OF-WEEK

Many of the Date impacts are warnings, so you miss seeing them if you exclude Non-critical (Nc) or Non-critical Warning (NcWn) impacts from your scans.

In addition to the date-related impacts described above, check your software for other common causes of date-related problems:

  • Less than four digits used to represent years. Applications that store only the last two digits of the year may not function correctly for dates on or after the year 2000. For example, if dates are compared as strings, 01/01/2000 appears as 01/01/00, which is less than 12/31/99.
  • Existing dates (such as 9/9/99) used as meta-values to represent information such as an expired or invalid date.
  • Date representations that have a limited range of valid values. For example, the representation used by the C/C++ type time_t is only valid from 1901 to 2038.

The minimum date supported by both 32-bit and 64-bit HP-UX 11.x is 1901/12/13 20:45:52 UTC. The maximum date supported by 32-bit HP-UX 11.x is 2038/01/19 03:14:07 UTC, and the maximum date supported by the 64-bit application development environment is 9999/03/02 06:00:00 UTC. A 4-digit year must be used with getdate for dates beyond the 21st century.

Note: To include only Date impacts when running the scansummary and scandetail tools, use the option:
  +C DA
To exclude these impacts, use the option:
  -C DA
For more information on filtering output in reports, see Customizing Your Scan.

 

For more information

 
» List of Date impacts
Printable version
Privacy statement Using this site means you accept its terms Feedback to DSPP
© 2007 Hewlett-Packard Development Company, L.P.