View previous topic :: View next topic
|
Author |
Message |
narasimha.g
New User
Joined: 10 Sep 2009 Posts: 68 Location: Liverpool
|
|
|
|
Hi All,
I am getting the following error when i am trying to insert a new segment into the databse.
Code: |
+** IGZSAL contains version of IGZERRE dated 25/08/1989. **
+** L20456Q9 Region will be treated as COBOL II ** 448
+TCS0341 - TRCEFILE or LOGSYSIN not defined in region. No trace set.
+TCS0411 - L20456Q9 is running in a region of 0216K
+TCSOCM03 - SETABLE and ANTABLEs built
+DFS0578I - READ SUCCESSFUL FOR DDNAME PROCLIB MEMBER = IMSLSSM1 IMSL
+ISRT - STELLA ROOT STATUS = II REF = 019780514 *
INVALID MESSAGE
DFS0782I NO INFO ABOUT ABENDING MODULE - R12 NOT POINTING CHANGEID IMSL
IEA995I SYMPTOM DUMP OUTPUT 546
USER COMPLETION CODE=0001
TIME=10.50.23 SEQ=08697 CPU=0000 ASID=0060
PSW AT TIME OF ERROR 078D1000 002B3A08 ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=002B06F8 OFFSET=00003310
NAME=PRICEPRO
DATA AT PSW 002B3A02 - 5810F010 0A0D8000 00010000 |
could you please let me know wat the problem is...?? |
|
Back to top |
|
|
narasimha.g
New User
Joined: 10 Sep 2009 Posts: 68 Location: Liverpool
|
|
|
|
Is it a Duplicate Key Error????? |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
Start with your colleagues. See if the output looks "normal" to them for the system you are working on.
Things don't look right about the messages, but I've no idea if that is how they are supposed to look. Let us know. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
Is it a Duplicate Key Error????? |
Why might you think this?
Because the II indicates a duplicate. . .(Edited)
Quote: |
USER COMPLETION CODE=0001 |
Look in the documentation for the program for the cause of a User 0001. . . Or look in the code itself. |
|
Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
To help you a little bit... IMS returns an II status code when a segment being inserted has a key that matches a key that is already in the database, AND the database is set up to not allow duplicate keys on that segment.
From what you posted, it's probably a key with value "019780514". |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Thanks Ed,
I don't "do" IMS (and did not even note the status), but was hoping to provide a nudge. . .
Quote: |
Is it a Duplicate Key Error????? |
Looks like it is
d |
|
Back to top |
|
|
narasimha.g
New User
Joined: 10 Sep 2009 Posts: 68 Location: Liverpool
|
|
|
|
Thanks Dick and Ed.... The problem is now resolved... |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
narasimha.g wrote: |
Thanks Dick and Ed.... The problem is now resolved... |
It'd be nice for us, if you could share the solution you've used. |
|
Back to top |
|
|
narasimha.g
New User
Joined: 10 Sep 2009 Posts: 68 Location: Liverpool
|
|
|
|
Anuj Dhawan wrote: |
narasimha.g wrote: |
Thanks Dick and Ed.... The problem is now resolved... |
It'd be nice for us, if you could share the solution you've used. |
Ya problem was because of the duplicate key as the database already had the data for some years.... and i had the whole dump of data in my file...
Donno to wat extent its a good programming practice but i just stopped the program from abending for status II as i neither wanted the already existing data to be inserted again nor the program to abend at that record but to continue with the remaining records in the input file..... |
|
Back to top |
|
|
|