Skip to main content

Connecting SEP processes or Batch Jobs to DB2/LUW app_handles

  • January 24, 2018
  • 3 replies
  • 0 views
A
  • Anonymous

When monitoring DB2/LUW activity by app_handle id's, is there a means to tie the app_handle to a Microfocus SEP process id or Batch Job?


#EnterpriseServer

    3 replies

    D
    • Dominique SacreRocketeer
    • Rocketeer
    • 19312 replies
    • January 24, 2018

    When monitoring DB2/LUW activity by app_handle id's, is there a means to tie the app_handle to a Microfocus SEP process id or Batch Job?


    #EnterpriseServer
    Use SQL Server Profiler within SQL Server Management Studio, and you'll see same SEPs as the one used in any MFES or Windows.
    D
    • Dominique SacreRocketeer
    • Rocketeer
    • 19312 replies
    • January 24, 2018

    When monitoring DB2/LUW activity by app_handle id's, is there a means to tie the app_handle to a Microfocus SEP process id or Batch Job?


    #EnterpriseServer
    Use SQL Server Profiler within SQL Server Management Studio, and you'll see same SEPs as the one used in any MFES or Windows.
    A
    • Anonymous
    • 0 replies
    • January 24, 2018

    When monitoring DB2/LUW activity by app_handle id's, is there a means to tie the app_handle to a Microfocus SEP process id or Batch Job?


    #EnterpriseServer
    Thanks for the reply! However, I'm trying to do this with a home grown monitor, written in ksh. At this point, it's simply displaying a list of the active LUW apps and the SQL statement currently being executed. I'm trying to find a way to find/display the MF batch job name (if batch) or SEP ID (if online transaction) that executed that SQL statement, based on it's app_handle.


    Terms & ConditionsAccessibility statement