AAF* - Adabas SAF Security Messages

#### Search Results

Search

# AAF* - Adabas SAF Security Messages

The following message groups are described:

- AAF0* - ADASAF Messages

- AAF1* - ADAEOPV Messages

## AAF0* - ADASAF Messages

### Overview of Messages

`AAF001 | AAF002 | AAF003 | AAF004 | AAF005 | AAF006 | AAF007 | AAF008 | AAF009 | AAF010 | AAF011 | AAF012 | AAF013 | AAF015 | AAF016 | AAF017 | AAF018 | AAF019 | AAF020 | AAF021 | AAF022 | AAF023 | AAF024 | AAF028 | AAF029 | AAF030 | AAF031 | AAF032 | AAF033 | AAF034 | AAF036 | AAF037 | AAF038 | AAF041 | AAF042`

AAF001 | Unable to load required modules
Explanation | A required module could not be loaded. Operation terminates with an abend U0042.
Action | Check that all required modules are available.

AAF002 | Unable to allocate required storage
Explanation | There is insufficient memory available for ADASAF to operate. Operation terminates with an abend U0042.
Action | Increase the amount of memory (above the 16-megabyte line) available to the failing job.

AAF003 | dbid Unable to allocate NRS storage
Explanation | ADASAF needs approximately 2KB of memory below the 16-megabyte line. If the memory is not available at initialization (or after a `newcopy` operator command), ADASAF issues this message and operation terminates.
Action | Ensure that enough memory is available.

AAF004 | dbid Module xxxxxxxx not loaded
Explanation | The indicated module could not be loaded during initialization or during the`newcopy` operator command. If the module is required (rather than optional), operation terminates.
Action | Ensure that the module is available.

AAF005 | dbid Invalid parameters detected
Explanation | One or more invalid parameters were specified in DDSAF. Operation terminates.
Action | Correct the invalid parameters.

AAF006 | dbid Allocation of user file cache failed
Explanation | ADASAF allocates a user file cache above the 16-megabyte line. If the storage is not available at initialization (or after a `newcopy` operator command), ADASAF issues this message and operation terminates.
Action | Ensure that enough storage is available or reduce the `MAXFILES` parameter (this may adversely affect performance).

AAF007 | dbid INPUT PARAMETER
Explanation | ADASAF echoes the parameters read from DDSAF for information and auditing purposes.
Action | None.

AAF008 | dbid Invalid parameter: INPUT PARAMETER
Explanation | ADASAF detected incorrect input in DDSAF. AAF008 is issued for each invalid parameter found and is followed by message AAF005.
Action | Correct the invalid parameter.

AAF009 | dbid Allocation of Password/Cipher Code cache failed
Explanation | There is insufficient storage available above the 16-megabyte line to allocate the table. Each entry requires 16 bytes and the table has a 32-byte header. Operation terminates.
Action | Ensure that enough storage is available.

AAF010 | dbid Password/Cipher Code cache too small - increase MAXPC
Explanation | ADASAF found more passwords and/or cipher codes in RACF than it could store in its table. Operation terminates.
Action | Increase the `MAXPCC` parameter.

AAF011 | dbid Error extracting Passwords/Cipher Codes from RACF
Explanation | ADASAF could not extract passwords and cipher codes from RACF. Operation terminates.
Action | Check that you have specified the correct resource class and entity name format. Activate tracing and check for any errors or warnings. Check the system log for RACF messages.

AAF012 | dbid Adabas SAF VX.X.X is active in XXXX mode
Explanation | ADASAF has successfully initialized in FAIL or WARN mode, as indicated by XXXX.
Action | None.

AAF013 | dbid Nucleus Administration (DBADMIN) is active in XXXX mode
Explanation | The DBADMIN configuration parameter is set to Y enabling nucleus administration function security in FAIL or WARN mode, as indicated by XXXX
Action | None.

AAF015 | dbid Newcopy of Configuration module failed
Explanation | After a `newcopy` operator command, ADASAF was unable to reload SAFCFG. Operation terminates.
Action | This error occurs only if there is a shortage of storage or the module SAFCFG was deleted from the load library after initialization. Determine which of these is the case and correct it.

AAF016 | dbid Newcopy reinitialization failed
Explanation | This message appears after a failure during `newcopy` processing. It should be accompanied by a more detailed error message specifying the nature of the failure.
Action | Take the action recommended by the accompanying message.

AAF017 | dbid Not APF authorized
Explanation | ADASAF must run APF-authorized. Operation terminates.
Action | Check that all STEPLIBs are in the APF list and that ADARUN is linked with `AC(1)`.

AAF018 | dbid No security details for job JOBNAME
Explanation | This message appears when an unsecured Adabas call is received from the indicated job.
Action | The most likely cause is an installation error, either of the Adabas Router security extensions or of the Adabas link module.

AAF019 | dbid ADASAF initialization error(s) - Nucleus will terminate
Explanation | This message appears after an initialization error and is preceded by a more specific error message.
Action | Take the action recommended by the accompanying message.

AAF020 | dbid Unable to add ADASAF Smart Management PIN
Explanation | This message appears during initialization if ADASAF fails to activate its Adabas Error Handling interface.
Action | None. ADASAF continues, with its Error Handling interface disabled.

AAF021 | dbid NOTOKEN is set - calls from unsecured clients are allowed
Explanation | The configuration option `NOTOKEN` has been activated. No security checks will be performed for unsecured mainframe clients.
Action | None.

