I have individual application single record control files to store thing
like last invoice number used, current billing date, etc.
Other things are defined as constants and stored in copy members. An
example of this is we use route 995 for customer pickups. So in a copy
member I have
D @PkpRot C 995
And yes, I know the @ could cause a problem if we go multinational, but I
don't see that happening.
On Fri, May 13, 2011 at 11:17 AM, Birgitta Hauser<Hauser@xxxxxxxxxxxxxxx>wrote:
we just had a discussion about using data areas.
In my opinion they are not heavily used or needed.
I either create a table/physical file or store the information in global
variables in a specific service program. The data within these global
variables is set and retrieved by calling procedures.
I’m just curious, are you using data areas (heavily) or not?
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives