How to ensure a hash file is 64bits.
Moderators: chulett, rschirm, roy
How to ensure a hash file is 64bits.
Dear All,
How or what command can i use to check whether a hash file is 64bits or not.
Thanks in advance.
How or what command can i use to check whether a hash file is 64bits or not.
Thanks in advance.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try as your command. Examine the first four bytes.
If they show acef 010c (or 010c acef on an Intel CPU), then it is a 32-bit hashed file.
If they show acef 020c (or 020c acef on an Intel CPU), then it is a 64-bit hashed file.
For static hashed files, omit the "/DATA.30" from the hashed file pathname.
Code: Select all
SH -c "od -x hashedfile/DATA.30 | head -1"
If they show acef 010c (or 010c acef on an Intel CPU), then it is a 32-bit hashed file.
If they show acef 020c (or 020c acef on an Intel CPU), then it is a 64-bit hashed file.
For static hashed files, omit the "/DATA.30" from the hashed file pathname.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Dear Ray,
I am not a premium poster so unable to read your full reply but was able to capture the command.Here what i did:
i. mkdbfile /crdrsk/data/HASH/PRV_MTH_ST_TEST 30 1 4 20 50 80 1639 -
64bit - The file was created successfully.
ii. executed SH -c "od -x /crdrsk/data/HASH/PRV_MTH_ST_TEST/DATA.30 | head -1" command.
Output was - This was supposed to be a 64bits.
0000000 acef 010c 0000 001e 0000 0000 0000 0001
I ran the command against a different hash file which was not changed to 64 and the output was still the same as above.
Where i went wrong?
Thanks
I am not a premium poster so unable to read your full reply but was able to capture the command.Here what i did:
i. mkdbfile /crdrsk/data/HASH/PRV_MTH_ST_TEST 30 1 4 20 50 80 1639 -
64bit - The file was created successfully.
ii. executed SH -c "od -x /crdrsk/data/HASH/PRV_MTH_ST_TEST/DATA.30 | head -1" command.
Output was - This was supposed to be a 64bits.
0000000 acef 010c 0000 001e 0000 0000 0000 0001
I ran the command against a different hash file which was not changed to 64 and the output was still the same as above.
Where i went wrong?
Thanks
Here is the part you missed:
If they show acef 010c (or 010c acef on an Intel CPU), then it is a 32-bit hashed file.
If they show acef 020c (or 020c acef on an Intel CPU), then it is a 64-bit hashed file.
For static hashed files, omit the "/DATA.30" from the hashed file pathname.
So maybe both hashed files are 32 bit.
If they show acef 010c (or 010c acef on an Intel CPU), then it is a 32-bit hashed file.
If they show acef 020c (or 020c acef on an Intel CPU), then it is a 64-bit hashed file.
For static hashed files, omit the "/DATA.30" from the hashed file pathname.
So maybe both hashed files are 32 bit.
Mamu Kim
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Your hashed file was created successfully but not as a 64-bit hashed file. I don't know why; your mkdbfile command looks OK. Can you perhaps try it with the -64BIT option in upper case? How did you execute the mkdbfile command? For example, was it through ExecSH?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.