Re: what did FILE-LIMITS mean?
From: Greg Huffstickler (greg.huffstickler_at_nospam.unisys.com)
Date: 11/11/03
- Next message: Alan: "Read fixed length sequential files"
- Previous message: Edward Reid: "what did FILE-LIMITS mean?"
- In reply to: Edward Reid: "what did FILE-LIMITS mean?"
- Next in thread: Peter E.C. Dashwood: "Re: what did FILE-LIMITS mean?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 11 Nov 2003 13:34:27 -0800
>From my old 68 manual:
[ { FILE-LIMIT IS } {data-name-2 } { THROUGH } {data-name-3 } ]
[ { FILE-LIMITS ARE } { literal-1 } { THRU } {
-2 } ]
"In the FILE-LIMITS clause, the pair of operands associated with the key
word THRU represents a logical segment of the file. The values of
data-name-2 and data-name-3 or literal-1 and literal-2 correspond to the low
and high values of the ACTUAL KEY of records available to the program: that
is, the logical beginning of disk file is concidered to be that address
represented by literal-1 or data-name-2. The operand END specifies that the
end of the disk file is to be the last record written before use of the file
as input."
"The value of the data items as specified in the FILE-LIMIT clause is
utilized by the system only at the time that the associated disk file is
opened by the execution of the OPEN statement."
There was a patch to CMT in 47.1 about translating FILE-LIMIT.
PLE 17384180 PRI-10034043
"Edward Reid" <edward@paleo.org> wrote in message
news:5cbdc996.0311111147.3f4f14ec@posting.google.com...
We are converting some COBOL68 (!!) programs that have a FILE-LIMITS
clause in the SELECT, such as
SELECT FINDIN ASSIGN TO 20 * 1000 DISKPACKS
FILE-LIMITS ARE FIRST-REC THRU END,
ACCESS MODE IS SEQUENTIAL.
where FIRST-REC is in working storage, PIC 9(6) VALUE 1. Don't worry
about the ASSIGN clause; we know what that means.
We've been assuming that this worked out to a no-op -- that
FILE-LIMITS meant start at the indicated first record and continue to
the end of the file. And so we just took out the clause, as the
conversion tool was generating a bunch of funky code as a substitute
and it didn't even compile.
But we are having trouble getting the converted program to produce the
same results, and this is an obvious potential problem.
Does anyone remember this clause, and what it meant? I've found a few
references by googling it -- and it appears that Burroughs wasn't the
only vendor implementing it -- but nothing that says any more than
"can't do that any more".
Thanks for dredging into the depths of your memories,
Edward Reid
- Next message: Alan: "Read fixed length sequential files"
- Previous message: Edward Reid: "what did FILE-LIMITS mean?"
- In reply to: Edward Reid: "what did FILE-LIMITS mean?"
- Next in thread: Peter E.C. Dashwood: "Re: what did FILE-LIMITS mean?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
