TWiki > TWiki > HP3000FAQ > HP3000OperatingSystemQuestions > Hp3000Databases > Hp3000Ksam > Hp3000KsamvVsKsamxl	TWiki webs: Main | TWiki | Sandbox
	TWiki . { Welcome | Register | Changes | Topics | Index | Search | Go }

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^?

-- ChrisBartram - 18 May 2006

Parents: Main > HP3000FAQ > HP3000OperatingSystemQuestions > Hp3000Databases > Hp3000Ksam

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.Hp3000KsamvVsKsamxl