|
View previous topic :: View next topic
|
| Author |
Message |
Jonai
New User
Joined: 03 Jun 2008
Posts: 11
Location: Hyderabad
|
|
|
|
Hi all,
I am getting Status code AK with a qualified GU call while accessing secondary index database.Call is a DLI call..
Field name is same as defined in DBD..
Can anyone help me out in this ..
Thanks ,
Jonai. |
|
| Back to top |
|
 |
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India
|
|
|
|
Hi,
What does manuals have to say about this? |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India
|
|
|
|
Hi again,
This might help you:
| Quote: |
AK: Explanation: For call- level programs: An SSA contains an invalid field name, or the field name is not defined in the DBD. The number in the segment level number field of the DB PCB is the level number of the SSA that contains the invalid name.
You can also receive this status code if the program is accessing a logical child through the logical parent. DL/ I returns AK if the field specified in the qualification has been defined for the logical child segment, and it includes (at least partially) the portion of the logical child that contains the concatenated key of the logical parent.
When you are using field- level sensitivity, a field you specified in the SSA has not been defined in the PSB. After this status code is returned, your position in the database is unchanged.
For command- level programs: A WHERE option contains an invalid field name. ( The field name is not defined in the DBD.) The number in the DIBSEGLV field of the DIB is the level number of the WHERE option that contains the invalid name.
Programmer Response: Correct the SSA or WHERE option. |
|
|
| Back to top |
|
|
Jonai
New User
Joined: 03 Jun 2008
Posts: 11
Location: Hyderabad
|
|
|
|
Thnaks for the reply Anuj..
Regards,
Jonai. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India
|
|
|
|
You're welcome ... hope you are making progress...  |
|
| Back to top |
|
|
|
|
