11.3 Starting Hercules with the Hercules Studio

The Hercules Studio can be started by navigating to the 'Applications -> System Tools -> Hercules Studio'
menu entry and selecting it from there. Then all necessary settings required to start Hercules can be spe-
cified using the Hercules Studio itself.

Alternatively the Hercules Studio may also be manually started from a command shell or can be started
by calling a script file. In both cases the syntax is the same.

11.3.1 Syntax

Descriptive

H [-f configfile] [-r
rcfile]

Diagram

Êʬ¬¬ ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê






-f configfile

ʬ¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ


-r
rcfile

11.3.2 Parameter

-f configfile

This is the name of a configuration file. If the Hercules Studio is started with the
name of a configuration file then it will automatically “power on” Hercules once the
Hercules Studio itself is started. This is called the “Auto-Power-On” feature. When
using this feature in conjunction with a Hercules “.RC” (run-commands) file it is
possible to totally automate Hercules startup and IPL.

-r rcfile

This is the name of an optional RC (run-commands) file. This file contains Hercules
console commands that are issued exactly as if the commands were entered from
the Hercules system console.

11.3.3 Examples

Example 1:

Start Hercules Studio using the configuration file “mvs38j.cnf” and the run-commands file "autoipl.rc".

HerculesStudio -f mvs38j.cnf –r autoipl.rc

12. The Run-Commands File

12.1 Function

Hercules supports the ability to have console commands automatically executed at startup via the 'run-
commands' file. If the run-commands file is found to exist when Hercules starts then each line of the file is
read and interpreted as a console command, exactly as if the command were entered from the HMC sys-
tem console.

The default filename for the run-commands file is "hercules.rc". The default name may be overridden by
setting the "HERCULES_RC" environment variable.

Except for the 'pause' command (see below), each command read from the run-commands file is logged
to the console preceded by a “>”' (greater-than sign) character. Thus you can easily distinguish between
console commands entered from the keyboard from those entered via the run-commands file.

Comment lines starting with '#' are treated as "silent comments" and are thus not logged to the console
whereas comment lines starting with '*' are treated as "loud comments" and will be logged.

12.2 Run-Commands File Statements

There is a number of different types of commands that can be specified within a run-commands file.
These commands are the following:

“herccmd” (any valid Hercules console command) PAUSE (delay the processing of the next command) # (issue silent comment) * (issue loud comment)

12.2.1 Hercules Console Commands

Descriptive

herccmd

Diagram

Êʬ¬¬ herccmd ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

In the run-commands file any valid Hercules console command (“herccmd”) can be specified. This in-
cludes the ‘sh’ (shell) command. Each command that is read from the run-commands file is logged to the
console preceded by a ‘>’' (“greater-than” sign) character. This is to distinguish between console com-
mands entered manually from the keyboard from thosecommands entered via the run-commands file.

Previous Page Next Page