AAF022 | dbid Incompatible Configuration module detected
Explanation | ADASAF has detected an incompatible Configuration module. The nucleus session terminates.
Action | Ensure that the Configuration module is created using the macros supplied with the version of ADASAF you wish to use.

AAF023 | dbid Invalid xxxx parameter returned by ADASAFX2
Explanation | Your password/cipher code exit has returned incorrect data, as indicated by xxxx: type: the returned code type was neither password nor cipher code code: no password/cipher code was returned file: no file number was returned The nucleus session terminates.
Action | Correct your exit.

AAF024 | ADASAF installation error: SAFPMAC not linked REUSable
Explanation | ADASAF cannot initialize because the module SAFPMAC has not been linked with the `REUS` attribute. The nucleus session terminates.
Action | Ensure that SAFPMAC is linked `REUS,NORENT`.

AAF028 | dbid SAF Kernel initialization error - Nucleus will terminate
Explanation | The SAF Kernel could not initialize for some reason (indicated by a SEFMxxx message preceding the AAF028 message). The Adabas nucleus terminates.
Action | Correct the problem which prevents the SAF Kernel from initializing (for example, increase region size or modify SAFCFG options) and restart the Adabas nucleus.

AAF029 | dbid No access to class/resource
Explanation | The execution security check made when starting a nucleus or utility has failed. The job abends U0042. Class and resource show the resource class and profile name against which the check was made.
Action | Check that the security class and resource name are correct and that they have been defined to the external security system, with the appropriate access permissions.

AAF030 | dbid Incompatible version of SAFKRN detected
Explanation | The SAFKRN module in use by this nucleus or daemon is not compatible with this version of Adabas SAF Security.
Action | Ensure that you use the correct version of the Adabas Limited libraries, as documented in the Installation Prerequisites section Adabas Limited Library.

AAF031 | dbid Utility execution permitted because FAILUTI=NO
Explanation | An Adabas utility security check failed. However, the utility is allowed to execute because the SAFCFG FAILUTI parameter is set to NO.
Action | None.

AAF032 | dbid Ignoring invalid SAFTRT
Explanation | A site defined translation table SAFTRT has been detected which does not begin with the eye-catcher "SAFTRT" and is therefore determined to be invalid. The default internal translation table will be used instead.
Action | Check the SAFTRT assembly and ensure the site defined translation table is of the correct format. Refer to the sample SAFTRT member supplied on Adabas Limited source library for the correct format.

AAF033 | dbid Incompatible version of SAFPSEC detected
Explanation | The SAFPSEC module in use by this nucleus or daemon is not compatible with the currently installed version of Adabas SAF Security.
Action | Ensure that you use the correct version of the Adabas Limited libraries, as documented in the "Adabas Limited Library" section of the "Software Prerequisites" section of the Adabas SAF Security Installation.

AAF034 | dbid SNEWCOPY in progress – operator command ignored
Explanation | Adabas SAF Security operator commands are ignored while newcopy processing is in progress.
Action | Wait a while and issue the operator command again.

AAF036 | dbid UTI value and utility version incompatible. Default to UTI=1
Explanation | The utility version is not compatible with a UTI configuration parameter value greater than 1. The current setting is overridden with the default value of 1.
Action | None.

AAF037 | dbid XXXXXXXX version not supported
Explanation | The version of the grouping table indicated by XXXXXXXX is not compatible with the version of Adabas SAF Security.
Action | Assemble a grouping table that is compatible with the version of Adabas SAF Security.

AAF038 | dbid No access to the following resource for class XXXXXXXX: resource-name
Explanation | The security check made when starting a nucleus or utility has failed. XXXXXXXX and resource-name show the resource class and resource name against which the check was made.
Action | Check that the security class and resource name are correct and that they have been defined to the external security system, with the appropriate access permissions.

AAF041 | dbid Incompatible version of ADAPOP detected. Terminating.
Explanation | This message indicates that Adabas SAF Security is operating under Entire Net-Work, however the version of ADAPOP is not compatible for this type of operation.
Action | Refer to the Installation section of the SAF Security Kernel (Adabas for Mainframes > SAF Security Kernel > Installation) for information regarding the necessary prerequisites for the correct operation of Adabas SAF Security under Entire Net-Work.

AAF042 | dbid Signal listeners requested but incompatible runtime
Explanation | This message indicates that signal listeners have been requested by configuration but there is an incompatibility between the Adabas SAF Security and the Adabas Limited Library (WAL) runtimes.
Action | Ensure Adabas SAF Security is at least version 8.4 SP1, and the Adabas Limited Library (WAL) is at least version 8.5 SP4 Patch level 1.

## AAF1* - ADAEOPV Messages

The following messages in response to operator commands may be issued by ADAEOPV, if you have linked it with ADAIOR.

### Overview of Messages

`AAF101 | AAF102 | AAF103`

AAF101 | SAF VIOLATION
Explanation | The operator command is not permitted for this Adabas nucleus.
Action | Review operator command security definitions for this Adabas nucleus.

AAF102 | NO ADAEOPTB
Explanation | ADAEOPTB (operator command grouping table) is in use but does not contain an entry for this operator command.
Action | Ensure the operator command was entered correctly. Review the contents of ADAEOPTB and add this command if necessary.

AAF103 | AAF NOT FOUND
Explanation | ADAEOPV could not locate the Adabas SAF Security load module.
Action | Review the Adabas SAF Security installation and ensure that it is active in this Adabas nucleus.