Skip to main content

1)Errors coming from one of cobol program .
Different errors coming in eslog at different times
a)
220630 16532697 90622 ESDEMO64 CASCS5100I Communications Process instance 01 is ready to accept requests 16:53:26
220630 17093438 90636 ESDEMO64 CASMG0001I inside nlnqtn prog :00 17:09:34
220630 17093438 90636 ESDEMO64 CASMG0001I Inside svlnqtn 00 17:09:34
220630 17094378 90636 ESDEMO64 CASMG0001I inside nlnqtn prog :00 17:09:43
220630 17094378 90636 ESDEMO64 CASMG0001I Inside svlnqtn 00 17:09:43
220630 17094435 CASCD0154S SEP 00002 for ES ESDEMO64 abended by signal 0000000011 17:09:44
220630 17094472 91070 ESDEMO64 CASSP0002I Server manager informed of process termination, pinfo = S,0000090636 17:09:44
220630 17094572 90611 ESDEMO64 CASKC0041E Transaction abend . The task has terminated abnormally because of a program check. 17:09:45
220630 17094572 CASCD0127I SEP 00003 created for ES ESDEMO64, process-id = 91080 17:09:45
220630 17094572 91080 ESDEMO64 CASSI1500I SEP initialization started 17:09:45
220630 17094573 91080 ESDEMO64 CASSI1600I SEP initialization completed successfully 17:09:45

b)
220630 18513283 21414 ESDEMO64 CASKC0027E Error executing service 'www.lic.com/.../SWOLoanQuotationWS
Execution error : file '/efeap/bin/db-connect.gnt'^@
error code: 114, pc=0, call=1, seg=0^@
114 Attempt to access item beyond bounds of memory (Signal 11) 18:51:32
220630 18513283 CASCD0127I SEP 00004 created for ES ESDEMO64, process-id = 21702 18:51:32
220630 18513283 21414 ESDEMO64 CASKC0003I SEP 0000021414 shutdown complete. 18:51:32
220630 18513284 21702 ESDEMO64 CASSI1500I SEP initialization started 18:51:32
220630 18513285 21702 ESDEMO64 CASSI1600I SEP initialization completed successfully 18:51:32
220630 18514839 21702 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:51:48
220630 18514839 21702 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:51:48
220630 18514984 21702 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:51:49
220630 18514984 21702 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:51:49
220630 18514987 21702 ESDEMO64 CASMG0001I rule-plans. 014 18:51:49
220630 18514989 21702 ESDEMO64 CASMG0001I Going back 18:51:49
220630 18514989 21702 ESDEMO64 CASKC0027E Error executing service 'www.lic.com/.../SWOLoanQuotationWS
Execution error : file '/efeap/bin/getfilename.gnt'^@
error code: 166, pc=0, call=1, seg=0^@
166 Recursive COBOL CALL is illegal 18:51:49

c)
220630 18533301 21702 ESDEMO64 CASXO0023S Severe error detected in odbc XA interface, RM interface disabled 18:53:33
220630 18533401 21702 ESDEMO64 CASSP0011S Syncpoint COMMIT failure - resource state unpredictable 18:53:34
220630 18533402 21702 ESDEMO64 CASKC0026E Error unloading service 'www.lic.com/.../SWOLoanQuotationWS
9076 Transaction commit failed 18:53:34

d)
220630 18572105 22050 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:57:21
220630 18572105 22050 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:57:21
220630 18572284 22050 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:57:22
220630 18572284 22050 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:57:22
220630 18572287 22050 ESDEMO64 CASMG0001I rule-plans. 014 18:57:22
220630 18572288 22050 ESDEMO64 CASMG0001I Going back 18:57:22
220630 18572288 22050 ESDEMO64 CASSP0014S Process termination due to RTS error. ^@
Execution error : file 'cashtsrv'^@
error code: 115, pc=0, call=1, seg=0^@
115 Unexpected signal (Signal 6) 18:57:22


Can you please help us to find out reason, why we are facing this issue.

