View previous topic :: View next topic
|
Author |
Message |
Kavitha SG
New User
Joined: 18 Feb 2011 Posts: 9 Location: Chennai
|
|
|
|
Hi...
I am facing ABEND U2222 in an cobol program which does area sweep of an IDMS DB. Kindly help me..
Thanks!! |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
Look in the source where the program calls "ABORT" to find which condition raised the abend. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
are You able to follow a logical process ?
read the manuals, as adviced for Your other topic
ibmmainframes.com/viewtopic.php?t=53530&highlight=
repeat on
Uxxxx are user abends
with the help of Your support determine which component issued the abend
IDMS/LANGUAGE ENVIRONMENT/COBOL/YOUR PROGRAM
read the appropriate manual, take with the help of your support the action described in the manuals |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Why do/did you believe this would not use the same diagnosis process as your other topic about a User Abend . . . |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
Quote: |
Why do/did you believe this would not use the same diagnosis process as your other topic about a User Abend . . |
because on the other topic he got a solution without disturbing his neurons |
|
Back to top |
|
|
Meenakshi Selvaraj
New User
Joined: 30 Oct 2009 Posts: 36 Location: Chennai
|
|
|
|
Hi Kavitha,
Before post your queries, check the existing topics. it is helpful to you.
If there is any abend in the IDMS, follow the steps to find out the abend details.
1.Identifying IDMS errors in Job Output (SYSOUT)
2. If there is any User abend like UXXXX (XXXX is the user abend), look for error-status
For Example:
10.16.46 JOB05801 IEF450I NRWDTSTE STEP01 - ABEND=S000 U2222 REASON=00000000
TIME=10.16.46
10.16.46 JOB05801 *END STEP STEP01 OF NRWDTSTE TIME 10:16 **** ABEND U2222
3. Do the following FIND command: “F ABORTING”
For Example:
10.16.46 JOB05801 +************************** ABORTING - TESTERR1, 1477,
4. After finding error-status, look for other IDMS diagnostics at bottom of //SYSOUT.
For Example:
10.16.46 JOB05801 +************************** ABORTING - TESTERR1, 1477,
TESTERR1 (the word after ABORTING”) is the problem program name. 1477 is the errorstatus.
A related IDMS DB message is “IDMS DB347011 dbname xxxxxxx invalid.”
For Example: for the error is 1477, then
Major code: 14: BIND
Minor Code: 77
Summary/Suggested Action:
The run unit has not been bound or has been bound twice.
Possible Causes:
1) A DML statement has been issued before the required initial “BIND RUN-UNIT” statement.
2) More than one “BIND RUNUNIT” statement has been issued.
3) No “BIND RUN-UNIT”statement was issued after a “FINISH”or “ROLLBACK” but other DML commands were
attempted.
4) The program got a different IDMS ERROR-STATUS on the prior verb, causing the run unit to terminate. The program code failed to check for this error, and allowed the program to continue, thus leaving the real cause of the error unknown.
you can get these kinds of details in the IDMS Documentation - Major and Minor error code details.
Regards,
Meenakshi |
|
Back to top |
|
|
Kavitha SG
New User
Joined: 18 Feb 2011 Posts: 9 Location: Chennai
|
|
|
|
Hi Meenakshi..
you gave me good info how to analyse the error.. thank you.. am facing this abend due to 0365.. it says that its due to IDMS statements. Its a wonder, when i run for production DB it goes fine if i run for test DBs it fails.. i will let you know if i find the reason behind it.. anyhow thank you very much.. :-)
Kind regards,
Kavitha |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
It sounds like your problem is that inconsistent/incorrect data in the test environment is pointing out a problem in the code. The code should not abend (unless this is a User abend to point out the bad data). |
|
Back to top |
|
|
|