× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I don't believe the IBM-shipped default is to create non-observable program
objects.  Mark, could you be more specific on that?

I agree on making all apps observable.  To my knowledge, there is absolutely
no performance impact - please correct me if I'm wrong on that.  Note,
however, that with OPTIMIZE(*FULL), "Optimization which generates the most
efficient code. Translation time is the longest. User variables may not be
modified but may be displayed, although the presented values may not be the
current values." - Might this impact what gets dumped as well?

That said, yes, program objects gain size as you increase observability
(question: Is this the DBGVIEW parameter on the CRTBNDRPG command?)  Usually,
though, your data takes up the mass majority of your available DASD.  Whether
having observability or not having it, should not impact your DASD utilization
to any meaningful degree.  If it does, I'd venture to say you're way
undersized on DASD.

FWIW, here's my thinking on the subject - will "saustad" be able to recreate
the problem once he recompiles the program to have observability?  Perhaps,
and hopefully he will be able to.  Sometimes, though, it may be too late to
add back the observability.  And, even if s/he can recreate the problem, how
much time will have been lost because the program did not have observability
in the first place?  Time = Money.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Your program is not observable; saves room and is the default, but DASD is
cheap, so
you will have to recompile so it is observable, then let is abend again and
dump,
then you will see your variables.  By default here we make all ILE
observable just for
this reason, the space savings IMHO is nominal, performance "could" be a
hit, I am not
a bare metal techo weenie though, but from an overall time saver, I feel you
are better
off just making them observable to begin with, why, because no one is
perfect, and we
will all miss the size at some point in time, or someone else will put some
erroneous
data in "our" files.

HTH
Mark A. Manske
[mailto:mmanske@minter-weisman.com]
Sr. Project Lead
Minter-Weisman




-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of saustad@deltadentalwi.com
Sent: Friday, March 02, 2001 10:43 AM
To: rpg400-l@midrange.com
Subject: RPG IV pgm dump


We had an RPG IV pgm abend this morning with the following error:  The
target for a numeric operation is too small to hold the result.  We
understand this msg.  But when we looked at the dump, there is no field
information.  At the end of the dump is the following stmt:  Dump
terminated because variable data not available.  Does anybody have any idea
what this means?  Thanks for any help.
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.