|
View previous topic :: View next topic
|
| Author |
Message |
kratos86
Active User
Joined: 17 Mar 2008
Posts: 148
Location: Anna NGR
|
|
|
|
I have a database where the database is defined in the below sturcture
| Code: |
1 ALEVEL0 Key Length = 27
2 BLEVEL1 Key Length = 8
3 CLEVEL1 Key Length = 3
2 BLEVEL2 Key Length = 15
3 CLEVEL2 Key Length = 37
2 BLEVEL3 Key Length = 23
3 CLEVEL3 Key Length = 3
2 BLEVEL4 Key Length = 13
|
When they calculate the key length for a psb accessing all the segments they are totalling to 90 bytes instead of 79 bytes which is the maximum length of a concatenated key.
Can anyone help me understand what i am missing here??? |
|
| Back to top |
|
 |
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
| I know it won't hurt anything to have it be longer. |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| Who did the KEYLEN calculation? It is possible that they made an error. |
|
| Back to top |
|
|
kratos86
Active User
Joined: 17 Mar 2008
Posts: 148
Location: Anna NGR
|
|
|
|
| It is provided by DBA and the code is running fine. |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
"Can anyone help me understand what i am missing here???"
It doesn't matter...that's what you're missing. |
|
| Back to top |
|
|
Gary Jacek
New User
Joined: 17 Dec 2007
Posts: 64
Location: Victoria, BC, Canada
|
|
|
|
Hi kratos86
If your KEYLEN specification is too small, your DBA should expect the following message during ACBGEN and you should expect the same message during execution of a Batch DLI job which uses
your PSB:
DFS0919I PSB-psbname-PCB-pcbname -KEYLEN SPECIFICATION TOO SMALL. KEYLEN SHOULD BE-xxxxx BYTES
Your DBA could simply observe the correct value shown in message DFS0919I, alter the value in the PSB source, and rerun the PSBGEN and ACBGEN.
If you are curious and you have access to ADFSSRC(DFSDLB00), ADFSSRC(DBFUDLB0) and ADFSSRC(DFSUMGT0), you should be able to examine the IMS code which issues message DFS0919I.
Since DFS0919I is an "I" level message, the return code may not be sufficient to trigger a "Code Not Running Fine" indication in your shop.
Gary |
|
| Back to top |
|
|
|
|
