MVX CONTEXT
Command | Parameters |
|---|---|
MVX CONTEXT | CHANNEL(channelName) PRODUCT(productName) TARGET(targetName) [SYSTEM(systemName)] [SERVER(serverName)] [WAIT(nn)] [RETRY(nn)] |
The following table describes the parameters:
Parameter | Function | Notes |
|---|---|---|
CHN|CHANNEL | Specifies the name of a local variable that receives the identification token for the connection | 1 to 32 alphanumeric characters This value is the token returned in the CHANNEL variable that is returned by the IMFEXEC MVX CONNECT command. |
PRD |PRODUCT | Specifies the product to which you want to connect | Use the MV PLEX Manager view, PLEXPROD, to display a list of available products. A partial sample list follows:
Use the product abbreviation, shown in the Product column of the PLEXPROD view. |
TARGET | Specifies the context or target to connect to | 1 to 17 alphanumeric characters When you specify TARGET, enter the target name or SSI context name that identifies the source of the data. SSI dynamic contexts in the form of xxxxxxxx:yyyyyyyy are permitted. For more information about targets, see Context determination. |
SYSTEM | specifies the system where the target resides | 1 to 8 alphanumeric characters Use this parameter when targets with the same name reside on different systems. Otherwise, you do not need to specify this parameter. |
SVR|SERVER | Specifies the server name of the target | 1 to 8 alphanumeric characters Use this parameter when more than one target on the same system has the same name. Otherwise, you do not need to specify this parameter. |
WAIT | Specifies the number of seconds the EXEC waits for a response or for data from the target | 0 through 999 The default is 10. |
RETRY | Specifies the number of seconds after a timeout to retry the request | 0 through 999 The default is 20. A retry is attempted only one time, after which the request terminates. |
Condition codes are listed in the following table:
Value | Description |
|---|---|
0 | The command completed successfully. |
8 | Due to an error, a write or read failure has occurred. |
12 | A missing or invalid channel was specified. |
16 | A syntax error has occurred. |
20 | An internal error has occurred and the command detected invalid response data. |
Example
This example shows an EXEC that requests to use BMC AMI Ops Automation in the context of BMCS. The command waits up to 60 seconds, if necessary, for the response:
"CHANNEL("CHANNUM")"