RE: User space blues

Note that while your proposed fix will work, it will have a significant negative impact on the
performance of the process.

It is considerably more expensive to read/write to the DB as opposed to a user space.

Which is probably why JDE is using user spaces in the first place; thus I disagree with your statement
that the user of user spaces is a poor design.

Personally, I hate to look at a GL journal batch with 1,000 entries let alone the JDE limit of
17,700...and you want to go higher???

I question the need for a journal batch that large, isn't there some logical way to break it up?

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of SJL
Sent: Friday, March 21, 2008 12:56 PM
To: midrange-l@xxxxxxxxxxxx
Subject: User space blues

All -

We had a JDE program blow up this week when it filled up a user space.

JDE uses lots of user spaces and user indexes for temporary data within
RPG
programs - for raw GL entry, inventory transactions, etc. In this
particular instance, a program tried to go beyond the 16 MB size limit on
the user space and dumped. This is very troublesome, because this
technique
is pervasive throughout the JDE World Software product.

For example, any program that needs to create journal entries will load
entries in the GL user space in QTEMP, then it will call the XT0911Z1
program to edit and process them.

IMO, JDE violated one of the prime directives of structured design, which
dictates that you should have high cohesion and low coupling between
programs/modules by using user spaces in this fashion, knowing that there
were such size limitations imposed by the OS.

Any suggestions on how to fix this without having to modify every program
in
the system that calls XT0911Z1 ?

What I had in mind was building a work file in QTEMP and have the programs
create the G/L transaction information in the work file, modifying
XT0911Z1
by passing an additional parm to it to tell it to process the work file
INSTEAD of the user space. By checking for the number of parms passed to
XT0911Z1, the unmodified programs could still use the user space technique
until we get around to modifying them - and most of them probably wouldn't
get modified...It would probably be programs that produce high-volumes of
transactions that would be modified first.

Regards,
sjl


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.