%META:TOPICINFO{author="ChrisBartram" date="1170388692" format="1.1" version="1.2"}%
%META:TOPICPARENT{name="Hp3000Ksam"}%
---+ Differences between KSAM/V and KSAM/iX (NM) on the HP3000

NM version much easier to use as a temporary work file from within     
Cobol programs - no need to KSAMUTIL etc.  I have used in 2 ways:

* consolidate bills of material from MM for homebrew backflush method,

* implement priority queue (to-do) list for system log-file processor.

In both cases (XL 3.0) could do easily as temp files - need file equation, then open as random - key stuff done by Cobol. 

  --[[TonyShepherd]]

You might want to include: KSAM/XL has the ;REUSE option. KSAM/V also has the ;REUSE option but it is undocumented, although widely used. 

  --[[GavinScott]]


Native Mode KSAM files (their file code will appear as KSAMXL when you do a :LISTF,2 on them) are attached to transaction management and will be automatically recovered to their last consistent point upon reboot. However, the old compatibility mode KSAM files that we know and hmmm... appreciate?, are *not* attached to transaction management and still must be recovered with KSAMUTIL. CM KSAM files can be distinguished by the fact that there are actually two files, the data file and the key file, that make up the logical CM KSAM file.

  --[[CraigFairchild]]


-- Main.ChrisBartram - 18 May 2006