IBM Mainframe Forum

Posted: **Tue Dec 03, 2013 7:04 pm**

Hi all,

I get this below when I compile a program which is COBOL WITH DB2 + Xpediter, and I don't get this if I exclude the Xpediter.

Suggestions please...

Select all

+WER999A xxxxxxNQ,NDVRSCL ,C1BM3000- UNSUCCESSFUL SORT B37 S REASON=00000004
IEA995I SYMPTOM DUMP OUTPUT 380
SYSTEM COMPLETION CODE=B37 REASON CODE=00000004
TIME=04.19.59 SEQ=50962 CPU=0000 ASID=0183
PSW AT TIME OF ERROR 475C1000 80DF0916 ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00DF0910 - 41003038 0A0DB20A 00509808
AR/GR 0: 00975168/00DF0B24 1: 00000000/A4B37000
2: 00000000/001822D0 3: 00000000/00DF0AEC
4: 00000000/00953420 5: 00000000/00E35000
6: 00000000/009536C4 7: 00000000/0095371C
8: 00000000/009536E4 9: 00000000/009768A0
A: 00000000/009BEDF8 B: 00000000/00DF05A2
C: 00000000/009BF7CC D: 00000000/7F344D20
E: 00000000/00DF05A2 F: 01000002/00000004
END OF SYMPTOM DUMP

Thanks

Posted: **Tue Dec 03, 2013 7:31 pm**

WERxxx messages are Syncsort messages. Syncsort does not "compile" anything.
A system B37 ABEND is generally a problem with a data set. There should be a related IEC030I message in the JESMSGLG data set for the failing job. What does this message say? Did you look up this message and attempt to match the message explanation to your environment? The people that respond to issues in this forum need this information before they can provide anything resembling useful assistance.

Posted: **Tue Dec 03, 2013 8:56 pm**

It might be that the Xpeditor step is trying to sort the program offsets or something. The B37 should be associated with an output file in the JCL. If you see a file name that is NOT in the JCL, then what could be happening is that SMS (stopx37 maybe?) is allocating a tiny file to prevent an I/O error. Find that DD name and add space for it and make sure it's explicitly defined in the JCL.

No matter what, your first task is to identify which DD is getting that B37. Once you know that, you're on your way to fixing the problem.

Posted: **Wed Dec 04, 2013 10:39 am**

steve-myers wrote:
WERxxx messages are Syncsort messages. Syncsort does not "compile" anything.
A system B37 ABEND is generally a problem with a data set. There should be a related IEC030I message in the JESMSGLG data set for the failing job. What does this message say? Did you look up this message and attempt to match the message explanation to your environment? The people that respond to issues in this forum need this information before they can provide anything resembling useful assistance.

here is

Select all

IEC030I B37-04,IFG0554A,xxxxxxNQ,C1BM3000,CWPWRK1,VIO ,
SYS13337.T041957.RA000.xxxxxxNQ.R0546659

Posted: **Wed Dec 04, 2013 10:43 am**

Ed Goodman wrote:It might be that the Xpeditor step is trying to sort the program offsets or something. The B37 should be associated with an output file in the JCL. If you see a file name that is NOT in the JCL, then what could be happening is that SMS (stopx37 maybe?) is allocating a tiny file to prevent an I/O error. Find that DD name and add space for it and make sure it's explicitly defined in the JCL.

No matter what, your first task is to identify which DD is getting that B37. Once you know that, you're on your way to fixing the problem.

Here is

Select all

IGD101I SMS ALLOCATED TO DDNAME (CWPWRK1 )
DSN (SYS13337.T041957.RA000.xxxxxxNQ.R0546659 )
STORCLAS (VIO) MGMTCLAS ( ) DATACLAS (DEFAULT)
VOL SER NOS= VIO

It seems, I can't add space to it. I need to contact admin or someone. Right? Advice please....

Posted: **Wed Dec 04, 2013 12:12 pm**

Look at the JCL for the step that failed to see if there is a CWPWRK1 DD statement. If there is, increase the space.
If there is no CWPWRK1 DD statement, add one. As an experiment specify SPACE=(CYL,(1,1)),UNIT=SYSDA. If the step then complains it cannot allocate a CWPWRK1 data set, you are probably out of luck, but the documentation may provide a mechanism to specify a larger allocation.

Posted: **Wed Dec 04, 2013 2:24 pm**

steve-myers wrote:
Look at the JCL for the step that failed to see if there is a CWPWRK1 DD statement. If there is, increase the space.
If there is no CWPWRK1 DD statement, add one. As an experiment specify SPACE=(CYL,(1,1)),UNIT=SYSDA. If the step then complains it cannot allocate a CWPWRK1 data set, you are probably out of luck, but the documentation may provide a mechanism to specify a larger allocation.

Tried. I am out of luck. Thank you so much.

Posted: **Wed Dec 04, 2013 6:23 pm**

Is not C1BM3000 an Endevor component that accepts requests from a workstation?

Posted: **Wed Dec 04, 2013 9:03 pm**

I'm not trying to embarrass you here, but HOW did you try to add the DD statement? After you tried, did the same B37 message show up?

The DD should have looked something like this:

Select all

//CWPWRK0 DD SPACE=(TRK,(60,30)),UNIT=SYSDA
//CWPWRK1 DD SPACE=(TRK,(60,30)),UNIT=SYSDA
//CWPWRK2 DD SPACE=(TRK,(60,30)),UNIT=SYSDA
//CWPWRK3 DD SPACE=(TRK,(60,30)),UNIT=SYSDA
//CWPWRK4 DD SPACE=(TRK,(60,30)),UNIT=SYSDA
//CWPWRK5 DD SPACE=(TRK,(60,30)),UNIT=SYSDA

I'm asking because you seem a little over your head, and you may not be that experienced in JCL, and so a small mistake may have made it so the DD was not recognized in the correct step.

Posted: **Thu Dec 05, 2013 11:53 am**

Akatsukami wrote:Is not C1BM3000 an Endevor component that accepts requests from a workstation?

Yes I use endevor to compile my element.

IBM Mainframe Forum

Compilation error +WER999A

Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A

Re: Compilation error +WER999A