Technical data

qualified because if not specified, OSM will only look in the default subvolume of
$system.zservice, which is not recommended for the placement of such script files.
Example: SHUTDOWN_SCRIPT_NAME = $SYSTEM.SYS00.SYSHTDWN
SHUTDOWN_SCRIPT_TIME = nn
nn is the time, in seconds, that the script is to be executed before the end of the configured
ride-through period. For example, if the ride-through time is set to 60 seconds and the specified
SHUTDOWN_SCRIPT_TIME is 25 seconds, then the shutdown script executes 35 seconds
after the ride-through time begins. The value of the SHUTDOWN_SCRIPT_TIME cannot exceed
the configured ride-through time minus 5 seconds (if the ride-through time is 60 seconds, the
SHUTDOWN_SCRIPT_TIME can be no greater than 55 seconds).
The goal in specifying a SHUTDOWN_SCRIPT_TIME is to wait as long as possible before
executing the shutdown script – in the hope that AC power is restored and the shutdown
avoided – while allowing enough time for the script to complete the application shutdown
steps before ride-through ends and the shutdown of I/O operations and processors begins.
To make changes to your OSMCONF file take effect, see “Creating and Using an OSMCONF
File” (page 15).
The Verify Power Fail Configuration action, located on the System object in the OSM Service
Connection, now checks the validity of these two variables in addition to verifying that OSM power
failure support has been properly configured and is in place for the system. The check will return
an error if OSM cannot find the script file in the specified location, the file does not have the file
code of 101, or the specified time is not at least 5 seconds less than the configured ride-through
time.
Configuring OSM Process File Security Levels
With version T0682 H02 ACE and later, OSM sets the default process file security to NCNC, and
gives you the option to change the security levels for OSM persistent processes using either of the
following methods:
• “Editing the ADDTOSCF File” (page 30)
• “Aborting, Altering, and Starting OSM Process Files” (page 31)
Editing the ADDTOSCF File
One way to can change the default security levels for OSM persistent process is by editing the
ADDTOSCF file. Within the file, locate the STARTUPMSG (startup message) line for the
OSM-CIMOM, OSM-APPSRVR, and OSM-OEV processes and change the security levels (the default
is “security NCNC”) as desired. The following is an example of an ADDTOSCF file showing
the default settings:
== Add $ZCMOM process to SCF database and issue start command
@ ABORT PROCESS $ZZKRN.#OSM-CIMOM
@ DELAY 1
@ DELETE PROCESS $ZZKRN.#OSM-CIMOM
@ ADD PROCESS $ZZKRN.#OSM-CIMOM, &
AUTORESTART 5, &
CPU FIRSTOF [listProcessors], &
DEFAULTVOL $SYSTEM.ZSERVICE, &
HIGHPIN ON, &
HOMETERM $ZHOME, &
NAME $ZCMOM, &
PRIORITY 150, &
PROGRAM $SYSTEM.SYSTEM.CIMOM, &
OUTFILE $ZHOME, &
STARTUPMSG "cpu-list cpu-list, security NCNC", &
STARTMODE APPLICATION
@ START PROCESS $ZZKRN.#OSM-CIMOM
30 OSM Server-Based Components