Problem with dates. -Reply -Reply
Deskin, Bob
Bob.Deskin@Cognos.COM
Thu, 4 Jun 1998 11:32:11 -0400
I notice that the date is a sub-item. I assume (always dangerous) that
the original definition was:
RECAP-LKUP CHARACTER 12
. CUST-ID CHARACTER 6
. TXN-DATE ZONED UNSIGNED 6
How was the date expanded from 6 to 8? If the others are okay, then was
something different done with this file. If the value in the item is
199805, then I'm not surprised you get crosshatches. That's what
displays with invalid data. Was the value in the item 19980500 or
00199805?
Bob Deskin
Senior Product Advisor bob.deskin@cognos.com
Cognos Inc. (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
> ----------
> From: COLIN GLASS[SMTP:cglass@mlcc.mb.ca]
> Sent: Thursday, June 04, 1998 12:10 PM
> To: Bob.Deskin@Cognos.COM; powerh-l@lists.swau.edu
> Cc: cgingera@mlcc.mb.ca; kbraun@mlcc.mb.ca
> Subject: RE: Problem with dates. -Reply -Reply
>
> We have tried all of the PowerHouse techniques, including the one
> mentioned below, and came up with the same problems. We used MPE's
> Query function, and found that the date portion of the field was
> truncated
> (eg. 199805 instead of 19980515).
>
> We converted the data from 6 to 8 digit dates in February, but all
> dates
> before that time are OK (all reloaded dates are OK). Any record
> processed
> after the implementation are a problem.
>
> Here is the PowerHouse element definition:
> Element: TXN-DATE
> Type: Date with Century Included
> Item Defaults: INTEGER-S Size 4
>
> Initial Value: 1901/01/01
> Date Picture: YYYY/MM/DD
>
> Here is the related PowerHouse file definitions:
> > SHOW REC D-HST-HDR
> 1998/06/04 PERMITS SYSTEM Page
> 1
> R E C O R D R E P O R T
> For DICTIONARY: phd
> Record: D-HST-HDR
> of File: PTNDDB
> Organization: DETAIL
> Type: TURBOIMAGE
> Open: D-HST-HDR of PTNDDB
> Description:
> ADDITIONAL FEE HEADER HISTORY FILE
> THIS FILE CONAINS THE TOTAL ADDITIONAL FEES
> CALCULATED FROM THE DETAILS FOR EACH PERMIT
> BY CUSTOMER ID.
> Record Size: 66 Bytes
>
> -- Record Contents --
> Item Type Size Occ
> Offset
> RECAP-LKUP CHARACTER 14
> 0
> .CUST-ID CHARACTER 6
> 0
> .TXN-DATE ZONED UNSIGNED 8
> 6
>
> > SHOW REC D-ADD-HDR
> 1998/06/04 PERMITS SYSTEM Page
> 1
> R E C O R D R E P O R T
> For DICTIONARY: phd
> Record: D-ADD-HDR
> of File: PTNDDB
> Organization: DETAIL
> Type: TURBOIMAGE
> Open: D-ADD-HDR of PTNDDB
> Description:
> ADDITIONAL FEE HEADER FILE
> THIS FILE CONAINS THE TOTAL ADDITIONAL FEES
> CALCULATED FROM THE DETAILS FOR EACH PERMIT
> BY CUSTOMER ID.
> Record Size: 66 Bytes
>
> -- Record Contents --
> Item Type Size Occ
> Offset
> RECAP-LKUP CHARACTER 14
> 0
> .CUST-ID CHARACTER 6
> 0
> .TXN-DATE ZONED UNSIGNED 8
> 6
>
>
>
> > SHOW REC A-TXN-LKUP
> 1998/06/04 PERMITS SYSTEM Page
> 1
> R E C O R D R E P O R T
> For DICTIONARY: phd
> Record: A-TXN-LKUP
> of File: PTNDDB
> Organization: AUTOMATIC
> Type: TURBOIMAGE
> Open: A-TXN-LKUP of PTNDDB
> Description:
> PERMIT FEE LKUP FILE
> THIS FILE PROVIDES AN ENTRY POINT TO THE FEE
> TRANSACTIONS
> BY CUSTOMER IDENTIFICATION IE.
> STORE/VENDOR/LICENSEE #
> Record Size: 14 Bytes
>
> -- Record Contents --
> Item Type Size Occ
> Offset
> RECAP-LKUP CHARACTER 14
> 0
> .CUST-ID CHARACTER 6
> 0
> ..CUST-TYPE CHARACTER 1
> 0
> ..CUST-NMBR ZONED UNSIGNED 5
> 1
> .TXN-DATE ZONED UNSIGNED 8
> 6
>
>
>
> > SHOW REC A-HST-LKUP
> 1998/06/04 PERMITS SYSTEM Page
> 1
> R E C O R D R E P O R T
> For DICTIONARY: phd
> Record: A-HST-LKUP
> of File: PTNDDB
> Organization: AUTOMATIC
> Type: TURBOIMAGE
> Open: A-HST-LKUP of PTNDDB
> Description:
> ADDITIONAL FEE HISTORY LOOKUP
> THIS FILE PROVIDES AN ENTRY POINT TO THE FEE
> TRANSACTIONS
> BY CUSTOMER IDENTIFICATION IE.
> STORE/VENDOR/LICENSEE #
> Record Size: 14 Bytes
>
> -- Record Contents --
> Item Type Size Occ
> Offset
> RECAP-LKUP CHARACTER 14
> 0
> .CUST-ID CHARACTER 6
> 0
> ..CUST-TYPE CHARACTER 1
> 0
> ..CUST-NMBR ZONED UNSIGNED 5
> 1
> .TXN-DATE ZONED UNSIGNED 8
> 6
>
> The problem file is D-HST-HDR. All of the other ones are showing
> proper
> dates.
>
>
> >>> "Deskin, Bob" <Bob.Deskin@Cognos.COM> 06/04/98 08:44am >>>
> The best way to check the value of a date is to use a DEFINE to equate
> it to a numeric item and then display the numeric with 8 digits. This
> way you don't get any interferance from the default century or the
> date
> format.
>
> Bob Deskin
> Senior Product Advisor bob.deskin@cognos.com
> Cognos Inc. (613) 738-1338 ext 4205 FAX: (613) 228-3149
> 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9
> CANADA
>
> > ----------
> > From: COLIN GLASS[SMTP:cglass@mlcc.mb.ca]
> > Sent: Thursday, June 04, 1998 11:22 AM
> > To: Bob.Deskin@Cognos.COM; powerh-l@lists.swau.edu
> > Cc: cgingera@mlcc.mb.ca; kbraun@mlcc.mb.ca
> > Subject: RE: Problem with dates. -Reply
> >
> > I get this value when I do an ad hoc Quiz on the file. What I
> failed
> > to
> > mention is when I do an ad hoc Quick screen, the last two digits of
> > the date
> > are truncated.
> >
> > >>> "Deskin, Bob" <Bob.Deskin@Cognos.COM> 06/04/98 08:19am >>>
> > When you say ######## exactly what do you mean. Is this a display
> > value
> > or the actual value on file? How did you determine the value?
> >
> > Bob Deskin
> > Senior Product Advisor bob.deskin@cognos.com
> > Cognos Inc. (613) 738-1338 ext 4205 FAX: (613) 228-3149
> > 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9
> > CANADA
> >
> >
> > > ----------
> > > From: COLIN GLASS[SMTP:cglass@mlcc.mb.ca]
> > > Sent: Thursday, June 04, 1998 11:14 AM
> > > To: powerh-l@lists.swau.edu
> > > Cc: cgingera@mlcc.mb.ca; kbraun@mlcc.mb.ca
> > > Subject: Problem with dates.
> > >
> > > We are running PowerHouse 7.29 on the MPE/iX operating system
> > > (HP3000). We converted this system to be year 2000 compliant. We
> > > have
> > > two identical files, one with current info and one with historical
> > > info. A
> > > date variable is part of the key for each file.
> > >
> > > When running a QTP to transfer the information from the current
> file
> > > to
> > > the history file, the date on the history file becomes ########.
> > The
> > > date is
> > > OK on the current file though.
> > >
> > > We have checked the dictionary to ensure that the field is a size
> 8,
> > > and it is.
> > > Checked the QTP when it was recompiled with the dictionary changes
> > for
> > > Y2K, and there were no errors.
> > >
> > > My question is why this is occurring and how can we fix it?
> > >
> > > Thanks
> > >
> > > Colin Glass
> > > Manitoba Liquor Control Commission
> > > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> > =
> > > = = =
> > > 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.
> > >
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> > = = =
> > 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.
> >
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> 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.
>
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.