5.47.4 Examples
Example 1:
Set the maximum number of installed processor engines to 8.
MAXCPU 8
Example 1:
Set the maximum number of installed processor engines to 8.
MAXCPU 8
MAXRATES sets the MIPS/SIO rate reporting interval. When the interval is expired a MAXRATES com-
mand is automatically issued. The current rates will also be displayed during shutdown of Hercules. The
default for the MAXRATES interval (if not coded in the configuration file) is 1440 minutes (1 day).
Descriptive
]
Diagram
Êʬ¬¬ ¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
¬¬¬«
1440
This is the default that takes place if there is no MAXRATES interval is specified in
the configuration file and sets the interval to 1440 minutes (1 day).
interval
This specifies the interval time in minutes. Changes to the MAXRATES interval that
are other than “MIDNIGHT” will set the current interval start time to the present; this
includes a value of “1440”.
MIDNIGHT
Sets the interval to 1440 minutes (1 day) and the start time for the interval timer to
midnight of the current day. This will cause the MAXRATE statistics to be date
aligned.
Example 1:
Set the MAXRATES interval to 60 minutes.
MAXRATES 60
Powered by Tizra® |
Example 1:
Set the maximum number of installed processor engines to 8.
MAXCPU 8
MAXRATES sets the MIPS/SIO rate reporting interval. When the interval is expired a MAXRATES com-
mand is automatically issued. The current rates will also be displayed during shutdown of Hercules. The
default for the MAXRATES interval (if not coded in the configuration file) is 1440 minutes (1 day).
Descriptive
]
Diagram
Êʬ¬¬ ¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
¬¬¬«
1440
This is the default that takes place if there is no MAXRATES interval is specified in
the configuration file and sets the interval to 1440 minutes (1 day).
interval
This specifies the interval time in minutes. Changes to the MAXRATES interval that
are other than “MIDNIGHT” will set the current interval start time to the present; this
includes a value of “1440”.
MIDNIGHT
Sets the interval to 1440 minutes (1 day) and the start time for the interval timer to
midnight of the current day. This will cause the MAXRATE statistics to be date
aligned.
Example 1:
Set the MAXRATES interval to 60 minutes.
MAXRATES 60
Example 2:
Set the MAXRATES interval to one day and and the start time for the interval timer to midnight of the
current day.
MAXRATES MIDNIGHT
The MEMLOCK system parameter is used to lock Hercules memory in storage. It defines the locking
state of the allocated Hercules memory (page lock by host operating system). If the Hercules memory is
locked in storage it cannot be paged out by the host operating system. This may result in some perfor-
mance improvements.
This system parameter is available if Hercules is built with option “_HAVE_MLOCKALL”. Currently
MEMLOCK is only supported under Linux host operating systems.
Descriptive
OFF
Diagram
Êʬ¬¬ ¬¬¬§¬¬¬ ¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
OFF
ON
ON indicates that the memory is to be locked into storage.
OFF
OFF indicates that the memory is not to be locked into the storage.
Example 1:
Lock the Hercules memory in the storage.
MEMLOCK ON
Example 2:
Do not lock the Hercules memory in the storage.
MEMLOCK OFF
Powered by Tizra® |
Example 2:
Set the MAXRATES interval to one day and and the start time for the interval timer to midnight of the
current day.
MAXRATES MIDNIGHT
The MEMLOCK system parameter is used to lock Hercules memory in storage. It defines the locking
state of the allocated Hercules memory (page lock by host operating system). If the Hercules memory is
locked in storage it cannot be paged out by the host operating system. This may result in some perfor-
mance improvements.
This system parameter is available if Hercules is built with option “_HAVE_MLOCKALL”. Currently
MEMLOCK is only supported under Linux host operating systems.
Descriptive
OFF
Diagram
Êʬ¬¬ ¬¬¬§¬¬¬ ¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
OFF
ON
ON indicates that the memory is to be locked into storage.
OFF
OFF indicates that the memory is not to be locked into the storage.
Example 1:
Lock the Hercules memory in the storage.
MEMLOCK ON
Example 2:
Do not lock the Hercules memory in the storage.
MEMLOCK OFF
MANUFACTURER specifies the manufacturer name returned by the STSI instruction. The default name
is HRC.
Descriptive
HRC name
Diagram
HRC ¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
name
name
Any name with a maximum length of 16 characters. Valid characters are A-Z and 0-
9. If MANUFACTURER is not specified in the configuration file then the default is
HRC.
Example 1:
Set the manufacturer name returned by the STSI instruction to “HERC”.
MANUFACTURER HERC
The MAXCPU system parameter specifies the maximum number of installed processor engines. The
combination of MAXCPU and NUMCPU controls the behaviour of how many CPU engines will be con-
figured online upon startup and how many can be configured online later. The NUMCPU statement
specifies the number of engines which will be configured online at startup time. All processors are CP
engines unless otherwise specified by the ENGINES statement.
MAX_CPU_ENGINES is a compile-time variable which sets an upper limit on the value of MAXCPU. The
value of MAX_CPU_ENGINES is displayed in the build information message on the Hercules control
panel at startup time. To change the value of MAX_CPU_ENGINES you must rebuild Hercules. For Unix
builds, specify "./configure --enable-multi-cpu=nn" before performing make. For Windows builds, specify
"SET MAX_CPU_ENGINES=nn" before performing nmake.
MAX_CPU_ENGINES may be up to 128 on 64-bit Linux platforms. On Windows, and on all 32-bit plat-
forms, the maximum value is 64. For performance reasons, values above 32 are not recommended for
32-bit platforms. If MAX_CPU_ENGINES is set to 1 then multiprocessing is disabled. See also the NUM-
CPU statement for a discussion of the performance implications of MAX_CPU_ENGINES.
The value of MAXCPU cannot exceed the value of MAX_CPU_ENGINES. If MAXCPU is not specified in
the configuration file, then its initial value is equal to NUMCPU. If MAXCPU and NUMCPU are both
omitted, then MAXCPU is set to 1.
For detailed explanations on the interrelationship between MAXCPU, ENGINES and NUMCPU please
see “
Descriptive
CPU 1 nn
Diagram
Êʬ¬¬ ¬¬¬§¬¬¬ 1 ¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
nn
nn
Specifies the maximum number of installed processor engines. The value of
MAXCPU cannot exceed the value of MAX_CPU_ENGINES (see description
above).
Powered by Tizra® |
MANUFACTURER specifies the manufacturer name returned by the STSI instruction. The default name
is HRC.
Descriptive
HRC name
Diagram
HRC ¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
name
name
Any name with a maximum length of 16 characters. Valid characters are A-Z and 0-
9. If MANUFACTURER is not specified in the configuration file then the default is
HRC.
Example 1:
Set the manufacturer name returned by the STSI instruction to “HERC”.
MANUFACTURER HERC
The MAXCPU system parameter specifies the maximum number of installed processor engines. The
combination of MAXCPU and NUMCPU controls the behaviour of how many CPU engines will be con-
figured online upon startup and how many can be configured online later. The NUMCPU statement
specifies the number of engines which will be configured online at startup time. All processors are CP
engines unless otherwise specified by the ENGINES statement.
MAX_CPU_ENGINES is a compile-time variable which sets an upper limit on the value of MAXCPU. The
value of MAX_CPU_ENGINES is displayed in the build information message on the Hercules control
panel at startup time. To change the value of MAX_CPU_ENGINES you must rebuild Hercules. For Unix
builds, specify "./configure --enable-multi-cpu=nn" before performing make. For Windows builds, specify
"SET MAX_CPU_ENGINES=nn" before performing nmake.
MAX_CPU_ENGINES may be up to 128 on 64-bit Linux platforms. On Windows, and on all 32-bit plat-
forms, the maximum value is 64. For performance reasons, values above 32 are not recommended for
32-bit platforms. If MAX_CPU_ENGINES is set to 1 then multiprocessing is disabled. See also the NUM-
CPU statement for a discussion of the performance implications of MAX_CPU_ENGINES.
The value of MAXCPU cannot exceed the value of MAX_CPU_ENGINES. If MAXCPU is not specified in
the configuration file, then its initial value is equal to NUMCPU. If MAXCPU and NUMCPU are both
omitted, then MAXCPU is set to 1.
For detailed explanations on the interrelationship between MAXCPU, ENGINES and NUMCPU please
see “
Descriptive
CPU 1 nn
Diagram
Êʬ¬¬ ¬¬¬§¬¬¬ 1 ¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ
nn
nn
Specifies the maximum number of installed processor engines. The value of
MAXCPU cannot exceed the value of MAX_CPU_ENGINES (see description
above).