Every pubset contains the SYSSRPM file under the TSOS ID. This forms the user catalog, in which information on the user IDs of BS2000 is stored.
The SYSSRPM.BACKUP file (also called .BACKUP) also exists under the TSOS ID. The .BACKUP file is a copy of the user catalog. It acts as a scratch file if the user catalog is backed up or has to be reconstructed from a backup.
Both files are opened by a system task when a pubset is imported, and are closed again by the same task when the pubset is exported. Direct access to the files is therefore not possible.
The $TSOS.SYSSRPM file
The system file $TSOS.SYSSRPM is an NK-ISAM file.
The $TSOS.SYSSRPM file is accessed from a server task (the SRPM task TSN RP01 or RP02). With the import, the file is opened by the server task and remains open until export. $TSOS.SYSSRPM cannot be accessed directly.
The file $TSOS.SYSSRPM includes:
information on access control for user IDs (also for extended access control with SECOS)
system-global privileges
BS2000 user groups
The SYSSRPM file forms the user catalog.
User catalog of the home pubset
The user catalog of the home pubset contains system-specific data such as BS2000 access rights (user ID, account number, logon password, SPOOLOUT class, mailing address, etc.) and the standard catalog ID.
User catalogs of the imported pubsets
The user catalogs of the imported pubsets contain pubset-specific data. Among other details, this includes information about:
the maximum storage space available to the individual users on each pubset
if applicable, the permission to exceed this limit
catalog allocation
The system-specific information of the home pubset may also be contained in the user catalogs of the imported pubsets; However, for checking purposes the system refers only to the user catalog of the home pubset. The system-specific data on the imported pubsets is required only if these pubsets are used as reserve home pubsets for BS2000 system initialization and for the subsequent session.