NET/MASTER Network Control Language (NCL) Programmer's Guide

The Standard Map $SEC
Standard and User-Defined Maps
106160 Tandem Computers Incorporated 11–23
The Standard Map
$SEC
The standard map $SEC is used by the SECCALL verbs. The SECCALL verbs—
SECCALL ADD, SECCALL CHANGE, and so on—manipulate user ID definition
records in the User ID Management Services (UMS) database. The default map used
by these verbs to interpret the data in an MDO variable that contains a record being
written to or read from the User ID Management Services (UMS) database is $SEC.
Figure 11-3 shows the structure of the map $SEC. It shows that data structured by this
map corresponds to the following MDO variable:
& stem-name .
stem-name .
specifies the name of the stem of the MDO variable that holds the record.
The name of a field in a record corresponds to MDO variables such as:
& stem-name .USERID
& stem-name .GROUP_USERID
& stem-name .NORM_UDEFN
If you are reading a record from the UMS database using SECCALL GET or SECCALL
QUERY, you do not have to use the ASSIGN verb to create the MDO variable that
holds the record. Mapping Services automatically creates an MDO variable using the
stem name you specify after the MDO operand. The following example reads a record
from the UMS database into the MDO variable &RECORD.:
SECCALL GET USERID=NNM001 MDO=&record.
If you are writing a record to the UMS database using SECCALL ADD, SECCALL
CHANGE, or SECCALL UPDATE, you can either use the ASSIGN verb to create the
MDO variable that holds the record before you store data in the MDO variable and
write it to the UMS database or you can use the MDO variable created by SECCALL
GET. The following example creates an MDO variable, &ABC., using the ASSIGN
verb and writes it to the UMS database using the SECCALL ADD verb:
ASSIGN MDO=&abc. MAP=$SEC
…
/* store data in MDO variable */
…
SECCALL ADD USERID=NNM002 MDO=&abc.
The SECCALL verbs are discussed in more detail in Section 18, “Advanced NCL
Programming.”
Note Elements in an MDO variable that are not documented in Figure 11-3 are not currently supported.