i am ending with status of AJ and AC while accessing child segments through GNP calls. please note that, both of these segments are at level 2 and parentage has been established at level 1.
since we do not have the key for the segments at level 2, i have coded unqualified SSAs for level 2 segments. and since i have only partial key value for the segment at level 1, i have coded the relational operator as '>='.
i know the meaning for these status codes but all i need to know is a good fix for them. as of now, i have resolved these by following the same technique for the SSA to segments at level 2 (passing '>=' relational operator with the key field as SPACES for segment at level 2)
i would like to give an important update that, i am accessing the root segment through secondary index.
please let me know for any queries. looking forward for your response...
Joined: 13 Jun 2007 Posts: 826 Location: Wilmington, DE
First of all why are you setting parentage? If you know the segment names and the structure of the database, using a fully loaded root key and an unqualified SSA for each segment type below the root will get you where you want to be.
You simply "do loop" with your fully loaded root SSA followed by you unqualified child SSA unitl you get either GB (end of data base) or GE (not found). You will not need to check for GA or GK - you will not need to set parentage.
Joined: 07 Nov 2005 Posts: 1105 Location: The Netherlands at Hole 19
As I understand it you found the desired root using >= and subsequently performed a GNP on the child also with >= SPACES. Could you explain why you did this? A command code *F would work to find the first dependent.
Further the status codes explain your SSA is not in order with the PCB. So.... like Sandy posted: give us the calls and the logical DBD since you work with SI.