Adabas Fastpath Messages

This message is either

• an unexpected error; or

• an error created intentionally by ZAP.

Report an unexpected error to Software AG.

Indicates an abnormal termination of the asynchronous buffer manager (ABM). The PSW is displayed at the point the ABM abended.

Indicates an abnormal termination of the asynchronous buffer manager (ABM). The PSW and registers were not available.

Normally follows message 0001 and is repeated 4 times. Each time it is repeated, a different set of 4 GP registers is displayed.

Indicates that a new buffer has been initialized and shows the buffer address, buffer length, starting date and time, all in hexadecimal.

Note:
For this message only, the severity code shown (xx) is overwritten with the message level parameter.

This is a warning that the buffer could not be initialized. It is preceded by a message showing the reason for failure.

The operating system would not permit Adabas Fastpath to perform certain commands; for example, GETMAIN.

Ensure that all AFPxxx and link modules are in an authorized library.

The Adabas Fastpath configuration file is not active. Adabas Fastpath will retry periodically. The Adabas response code and the configuration file SVC, DBID, and FNR are shown in hexadecimal.

Check the status of the configuration file.

An invalid Adabas response code was encountered while trying to access the Adabas Fastpath configuration file. The response code and configuration file SVC, DBID, and FNR are shown, in hexadecimal.

Check the status of the configuration file.

Global or member buffer parameters could not be found on the Adabas Fastpath configuration file for the buffer name shown.

Check the status of the configuration file.

Connected buffer parameters could not be found on the Adabas Fastpath configuration file for the buffer name shown.

Check the status of the configuration file.

The parameters for the buffer name shown would require more memory than requested in the size parameter. Buffer initialization is terminated.

Check the parameter values and adjust as necessary.

The asynchronous buffer manager (AFPABM) must be able to intercept any abnormal ABENDs to preserve operational integrity. Initialization failed for the buffer named while attempting to set the operating system ABEND trap.

An attempt was made to start the buffer named, which is already active.

The operating system GETMAIN operation failed while initializing the named buffer.

A failure occurred during the preformatting stage of initialization for the named buffer.

An error occurred during file parameter initialization of the named buffer.

The buffer parameter record on the Adabas Fastpath configuration file was updated sometime between the start and end of initialization for the buffer named.

Logon to the ID table failed. Possible reasons are as follows:

• the SVC specified in the named buffer parameters could not provide Adabas communication; or

• the database number defined for the buffer was already in use by a database or another buffer.

The specified command is valid and recognized by the asynchronous buffer manager.

The specified command is not recognized as a valid command.

The specified command is valid but processing is rejected.

Response to the HELP command.

The buffer is in the process of terminating. During this process, all tasks within the Adabas Fastpath buffer are allowed to complete normally and no new tasks are started.

Initialization for the specified buffer could not be completed because it was not possible to obtain a buffer session area for the asynchronous buffer manager.

An attempt to load the specified AFPLOOK module failed.

The database component accepted a Newcopy request.

The database component could not successfully disconnect.

The buffer ended abnormally but no specific action was necessary to provide an orderly shutdown.

An attempt to free memory after an abnormal termination failed. The attempted address is shown and should be the same as that portrayed in message 0004.

An abnormal termination occurred. The memory address shown appears to be invalid and should be the same as that portrayed in message 0004.

An abnormal termination occurred while attempting to log off from the Adabas ID table.

The snap dump of the Adabas Fastpath buffer has completed successfully. This message is issued in response to a request to snap the contents of the buffer.

The snap dump of the Adabas Fastpath buffer failed.

Adabas Fastpath processes only one operator command at a time and one is already being processed.

Resubmit the failed command.

AFPABM is attempting to stop but cannot do so until all jobs have released all Adabas Fastpath resources. The job named has not yet released resources and disconnected from the Adabas Fastpath buffer.

The database component disconnected successfully but could not log the final statistics.

An invalid Adabas response code was encountered while attempting to write a statistics log to the Adabas Fastpath configuration file. The Adabas command code and response code are shown in hexadecimal.

If the job parameter Job End Stats is set to Y, AFPABM shows the above message when the named job completes. The message shows the job name and the total number of commands for the job seen by Adabas Fastpath. Messages 0041 and 0042 should follow.

This message follows either message 0040 or 0051. It shows the Adabas Fastpath direct access optimization attempts, the number of commands saved, and the number of associated RC commands saved.

This message follows either message 0040 or 0051. It shows the Adabas Fastpath read-ahead optimization attempts, the number of commands saved, and the number of commands that were not needed (over-reads).

A buffer STOP request was issued from SYSAFP by the user shown.

A buffer RESTART request was issued from SYSAFP by the user shown.

A LOG request was issued from SYSAFP by the user shown.

A NEWCOPY request was issued from SYSAFP by the user shown.

A STOP request was issued from SYSAFP by the user shown.

The buffer is being shut down due to an operating system cancel.

The file is subject to optimization by time period and a stop time period has been reached. The scheduled stop time plus the file and database number are also shown.

The file is subject to optimization by time period and a new start time period has been reached. The scheduled start time plus the file and database number are also shown.

This message is issued automatically at normal buffer end or when the operator command STAT is issued. It shows the buffer name and the total number of commands seen by Adabas Fastpath. It is followed by messages 0041 and 0042.

The database component successfully reloaded the Adabas Fastpath nucleus.

AFPABM was unable to load the module named in the message.

Check that the Adabas Fastpath library is defined to the buffer start task and that it contains the module named.

AFPABM loaded the module named in the message but then found an error in it.

Check that the version of Adabas Fastpath matches for AFPABM and the module named.

AFPADA cannot send updates to the SYSCO daemon named. In most cases, this indicates an Entire Net-Work problem.

To maintain data integrity, stop or restart the named AFPABM hosted by the named SYSCO daemon.

The file housekeeping pulse has reinforced coherence settings that had been lost.

Contact Software AG for assistance. An internal error is happening (which is being auto-corrected) but the cause needs to be investigated.

If the job parameter Job End Stats is set to Y, Fastpath displays this message when the job completes. The message shows the job name and job number of the ending job (step).

This message is issued by the Adabas Fastpath buffer manager at startup and also at midnight.

The Adabas System Coordinator group name defined for the AFPABM does not match the group name defined for the host SYSCO daemon.

Correct the group names in the defined parameters.