Getting kicked out of a Netview session in CA TPX with SENSE 00002022
search cancel

Getting kicked out of a Netview session in CA TPX with SENSE 00002022


Article ID: 9120


Updated On:


TPX - Session Management Vman Session Management for z/OS


I have an odd problem that I can't seem to understand what is causing it.

I am using a TPX and occasionally I will get the following message after entering a command within Netview:



The only message I see in the log is:

TPXL0050 01/10/18.010 09:30:50.16 LOSTERM EXIT ENTERED FOR SESSION xxxxxxxx                 

        SB: 1A712188, REASON 20, UNCONDITIONAL TERMINATION                                  

TPXL0085 01/10/18.010 09:30:50.16 RPL ERROR MANAGEMENT ROUTINE ENTERED                      

         PLU=xxxxxxxx  SLU=xxxxxxxx  USER=xxxxx    REQ=22 C0001024 00800000 TO TERM         

          TERMSB=1A712188 APPLSB=1A7126E0 EB=1A041300 RPL=1A042908                          

          RTNCD=10 FDBK2=09 MEANING=UNCOND TERMSELF OR USS LOGOFF                           


          ACTIONS TO BE TAKEN:                                                              


                               EVENT STORAGE PURGED


CA TPX for z/OS


All information points to this being a problem with Omegamon ETE rather than TPX interfering with the Netview session. 

Previous reports have been noted where Omegamon ETE intercepts the exception response, converts it into a definite response and does not block the next response. 




Contact your group that manages Netview and/or Omegamon ETE.

Additional Information

Try a Google search: Omegamon ETE 00002022





Definite response unit failures in VTAM, DB2, and CICS

Definite response unit failures can be apparent in a number of products that use ETE services, and product-unique situations and error codes are produced:


--- Intermittent VTAM SENSE 00002022 is found in the SYSLOG. This error usually indicates that required maintenance has not been applied. Check the support pages to ensure that the most recent maintenance has been applied and that the PARM=',NFNDFC=YES' is being used on startup.


To resolve these types of issues, a new keyword parameter (NFNDFC) was created to enable ETE users to configure ETE to control whether or not the ETE subsystem forces definite response for non-data flow control RUs. The default is NFNDFC=NO. See “Step 2: Customize the ETE startup JCL” on page 7 for more information.

Refer to “Step 2: Customize the ETE startup JCL” on page 7 for information about how to code this parm statement and for other positional and keyword parameters for the ETE product.





OMEGAMON and IBM Tivoli Management Services on z/OS 

Version 6.2.0 

End-to-End Response Time Feature 



Chapter 2. Understanding end-to-end response time 

ETE measures end-to-end response time for applications that use either definite response protocol or exception response protocol. 

End-to-end response time is the elapsed time between the moment that a user presses a key (Enter, F1 through F24, PA1, PA2, PA3, or Clear) and the moment that a response is received at the terminal. For example, if you start a stopwatch when a user presses Enter and stop it when the terminal receives the application's first response to the user's request, the stopwatch shows the end-to-end response time for that request. 

To measure end-to-end response time, ETE places itself inside one of the VTAM SNA layers. In this location ETE can time all SNA traffic that flows through VTAM. End-to-end response time measurement requires that VTAM internal trace with the PIU option is active. The measurement is started automatically when ETE is activated. 


Chapter 5. Customizing ETE to work with a multi-session manager 


If you want to run ETE with IBM Tivoli NetView® Performance Monitor, there are special operational considerations when running concurrent ETEs and the IBM Tivoli NetView Performance Monitor (NPM) product.