*d* The occurrence count exceeds the defined occurrence for thisfile.

roger32909 at bellsouth.net roger32909 at bellsouth.net
Wed Sep 28 07:25:56 CDT 2005


Here is the FILE statement and associated ITEMs & TEMPs.  Tests indicate that all is working OK, but the message worries us:

	FILE VI-LINES DETAIL OCCURS 5 TIMES CACHE 255 NOITEMS
	  ACCESS VIA VI-ID USING VI-ID OF VI-HEADER

	  ITEM  VI-ID     INITIAL VI-ID OF VI-HEADER FIXED
	  ITEM A-FLAG INITIAL "N"
	  ITEM APPLY   INITIAL 0 FIXED

	  DEFINE W-O CHAR*1 = "W" IF WO-AMOUNT > 0 ELSE " "

	   TEMP T-OPEN-BALANCE OCCURS WITH VI-LINES

	   TEMP T-OPEN-BALANCE-DISPLAY OCCURS WITH VI-LINES

	   ITEM GL-TRANS-AMOUNT OF VI-LINES &
		SUM NEGATIVE INTO T-OPEN-BALANCE WHEN POSITIVE

	   ITEM WO-AMOUNT OF VI-LINES &
		SUM NEGATIVE INTO T-OPEN-BALANCE WHEN POSITIVE

	   ITEM ORIG-AMOUNT OF VI-LINES &
		SUM INTO VERIFIED-BALANCE OF VI-HEADER

Roger
> 
> From: "Deskin, Bob" <Bob.Deskin at Cognos.COM>
> Date: 2005/09/27 Tue PM 03:44:51 EDT
> To: "Whittall, Conrad" <Conrad.Whittall at Cognos.COM>, 
> 	"Findlay, Colin" <colin.findlay at fmglobal.com>, 
> 	<roger32909 at bellsouth.net>
> CC: <powerh-l at lists.sowder.com>
> Subject: RE: *d* The occurrence count exceeds the defined occurrence for thisfile.
> 
> Does the file have a repeating item by any chance? There is an issue
> that has been around since the early days involving initializing
> repeating items within a repeating file depending on the circumstances.
> If the file has a repeating item I'll go into more detail.
> 
> Bob
> 
> -----Original Message-----
> From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
> [mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
> Behalf Of Whittall, Conrad
> Sent: September 27, 2005 3:01 PM
> To: Findlay, Colin; roger32909 at bellsouth.net
> Cc: powerh-l at lists.sowder.com
> Subject: RE: *d* The occurrence count exceeds the defined occurrence for
> thisfile.
> 
> 
> 
> Haven't been sitting on the fence at all...in fact I just got back from
> a 2-week grand tour of Nova Scotia, with a week back in Ottawa to
> recover -- covered over 2,500 miles in my Saab Viggen (the car, not the
> plane), excluding the distances travelled on The Cat between Bar Harbor,
> Maine and Yarmouth, Nova Scotia and on the more traditional ferry from
> Nova Scotia to Prince Edward Island...and enjoyed every minutes of it :)
> 
> To be honest its so long since I saw any *d* errors I can't remember
> what the "d" might relate to.
> 
> I did take a quick look at the qkmsge.txt file that ships with PH8.41D1
> and found quite a few messages prefixed with *d* (many related to QKGO
> parameters) and some others prefixed *s*, but I have no idea what this
> signifies. Maybe Bob Deskin can step in an point us in the right
> direction?
> 
> Best regards,
> Conrad
> 
> -----Original Message-----
> From: Findlay, Colin [mailto:colin.findlay at fmglobal.com] 
> Sent: Tuesday 27 September 2005 03:38
> To: roger32909 at bellsouth.net
> Cc: Whittall, Conrad; powerh-l at lists.sowder.com
> Subject: RE: *d* The occurrence count exceeds the defined occurrence
> forthisfile.
> 
> No - I never said anything about it compiling with NO errors!
> 
> All I'm saying is that the only times I've seen *d* errors issued by
> Quick have been where:
> 
> A)	there WERE compile errors,
> or
> B)	there was a bug in that release.
> 
> Although the last time I saw it was a VERY long time ago, I vividly
> remember the first time I saw the dreaded
> "*d* This screen has design errors" message. I was using version 4 (4.05
> I think) on an HP3000 and it was 1985...
> 
> Call me simplistic, but for the last 20 years I've been under the
> impression that the first D in "*d* This screen has design errors" and
> the D in "design" might be related in some way. So naturally I jumped to
> the (no doubt totally erroneous) conclusion that "*d* The occurrence
> count exceeds the defined occurrence for this file." might also be a
> "design" error. Silly old me...
> 
> ;o)
> 
> Ps - Oi! Whittall!! Get off the fence!!!
> 
> <snip> 
>   
>        This message may contain privileged and/or confidential
> information.  If you have received this e-mail in error or are not the
> intended recipient, you may not use, copy, disseminate or distribute it;
> do not open any attachments, delete it immediately from your system and
> notify the sender promptly by e-mail that you have done so.  Thank you. 
>         
>  
> 
> -- 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe &lt;password&gt;" 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