18.08.2013 Views

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Distributed Data Processing Program-to-Program Communications (DDP-PPC)<br />

Refer to the SYS$LIB$*DDP-FJT-3.README element for additional release<br />

documentation.<br />

5.14. Distributed Data Processing<br />

Program-to-Program Communications<br />

(DDP-PPC)<br />

This subsection describes the considerations for DDP-PPC. Refer to the DDP-PPC<br />

Implementation <strong>and</strong> Administration Guide before installing DDP-PPC.<br />

General Considerations<br />

You must install I18NLIB before you execute DDP-PPC. This is necessary because<br />

DDP-PPC uses ELMS, which in turn, requires I18NLIB.<br />

DDP-PPC starts a run named BNKLST when the PPCMASTER detects that the DDP-PPC<br />

subsystem has been deactivated since the last execution of the PPCMASTER. This run<br />

is used to obtain BDI information for the current execution of the PPCMASTER<br />

subsystem. It writes the information into a file named SYS$LIB$*DDP$BNKLIST. Once<br />

the information is obtained, the run terminates, usually after about 5 minutes. The dump<br />

routines then read this file whenever a DDP-PPC dump is taken. You should make sure<br />

the SYS$LIB$*DDP$BNKLIST file is secured.<br />

Because DDP-PPC executes as a fixed-gate subsystem, the files containing the<br />

subsystem (SYS$LIB$*PPC$$GATES) must be owned by a user-id that has fixed-gate<br />

subsystem privileges at shell level <strong>and</strong> can deactivate the subsystem.<br />

You can change the file ownership through the security management product after<br />

completing the DDP-PPC installation. Refer to the DDP-PPC Implementation <strong>and</strong><br />

Administration Guide for more information about user-id requirements for running<br />

DDP-PPC.<br />

The SYS$LIB$*PPC$$GATES.SSD element determines the security (ring level) of the<br />

DDP-PPC subsystem. For Fundamental Security environments it executes at the<br />

TRUSTED level, for all others it executes at the SHELL level.<br />

DDP-PPC determines the security level of the system during the SOLAR installation<br />

process <strong>and</strong> loads the appropriate version of the SSD element. If you change security<br />

levels after installing DDP-PPC, you can either reinstall DDP-PPC or copy the appropriate<br />

SSD element with the following comm<strong>and</strong>s:<br />

• To go from a FUNDAMENTAL level to a SECOPT 1, 2, or 3 level, enter<br />

@COPY,A SYS$LIB$*PPC$$GATES.SSD/SHELL,SYS$LIB$*PPC$$GATES.SSD<br />

• To go from a SECOPT 1, 2, or 3 level to a FUNDAMENTAL level, enter<br />

@COPY,A SYS$LIB$*PPC$$GATES.SSD/TRUSTED,SYS$LIB$*PPC$$GATES.SSD<br />

5–18 7831 0349–043

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!