IBM Z Software
This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
We have no plans for a CMAS and WUI to invoke DFH0STAT. Sounds like what you require is something sort of health check/status inquiry to ensure CPSM is up and running correctly. It would be best if that is reworded and a new RFE raised.
Right after a CMAS recycle about 5 min after it connects to all other CMASes
and connects/joins its MASes, we need to see peak active tasks, total storage,
EYUDREP file activity CI splits, LSRPOOL...etc. STAT is also helpful to
determine if various other functions are active.
The following reports assist to verify the configuration and health of the
CMAS when only a joblog is available.
System Status. . . . . . . . . . . Y Page Index . . . . . . . . . . . . N
Storage Manager. . . . . . . . . . Y Dispatcher . . . . . . . . . . . . Y
Storage Subpools . . . . . . . . . Y Dispatcher MVS TCBs. . . . . . . . N
Loader . . . . . . . . . . . . . . Y
Transaction Manager. . . . . . . . Y LIBRARYs . . . . . . . . . . . . . Y
Transactions . . . . . . . . . . . Y Program Definitions. . . . . . . . Y
Transaction Classes. . . . . . . . Y Programs . . . . . . . . . . . . . Y
Programs by DSA and LPA. . . . . . Y
Temporary Storage. . . . . . . . . Y DFHRPL and LIBRARY Analysis. . . . Y
Temporary Storage Queues . . . . . N Transient Data . . . . . . . . . . Y
Temporary Storage Queues by Pool . N Transient Data Queues. . . . . . . Y
Temporary Storage Models . . . . . Y
Logstream Global (System Logs) . . Y
Files. . . . . . . . . . . . . . . Y Logstreams . . . . . . . . . . . . Y
Data Set Names . . . . . . . . . . Y Journals . . . . . . . . . . . . . Y
LSR Pools. . . . . . . . . . . . . Y Coupling Fcty Data Table Pools . . Y
DB2 Connection . . . . . . . . . . N WebSphere MQ Connection. . . . . . N
DB2 Entries. . . . . . . . . . . . N
Program Autoinstall. . . . . . . . Y
JVM Pool and Class Cache . . . . . N Terminal Autoinstall and VTAM. . . Y
JVMs . . . . . . . . . . . . . . . N Connections and Modenames. . . . . Y
JVM Profiles . . . . . . . . . . . N TCP/IP . . . . . . . . . . . . . . N
JVM Programs . . . . . . . . . . . N TCP/IP Services. . . . . . . . . . N
JVMSERVERs . . . . . . . . . . . . N IPCONNs. . . . . . . . . . . . . . N
BUNDLEs. . . . . . . . . . . . . . N URIMAPs. . . . . . . . . . . . . . N
Virtual Hosts. . . . . . . . . . . N
Event Processing . . . . . . . . . N ATOMSERVICEs . . . . . . . . . . . N
EPADAPTERs . . . . . . . . . . . . N PIPELINEs. . . . . . . . . . . . . N
EVENTBINDINGs. . . . . . . . . . . N WEBSERVICEs. . . . . . . . . . . . N
CAPTURESPECs . . . . . . . . . . . N DOCTEMPLATEs . . . . . . . . . . . N
XMLTRANSFORMs. . . . . . . . . . . N
Trace Settings and Levels. . . . . Y
User Exit Programs . . . . . . . . Y Global User Exits. . . . . . . . . Y
Recovery Manager . . . . . . . . . N
Enqueue Manager. . . . . . . . . . N Enqueue Models . . . . . . . . . . Y
CorbaServers and DJARs . . . . . . N
DJARs and Enterprise Beans . . . . N
Requestmodels. . . . . . . . . . . N
EJB System Data Sets . . . . . . . N
What specific information from the WUI and/or CMAS are you wanting to collect. Running STAT (a sample) every so often will probably be an unacceptable overhead to customers. End of day stats records are always collected at shutdown for example.