Originally posted by: SystemAdmin

Our Event Server is shutting down without any indication that there is an issue. When it happens, we see the following message in the EventServer Log:

"System DSTX_HIPAA_Compliance.msl;Msg_Mgr.msl; etc. has stopped with result 143."

What is "result 143" ? What could be our issue ?

We are running DSTX 8.0 in a Windows environment interfacing with Sybase DB.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SPG

Have you checked the compound system log if that tells you anything /
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

We have, and there is nothing. The last entry in the Compound System Log happened more than 1 hour before the shutdown recorded in the Event Server Log.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: jvanboga

Compound system file will not be updated if the system is shutting down as described.

look for gpf file(s) in 8.0 directory.

#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: jvanboga

Look for issues related to resource conflicts in your systems. Hard to narrow down sometimes but possible. Also, search this forum for similar issues. Seems like it's been posted here before. If you can't find it here you can also search the DSXchange and Tek Tips forums. One of them might have what you are looking for.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: janhess

I've had this on Windows and it's always been resoource conflict but there has also been a GPF as well.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Oh yes, we have been getting the GPF's. But they don't say much... see attached files

#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: jvanboga

Did you attach the file or am I missing it?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: jvanboga

See it now. Looks like you have a conflict related to your DB Connections.

Can you tell which resource ran @ 8:53:41? If so, it might help. Also, do you see anything in the sessions's "MessageManager.msl*.txt" occuring about that time? In addition, in the same file do you see any warnings similar to below?

==============================================================================

• STARTUP:

Status: Successful
Time: Tue Aug 15 14:31:08 2006

WARNING: Watch 36 - Unknown input path found:
D:\IBM\DSTX80\cmgr_v7.7\mmgr\-QN .
==============================================================================
.
.
.

Or some indication in the Mgmnt Console log that might point to the system file that might be in conflict?

Event Server:localhost
SystemFile1.msl System Not Responding
Another thought, a bit harder in production but.... I have systems that have been deployed for years and some that are newer. If you can't determine which deployed system is causing the gpf try renaming any system file(s) that's been deployed since the gpfs started. Test the condition that seems to occur then implement each system one by one until you ID which one causes the problem. Then go over the related MSD file until you narrow down the issue. (you could also restore all msl files to their status at a time prior to the issue appearing). In this case I'd focus on systems that touch your DB.

Also, could you post your DB setting from your ini file?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Have you got your database update keys defined correctly? In my experience update keys are compiled into the map, not picked up from the mdq at run time. Do you have a database trace file related to the failing action?
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

In my old shop, we used to get the same exact message.

First, I believe there is a setting in the ini file that says either shut down when a GPF happens, or keep running. I'd go straight to that, but from what I recall, it still happened, though very seldom.
Second, we never truly resolved it, we kept getting the GPF, but it stopped shutting down.

When we call the support, they couldn't identify the problem exactly nor tried to, but instead, we sent them a copy of our ini, a copy of the compound system log, and possibly some other log, and they gave us recommendations for settings to change, and looked for items that could have been better.

Good luck! I have to run now, but if I think of anything else, Ill be sure to write back.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

The ini file setting is
IgnoreGPFs=1 in Connections Manager section. It's supposed to make the map fail rather than Launcher but I haven't found it makes any difference when it's a contention issue.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: jvanboga

I believe you are correct, janhess. We have the switch set to fail the map but on rare occation we still get a system shut down. Very infrequent and it usually ties back to a recent deployment that can be backed out until resolved.

for what its worth, googling the message code comes up with numerous hits typically revolving around access violations.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender