This is a list of steps you can take if you have an RPF or RPFs that are using High CPU.
- If RPFs are using high CPU, the most likely cause is that they are calling large ETSO applications.
- Issue "QUERY CALL ALL" to determine what ETSO applications are being executed.
- An application such as ISPF or JOBSCAN can take a lot of storage and must be limited through the EPL to a single concurrent user. Smaller applications may be granted more concurrent users, but you must be familiar with all that is going on in the system. You can adjust the number of users and the time slices for each program in the EPL. See TEC499359 What is the CA ROSCOE Eligible Program List (EPL) and How do I Update it? for details on how to update the EPL.
- Verify that two ETSO applications are not issuing an exclusive ENQ on the same data set. This can cause a Roscoe hang.
- Verify that you have applied all ETSO related maintenance for CA Roscoe. Apply them all even if you think they do not fit your problem.
Search on support.ca.com to find them.
- Make sure that you are using the DIVERT command for WTP, WTO and TPUT so users can see messages from ETSO programs. For example:
DIVERT TPUT TERMINAL DIVERT WTP TERMINAL DIVERT WTO TERMINALOtherwise Roscoe may appear to hang. For more details, see section 1.63 DIVERT in the CA Roscoe Command Reference Guide.
- CA SYSVIEW Performance Manager, for example, will give the overall CPU usage of CA Roscoe. SYSVIEW, "user status" will display the current users and their last command. Especially when there is high CPU usage, look at what each user is doing. Is there much activity? Is Roscoe Hanging? What is the MPL? How many users are in ETSO?
If you need assistance in troubleshooting, please contact CA Support.