If CA VM:Secure is not available during a command’s initial attempt, the WAITCHK record takes over. The WAITCHK record is used with the WAIT parameter on the CPACTION record.
If the program becomes available during the WAITCHK period, the CP command goes through CA VM:Secure processing at the end of the current wait interval. If the maximum number of retries is exceeded, the request to retry the CP command is canceled.
Calculate the amount of time necessary to reinitialize the program and set up your WAITCHK values based on that time frame. If you want to allow yourself 20 minutes, you could set your values at 60 and 20. This specifies to CA VM:Secure that CP commands with wait status should be reattempted every 60 seconds for 20 attempts.
Example
The WAITCHK record is tied to the CPACTION record with the WAIT option. Suppose the VMXRPI configuration file includes the following records:
CPACTION VMBAT001 WAIT WAITCHK 55 20
Also suppose that the CA VM:Batch worker machine VMBAT001 is processing a batch job when CA VM:Secure becomes unavailable.
VMBAT001 tries to issue the following CP command:
link john 191 491 rr
VMBAT001 is forced to wait for completion of the LINK command. The LINK command is retried every 55 seconds for 20 attempts. If CA VM:Secure becomes available during those 20 attempts, evaluation of the LINK command proceeds normally. Otherwise, the LINK request is canceled.
Note: For more information, see the CPACTION Record.
|
Copyright © 2014 CA.
All rights reserved.
|
|