PowerHouse 7.10G on OVMS 7.2

[csysprog@taipan.admin.bhtafe.edu.au]

Dear all,

  I can't comment on version 710G2 as I haven't seen it yet.  We have just 
completed a series of Y2k compliance tests for Powerhouse version 710G1 on both 
VAX and Alpha. We use Oracle Rdb (Rdb version 7.0-11, OpenVMS v7.1). We store 
dates as YYYYMMDD integer numbers.

  The tests went well and version 710G1 appears fully compliant. Our tests 
included moving the system date forward into the year 2000 and testing:
  * date entry (various),
  * general data entry,
  * reporting,
  * year split between 19th and 20th century using DDMMMYY as set in the 710G1   
    dictionary,
  * batch processing,
  * running, date entry etc for year 2000 leap year day,
  * recompiling in year 2000.

  We will sign off to the central organisation to which we report.  This raises 
the questions - 

  *If version 710G2 is released, do we assume it is as compliant as the version  
   just tested?

  *What about patches etc. for the other layered products associated with our    
   overall implementation here?

We are also testing Finance, Payroll etc in a similar manner. Each has its own 
set of non VAX, non Powerhouse, non Rdb software (yeah, I know, why don't we 
limit the number of systems in use - well it's not my fault!). Each of these is 
accumulating patches - one for SQL server arrived while we were testing our 
Payroll system.

I think we will use the general strategy of limiting ourselves to essential 
upgrades/patches and performing a small suite of tests after each upgrade/patch 
without setting the system date forward to the year 2000.

I'll be watching for other comments or feedback on the issue of ongoing testing 
for compliance.

John Hogan,
Box Hill Institute,
Melbourne. Australia.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.