IT05781: NDM ERROR AND FATAL EMS MESSAGES ARE NOT MARKED AS CRITICAL

3.6.0.1-SterlingConnectDirectforHPNonStop-x86-fp0001
3.6.0.1-SterlingConnectDirectforHPNonStop-MIPS_I64-ifix030
3.6.0.1-SterlingConnectDirectforHPNonStop-MIPS_I64-ifix025
3.6.0.1-SterlingConnectDirectforHPNonStop-MIPS_I64-ifix021

APAR status

• Closed as program error.

Error description

• In EMS several Error and Fatal messages were shown of the
  Session Manager processes but all of them were normal messages.
  As a result the failed transfers were not noticed.
  
  All Error and Fatal EMS messages should be marked as critical.
  Other messages should be marked as Normal.
  

Local fix

• STRRTC - 447164
  GL / SF
  Circumvention: None
  

Problem summary

• Users Affected:
  All C:D for HP NonStop users
  
  Problem Description:
  Many serious EMS errors emitted by C:D are not flagged as
  "critical". This occurs on all supported releases.
  Platforms Affected:
  MIPS, I64
  

Problem conclusion

• Resolution Summary:
  Two new NDMINIT initialization parameters now control the
  flagging of EMS events as "critical".
  EMSERRSCRITICAL YES causes all C:D error events emitted by the
  C:D Server, Session Managers, and API Managers to be flagged as
  critical (event types 74,75,76,77,78,79,82,92,93).
  EMSALERTSCRITICAL YES causes all NDM_EVT_ALERT_MSG events
  (event type 82) to be flagged as critical.
  When both parameters are set to NO (the default) the
  application behavior is unchanged.
  3.6.0.1 iFix 010
  Publication date: Feb 20, 2015
  The fix will be included in all future iFixes to 3.6.0.1, and
  in all future releases.
  

Temporary fix

• None available
  

Comments

• iFix 010 to Fix Pack 3.6.0.1
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• n/a
  

Fix information

• Fixed component name

  STR CD HP NONST

• Fixed component ID

  5725C9904

Applicable component levels