This section contains a description of the SAF Security Kernel messages.
This document covers the following topics:
The following messages are displayed on the operator console and system message datasets. The messages may be issued by the SAF Security Kernel component (in a daemon, an Adabas nucleus, an Entire Net-Work node, or an Adabas SQL server) or by another product into which SAF Security is installed, such as Natural, Entire Broker, Entire Net-Work, or Adabas SQL Server.
SEFM001 | SEFM002 | SEFM004 | SEFM006 | SEFM008 | SEFM009 | SEFM013 | SEFM014 | SEFM015 | SEFM016 | SEFM017 | SEFM020 | SEFM021 | SEFM025 | SEFM026 | SEFM028 | SEFM029 | SEFM030 | SEFM031 | SEFM049 | SEFM050 | SEFM051 | SEFM255
SEFM001 | *SSSSSSSS : user : resource |
Explanation |
The security system determined user does not have authorization for resource. System return and reason codes are given in the hexadecimal string SSSSSSSS. This message is displayed when access has been denied to a particular resource. |
SEFM002 | *XX to request FF : user : resource |
Explanation |
An unexpected response code XX was received from the SAF Security Kernel for user when requesting function FF to be performed. |
SEFM004 | *NATURAL programs not extracted |
Explanation |
The SAF Security Kernel was not able to extract a list of protected program objects from the security system on behalf of Natural users. |
Action |
Obtain a trace of SAF call RACROUTE EXTRACT from the security system and contact your Software AG technical support representative. ACF2 and Top Secret users should ensure that the protected programs have been extracted from the security system and supplied to the SAF Security Kernel via the SEFEXT DD statement in the daemon started task JCL. |
SEFM006 | *ADARSP XX(xx) to request FF : user |
Explanation |
The SAF Security Kernel returned Adabas response XX and subresponse xx to request FF for user. |
Action |
Ensure that the SAF Kernel started task is active. Check its output for error messages. Take the necessary remedial action indicated by the Adabas response code. |
SEFM008 | *SAF Security Kernel (Vx.x) started |
Explanation |
The SAF Security Kernel initialized successfully. |
Action |
Information message only. |
SEFM009 | *Module MMMMMMMM not loaded |
Explanation |
The SAF Security Kernel could not load the stated module. |
Action |
Ensure that the module is in the steplib and the region size is sufficient. |
SEFM013 | *Less storage acquired than specified |
Explanation |
The SAF Security Kernel was not able to allocate all the storage required to satisfy the buffer size specified in its parameters. |
Action |
Operation continues. |
Action |
Ensure region size is sufficient and parameters are appropriate. |
SEFM014 | *No storage could be acquired |
Explanation |
The SAF Security Kernel could obtain no storage at system start-up. |
Action |
Operation has terminated. |
Action |
Ensure region size is sufficient and system parameters are appropriate. |
SEFM015 | *Logic error - XXXX for request FF : user |
Explanation |
The SAF Security Kernel suffered an internal error. |
Action |
A general restart is performed and the operation continues. |
Action |
Keep all information written to DDPRINT and contact your Software AG technical support representative. |
SEFM016 | *SAF logoff failed SSSSSSSS ACEE AAAA : user |
Explanation |
The SAF Security Kernel was unable to logoff user from the security system. The SAF error code is SSSSSSSS. |
Action |
Contact your Software AG technical support representative. |
SEFM017 | *Insufficient space to initialize - make Natural buffer XX |
Explanation |
The Natural SAF interface requires a larger value to be specified for the length of IDMSBUF parameter. |
Action |
Increase the Natural IDSIZE parameter or NSFSIZE if using Natural 4.1 or above. |
SEFM020 | *GETMAIN failed / IDSIZE error |
Explanation |
The NATURAL SAF interface could not acquire storage from the designated IDMSBUF. |
Action |
Increase NATURAL region and/or thread size. |
SEFM021 | *Illegal storage use / relocation problem |
Explanation |
Internal problem in NATURAL SAF storage use. |
Action |
Contact your Software AG technical support representative. |
SEFM025 | *NATURAL IDMSBUF parameter is not defined |
Explanation |
The Natural IDSIZE parameter has not been specified. |
Action |
Ensure IDSIZE (or NSFSIZE if using Natural 4.1 or above) is set correctly in the Natural parameters. |
SEFM026 | *NATURAL protected programs not extracted code: XX |
Explanation |
The list of protected programs could not be returned from the SAF Security Kernel to Natural. |
Action |
Ensure the same copy of the configuration module SAFCFG is used by all system components. Check that the GWSTYP parameter defined in SAFI010 and STY parameter in SAFI020 are both correctly set for the installed security system and that all installation requirements have been met. |
SEFM028 | *System files not found in environment table |
Explanation |
The current Natural system files were not matched in the table defining all possible system file sets. |
Action |
Ensure that the environment definitions in Natural Security are correct. |
SEFM029 | *Error in communications layer - check installation procedure |
Explanation |
Possible reasons for error: Adabas link module installed into this component is not reentrant. |
SEFM030 | *SQL table / view could not be identified for file (XX,YY) |
Explanation |
Interface could not identify table name for DBID/FNR of an SQL request. |
Action |
Ensure interface is correctly installed, then contact your Software AG technical support representative. |
SEFM031 | *DBID / FNR identified with SQL request not recognized XXXX |
Explanation |
Interface component could not determine the DBID/FNR associated with this SQL request. |
Action |
Contact your Software AG technical support representative. |
SEFM049 | *User type T not permitted by installed options |
Explanation |
The SAF Kernel will not permit user type T to operate using the currently installed options. |
SEFM050 | *Error writing SMF record : XX |
Explanation |
The stated error occurred when an SMF record was being written. |
SEFM051 | *SAFPRINT dataset not defined, DDPRINT will be used |
Explanation |
SAFPRINT=Y is set in SAFCFG, but no SAFPRINT dataset is defined. |
SEFM255 | *Unauthorized use of request |
Explanation |
Attempted illegal use of security request. |
Action |
Contact your Software AG technical support representative. |
The following messages are displayed in response to operator commands being processed by the SAF Security Kernel.
SEFM900 | SEFM901 | SEFM909 | SEFM910 | SEFM911 | SEFM913 | SEFM914 | SEFM916 | SEFM918 | SEFM919
SEFM900 | * Operator issued command : XXXXXXXX |
Explanation |
SAF Security Kernel received the stated operator command. |
Action |
Information message only. |
SEFM901 | * SAF Security Kernel - general statistics (at hhhhhhhh) |
Explanation | SEFM901 * SAF SECURITY KERNEL - SERVER STATISTICS (AT 12C47000) SEFM902 * RESOURCE CHECK(+VE) CHECH(-VE) CHECK SAVED OVERWRITES LEN SEFM903 * APPLICATION 10 0 0 0 8 SEFM903 * DBMS CHECK 0 0 0 0 17 SEFM903 * SYSMAIN 0 0 0 0 21 SEFM903 * SYSTEM FILE 2 0 0 0 40 SEFM903 * PROGRAM 0 0 0 0 17 SEFM903 * BROKER 0 0 0 0 68 SEFM903 * NET-WORK 0 0 0 0 17 SEFM903 * SQL SERVER 0 0 0 0 32 SEFM904 * USERS - ACTIVE: 1 FREE: 2051 OVEWRITES: 0 Operator command for general statistics was issued. The address in the first line is the address of the SAF Kernel's storage cache. |
SEFM909 | * SAF Gateway - shutdown initiated |
Explanation |
Operator issued command to shut-down the daemon started task. This message is also issued when a secure Adabas nucleus, Net-Work node or Adabas SQL server terminates. |
SEFM910 | *SAF Gateway - list all active users |
Explanation | SEFM910 * SAF GATEWAY - LIST ALL ACTIVE USERS SEFM911 * USERID CHECK(+VE) CHECH(-VE) CHECK SAVED OVERWRITES BUFF SEFM912 * K11079 3 0 0 0 0 Operator issued command to display list of currently active users. |
SEFM911 | *userid . . . |
Explanation | SEFM911 * SJU CHECK(+VE) CHECH(-VE) CHECK SAVED OVERWRITES BUFF SEFM912 * APPLICATION 10 0 0 0 10 EFM912 * DBMS CHECK 0 0 0 0 0 EFM912 * SYSMAIN 0 0 0 0 0 EFM912 * SYSTEM FILE 2 0 0 0 2 EFM912 * PROGRAM 0 0 0 0 0 EFM912 * BROKER 0 0 0 0 0 EFM912 * NET-WORK 0 0 0 0 0 EFM912 * SQL SERVER 0 0 0 0 0 Operator issued command to display statistics specific to a currently active user. |
SEFM913 | * No active users found in SAF Security Kernel |
Explanation |
No active users were found in SAF Security Kernel. |
SEFM914 | * Requested user xxxxxxxx not found in SAF Security Kernel |
Explanation |
The requested user was not found in the SAF Security Kernel. |
SEFM916 | * 129D2000 D5C1F2E2 C9C1F3F2 B79931B7 NA2SIA32.r..R.Y/ |
Explanation |
This message contains the results of an SSNAP command. Each SSNAP snaps up to 256 bytes and shows the address, the hexadecimal storage contents, and the interpretation. |
SEFM918 | * Supplied address is outside of legal range |
Explanation |
An attempt was made to snap storage outside the bounds of the SAF Kernel's cache. |
SEFM919 | *Operator command did not contain required argument(s) |
Explanation |
A required parameter was omitted from an operator command. For example, SUSTAT with no userid specified. |
These informational messages are issued by the SAF Security Daemon during initialization:
SAFD04I | SAFD11I | SAFD12I | SAFD21I | SAFD14I | SAFD15I | SAFD40S | SAFD42S | SAFD43S
SAFD04I | Input parameter: XXX |
Explanation |
The daemon echoes the values of the supplied DDCARD parameters. |
SAFD11I | SAF Kernel is active on node nnnnn sss CIB=aaaaaaaa |
Explanation |
The daemon is now active and ready to receive security requests; nnnnn is the node ID, sss is the SVC number, and aaaaaaaa is the address of the daemon's main storage area. |
SAFD12I | Oper type in: SAF xxxxx |
Explanation |
Message 12I is issued before processing of an operator command. |
SAFD21I | Operator command processed successfully |
Explanation |
Message 21I is issued after processing of an operator command. |
SAFD14I | Target nnnnn termination in progress |
Explanation |
Message 14I is issued during daemon termination (nnnnn is the daemon's node ID). |
SAFD15I | Target nnnnn ended normally |
Explanation |
Message 15I is issued during daemon termination (nnnnn is the daemon's node ID). |
SAFD40S | Abend code Psw pppppppp pppppppp |
Explanation |
Message 40S is issued during abnormal termination. It shows the abend code, Program Status Word, module that abended and register contents. In the event of an abend, please ensure you collect the messages, the dump and any trace messages or snaps that have been generated. |
SAFD42S | Module module entry entry-point offset offset |
Explanation |
Message 42S is issued during abnormal termination. It shows the abend code, Program Status Word, module that abended and register contents. In the event of an abend, please ensure you collect the message, the dump and any trace messages or snaps that have been generated. |
SAFD43S | Regs 00-03 register contents Regs 04-07 register contents Regs 08-11 register contents Regs 12-15 register contents |
Explanation |
Message 43S is issued during abnormal termination. It shows the abend code, Program Status Word, module that abended and register contents. In the event of an abend, please ensure you collect the message, the dump and any trace messages or snaps that have been generated. |