There are three ways to communicate with the CLI:
o with command statements in a processor initialization file
o interactively using an RS-232-C serial terminal connected to a CP or TP CLI port
You define a CP or TP CLI port by adding the phrase connect=ctos to the end of the RS-232-C channel's entry in the processor configuration file. There can only be one CLI port per CP or TP. For a CP, it must be channel 3; for a TP, it must be channel 10.
o interactively from a workstation using the mCdtIO or mCli utility
You invoke the mCdtIO or mCli utility from the BTOS II Executive by using the MCDTIO or MCLI command.
Note: The destination processor you want to run a eLi session with must be running elLrun in its primary partition, unless you are using the MCLI command. (If you are using mCIi, the AdminAgent must be running in the destination processor's primary partition.) You can check whether elLrun is running in the processor's primary partition by running mPartition Status on that processor (refer to section 7).
Cli.run will be running in the processor's primary partition unless the application installed in the primary partition never exits. Some BTOS servers that are executed in the primary partition through processor initialization files do exit: for example, the Queue Manager. Others, such as AdminAgent, the printer spooler manager, and the Tape Server, do not exit.
Using Processor Initialization Files Each processor normally has an initialization file.
Processor initialization file names take the form [sys]<sys>initXpnn.jcl, where Xpnn is the processor
designation (for example, FPOO, CP02).
The initialization file is a text file that has a line entry for each system service to be run on the processor. Each line entry in an initialization file is a run statement that loads and activates the system service's run file on the
processor.
For more information about processor initialization files and the services you can run on them, refer to the XE500 BTOS Installation and Implementation Guide.
Using
ell
PortsEach CP or TP can have one CLI port. To designate an RS-232-C channel as the CLI port, you add the phrase connect=ctos to that channel's entry in the processor's configuration file.
If you run CLI from this channel, an RS-232-C serial terminal must be connected to the channel.
The terminal hardware must be set with the following line parameters:
o 9600 baud o 8 data bits o one stop bit
o
no parityWhen the terminal is turned on, CLI prompts for input with a dollar sign ($).
Commands executed through the CLI port can only be run on the processor to which the CLI port is connected.
However, by executing the run statement for the mCdtIO or mCli utilities, you can have programs execute on other processors. This allows you· to execute commands on processors other than CPs and TPs. The next subsections discuss the mCdtIO and mCli utilities.
Using the mCdtlO Utility
The mCdtIO utility provides the same level of interaction with any processor that a CLI port provides for a CP or TP. For example, usingthe mCdtIO utility, you can connect a debugger to an FP or execute a set of CLI initialization commands on an SP, with full interactive capabilities.
9·6 Using the Command Line Interpreter You can invoke the mCdtlO utility in two ways: from the Executive, through the MCDTIO command; or from the CLI, through a CLI run statement that specifies the mCdtlO run file. The MCDTIO command form has two optional fields that allow you to specify:
o whether a log file of the MCdtlO session is to be created or automatically printed at the end of the session
o
whether you are to be prompted to continue with each screen of textBy default, the utility does not use page pauses.
Executing MCdtlO Through the Executive
To execute the mCdtIO utility through the BTOS Executive, use the following procedure:
1 Enter MCDTIO at the Executive command line and press RETURN.
The system displays the MCDTIO command form shown in figure 9-2. Table 9-1 lists the fields in the MCDTIO command form.
2 In the Processor field, enter the name of the target processor (for example, FPOO, CP02).
3 To exercise either of the available options, creating a log file or requesting page pauses, press RETURN and fill in the appropriate field.
4 When you have filled in the appropriate fields of the command form, press GO.
The utility begins running and the CLI dollar sign ($) prompt displays.
Figure 9-2 MCDTIO Command Form mCdtlO
I
Processor[Log File)
[Pause between pages?)
Table 9-1 MCDTIO Command Form Fields
Field Action/Explanation
Processor Enter the name of the target processor (for example, FPOO, CP02).
[Log file] Enter the name of the file the log of the MCDTIO session is to be written to. If the log file already exists, the existing file is deleted and the new file is created in its place. If the log file does not exist, it is created.
[Pause between pages?]
If you leave this field blank, the interaction is not recorded.
To have the log automatically printed out and not save the log file, enter the name of a printer queue, enclosed in square brackets.
If you do not name a print file, the information is only sent to the screen.
The default is video.
Leave the field blank if you do not want a system prompt at the end of each screen of text.
If you enter yes, the McdtlO utility pauses every time it displays or echoes 23 lines. When the McdtlO utility pauses, it displays Press <NEXT PAGE>/<RETURN> to continue. Press NEXT PAGE if you ran the McdtlO utility through the Mcli utility. Press RETURN if you ran the McdtlO utility any other way.
The default is no.
Note: Next page prompts appear during the MCdtlO utility if you specify yes in the Suppress pause between pages? field of the SCREEN SETUP or VIDEO command or yes in the Pause between pages field of the MCDTIO command.
Therefore, if you request page pauses both ways, you will be prompted twice for Next Page during the mCdtlO utility.
9-8 Using the Command Line Interpreter To eliminate page pauses, you specify no page pauses in both the SCREEN SETUP or VIDEO command and the MCDTIO command.
mCdtlO pagination does not permit you to abort the program you are running by pressing CANCEL or FINISH.
Executing mCdtlO Through a CLI Port
To execute the mCdtIO utility from a serial terminal connected to a CLI port, you enter the run statement for the mCdtIO utility at the CLI prompt as follows:
$run [sys]<sys>mCdtIO.run,cpu,log,pause
where the parameters cpu, log, and pause are as described for the MCDTIO command.
Terminating an mCdtlO Utility Session
To terminate an mCdtIO utility session from a workstation, you press CODE-D twice.
To terminate an mCdtIO utility session from a serial terminal connected to a CLI port, you press CONTROL-Z once or CONTROL-D twice.