# Effect of eliminating ISNs?

**URL:** <https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Mainframes, Adabas-Basics-on-Mainframes\
**Created:** [May 16, 2010, 8:22pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605 "2010-05-16T20:22:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flakes\_Rice](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/flakes_rice/32/272_2.png) [@Flakes\_Rice](https://techcommunity.softwareag.com/u/Flakes_Rice)\
**Post date:** [May 16, 2010, 8:22pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605/1 "2010-05-16T20:22:55Z")

</div>

Hi,

I recently faced an interesting hypothetical question in one of the interviews:

> [@](#):
>
> “What will happen if inverted list directly gives data address instead of ISN? Can ISNs be eliminated altogether? What will be the issues?”

The answer I could think of at that moment was -

> [@](#):
>
> “This will indeed make the logical read more efficient. However, processing of complex queries (using FIND) will become very inefficient. ISN acts as a non-intelligent key during processing of complex queries. (Non-intelligent key is unique key having no business sense; it is small in size and has no danger of ever being updated). Moreover it would not be possible to use the GET command.”

I hope my answer was not totally wrong… :oops: What would be the correct, and a more convincing answer for this question?

---

<div class="post-metadata">

**Author:** ![Steve\_Robinson](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/steve_robinson/32/107_2.png) [@Steve\_Robinson](https://techcommunity.softwareag.com/u/Steve_Robinson)\
**Post date:** [May 16, 2010, 11:48pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605/2 "2010-05-16T23:48:28Z")

</div>

The biggest problem with your answer is that you did not mention what would make the idea all but totally infeasible.

Adabas records are variable length (variable length fields, MU fields, PE groups). Adabas will move records, physically , from one location to another, if an update causes the record to overflow the block. This would mean that all the inverted tables would have to be updated when a record was moved from block to block. This would be VERY expensive.

Actually, any length change for a record could cause a rippling effect since the actual address of other records in a block would likely be affected.

steve

---

<div class="post-metadata">

**Author:** ![Flakes\_Rice](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/flakes_rice/32/272_2.png) [@Flakes\_Rice](https://techcommunity.softwareag.com/u/Flakes_Rice)\
**Post date:** [May 17, 2010, 12:47pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605/3 "2010-05-17T12:47:00Z")

</div>

Thank you, Steve.  
Yes, I completely missed this aspect…

---

<div class="post-metadata">

**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\
**Post date:** [May 17, 2010, 8:42pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605/4 "2010-05-17T20:42:57Z")

</div>

Steve’s point is indeed the main issue. All one has to do is look at Oracle… Oracle uses a ROWID instead of an ISN even though DBAs familiar with both might think of them as the same. What makes them different is that the ROWID points to a very specific address within data storage, whereas ISN has to be looked up in the address converter to find the DS block where the record exists.

One might think then that ROWID would be better, since you save yourself the AC lookup. However, as Steve says, data moves around because of changing record lengths, and can move several times. What Adabas does is simply update the address converter as to where the new location is. What Oracle does is it leaves pointers in data storage so that the engine knows where to look next. Sometimes then there is a chain of many of these things to get to your physical data record! You can imagine this would slow down your calls, plus regardless how little space is taken, all these chain pointers do take up space in your database.

Imagine that you move into a new house, and instead of telling your friends where you live, they all had to travel to the first place you lived, then read a note on the door telling them where you moved to next, and then reading a note on the door there telling them where you moved to next, etc, until they found your current place. Then, next time they visit you, they had to go through the same thing again all over, starting with your first address. How long would they be your friends?

Is my SAG bias showing?

---

<div class="post-metadata">

**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\
**Post date:** [May 18, 2010, 1:52pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605/5 "2010-05-18T13:52:58Z")

</div>

> [@](#):
>
> I hope my answer was not totally wrong… :oops: What would be the correct, and a more convincing answer for this question?

Maybe my answer is not as good as Steve’s…

I think this is a very “philosophical” question. Every access method has its advantages and disadvantages. If the questioner want to know more about it:

> **[Access method](https://en.wikipedia.org/wiki/Access_method)**
>
> An access method is a function of a mainframe operating system that enables access to data on disk, tape or other external devices. Access methods were present in several mainframe operating systems since the late 1950s, under a variety of names; the name access method was introduced in 1963 in the IBM OS/360 operating system. Access methods provide an application programming interface (API) for programmers to transfer data to or from device, and could be compared to device drivers in non-main Sy...

Escpecially:

> **[ISAM](https://en.wikipedia.org/wiki/ISAM)**
>
> ISAM, an acronym for Indexed Sequential Access Method, is a method for creating, maintaining, and manipulating computer files of data so that records can be retrieved sequentially or randomly by one or more keys. Indexes of key fields are maintained to achieve fast retrieval of required file records in indexed files. IBM originally developed ISAM for mainframe computers, but implementations are available for most computer systems.
> The term ISAM is used for several related concepts:
> In an ISAM s...

> **[Virtual Storage Access Method](https://en.wikipedia.org/wiki/VSAM)**
>
> Virtual Storage Access Method (VSAM) is an IBM DASD file storage access method, first used in the OS/VS1, OS/VS2 Release 1 (SVS) and Release 2 (MVS) operating systems, later used throughout the Multiple Virtual Storage (MVS) architecture and now in z/OS. Originally a record-oriented filesystem,\[NB 2\] VSAM comprises four\[NB 2\] data set organizations: key-sequenced (KSDS), relative record (RRDS), entry-sequenced (ESDS) and linear (LDS). The KSDS, RRDS and ESDS organizations contain records, w An IB...

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:58pm UTC](https://techcommunity.softwareag.com/t/effect-of-eliminating-isns/93605/6 "2021-04-02T14:58:30Z")

</div>


