beautypg.com

Ignore-safeguard-protection param, Curity instead of safeguard. see, Ignore – HP Integrity NonStop H-Series User Manual

Page 412: Safeguard-protection param, Fabricated names). see, Examples

background image

ASSIGNs and PARAMs

DSM/SCM User’s Guide — 529846-014

E - 11

IGNORE-SAFEGUARD-PROTECTION Param

SYSGEN-SPOOLER-OUTPUT-OWNER-ID "user-id "

DSM/SCM makes the Planner ID the owner of the system generation spooler
output unless this PATHWAY PARAM is specified. Pass this PARAM to the
PATHWAY server CB-001.

Examples

This command builds public DLLs for this configuration being built on \Wylee:

> PATHCOM $yphi
= ALTER server,PARAM FORCE-PUBLIC-DLL-BUILD "\WYLEE &
= DEFAULT 43"

This command gives delphi fingerprints to all files in the SYSnn subvolume. All
other files get real fingerprints.

> PATHCOM $yphi

= ALTER server,PARAM FP-MFG-SYSNN-VERSION "999"

This command gives a real version 1 fingerprint to the OSIMAGE file.
All files in the SYSnn subvolume, except the OSIMAGE file, are given delphi
fingerprints. All other files get real fingerprints.

> PATHCOM $yphi
= ALTER server, PARAM FP-MFG-F-OSIMAGE-VERSION "1", &
= PARAM FP-MFG-SYSNN-VERSION "999"

IGNORE-SAFEGUARD-PROTECTION Param

Even if Safeguard is running on the target system, you can protect the files in your new
configuration with Guardian security instead of Safeguard:

1. Set the PERSISTENT attribute to ON for all existing Safeguard-protected files in

the SYSnn, CSSnn, and system TSV.

PERSISTENT retains the protection record of a disk file even when the underlying
disk file is purged. Normally, a protection record is associated with a specific disk
file. When the file is moved or removed, so is the protection record. However,
PERSISTENT specifies that the protection record is associated with a particular
disk file name, not with the file identified by that name.

2. Use the Planner Interface to set the default Guardian security for the target. (See

3. Collect the Information Needed for the Build

on page 9-5 and

Guardian Default

for New Files

on page 9-17). The security you set must be sufficient to protect files

being placed by the Apply from unauthorized access.

3. Specify the IGNORE-SAFEGUARD-PROTECTION PARAM to the Target Activator:

> PATHCOM $YPHI

= ALTER ta-001, PARAM "ignore-safeguard-protection"

When the Target Activator detects this PARAM, a newly placed file does not inherit
Safeguard protection unless PERSISTENT is set to ON for the file.

This manual is related to the following products: