Hi, Gregory.
On Fri, 27 Jun 1997 19:46:17 -0400, Gregory Stigers wrote:
|Is this accurate? KSAMUTIL reports "THE REFERENCED FILE IS NOT A KSAM
|FILE (1062)". I realize that one can build an indexed file that is not
|KSAM. Yet the LISTF ,7 gives:
|
|FILE: I213450.PUB.HP01
|
|KEY KEY TYPE KEY LOCATION KEY SIZE DUP/RDUP
|--- -------- ------------ -------- --------
| 1 BYTE 1 66 NONE
| 2 BYTE 67 66 RDUP
| 3 BYTE 133 66 RDUP
|
|NUM KSAM KEYS: 3 FIRST KSAM RECORD: 0
|LANGUAGE : ENGLISH REUSE RECORD : YES
|PRIMARY KEY : RANDOM COMPUTE BLK SIZE : DEFBLK
|VERSION : 2 DATA BLOCK SIZE : 4096
|
|>----------
|>> All "KSAM" files including I213450, are built as KSAMXL files on the
|>> HP. They are built using the "BUILD" command, with all of the file
|>> definitions, including the KEYS, KSAMXL option, and the REUSE option.
|>> Doing a "LISTF I213450.PUB,2" will not indicate in the CODE column
|>> that this file is a KSAM file. However, if you do a "LISTF
|>> I213450.PUB,7", it will show you all the KEY parameters for this KSAM
|>> file.
|>>
|>> These "new" KSAMXL files are more efficient in that a reorg is not
|>> necessary, if the "REUSE" option is specified. Also, there is no need
|>> to rebuild key files after system crashes.
You seem confused about the differences between "old" and "new" KSAM files
on MPE. "Old KSAM" is often called "compatibility-mode" or "CM" KSAM files.
"New KSAM" is often referred to as "Native-mode" or "NM" KSAM files. CM and
NM are indicators which usually refer to what kind of code is used to
implement something on MPE: CM implies that it is code interpreted on
PA-RISC machines, whereas NM is code which is native to PA-RISC and
therefore is the "native code for the processor". This is true for CM-KSAM
and NM-KSAM too. CM-KSAM is a port of the old KSAM code from MPE/V.
NM-KSAM is a rewrite for PA-RISC. The API for them is almost identical and
in fact, I understand that it's possible (perhaps with some exceptions) to
replace a CM-KSAM file with an NM-KSAM file and have the exact same programs
work correctly with it. The difference in them is what code is actually
handling the KSAM file in MPE and how the files are built and managed by the
"DBA" or equivalent.
CM-KSAM files are built and managed by KSAMUTIL or by using the CM-KSAM
options documented in FOPEN and other file system intrinsics. One of the
things KSAMUTIL can do is show the key info of a CM-KSAM file. NM-KSAM
files, on the other hand, are not supported by KSAMUTIL (which is part of
the port of CM-KSAM from MPE/V). LISTFILE modes 5 and 7 show the key info
for a NM-KSAM file. Building an NM-KSAM file can be done with the :BUILD
command or via the FOPEN intrinsic using the NM-KSAM options. NMKSAM files
provide several advantages over CMKSAM files including improved performance
and better data integrity.
Hmmm... It just occured to me that HP's support for CM-KSAM may be ending
in September 1998 given the following announcement that came across my desk
from HP this week regarding MPE/V "End of Support":
MPE/iX Compatibility Mode Software Subsystem Support
HP will provide ongoing support for those compatibility mode (CM)
products used on MPE/iX systems that do not have equivalent native mode
replacements. However, for CM products used on MPE/iX systems that have
equivalent native mode replacements, support will end on September 1,
1998.
Further info is supposed to be available via http://www.hp.com/go/vintagesw
under the "MPE/V" link, via a fax server at 800-231-9000 document id #12977,
and via SupportLine at http://us-support.external.hp.com and
http://europe-support.external.hp.com
P.S. Perhaps info on the differences in CM-KSAM and N_KSAM should be added
to the FAQ, if it's not already there. Also, perhaps a note regarding
MPE/V and CM product "End of Support" would be appropriate there.
Just a thought....
--
Jeff Woods
[log in to unmask] at Unison Software
[log in to unmask] at home [PGP key available here via finger]
"My life is one long curve, full of turning points." -- Pierre Trudeau
|
