Introduction

Important: OECN RPC based on USP is considered obsolete. The SSDT recommends that ITC sites use OECN VXS for OECN RPC services. This document is retained for historical purposes for sites still maintaining a USP installation.

...

Start the configuration process with:

$ @OECN$:OECNRPC_CONFIG

See the following sections for more information about the operation of the configuration utility.

...

Below is an example of a minimal OECN$SETUP.INI file suitable for OECN RPC. The example has been simplified to just the parameters required by OECN RPC. However, DA Sites are free to use other features of SETUPENV to set logicals depending on their configuration and other uses of SETUPENV. See the OECN System Managers Manual for more information regarding SETUPENV and the OECN$SETUP.INI file.

! Define entry for District A
!
SECTION=DISTA
TYPE=DISTRICT
DESCRIPTION="District A"
LOGICAL=OECN$DTA,DKA100:[DISTA.DATA]
IDENTIFIER=”[DISTA,*]”      ! UIC group of District A users
! Define entry for District B
!
SECTION=DISTB
TYPE=DISTRICT
DESCRIPTION="District B"
LOGICAL=OECN$DTA, DKA100:[DISTB.DATA]
IDENTIFIER=DISTB_BUSINESSOFFICE  ! Identifier of District B Business Office users
IDENTIFIER=DISTB_SECRETARIES     ! Identifier of District B Secretaries posting REQs

...

For SETUPENV used interactively, the default IDENTIFIER parameters is:

IDENTIFIER=”[*,*]”

This allows all users to see the entry. For OECN RPC the default IDENTIFIER is:

IDENTIFIER=OECN_SYSMAN

This restricts the entry to only OECN DAS personnel by default. This difference in behavior is intended as a security constraint to make it more difficult for remote network clients from discovering district databases inappropriately. It also reduces confusion on the remote client by preventing a user from attempting to select a district they do not have access to.

...