|
|
|
This command defines the VTAM LU to LU sessions that the MSF establishes and maintains with copies of CA OPS/MVS running on other systems. Typically, the MSF uses these sessions to send and receive commands and command responses.
This command has the following format:
ADDRESS OPSCTL "MSF DEFINE keywords"
{msfid(sysname)}
{APPLID(vtamname)}
[PASSWORD(password)]
[NORETRY|RETRY(seconds retries)]
[ALIAS(alias1,...alias8)]
[DELAY(seconds)]
[APPC|CCI|AP]
[SECURE|NOSECURE]
[LOGMODE(logmode)]
[OUTPUT|NOOUTPUT]
[SYSTEM(sysid)]
[SYSWAIT(seconds)]
[WAIT(seconds)]
Defines the system name. System names can contain one to eight characters. The first character must be @, #, or $ or an alphabetic character, but the remaining characters can be any alphabetic, numeric, or national characters. The words ALL and EXT are reserved names and cannot be used as a system name or an alias.
Defines one of the following:
For the value of the APPLID keyword to be valid, ensure that it has the following characteristics:
The value that you specify for the APPLID keyword must match the value specified on the APPL statement you placed in your SYS1.VTAMLST data set for the MSF when you installed CA OPS/MVS. For information about installing the MSF, see the Installation Guide.
(Optional) Defines the password the MSF uses when opening its VTAM ACB. It is required only when you define the local MSF system and when the APPL specification in SYS1.VTAMLST requires a password. This password must match the password on the APPL statement.
(Optional) Instructs the MSF not to reestablish the session. Use this optional keyword only when defining a remote system.
(Optional) Tells the MSF on the local system to try to reestablish the session and, if the attempt fails, to try again. The seconds value specifies how many seconds the MSF waits between attempts to connect to the system being defined (if you are defining a remote system) or between attempts to start the local MSF. The value for seconds must be an integer between 30 and 86400, and the default is 30 seconds.
The retries value specifies the maximum number of times the MSF tries to start the local MSF or establish a remote session. This value must be an integer between 0 and 65535. Zero, which causes the MSF to make no retry attempt, is the default.
(Optional) Defines one to eight alternate names that the MSF can use for this system. Use the same syntax rules for aliases as for system names. You can use an alias only when you issue cross-system commands using the OPSRMT command or the SYSID keyword of the OPSCMD command.
(Optional) Defines the network delay time between the local MSF system and the remote system being defined. The seconds value must be an integer between 0 and 60, and 1 second is the default.
Use the DELAY keyword together with the WAIT value for the OPSCMD command or the default wait value for the OCWAIT command, as follows:
(Optional) Tells the MSF to use LU 6.2 protocols to communicate with this remote system. The APPC keyword is valid only for releases of the CA OPS/MVS product after 2.2.0.
(Optional) If you are using CAICCI at your site, this value tells the MSF to use the CAICCI cross-platform communications services to communicate with the remote system. To use this value, you must have CCS for z/OS installed on your system, and the CAICCI interface must be enabled. For more information, see the CCS for z/OS documentation.
Each local CAICCI system must have a unique system identifier (sysid). ADDRESS OPSCTL MSF uses the sysid to establish a connection to a remote system. For example:
ADDRESS OPSCL "MSF DEFINE MSFID(OPSS0B) APPLID(CCI0B) CCI"
Note: CCI0B is the sysid of CCI on system B.
(Optional) An optional keyword, when specified on a remote system, which is used to identify a connection to a CA Automation Point system. This connection is actually a special case of a CCI connected system. However, since the remote CA Automation Point system has different capabilities than a remote CA OPS/MVS system, a different connection type designation is used to avoid sending commands to CA Automation Point that it does not support. To use this value, you must have the CCS for z/OS installed on your system, and the CAICCI interface must be enabled. For more information, see the CCS for z/OS documentation.
(Optional) To help you secure your automation environment, specify the optional SECURE or NOSECURE keyword when using the MSF DEFINE command to define an MSF system. These keywords can be particularly useful in an environment where you want to connect production and test systems through the MSF.
For example, by specifying SECURE on your MSF DEFINE command, you indicate that the remote system you are defining is secure, and thus any commands received from that system can be processed by the local system. In contrast, specify NOSECURE to indicate that the remote system is not secure (that is, it is a test system). When the local system receives a command from a non-secure remote system, it processes the command only if it is a display command. Any commands that could do harm to the production system (such as an ENABLE command) are ignored. The SECURE and NOSECURE keywords are ignored for the local system, whose commands are always processed. SECURE is the default.
(Optional) Defines a logmode name. If you do not specify a logmode name, CA OPS/MVS uses the value of its MSFLOGMODE parameter.
(Optional) You may specify the OUTPUT, NOOUTPUT, SYSTEM, SYSWAIT, and WAIT keywords described in Keywords Common to ADDRESS OPSCTL MSF Commands in this chapter.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |