BP-FILE-DCOM-01 DCOM should be secured “UUCU”.
BP-OPSYS-LICENSE-01 DCOM must be LICENSED.
BP-OPSYS-OWNER-01 DCOM should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-01 DCOM must reside in $SYSTEM.SYSnn.
If available, use Safeguard software or a third party object security product to grant
access to DCOM object files only to users who require access in order to do their jobs.
BP-SAFE-DCOM-01 Add a Safeguard Protection Record to grant appropri-
ate access to the DCOM object file.
Discovery Questions Look here:
OPSYS-OWNER-01 Who owns the DCOM object file? Fileinfo
OPSYS-LICENSE-01 Is the DCOM object file licensed? Fileinfo
FILE-POLICY Who is allowed to execute DCOM on the system? Policy
Is the DCOM object file correctly secured with the
Guardian or Safeguard system?
Data Definition Language (DDL) Subsystem
The Data Definition Language (DDL) language enables users to define data objects in
Enscribe files and to translate these object definitions into source code definitions for
programming languages and other products on HP subsystems.
DDL performs two main functions:
Compiling statements that define data objects
Translating compiled definitions into source code for host languages and FUP
Using DDL Definitions
DDL Statements are used to define, modify, delete or display definitions in the
DDL Dictionary and to generate data definition output files for other subsystems and
DDL Functions Description
Create a data dictionary DDL schemas are stored in one or many DDL Dictionaries.
Create a Schema Using DDL commands, record schema definitions are created and
stored into the dictionary
Data Definition Language (DDL) Subsystem 245