U3134 in IDMS program while doing area sweep

arun.gopal · Posted: Fri Nov 26, 2010 1:12 pm

HI,

I can see simillar question some one asked some where arround Aug 2005. But there also I didnt find any helpful info by which we were able to resolve. So I just made sure I am not repeating this question.

Im getting a U3134 while doing a area sweep of a record. This issue is not happening if we are running for few thousand record. Can see when it tries to obtain more than 1lack record this issue is coming.
We tried disable the limits both external and online. Still this issue is coming.

Some where I read this can be corrected if we are changing the complier option, but no where mentioned which option to use.

We are using ENDEVOR to complie the IDMS program. And the default complier options are,
//* ** NOADV, APOST, NOAWO, BUFSIZE(4096), NOCMPR2, NOCOMPILE(W), *
//* ** DATA(31), NODBCS, NODECK, NODUMP, NODYNAM, NOEXIT, NOFASTSRT, *
//* ** NOFDUMP, FLAG(I,W), NOFLAGMIG, NOFLAGSAA, NOFLAGSTD, *
//* ** LANGUAGE(EN), LIB, LINECOUNT(60), NOLIST, MAP, NONAME, *
//* ** NONUMBER, NUMPROC(NOPFD), OBJECT, OFFSET, NOOPTIMIZE, *
//* ** OUTDD(SYSOUT), RENT, RESIDENT, NOSEQUENCE, SIZE(MAX), *
//* ** SOURCE, SPACE(1), SSRANGE, NOTERM, NOTEST, TRUNC(STD), *
//* ** NOVBREF, NOWORD, XREF(FULL), ZWB *

Please see the error message from JCL output..

IDMSDMCL module not found - R15 return code X'14'
IDMS job abending with abend code 5004
#ABEND from Module IDMSBLDR at Location 15572038 Offset 008828
SYSTEM mode registers at entry to #ABEND
R0/R8 R1/R9 R2/R10 R3/R11 R4/R12 R5/R13 R6/R14 R
00000000 15534C50 0000138C 1558341B 0006BB80 15534C50 95572038 15
15535060 0006B2F8 00062068 0006BB80 1557A53C 0006BCE0 9557A860 15
USER mode registers at entry to #ABEND
R0/R8 R1/R9 R2/R10 R3/R11 R4/R12 R5/R13 R6/R14 R
E5C9C2C1 00049058 0004A3E8 0000006A 0004A758 00000000 009C9FE0 00
0007E3E8 0004A028 00062068 00008F7C 6000A4C0 00048E80 0007E5E0 00

If any one has any thought over this let me know...

Thanks in Advance,
Arun....

dick scherrer · Posted: Sat Nov 27, 2010 8:43 am

Hello,

What does the documentation have regarding this error?

Post what you read about changing compiler options and possibly someone can clarify.

enrico-sorichetti · Posted: Sat Nov 27, 2010 2:29 pm

U3134 is a user abend,
You your support have to understand whether it is an IDMS or a COBOL or a Language environment abend

after that following the advices given by the manuals should be easy enough!

before hitting the submit button I reread ( as I usually do ) the starting post and I found

Meenakshi Selvaraj · New User Joined: 30 Oct 2009 Posts: 36 Location: Chennai

Hi Arun,

As enrico-sorichetti said, U3134 is a user abend. 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 (do the following FIND command: “F ABORTING”)
3. After finding error-status, look for other IDMS diagnostics at bottom of //SYSOUT.
You mentioned that you got 5004, it may be the following reason.

Major code may be anything say nn
Minor code - 04
Summary/Suggested Action - Bad value in OCCURS DEPENDING ON
Possible Causes
1) Look for an “occurs depending on” in the IDMS record layout.
2) Might be less than zero or greater than maximum
3) Wrong Subschema

you can get these kinds of details in the IDMS Documentation - Major and Minor error code details.

4. And also check the DC###### (6 digit) Abend Messages in the job log. These details will give you the clear idea about the abend details.

Kavitha SG · New User Joined: 18 Feb 2011 Posts: 9 Location: Chennai

check whether you have gievn SYSJRNL dd card or not.