Active Report  Time Out: ___ min.
 Print Classes: _________________________________________  SMTWTFSH
  Authorized Hours : __ __ to __ __ Days: ________
...............MAXIMUM AUTHORIZATION LEVELS BY APPLICATION......................
  Empl(01) : 9
  SPLR(48): 9  SEC.(49): 9  PROG(50): 9
**
```
Figure 14 — Device Definition Screen
# Review
## What You Have Learned
As you can readily see, the security authorization profiles for operators and terminals combine to form the (cont.)
authorizations for any given session. The authorizations consist primarily of one-digit codes where 0 is the lowest (cont.)
possible and 9 is the highest, for each of up to 50 logical applications.
You can define the logical applications via the MAGEC dictionary. Every function code must belong to one logical (cont.)
application, it may not belong to more than one. The various functions handled by a given MMP (program) may, however, (cont.)
each belong to a different logical application from one another.
As the operator attempts to do any given function, MAGEC compares his/her authorization (for the logical applications (cont.)
to which that function belongs) against the authorization level required to do that function. If the operator is not (cont.)
authorized, MAGEC never even invokes the application program; instead, a message is sent telling him/her (cont.)
"Unauthorized".
MAGEC's menu system is driven by the dictionary security parameters and definitions. It can never be out of "sync" with (cont.)
security. It requires no coding, no maintenance, and no unnecessary overhead. Operators who do not desire a menu simply (cont.)
do not request one; they can "fast path" directly to any function/screen for which they are authorized. In order to (cont.)
retain the advantages of a fully dictionary-driven system without the usual I/O overhead involved with such an (cont.)
architecture, MAGEC loads the active security and data definition specifications into main memory. You can (if you are (cont.)
authorized to do so) tell MAGEC to re-load the data at any time in order to make recent changes effective (cont.)
immediately.
The security system helps control separation of test and production environments. This enables you, in one MAGEC (cont.)
system, to conduct production work, development, and testing (prototyping) without interfering with one (cont.)
another.
## Other Interesting Functions
There are several query functions which are useful to a security officer on a day-to-day basis. Refer to the "Security" section of the *Programmer's Reference Guide* for more details.
WHOMAY xxxxxx (where xxxxxx is a valid function code)
WHODID xxxxxx (where xxxxxx is a valid function code)
WHOSON )
OPRACT nnnnnnnnn (where nnnnnnnnn is an employee#)
MALLOC 1
There are also "global change" functions for security profiles and definitions. They ask you for selection criteria to (cont.)
select which items are to be changed and to specify which parameters are to be changed and to what values within the (cont.)
selected items. The functions are:
SIFGBL
DVCGBL
FCDGBL
# Appendix A -- Starting Fresh
## On a PC
If you are doing the tutorial projects on a PC or PS/2, rather than on a mainframe computer, you have the advantage of (cont.)
being the only user of the system. In such an environment, the simplest way to ensure that you are starting fresh is to (cont.)
re-install MAGEC from the initial installation diskettes before beginning the tutorials. You should do this only if you (cont.)
are running MAGEC from your local disk, not from a shared network server--unless you coordinate your actions with the (cont.)
other users of MAGEC on your network. You can also do the procedure described below for maniframe users, if you (cont.)
prefer.
## On a Mainframe
Because it is most likely that you will interfere with other users on your multi-user mainframe system, we suggest (cont.)
strongly that you try to do these tutorials on a PC instead. If however, you must (or prefer) to do them on the (cont.)
mainframe, you should be especially careful to coordinate your activities with any other users.
At the time MAGEC is initially installed, and periodically thereafter, we strongly recommend(ed) that you backup and (cont.)
reorganize you MAGEC dictionary using the IDCAMS (or AMSERV) REPRO facility. If you have done (been doing) that, you (cont.)
can restore the FCDK1, SIFK1, and LAPK1 VSAM files to un-do the dictionary changes made in this (and the other) (cont.)
tutorials. This process must be done with careful consideration as to how it might affect other work which is being (cont.)
done at the same time. It is necessary to close the MAGEC dictionary files to your TP Monitor (CICS, Westi, etc.) while (cont.)
you are restoring them
therefore, MAGEC would be inactive during the process.
## Manually
You could, in any environment, un-do the changes made in this tutorial by manually deleting and updating the effected dictionary records, i.e.:
LAPDEL 01 ENTER (LAP 01 definition is displayed)
ENTER (LAP 01 definition deleted)
FCDCHG VACADD (FCD definition for VACADD displayed)
key changes to set all parameters to original values as shown in Figure 06 in this sectionl
ENTER
repeat above for all other VAC functions
SIFDEL 123456789 (where 123456789 is your test ID)
ENTER (your ID is deleted)
# Appendix B -- Security Data Classes
## SIF
The SIF data class is the Security Information File for operator profiles. Online maintenance is done to it via the (cont.)
SIFxxx functions. A batch index of operators can be produced using the MAGECLBR utility program with a control card (cont.)
of:
-MAGECIDX SIF
## DVC
The DVC data class is the Device profiles. Online maintenance is done via the DVCxxx functions.
## FCD
The FCD data class is the definitions of every online Function Code. Online maintenance is done to it via the FCDxxx functions. An index listing can be produced using MAGECLBR with a control card of:
-MAGECIDX FCD
## LAP
The LAP data class is the defintions for each Logical Application (a grouping of function codes). The index listing for the FCD data class above also shows Logical Applications.
## ELT
The ELT data class is the definitions for data elements. A data element is a record or portion of a record, it is the (cont.)
basic unit of transfer between the database (files) and programs. The ELT definition provides for security (cont.)
authorization requirements to control who may develop batch and online applications accessing the data element. The ELT (cont.)
data class is subordinate to the DCL (Data Class) definition. A batch report documenting all available parameters and (cont.)
information, including where-used, can be produced using the DCLDOC utility program with a control card (cont.)
of:
DCLDOC xxx
where xxx is a valid DCL name.
# Appendix C -- Global Changes
## Security Entities
The security entities in MAGEC can be maintained using the standard ...ADD, ...CHG, etc. functions as shown in this (cont.)
tutorial; or they can often be maintained using several handy global change functions provided.
A global change function simply allows you to select a set of records meeting a particular set of criteria and to (cont.)
update them all in one transaction. The special function codes used to do global changes to security entities (cont.)
are:
SIFGBL operator profiles
FCDGBL function codes
DVCGBL video and printer devices
These functions all operate in generally the same way. You first enter the function code (with a blank key value, (cont.)
usually), then you receive a screen asking you to indicate the changes you wish to make. For example, in the FCDGBL (cont.)
process you will be presented a screen which resembles the FCDCHG screen, but has underscores in all the data fields. (cont.)
You can enter the desired value into the field (or fields) you wish to alter, leaving all other fields untouched. For (cont.)
example, if you wished to change the Logical Application for a set of function codes to '01', you would type '01' into (cont.)
the Logical Application field and not type anything into any other screen field.
Next, you will be taken to a sequence of screens designed to let you select which function codes are to be updated. The (cont.)
selection is done using a screen which is very similar to a standard ...SCN function, wherein you enter a selection (cont.)
mask to search for matches. For example, you might enter 'VAC' into the first three positions of the "function code" in (cont.)
the dot mask line.
Once the screen is returned to you displaying the function codes which match your selection mask, you have one more (cont.)
chance to de-select any function codes you do not wish to update. This is done by pointing with the cursor and pressing (cont.)
a PF key; instructions are displayed on the screen to help you remember which key to use.
When you are satisfied that you have selected the function codes you wish to update, you simply press a PF key to tell (cont.)
MAGEC to apply the changes. If there were more items than could be displayed on one screenful from the scan, you can (cont.)
press a PF key to proceed forward to process another screenful in exactly the same way.
Online instructions are presented at the bottom of every panel in this sequence. No updating is done until you press (cont.)
the appropriate PF key at the end of the sequence to indicate that you wish to apply the updates to the "marked" items. (cont.)
You can abort the sequence harmlessly at any time.