×
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.
Deleted is deleted. When the record is deleted, so is it's key.
Any possibility you're trying to update a logical? That could be an
issue. Like a logical that has an Omit on "inactive records". Thus you
do a chain, get no hit, try a write and the physical complains. More
detail... Suppose your physical file (IIM) has these three fields:
IID - A2 Record ID; IM/IZ
IPROD - A15 Item Number
IDESC - A30 Item Description
and there's a primary key constraint on IPROD. Now, suppose there's a
logical called IIML01. It has an Omit where IID='IZ' and a key by IPROD.
Let's say IIM contains the following:
IZ 001 Sample
IM 002 Dirt
IM 003 Gravel
If you chain IIML01 for IPROD='001' the chain will tell you that no record
was found. So, you do a write on that and it fails with a duplicate key.
(Granted, BPCS wouldn't because they wouldn't put a primary key on there
because they only do what was recommended on early versions of the S/38
operating system. Thus you would now have two rows with IPROD = '001'.)
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
