MV CONNECT
This command causes a new channel to be used in subsequent channel requests.
A channel must be connected before any MainView data can be requested by using the low-level API.
Command | Parameters |
|---|---|
MainView | MV CONNECT | Channel [MSG | NOMSG] |
The following table describes the parameters:
Parameter | Function | Notes |
|---|---|---|
name of channel | shows the variable name to receive the token that identifies the connected channel | 1- to 32-characters alphanumeric This variable name is used by other IMFEXEC MV statements. |
message option | controls the writing of diagnostic messages to the journal for each IMFEXEC MV command issued within this connection | one of the following values: MSG: Diagnostic messages for each IMFEXEC MV command issued within this connection are written to the journal. NOMSG: No diagnostic messages for each IMFEXEC MV command issued within this connection are written to the journal (default). BMC Software recommends using the MSG keyword when you are first trying to create an EXEC so you can receive the diagnostic messages and coding the NOMSG keyword when you are ready to move the EXEC into production. |
Condition codes are listed in the following table:
Value | Description |
|---|---|
0 | A new channel was successfully connected and may be referenced by the supplied variable token. |
8 | A channel could not be acquired. This condition can occur when a BBI-SS PAS or CAS has not been started. Otherwise, use MV TRACE to collect trace information and then contact BMC Customer Support. |
16 | Syntax error was detected during parsing:
|
20 | The maximum MainView session count has been exceeded. The request fails. The total number of sessions supported PER SS is 150. You might want to retry the request after inserting an IMFEXEC WAIT(). |
Example
This example shows an EXEC that requests a new channel to be used in subsequent channel requests. The token for this channel is placed into the variable JOBCHANNEL.
REXX EXEC example:
CHANNEL'
CLIST example:
CHANNEL
All other examples in this chapter use the variable named JOBCHANNEL to represent the token that identifies the connected channel.