MXI – FAQs
- Can MXI terminate address spaces and tasks?
- Can MXI alter storage?
- Can DB2 plug-in be used to perform actions such as canceling a thread?
- Can you see in-flight SQL statements in DB2?
- Can CICS plug-in be used to cancel transactions?
- Can CICS plug-in modify CICS parms such as DSA & EDSA values?
- Can CICS plug-in alert on storage shortage conditions?
- Can you jump between plug-ins, for example between CICS and DB2?
- Can MXI alert an external monitor (an example would be to issue a WTO that could be picked up by AFOPER)?
Yes - the MXI "KILL" command can MEMTERM an address space or ABTERM an individual TCB within any address space.
Yes - the MXI "ZAP" command can alter common storage, private storage in any address space and also storage in any dataspace.
Yes - from the MXI "DBDA" command display that shows current active threads, you can use the "C" line command to cancel the thread.
Yes - from the MXI "DBDA" command display, issuing the "SQ" line command will show the current dynamic or static SQL statement information.
Yes, from the MXI "CIDA" command display that shows the current active transactions, you can use the "P" line command to purge the transaction, "PF" to forcepurge or "KILL" to kill.
Not currently - however this functionality is coming in 2009 via a PTF.
Yes – the MXI CAE can monitor storage statistics, and can issue an alert when a threshold has been crossed. Using the MXI CAE actions, users can configure e-mails and WTOs that can be issued when thresholds are crossed. The statistics are kept (off host) to be available for historical analyses such as trends and historical snapshot comparisons.
Yes - point-and-shoot on a correlation ID and seamless transition occurs both ways between the CICS and DB2 plug-ins.
Yes, the MXI CAE piece can issue a WTO in response to an “alert” (e.g. a storage threshold being crossed). The contents of the WTO can be defined by the user, and can use substitution variables from the alert.