1)Errors coming from one of cobol program .
Different errors coming in eslog at different times
a)
220630 16532697 90622 ESDEMO64 CASCS5100I Communications Process instance 01 is ready to accept requests 16:53:26
220630 17093438 90636 ESDEMO64 CASMG0001I inside nlnqtn prog :00 17:09:34
220630 17093438 90636 ESDEMO64 CASMG0001I Inside svlnqtn 00 17:09:34
220630 17094378 90636 ESDEMO64 CASMG0001I inside nlnqtn prog :00 17:09:43
220630 17094378 90636 ESDEMO64 CASMG0001I Inside svlnqtn 00 17:09:43
220630 17094435 CASCD0154S SEP 00002 for ES ESDEMO64 abended by signal 0000000011 17:09:44
220630 17094472 91070 ESDEMO64 CASSP0002I Server manager informed of process termination, pinfo = S,0000090636 17:09:44
220630 17094572 90611 ESDEMO64 CASKC0041E Transaction abend . The task has terminated abnormally because of a program check. 17:09:45
220630 17094572 CASCD0127I SEP 00003 created for ES ESDEMO64, process-id = 91080 17:09:45
220630 17094572 91080 ESDEMO64 CASSI1500I SEP initialization started 17:09:45
220630 17094573 91080 ESDEMO64 CASSI1600I SEP initialization completed successfully 17:09:45

b)
220630 18513283 21414 ESDEMO64 CASKC0027E Error executing service 'www.lic.com/.../SWOLoanQuotationWS
Execution error : file '/efeap/bin/db-connect.gnt'^@
error code: 114, pc=0, call=1, seg=0^@
114 Attempt to access item beyond bounds of memory (Signal 11) 18:51:32
220630 18513283 CASCD0127I SEP 00004 created for ES ESDEMO64, process-id = 21702 18:51:32
220630 18513283 21414 ESDEMO64 CASKC0003I SEP 0000021414 shutdown complete. 18:51:32
220630 18513284 21702 ESDEMO64 CASSI1500I SEP initialization started 18:51:32
220630 18513285 21702 ESDEMO64 CASSI1600I SEP initialization completed successfully 18:51:32
220630 18514839 21702 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:51:48
220630 18514839 21702 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:51:48
220630 18514984 21702 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:51:49
220630 18514984 21702 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:51:49
220630 18514987 21702 ESDEMO64 CASMG0001I rule-plans. 014 18:51:49
220630 18514989 21702 ESDEMO64 CASMG0001I Going back 18:51:49
220630 18514989 21702 ESDEMO64 CASKC0027E Error executing service 'www.lic.com/.../SWOLoanQuotationWS
Execution error : file '/efeap/bin/getfilename.gnt'^@
error code: 166, pc=0, call=1, seg=0^@
166 Recursive COBOL CALL is illegal 18:51:49

c)
220630 18533301 21702 ESDEMO64 CASXO0023S Severe error detected in odbc XA interface, RM interface disabled 18:53:33
220630 18533401 21702 ESDEMO64 CASSP0011S Syncpoint COMMIT failure - resource state unpredictable 18:53:34
220630 18533402 21702 ESDEMO64 CASKC0026E Error unloading service 'www.lic.com/.../SWOLoanQuotationWS
9076 Transaction commit failed 18:53:34

d)
220630 18572105 22050 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:57:21
220630 18572105 22050 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:57:21
220630 18572284 22050 ESDEMO64 CASMG0001I inside nlnqtn prog :00 18:57:22
220630 18572284 22050 ESDEMO64 CASMG0001I Inside svlnqtn 00 18:57:22
220630 18572287 22050 ESDEMO64 CASMG0001I rule-plans. 014 18:57:22
220630 18572288 22050 ESDEMO64 CASMG0001I Going back 18:57:22
220630 18572288 22050 ESDEMO64 CASSP0014S Process termination due to RTS error. ^@
Execution error : file 'cashtsrv'^@
error code: 115, pc=0, call=1, seg=0^@
115 Unexpected signal (Signal 6) 18:57:22


Can you please help us to find out reason, why we are facing this issue.

Hello Sanjay Singh,

 

I'm guessing this is a COBOL application built to a SOAP or REST web service?

 

You've shown several different Runtime System errors, happening at different times as you pointed out. Does the Web Service ever work successfully? Have you tried debugging it?

 

Finally, investigating issues with Enterprise Server can be complex, and might require gathering diagnostics that should not be shared on a public forum. For these reasons (and to get faster assistance) you might want to create a Support Case for this problem.


Hello Sanjay Singh,

 

I'm guessing this is a COBOL application built to a SOAP or REST web service?

 

You've shown several different Runtime System errors, happening at different times as you pointed out. Does the Web Service ever work successfully? Have you tried debugging it?

 

Finally, investigating issues with Enterprise Server can be complex, and might require gathering diagnostics that should not be shared on a public forum. For these reasons (and to get faster assistance) you might want to create a Support Case for this problem.

I'm guessing this is a COBOL application built to a SOAP or REST web service? --> SOAP Service

You've shown several different Runtime System errors, happening at different times as you pointed out. Does the Web Service ever work successfully? Have you tried debugging it? --> It has not worked single time successfully, we have not tried with debugging, we will try with debugging.