W dniu 2018-02-14 o 17:06, Pew, Curtis G pisze:
On Feb 14, 2018, at 9:47 AM, R.S. <[email protected]> wrote:
1. KEY
Nowadays there are two "datasets" using hardware key: VTOC and PDS directory.
What about other files? Is it possible to allocate new dataset with hardware 
key?
According to JCL Reference, KEYLEN keyword can  be used for VSAM KSDS or for 
non-SMS datasets including BDAM, SAM, BPAM, QISAM (!) and EXCP datasets.
Is it still supported or just documentation is out of date?

My understanding is that the KEYLEN for a VSAM KSDS doesn’t refer the the CKD 
hardware key.
That's obvious. VSAM does not use hardware key.

But why does it matter? Hardware keys are one of those “it seemed like a good 
idea at the time” things that didn’t pan out. CKD hardware keys are extremely 
slow and inefficient; you really don’t want to use them. IBM added the VTOC 
index to avoid using the hardware key when searching the VTOC, and PDSE to get 
away from the hardware keys in the PDS directory. Our lives would all be 
simpler and better if we could actually eliminate hardware keys.

I just wanted to learn old things. Sometimes it helps to understand current things.


As far as I know, the PDS directory consist of 256-byte blocks, but the 8-byte 
key is not part of the block. Is it correct?
Or maybe it is 256 bytes including some 8-byte field which is repeated in Key 
area?
The hardware key for a PDS directory block contains the name of the last member 
whose entry is contained in that block. The 256 bytes is the data portion of 
the block and does not include the 8 bytes of the key.

Thank you for your help.

Regards
--
Radoslaw Skorupka
Lodz, Poland




======================================================================


       --
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: [email protected]ąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 0000025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to