PM49106: NEED BETTER LOGGING AND TRACING INFORMATION FOR DEBUGGING JEXIT ISSUES

APAR status

• Closed as program error.

Error description

• We need better  logging and tracing information for debugging
  Jexit issues on unix environments in particular.
  
  When debugging an issue reported with jexit , no jni logs or
  debug information was reported. Even using the LASTERRORMESSAGE
  and LASTERRORCODE functions with Valid for a Jexit call did not
  provide any information in the map audit generated.
  

Local fix

• WTXCQ - WTX00038981
  AR / AR
  Circumvention: None
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender customers using JEXIT, EXIT
  function
  
  Problem Description:
  There is not information for users to diagnose problems when
  running EXIT or JEXIT.
  
  Platforms Affected:
  ALL
  

Problem conclusion

• Added ability to trace errors in external functions EXIT and
  JEXIT
  
  Delivered in:
  8.3.0.5
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WTX FOR INT SER

• Fixed component ID

  5724M4010

Applicable component levels

• R830 PSY

     UP