Com-plete SECURITY

The Com-plete security system has been activated.

The Com-plete Security System could not be initialised.

Detailed information as to why Com-plete Security could not be initialised is given in the accompanying ZSSnnnn messages.

The Com-plete system has been initialised without Com-plete security as no request was made in the Com-plete sysparms to initialise Com-plete security.

Com-plete initialisation continues, however the Com-plete Security System is not active.

If Com-plete Security should be activated at initalisation, the correct SECSYS sysparm value should be set. Refer to the systems programmer's manual for more information.

A request to load the security tables into main storage was issued whilst a request to load the security tables was already in progress.

The request to load the security tables a second time is ignored.

Wait until the first request to load the tables has completed before issuing a new request to load the tables.

A request was made to load the security tables into main storage, however, the Com-plete security system received a reponse code indicating that the database on which the security tables should be found is not active.

The request to load the security tables is terminated.

If the database id and file number as specified in the Com-plete sysparms are correct, insure that the datbase is up before attempting to load the security tables.

A request was issued to load the Com-plete security tables, however, while reading the data from the database containing the Com-plete security file, a bad response code $1 was received.

The request to load the security tables is aborted.

Refer to the Adabas Messages and Codes manual to determine the meaning of the response code. If the databaset is in error, correct the problems with the database and retry. If not, insure that the database id and file number specified for the Com-plete security file in the Com-plete sysparms point to the correct database and file number.

A request to load the security tables into main storage was issued, however, not enough storage was available to hold the tables.

The load operation is aborted. If a valid set of tables was already present in storage, Com-plete security continues using these tables.

If this occurs at initialisation, check the storage estimates to insure that enough main storage is available for the tables that you wish to load. If it occurs during a 'reload' operation, then the storage estimates must allow for the fact that Com-plete security must maintain two copies of the tables in core to effect the changeover. Refer to the systems programmer's manual for more information on estimating storage.

When a backup file is available to Com-plete , Com-plete security first attempts to load the security tables from the backup copy. This indicates that there is an error in the backup dataset. Note, this will occur the first time that Com-plete security is started with a backup file.

The Com-plete Security System will try to read the security tables from the database. The newly loaded tables will then be stored in the backup file for future startups.

This message indicates the status of security in the Com-plete system. If $1 is yes, then Com-plete Security is active in the system. $2 indicates whether the external security system interface is active or not. This can contain NO, RACF, ACF2 or TOP-SECRET depending on the Com-plete sysparms.

An invalid COMSEC operator command was entered.

The command is ignored.

Refer to the appropriate Com-plete security system manual for details of the valid COMSEC commands.

An valid COMSEC operator command was entered, however, the paramter for the command was not valid.

The command is ignored.

Refer to the appropriate Com-plete security system manual for the correct syntax of the command.

An operator command has been entered which has changed the database id on which Com-plete expects to find the Com-plete Security file from $1 to $2.

Future requests to load the security tables will load the data from database id $2.

An operator command has been issued which has changed the file number where Com-plete expects to find the Com-plete Security file from $1 to $2.

Future requests to load the security tables will reference file number $2

A COMSEC LOAD operator command was issued, however no database id and/or file number for the Com-plete security file was available to Com-plete .

The load command is not executed.

Either identify the Com-plete secrutiy file in the Com-plete sysparms COMSECDB and COMSECFN or use the COMSEC FNR and COMSEC DBID operator commands and reissue the load.

The Com-plete security system has not been loaded. This message is always accompanied by another message which indicates the reason for the failure.

The Com-plete security system has successfully load the security data into tables in main storage.

Security checks will henceforth use the newly loaded tables.

THe Com-plete security system has been unloaded in response to a COMSEC UNLOAD operator command.

The security tables are released and no more access checks will be made by the Com-plete security system.

The Com-plete security system is not active.

The Com-plete security system has been activated in response to a COMSEC ACT operator command.

An attempt was made to activate the Com-plete security system whilst it was already active.

The activation request is ignored.

The Com-plete security system has been deactivated in response to a COMSEC DEACT operator command.

The COMSEC ENABLE command has been issued and accepted for user $1.

User $1 is henceforth allowed to access all objects.

A COMSEC RESET operator command has been issued and accepted for user $1.

Normal access checks will henceforth be performed for user $1.

A COMSEC DISABLE operator command has been issued and accepted for user $1.

User $1 is henceforth not allowed to access any objects.

An attempt has been made to modify the status of a user who is not known to the Com-plete security system.

The request is ignored.

The Com-plete security system has identified an internal logic error.

Contact your local support centre with the details of the circumstances surrounding this error.

The Com-plete security system will henceforth log security violations on the operator's console.

The Com-plete security system will not log security violations.

Three consecutive attempts have been entered to the Com-plete security system maintenance program (normally called 'COMSEC') by user id $1 from tid $2.

The program is terminated.

A security violation has occurred. The details in the message are as follows.

1. $1 - The userid of the user causing the violation.

2. $2 - The TID on which the user is running.

3. $3 - The class of access requested by the user (eg. READ, WRITE etc.)

4. $4 - Name of the object to which access was denied.

Access to the object is denied.

The Natural Security interface routine LGNSPL returned an unexpected return code $1.

The logon request is denied.

Report the circumstances surrounding the error along with the unexpected error code $1 to your local support centre.