Belkin F5D5230-F Manual de instalación Pagina 102

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 115
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 101
102
© 2002. Xephon UK telephone 01635 33848, fax 01635 38345. USA telephone (303) 410 9344, fax (303) 438 0290.
BUILDING THE RACF DATABASE
Before starting to build the RACF database, we had to impose a
freeze on changes to the ACF2 database. However, since this was a
production database, a total freeze was impossible and emergency
changes to ACF2 were allowed. There was a cut-over point to
security changes, after which we itemized all changes for later transfer
to RACF.
Once the RACF group structure was finalized (on paper), we proceeded
to define to RACF the various profiles groups, userids, dataset, and
resource in that order. This order is very important without groups,
you cannot build userids, because userids require you to specify the
default group for the user. And without userids and groups, you cannot
define profiles the access lists in profiles require userid and group
information.
We made a lot of use of the EDIT function of ISPF/TSO to define the
RACF profiles. However, although ISPF/TSO edit functions (and
CLISTs) are sufficient for smaller installations, larger installations
may prefer to use programming languages such as SAS to build RACF
profiles from the ACF2 database. The benefit of this method is that
you make fewer typographical errors.
The idea is to dump all ACF2 information into flat files, and use this
as input, to come up with RACF commands in a flat file (output).
These RACF commands can then be executed in batch to build the
RACF database.
To define the group profiles, we used listings containing all unique
UID strings, and then used the grouping information provided therein.
This, together with the group structure described above, provided the
material to build a list of ADDGROUP commands for RACF. These
commands were processed in batch, on the test machine that had the
RACF database.
Similarly, to define all user profiles, we obtained a list of userids in
ACF2, using one of the ACF2 reporting utilities. We then edited this
list to derive a list of ADDUSER commands for input to RACF, in
batch.
Vista de pagina 101
1 2 ... 97 98 99 100 101 102 103 104 105 106 107 ... 114 115

Comentarios a estos manuales

Sin comentarios