*d* The occurrence count exceeds the defined occurrence
forthis file.
roger32909 at bellsouth.net
roger32909 at bellsouth.net
Mon Sep 26 10:29:21 CDT 2005
Thank you, Colin, for the tip. I never thought of looking in the "PowerHouse and Relational Databases" manual. I forgot to mention that this client uses only RMS files and no database.
As for asking Cognos support, I used to be able to do this frequently (with excellent answers and results, I may add) back in the earlier days when clients paid for support. Unfortunately, recent clients for a variety of reasons choose to operate without support and without upgrading. These clients are developing replacement systems not based on PowerHouse, although some are planning on using Cognos BI or other products. Others on this list have commented more eloquently about the trend from 4GL to 3GL and from reliable to cheaper operating systems, software and hardware.
>
> From: "Findlay, Colin" <colin.findlay at fmglobal.com>
> Date: 2005/09/26 Mon AM 10:07:17 EDT
> To: "Joe Boyle" <atla38 at dsl.pipex.com>,
> <roger32909 at bellsouth.net>,
> <powerh-l at lists.sowder.com>
> Subject: RE: RE: *d* The occurrence count exceeds the defined occurrence forthis file.
>
> Isn't this just a "design error" as defined on p.58 of the 8.3 manual
> (and in every QUICK manual since the year dot) ?
>
> "Severe Errors
> Any of the following error conditions are considered Severe errors:
> * QUICK executes a SEVERE verb
> * QUICK detects a screen design error (*d* error)
> * QUICK detects a design inconsistency (e.g., the file definition in the
> dictionary does not
> match the physical file)
> * an internal error occurs..."
>
> -----Original Message-----
> From: powerh-l-bounces+colin.findlay=fmglobal.com at lists.sowder.com
> [mailto:powerh-l-bounces+colin.findlay=fmglobal.com at lists.sowder.com] On
> Behalf Of Joe Boyle
> Sent: 26 September 2005 14:54
> To: roger32909 at bellsouth.net; powerh-l at lists.sowder.com
> Subject: RE: RE: *d* The occurrence count exceeds the defined occurrence
> forthis file.
>
>
> you don't say if you are allowing a default cluster statement to be
> built,
> and to be honest I assumed that the cluster statement may have been the
> cause; I suspected that the file may have not had an occurs option when
> the
> screen was built originally.
>
> Assuming that the cluster is comprised of standard default syntax, I
> think
> you may well have a bug as suggested by Chris, and probably need to
> upgrade
> to a later 7.10.G version.
>
> I would guess the *d* is for data, have you asked Cognos to look in
> their
> bug base for known issues ?
>
> Regards, Joe.
>
>
> -----Original Message-----
> From: roger32909 at bellsouth.net [mailto:roger32909 at bellsouth.net]
> Sent: 26 September 2005 14:19
> To: Joe Boyle; powerh-l at lists.sowder.com
> Subject: Re: RE: *d* The occurrence count exceeds the defined occurrence
> for
> this file.
>
> I am familar with the *W* warning and the *E* error messages, but what
> is a
> "*d*" message?
>
> Anyhow, here are the default procedures:
>
> > BUILD LIST DETAIL
> *W* Update on linked screen may bypass PREUPDATE/UPDATE/POSTUPDATE
> procedures.
> > PROCEDURE APPEND
> > BEGIN
> > ACCEPT M-ID OF XYZ-LINES
> > DISPLAY V-ID OF MMENTS
> > DISPLAY BL_DATE OF MMENTS
> > ACCEPT G_LINE OF XYZ-LINES
> > ACCEPT P_S OF XYZ-LINES
> > EDIT T-P_S
> > DISPLAY M-QTY OF MMENTS
> > DISPLAY L_LINK OF XYZ-LINES
> > DISPLAY T-OPEN-BAL
> > DISPLAY W-O
> > ACCEPT OC-AMT OF XYZ-LINES
> > DISPLAY D-USD-LABEL
> > DISPLAY D-USD-AMOUNT
> > END
> > PROCEDURE ENTRY
> > BEGIN
> > DISPLAY X-TIME
> > DISPLAY X-FILLER3
> > DISPLAY R-ID OF XYZ-HEADER
> > DISPLAY C-CODE OF XYZ-HEADER
> > DISPLAY V-INV OF XYZ-HEADER
> > DISPLAY DESCRIPTION OF CURRENCY
> > DISPLAY NAME OF CPARTS
> > DISPLAY OC-AMOUNT OF XYZ-HEADER
> > DISPLAY I-DATE OF XYZ-HEADER
> > DISPLAY D-DATE OF XYZ-HEADER
> > DISPLAY V-BAL OF XYZ-HEADER
> > DISPLAY D-STATUS
> > DISPLAY POST-PER OF XYZ-HEADER
> > DISPLAY T-REMAINING
> > DISPLAY SEL-FOR-PAY-DISP
> > DISPLAY D-PAY-MET
> > DISPLAY CT-ID OF VP-HEADER
> > DISPLAY D-ON
> > DISPLAY T-DATE OF VP-HEADER
> > DISPLAY CURRENCY OF XYZ-HEADER
> > FOR XYZ-LINES
> > BEGIN
> > PERFORM APPEND
> > END
> > END
> > PROCEDURE PATH
> > BEGIN
> > LET PATH = 1
> > END
> > PROCEDURE FIND
> > BEGIN
> > GET XYZ-HEADER VIA VI-ID USING &
> > T-VI-ID
> > END
> > PROCEDURE DETAIL FIND
> > BEGIN
> > FOR MISSING XYZ-LINES
> > BEGIN
> > GET XYZ-LINES OPTIONAL
> > GET MMENT-EST OPTIONAL
> > END
> > END
> > PROCEDURE UPDATE
> > BEGIN
> > LOCK MMENT-EST FILE , MMENT-EST-AUDIT FILE , &
> > XYZ-HEADER FILE , XYZ-LINES FILE
> > PUT XYZ-HEADER
> > FOR XYZ-LINES
> > BEGIN
> > PUT XYZ-LINES
> > PUT MMENT-EST
> > END
> > UNLOCK ALL FILE
> > END
> > ALLDONE
>
> >
> > From: "Joe Boyle" <atla38 at dsl.pipex.com>
> > Date: 2005/09/23 Fri PM 05:30:50 EDT
> > To: <roger32909 at bellsouth.net>, <powerh-l at lists.sowder.com>
> > Subject: RE: *d* The occurrence count exceeds the defined occurrence
> for
> this file.
> >
> > Did you allow the screen to build a default cluster ?
> > What is the full syntax displayed when you do a 'build list detail' ?
> >
> > Regards, Joe.
> >
> > -----Original Message-----
> > From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> > [mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On
> Behalf
> Of
> > roger32909 at bellsouth.net
> > Sent: 23 September 2005 20:22
> > To: powerh-l at lists.sowder.com
> > Subject: *d* The occurrence count exceeds the defined occurrence for
> this
> > file.
> >
> > OpenVMS V7.3-2 on an Alpha, Q D E S I G N (7.10.G1)
> > Copyright 1998 COGNOS INC. (ALPHA)
> > Licensed PH-AXP-DEVELOPMENT
> >
> > Have a detail file in a screen that occurs 5 times
> > FILE XYZ-LINES DETAIL OCCURS 5 TIMES CACHE 255 NOITEMS
> >
> > In testing a screen, I just updated 9 detail records and received this
> > message which I have never
> > seen before:
> >
> > *d* The occurrence count exceeds the defined occurrence for this file.
> >
> > I looked at the 9 records in QUIZ and everything appears to be normal.
> When
> > I do a QUICK (F)ind,
> > all 9 records show up normally.
> >
> > But surely a message like this would alarm a user. Anybody have a
> clue?
> >
> > --
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> > Mailing list: powerh-l at lists.sowder.com
> > Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> > Unsubscribe: "unsubscribe <password>" in message body to
> > powerh-l-request at lists.sowder.com
> > http://lists.sowder.com/mailman/listinfo/powerh-l
> > This list is closed, thus to post to the list you must be a
> subscriber.
> >
> >
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe <password>" in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
>
>
>
More information about the powerh-l
mailing list