| View previous topic :: View next topic |
| Author |
Message |
JoanIke
Beginner
Joined: 22 Aug 2006
Posts: 2
Topics: 1
Location: NJ
|
 Posted: Tue Aug 22, 2006 8:24 am Post subject: IMS abend AC |
 |
|
My batch pgm is returning AC on a GN statement.
It does a GU on the root segment and does several GN on other child segments.
A change was made recently to re-establish parentage on the root again and do several GN's on a child segment. (loops several times)
Then the program does a GN on another child segment (this is where it failed in production with AC).
My question is - do I have to establish parentage on the root segment again??? |
|
| Back to top |
|
 |
Sreejith
Intermediate
Joined: 02 Dec 2002
Posts: 155
Topics: 25
Location: N.Ireland
|
| Posted: Tue Aug 22, 2006 8:38 am Post subject: |
|
|
An AC means you have an in correct SSA or the segment you are trying to access is not defined in PSB. Since you didn't touch the PSB I guess it's the SSA. Do a Display of your SSA and see whether it got the stuff you wanted. I have seen cases where the SSA get corrupted by a DLI call if the IO-AREA is not big enough and the SSA is defined immediatley after IO_AREA.
Sreejith |
|
| Back to top |
|
|
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose
|
| Posted: Tue Aug 22, 2006 8:39 am Post subject: |
|
|
JoanIke,
Use P command code with a GNP call.
Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
JoanIke
Beginner
Joined: 22 Aug 2006
Posts: 2
Topics: 1
Location: NJ
|
| Posted: Tue Aug 22, 2006 9:04 am Post subject: |
|
|
| So the last GN call should be changed to GNP in order to retain the original parentage? It will not get lost from the previous loop? |
|
| Back to top |
|
|
shekar123
Advanced
Joined: 22 Jul 2005
Posts: 528
Topics: 90
Location: Bangalore India
|
| Posted: Tue Aug 22, 2006 9:36 am Post subject: |
|
|
JoanIke,
Some Info on Status code AC:
| Code: |
|------------------------------------------------------------------------|
| Table 35. Database Calls |
|-------|-------------|------|-------------------------------------------|
| PCB | | | |
| Status| Database | Cate-| |
| Code | Calls | gory | Description |
|-------|-------------|------|-------------------------------------------|
| AC | GU, GHU | 4 | Hierarchic error in SSAs. |
| | GN, GHN | | |
| | GNP, GHNP | | |
| | DLET, REPL | | |
| | ISRT (LOAD) | | |
| | ISRT (ADD) | | |
|-------|-------------|------|-------------------------------------------|
|------------------------------------------------------------------------|
| Table 37. System Service Calls |
|-------|-------------|------|-------------------------------------------|
| PCB | System | | |
| Status| Service | Cate-| |
| Code | Calls | gory | Description |
|-------|-------------|------|-------------------------------------------|
| AC | STAT(1) | 4 | Hierarchic error in SSAs. |
|-------|-------------|------|-------------------------------------------|
AC
Explanation:
For call-level programs:
An error is in an SSA for a DLET, Get, ISRT, or REPL call for one of these
reasons:
* 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.
IMS also returns this status code when a STAT (3) call has an invalid
statistics function. After this status code is returned, your position in
the database is unchanged.
For command-level programs:
An error is in one of the WHERE or SEGMENT options on a Get or ISRT
command for one of these reasons:
* DL/I could not find a segment in the DB PCB specified in the segment
name given in the SEGMENT option.
* The segment name is in the DB PCB, but the qualification for the
command does not specify it in its correct hierarchic sequence.
* The command specifies two SEGMENT options for the same hierarchic
level.
Programmer Response: Correct the segment name in the SSA or SEGMENT
option or in the statistics function of the STAT (3) call.
(3) STAT is a Product-sensitive programming interface. |
_________________
Shekar
Grow Technically |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
