|
|
|
Reason:
The maximum number of commands that have been on the OSF TSP queue as a percentage of the maximum number of commands that the queue can hold, is higher than recommended. That is, the maximum utilization reached by the OSF TSP queue is too high. This queue is where CA OPS/MVS sends TSO commands to be executed in the OSF TSP servers. The OSF execution scheduler dispatches these commands to OSF TSP servers as the servers become available to process work. If the queue utilization reaches 100% and occurrences of message OPS4349S with RC=4 have been issued since CA OPS/MVS started, then CA OPS/MVS has had failures in attempting to send a command to an OSF TSP server because the queue was full. Requested automation commands have failed to be executed.
Action:
You have multiple options to decrease queue utilization:
The first option would be to decrease the value of parameter OSFTSPQADD which is currently &VAR1. This parameter sets the threshold that CA OPS/MVS uses to determine whether more OSF TSP servers need to be started. When the number of commands in the OSF TSP execution queue exceeds the value of the OSFTSPQADD parameter, CA OPS/MVS starts another OSF TSP server unless the number of servers has already reached the value of the OSFTSPMAX parameter. If your preference is for CA OPS/MVS to make use of the maximum number of defined OSF TSP servers to process the command load, then this may be the best option for you. With more servers executing commands, the queue utilization can be expected to decrease. A reasonable new value for OSFTSPQADD would be to decrease it to &VAR2. It can be changed while CA OPS/MVS is active.
The second option for decreasing OSF TSP queue utilization is to increase the maximum number of commands that can be held in the queue. If your preference is to maintain, rather than increase, the number of CA OPS/MVS address spaces, then this may be the best option for you. A reasonable new value for OSFTSPQUE would be to increase the current value &VAR3 to &VAR4. This option requires a restart of CA OPS/MVS.
A third option is to increase the value of the OSFTSPMAX parameter which is currently &VAR5. If you are currently not using the maximum number 30 of defined OSF TSP servers to process the command load and prefer to not have longer command queues, then this option may be for you. That is, rather than further decreasing the value of parameter OSFTSPQADD or increasing the value of parameter OSFTSPQUE, a reasonable new value for the OSFTSPMAX parameter would be to raise it by one. With more servers executing the commands from the queue, the queue utilization is expected to decrease. OSFTSPMAX can be changed while the CA OPS/MVS is active.
You can start by lowering OSFTSPQADD and then alternate between adding one to OSFTSPMAX and reducing OSFTSPQADD again. OSFTSPQADD should never be lower than 2 and OSFTSPMAX cannot be greater than 30. If queue is still full, a larger queue size OSFTSPQUE is the last resort.
To modify the value of the parameters, use the OPSPRM function with the SET keyword, that is, OPSPRM('SET','OSFTSPQADD','&VAR6'), or OPSVIEW option 4.1.1. Rerun this health check after a few minutes to see if the OSF TSP queue utilization is decreasing. The OSFTSPQUE parameter can only be set at product initialization.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |