OPCA
Purpose
With the OPCA entry, you define the state that is the expected result of a request (with or without parameters), and the time interval within which this state must have been reached. The OPCA entry is defined in the MESSAGES/USER DATA policy item of the subsystem that is to be put under control of TWS.
Format
Code 1 Code 2 Code 3 Value Returned
START UP,3,RMFUTMER
STOP DOWN,2,RMFDTMER
Parameters
- Code 1
- Request specified in the TWS operation text.
- Code 2
- Parameter 1 as specified in the TWS operation text.
- Code 3
- Parameter 2 as specified in the TWS operation text.
- Value Returned
-
- expstatus
- Expected status of the subsystem at the completion of the request. expstatus stands for one of the following values:
UP, RUNNING or DOWN.
Note: For backward compatibility CTLDOWN and AUTODOWN are also allowed for this entry and will be treated the same as DOWN.
- timerint
- Timer interval in minutes. The maximum value permitted is 1439
(23 hours and 59 minutes).
Set a timer interval that is long enough for the operation to complete reasonably. If the operation does not complete in the interval specified, then an error is posted to TWS.
- timerid
- Timer ID — from 1 to 8 characters.
This must be a valid NetView timer ID with a value not equal to
ALLor beginning withSYS,ING, orAOF. This field is optional.
Usage Notes
For every OPCACMD entry there must be a corresponding OPCA entry.
Example
Code 1 Code 2 Code 3 Value Returned
START AUTO UP,5,CICS1TMR
START COLD UP,10,CICS1TMR
This example shows two entries, one for an automatic start, and one for a cold start. The AUTO or COLD parameter is added to the START request in TWS to indicate which one of several startup procedures is to be used. Presumably the two operations will take differing amounts of time, so the timer intervals are different.
This OPCA code entry is used in conjunction with a user-written CLIST, specified in the OPCACMD entry; see Example 1 for details of that entry and the sample CLIST.