HP3000-L Archives

June 1996, 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:
Dean Lavoie <[log in to unmask]>
Reply To:
Date:
Mon, 17 Jun 1996 03:25:00 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
Problem: ALLBASE/SQL upgrade from G1.11 to G1.15. causing the following
         error in our COBOL programs that convert the date/time value:
 
         'Date time value does not match default format'
 
         G1.15 uses a new Explicit Data Type Conversion (CAST) statement that
         uses a new Date/Time API. The upgrade was done by installing the
         patch SQLHXW0A and SQLHXM2B.
 
         Our COBOL programs do not do any unstandard or unusual DateTime
         manipulations. HP had several suggestion's, none which worked. I
         finally had to backout the upgrade off the system. The first time in
         seven years as a system's administrator that I had to  roll back an
         upgrade. Under G1.11 the COBOL programs work fine.
 
Request/Alert:
         Has any one else upgraded to ALLBASE/SQL G1.15 who use COBOL program
         and run in to a similar problem? HP was not sure, if any, how many
         COBOL shops were on this version. Does any one have a suggestion on
         what to try? We no longer have the version G1.15 on a system to test.
 
         Be warned, if you are considering this upgrade you may want to move
         ahead cautiously. HP original indicated the changes in the version were
         minima and would cause no problems. I believe G1.15 is part of Power
         Patch 5 due out June 21.
 
Here are some additional findings:
 
1)  The program failures occurred when an Insert/upgrade was attempted on a
    table with 3 DateTime columns.  Two of the columns default to the system
    generated current DateTime value.  The other column has an application
    generated DateTime value.
 
2)  We changed all 3 columns to default to the Current DateTime value.
    The program received the same error as in #1 above.
 
3)  HP sent us some COBOL code suggestions.  We tried these and
    they did not work.  HP said the Cobol programs must be modified to
    access a C subroutine that calls the API named CDBTODATE. This
    statement surprised us all, we were refused to code a 'C' module
    in order to get our COBOL programs working, when they worked fine
    on G1.11. There was no guarantee this subroutine would fix our problem.
 
4)  We do not get the error when we attempt to Insert thru ISQL.
    This suggests that there is a problem in the Cobol Precompiler.
 
5)  The error message refers to a "Date" problem not a "DateTime"
     problem, but there are no "Date" type columns in the table.
 
6)  HP informed us that there were no G1.15 version release notes
    available.  The only thing that was found was a write up on the
    CAST statements version.

ATOM RSS1 RSS2