Re: Revised Index versus Subscript
- From: Robert Jones <rjones0@xxxxxxxxxxx>
- Date: Fri, 28 Sep 2007 10:46:16 -0700
On Sep 28, 6:05 pm, Robert <n...@xxxxxx> wrote:
On Fri, 28 Sep 2007 13:21:51 +0200, "Roger While" <si...@xxxxxxxxxxxx> wrote:
"Robert" <n...@xxxxxx> schrieb im Newsbeitrag
news:nvtlf3hflf9ispjjcjmha203ml6fa8s7h2@xxxxxxxxxx
On Wed, 26 Sep 2007 15:55:59 +0200, "Roger While" <si...@xxxxxxxxxxxx>
Not only that, a particular compiler implementation has it's
own INDEX definition which is somewhat difficult to ascertain.
(And which is not necessarily a C-5 item)
It's EASY to ascertain. Set a data item of type index to the
table-oriented index,
redefine as comp-5 and display.
Really ?
Ever heard about 64 bit index?
How do you redefine (compatibly) an index ?
01 an-index usage index.
01 an-iindex-redefined redefines an-index usage binary-double.
set an-index to table-index
display an-index-redefined
While it may seem reasonable to assume that a data item with usage
index has the same format as the index that is actually associated
with the table from which it has been derived with a SET statement, an
implementor is not bound to do this. For example in a small table in
an IBM mainframe compiler the actual index could be a binary halfword,
if that is big enough to do the job. A compiler's optimiser might
well do this.
.
- References:
- Revised Index versus Subscript
- From: Roger While
- Re: Revised Index versus Subscript
- From: Robert
- Re: Revised Index versus Subscript
- From: Roger While
- Re: Revised Index versus Subscript
- From: Robert
- Revised Index versus Subscript
- Prev by Date: OT: Iraq
- Next by Date: Re: IBM's CCCA and customized LCPs for Enterprise COBOL migration
- Previous by thread: Re: Revised Index versus Subscript
- Next by thread: [OT[ - Keep off-topic, off-topic
- Index(es):
Relevant Pages
|