AAF* - Adabas SAF Security Messages

A required module could not be loaded. Operation terminates with an abend U0042.

Check that all required modules are available.

There is insufficient memory available for ADASAF to operate. Operation terminates with an abend U0042.

Increase the amount of memory (above the 16-megabyte line) available to the failing job.

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.

Ensure that enough memory is available.

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.

Ensure that the module is available.

One or more invalid parameters were specified in DDSAF. Operation terminates.

Correct the invalid parameters.

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.

Ensure that enough storage is available or reduce the MAXFILES parameter (this may adversely affect performance).

ADASAF echoes the parameters read from DDSAF for information and auditing purposes.

None.

ADASAF detected incorrect input in DDSAF. AAF008 is issued for each invalid parameter found and is followed by message AAF005.

Correct the invalid parameter.

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.

Ensure that enough storage is available.

ADASAF found more passwords and/or cipher codes in RACF than it could store in its table. Operation terminates.

Increase the MAXPCC parameter.

ADASAF could not extract passwords and cipher codes from RACF. Operation terminates.

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.

ADASAF has successfully initialized in FAIL or WARN mode, as indicated by XXXX.

None.

After a newcopy operator command, ADASAF was unable to reload SAFCFG. Operation terminates.

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.

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.

Take the action recommended by the accompanying message.

ADASAF must run APF-authorized. Operation terminates.

Check that all STEPLIBs are in the APF list and that ADARUN is linked with AC(1).

This message appears when an unsecured Adabas call is received from the indicated job.

The most likely cause is an installation error, either of the Adabas Router security extensions or of the Adabas link module.

This message appears after an initialization error and is preceded by a more specific error message.

Take the action recommended by the accompanying message.

This message appears during initialization if ADASAF fails to activate its Adabas Error Handling interface.

None. ADASAF continues, with its Error Handling interface disabled.

The configuration option NOTOKEN has been activated. No security checks will be performed for unsecured mainframe clients.

None.

ADASAF has detected an incompatible Configuration module. The nucleus session terminates.

Ensure that the Configuration module is created using the macros supplied with the version of ADASAF you wish to use.

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.

Correct your exit.

ADASAF cannot initialize because the module SAFPMAC has not been linked with the REUS attribute. The nucleus session terminates.

Ensure that SAFPMAC is linked REUS,NORENT.

The SAF Kernel could not initialize for some reason (indicated by a SEFMxxx message preceding the AAF028 message). The Adabas nucleus terminates.

Correct the problem which prevents the SAF Kernel from initializing (for example, increase region size or modify SAFCFG options) and restart the Adabas nucleus.

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.

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.

The SAFKRN module in use by this nucleus or daemon is not compatible with this version of Adabas SAF Security.

Ensure that you use the correct version of the Adabas Limited libraries, as documented in the Installation Prerequisites section Adabas Limited Library.

An Adabas utility security check failed. However, the utility is allowed to execute because the SAFCFG FAILUTI parameter is set to NO.

None.

The operator command is not permitted for this Adabas nucleus.

Review operator command security definitions for this Adabas nucleus.

ADAEOPTB (operator command grouping table) is in use but does not contain an entry for this operator command.

Ensure the operator command was entered correctly. Review the contents of ADAEOPTB and add this command if necessary.

ADAEOPV could not locate the Adabas SAF Security load module.

Review the Adabas SAF Security installation and ensure that it is active in this Adabas nucleus.