|
View previous topic :: View next topic
|
| Author |
Message |
vankarthik
New User
Joined: 31 Dec 2010
Posts: 4
Location: Pune
|
|
|
|
| I have just used a GU with a qualified segment which performed well for the first account.. But for the second account its showing AC.. Can some one say the reason?? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
vankarthik
New User
Joined: 31 Dec 2010
Posts: 4
Location: Pune
|
|
|
|
| sorry enrico.. |
|
| Back to top |
|
|
vankarthik
New User
Joined: 31 Dec 2010
Posts: 4
Location: Pune
|
|
|
|
Since my question was related to that same topic.. i just posted there...
Thanks,
Karthik |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
AC Status code is pretty straight forward, have you checked the possibilty of any of these:
| Quote: |
- DL/ I could not find a segment in the DB PCB specified in the call that has the segment name given in the SSA.
- The segment name is in the DB PCB, but the SSA specifying that segment name is not in its correct hierarchic sequence.
- The call specifies two SSAs for the same hierarchic level. |
|
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
Hmmm...
Are you telling me the same call worked once, but not the second time? As in, the SSA worked, but you change the value of the key in the SSA, and it didn't work?
If I had to guess, I'd say you accidentally changed the SSA by more than the key value.
Here's a great trick to help with these types of problems: turn on DLI Trace.
Find the DFSVSAMP DD statement in your job, and add this line to the bottom:
Then add a new DD like this:
| Code: |
//DFSTROUT DD SYSOUT=*
|
Don't run a lot of data through it, because the output can be very large.
This will show you all of the IMS calls and how they are being formatted. It's helped me find a LOT of stupid mistakes that I just couldn't see when looking at the code.
If we were betting a cup of coffee, I'd say your first call is UNQUALIFIED, but then somewhere in the program, it's QUALIFYING it so that IMS sees the badly formed SSA. So you'll see something like:
On the first call, then something like:
| Code: |
GU SEGNAME*---(KEYNAME EQxxxxxxx)
|
for the second call, and you'll be able to see that the SEGMENT, KEYNAME, or KEY VALUE is not correct. |
|
| Back to top |
|
|
vankarthik
New User
Joined: 31 Dec 2010
Posts: 4
Location: Pune
|
|
|
|
Thanks Anuj & Ed.
I found the mistake. Actually the qualified ssa had a path call. I just commented it out and defined a qualified ssa again with different key name with path call (since it was used at another place). And it ran fine. 
Thanks,
Karthik |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
| Dang, now I owe you a coffee! If I'm ever in Pune, I'll look you up. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Ed Goodman wrote: |
| Dang, now I owe you a coffee! If I'm ever in Pune, I'll look you up. |
If you do so, come to Mumbai too - just 4 hrs, by road, away from Pune.  |
|
| Back to top |
|
|
|
|
