MOBATCH PROCEDURE.

1.Definitions:
-p: number of parallel sessions that can be run during an mobatch session.
-t: defines the timeout period (seconds) for attempted logon.
-i- ignores case of the output.
egrep i non case sensitive filter.
2. Preparation:
To start an mobatch session ensure that a text file with the list of sites where the mobatch
command is to run are ready, the text file maybe the ipdabase information of the sites
(logon names used in place of ip addresses) if this is not available then the ip addresses of
the sites may be used. If for example while logging onto a site you type: amos u0001 or
amos u0002, your text file would be as outlined below;
Fig 01

Create a 2nd text file with the commands to be run on the nodes, the text file may be
important if you are running many commands on the nodes in a single mobatch session, if
2 or 3 commands then you may enter the commands as lt all;get . rbsid for text file the
commands may be entered sequentially as below;
Fig 02

Ensure that the 2 files created above are in your home directory in the OSS.

3. Procedure.
(i)

1 or 2 Commands at a go.

From the OSS window enter the command;

Fig 03

(ii)

Many commands in 1 mobatch session

From the OSS window enter the command as follows;

Fig 04

4. Merging and Filtering Files.

The generated results are on per site basis and it maybe tedious to open the reports one at
ago, hence merging of the reports can be done as follows;
Change directory to the out_folder directory by entering the command
Fig 05

ls: to view the generated reports which will have been named as *.log where * is the
ipdatabase logon name for the site. To merge the results do as follows;
fig 06

The above will merge all the reports into 1 text file but the output may still be
cumbersome to sort and hence the need to specifically filter on parameter basis, as an
example please refer to the sample below; the report still contains so much information
that is not required for the report and if you ran mobatch for 100 sites the format below
will repeat 100 times in your merged report. Being a text file this maybe cumbersome to
read and sort the required information accurately;
Fig 07

Filtering on attribute basis can be done thus; below I am filtering on Iub because the
parameter rbsid is contained within the Iub. The report can then be viewed by
cat rbsid_1 this much easier to read and sort.

Fig 08

If need be to filter further, e.g. eliminate a common word get that is appearing in the
final report then;

egrep i electricalantennatilt *.log | egrep iv get > <filename>

This can be done without going through the stages above and still the final report will be
a merged result of all the sites in the specific mobatch session.