×
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.
Also, SQL SESLECT statements, if their ORDER BY is not down to a granular level of uniqueness - can give different results because of the Sequence of the records. There could be applications that have always behaved one way, and with REUSEDLT(*YES) they behave differently
- John Voris
Philadelphia
-====================================-
message: 4
date: Mon, 27 Jul 2020 11:08:56 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: REUSEDLT(*NO) - what's the point?
I've actually worked on such a bill of materials application. And it if got clobbered the vendor had a utility. Something about rebuilding the chain chase sequence comes to mind.
Rob Berendt
--
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Vernon Hamberg
Sent: Saturday, July 25, 2020 6:32 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: REUSEDLT(*NO) - what's the point?
Patrik
One cannot safely assume that the arrival order does not matter. The
chances are that the technique of linked lists using RRNs is not in use,
but you can't guarantee it. That used to be used for bills-of-materials
in ERP products.
So it is still important to check before setting REUSEDLT(*YES).
what could be the reason for CRTPF and CHGPF having a default setting of REUSEDLT(*NO)?
Thanks for all of your valuable feedback. All in all, it seems to be mostly a leftover from ancient times, so I guess it's helpful to always switch to REUSEDLT(*YES) nowadays, even with older machines.
midrange.com
