Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

·Table 1 Minimal SETUPENV parameters

{table:border=1} {tr} {td:valign=top}{*}Parameter{*}{td} {td:valign=top}{*}Value{*}{td} {td:valign=top}{*}Notes{*}{td} {tr} {tr} {td:valign=top}SECTION{td} {td:valign=top}district code{td} {td:valign=top}Entity code for the district{td} {tr} {tr} {td:valign=top}DESCRIPTION{td} {td:valign=top}District name{td} {td:valign=top}Description of the district as it will be seen by the remote user{td} {tr} {tr} {td:valign=top}TYPE{td} {td:valign=top}DISTRICT{td} {td:valign=top}OECN RPC will only allow access to “DISTRICT” type entries{td} {tr} {tr} {td:valign=top}LOGICAL Or:GROUP_TABLE Or:TABLE{td} {td:valign=top}\[Varies by package\] {td} {td:valign=top}At a minimum, each district entry must provide a definition for logicals required by the package(s) being used by the district. For USAS and USPS, OECN$DTA must be defined. The definition may be provided as a hard-coded location using LOGICAL or as a reference to a logical name table, as appropriate for the DAS configuration. For EMIS, the entry might provide a definition for EMIS_ROOT or other similar logical that is used in conjunction with EMIS_SELECT.{td} {tr} {tr} {td:valign=top}IDENTIFIER{td} {td:valign=top}UIC or identifiers{td} {td:valign=top}One or more IDENTIFIER parameters must be specified to allow access to the appropriate users. OECNRPC will not permit a remote client to see entries to which they have not been explicitly granted access.{td} {tr} {table}
Wiki Markup
HTML Table
border1
Table Row (tr)
Table Cell (td)
valigntop
Parameter
Table Cell (td)
valigntop
Value
Table Cell (td)
valigntop
Notes
Table Row (tr)
Table Cell (td)
valigntop
SECTION
Table Cell (td)
valigntop
district code
Table Cell (td)
valigntop
Entity code for the district
Table Row (tr)
Table Cell (td)
valigntop
DESCRIPTION
Table Cell (td)
valigntop
District name
Table Cell (td)
valigntop
Description of the district as it will be seen by the remote user
Table Row (tr)
Table Cell (td)
valigntop
TYPE
Table Cell (td)
valigntop
DISTRICT
Table Cell (td)
valigntop
OECN RPC will only allow access to “DISTRICT” type entries
Table Row (tr)
Table Cell (td)
valigntop
LOGICAL
Or:GROUP_TABLE
Or:TABLE
Table Cell (td)
valigntop
[Varies by package]
Table Cell (td)
valigntop
At a minimum, each district entry must provide a definition for logicals required by the package(s) being used by the district. For USAS and USPS, OECN$DTA must be defined. The definition may be provided as a hard-coded location using LOGICAL or as a reference to a logical name table, as appropriate for the DAS configuration. For EMIS, the entry might provide a definition for EMIS_ROOT or other similar logical that is used in conjunction with EMIS_SELECT.
Table Row (tr)
Table Cell (td)
valigntop
IDENTIFIER
Table Cell (td)
valigntop
UIC or identifiers
Table Cell (td)
valigntop
One or more IDENTIFIER parameters must be specified to allow access to the appropriate users. OECNRPC will not permit a remote client to see entries to which they have not been explicitly granted access.

EMIS Configuration

OECN RPC will also use SETUPENV to establish the EMIS logical context for multiple databases. This is done using the same OECN$EMIS_DBS file used by EMIS_SELECT. Therefore, sites using OECN RPC must establish the standard OECN$EMIS_DBS file to define the available databases.

...