Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

IMS Call with AJ and AC status.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IMS DB/DC
View previous topic :: :: View next topic  
Author Message
gowtham_1982
Warnings : 1

Active User


Joined: 02 Dec 2005
Posts: 109

PostPosted: Tue Mar 04, 2008 9:55 am    Post subject: IMS Call with AJ and AC status.
Reply with quote

hi,

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...

kind regards,

gowtham
Back to top
View user's profile Send private message

Sandy Zimmer

Active Member


Joined: 13 Jun 2007
Posts: 826
Location: Wilmington, DE

PostPosted: Tue Mar 04, 2008 6:10 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
Bitneuker

CICS Moderator


Joined: 07 Nov 2005
Posts: 1105
Location: The Netherlands at Hole 19

PostPosted: Wed Mar 05, 2008 12:35 am    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IMS DB/DC All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. session stuck in TPX with status ACL amitc23 CA Products 1 Tue Dec 13, 2016 12:53 pm
No new posts Cobol EZASOKET call to SETSOCKOPT fails Andi1982 COBOL Programming 6 Thu Oct 06, 2016 7:12 pm
No new posts Strange EXEC function call in z/VM Willy Jensen CLIST & REXX 3 Wed Oct 05, 2016 2:07 pm
No new posts COBOL DB2 - CALL statement - high CPU... TS70363 DB2 15 Sun Sep 11, 2016 6:07 am
No new posts Is possible to call subprogram from c... cmsmoon COBOL Programming 3 Fri Aug 05, 2016 6:46 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us