× 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 get "This file accessed with wrong key location." when I try that.

-----Original Message-----
From: Jerry Adams [mailto:jerry@xxxxxxxxxxxxxxx]
Sent: Friday, March 21, 2008 11:59 AM
To: RPG Midrange
Subject: RPG II Question

I really don't expect an answer. In fact most people will probably just

delete this when they see the subject line. But this is puzzling the
heck out of me.

I went in to an RPG II program (old package) to do some simple
maintenance changes. I noticed that one of the files was defined as:

FFilenameIPEAFBlenRlenLK1AIOvKlocEDevice+
FLISTCONSIF 27 1AI 1 DISK

Well, the key length is '1' but the key actually starts in position '2'
of the record. The purpose of the file is to validate a code entered on

a panel:

C WRCONS CHAINLISTCONS 54
C 54 SETON 99
C 54 *ZEROS ADD 23 $
C 54 GOTO X2A

The first position of LISTCONS is a status byte. Currently every record

has an 'A' in position 1. The program has been successfully validating
these codes for years. How is that possible? I even put the program
under debug (ISDB) and verified the codes entered (WRCONS) and in the
file (ABCONS) are the same after the chain, and that indicator 54 is
turned *Off.

It has been awhile since I programmed on a S/36, but I'm pretty sure
that, first, when the program started up it would give me a file
mismatch error. Is the i5 really smart enough to say, "Well, he botched

that. Let's just use what is really in the file."?

Thanks.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.