MV CONTEXT
This command connects a channel with a specified context or target and optionally waits for it to become available.
Command | Parameters |
---|---|
MainView | MV CONTEXT | PRODUCT(product name) [TARGET(target identifier)] [SERVER(server name)] [WAIT(n)] CHANNEL(channelname) |
The following table describes the parameters:
Parameter | Function | Notes |
---|---|---|
PRODUCT | product to which a connection is to be established | 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 | context or target to which a connection is to be established | 1- to 8-characters alphanumeric This keyword is optional. If not specified, the first MainView PAS (chronologically) connected to the MainView CAS that has the requested PRODUCT running is interrogated. If specified, the value is the SSID of the MainView PAS from which data is retrieved or it can be ALL, which means that all MainView PASs connected to the MainView CAS are interrogated. |
SERVER | can be used in target mode to distinguish between different products that contain the same target name | 1- to 8-characters alphanumeric The default is all servers. |
WAIT | number of minutes to wait until target becomes available | 0 - 99999 The default is 0. If WAIT is specified and a target is not available, a connection is implicitly retried every 10 seconds. |
CHANNEL | token that identifies a previously connected channel | 1- to 32-characters alphanumeric |
Condition codes are listed in the following table:
Value | Description |
---|---|
0 | The product or target connection was successfully established. The channel is available to retrieve data from the databus. |
8 | The connection could not be established. |
12 | The specified channel could not be located. |
16 | Syntax error detected or invalid channel token supplied. |
Example
This example shows an EXEC that requests an immediate connection to product MVMVS with a target of SJSB. The connection is to use the previously connected channel whose token is contained in the variable JOBCHANNEL.
REXX EXEC example:
CHANNEL('JOBCHANNEL')'
CLIST example:
CHANNEL(&JOBCHANNEL)