ACC-ESS - Com-plete TP MONITOR COMMUNICATION

This message is output when ACCESS has successfully initialised.

This message indicates that an error occurred during ACCESS initialisation, other messages will indicate the exact cause.

Communication with this ACCESS node is not possible. Attempts to communicate with this ACCESS node will be rejected with an error code (typically ADABAS response 148).

Determine the reason for the error and re-start ACCESS.

Determine the reason for the error and re-issue the ACCESS START.

This message indicates that the ADAMPM module loaded during ACCESS initialisation was found to be incorrect.

ACCESS initialisation is terminated.

Check that the correct version of the ADABAS MPM module is included in the COMPLIB concatenation.

Contact the system programmer.

This message indicates that insufficient storage was available to satisfy the GETMAIN request for access buffers.

Access initialisation is terminated.

Check that sufficient storage is available.

The amount of storage required is ((CQELEN*NCQE)+CQHLEN+8), where:

• CQELEN is the length of an ADABAS command queue element.

• NCQE is the number of CQEs requested in Com-plete sysparms.

• CQHLEN is the length of an ADABAS command queue header.

Contact the system programmer.

This message indicates that at least one parameter required for ACCESS has not been specified.

Access initialisation is terminated.

Check that the following sysparms have been specified correctly:

- ACCESS-SVC

- ACCESS-DBID

- ACCESS-NCQE

- ACCESS-NABS

Contact the system programmer.

This message indicates that access initialisation was unable to load the indicated ADABAS interface module.

Access initialisation is terminated.

Check that the indicated module is contained in the COMPLIB load library concatenation.

Contact the system programmer.

This message indicates that an ACCESS START command was issued when ACCESS was already active.

The command is ignored.

Before issuing an ACCESS START command, ACCESS must be terminated via an ACCESS STOP command.

This message indicates that the ADABAS interface modules have been loaded successfully.

This message indicates that the Com-plete ACCESS printer program has abnormally terminated.

The task ACSBEG will be automatically re-started if it has been included in ULPGMTAB.

Investigate the cause of the failure. ACSBEG should be included in ULPGMTAB so that it will be automatically re-started.

Contact the system programmer.

This message indicates that an program running on an ACCESS terminal issued a READ and a valid session does not exist.

The thread task is terminated.

Contact the system programmer.

Contact SOFTWARE AG.

This message indicates that a program running on an ACCESS terminal issued a WRITE and a valid session does not exist.

The thread task is terminated.

Contact the system programmer.

Contact SOFTWARE AG.

This message indicates that a thread task has issued a write to an ACCESS terminal and the access method has found that the output length exceeds the length of the supplied ADABAS request buffer.

The data transmitted is truncated to fit into the supplied request buffer and a response 53 is generated in the ACB.

Contact your system programmer.

The length of the request buffer generated is determined by the terminal definitions in the host system.

This message indicates that a request to reset a printer has been unsucessful.

Self-explanatory message.

This message is output access communication has been successfully terminated.

This message is output when access communication has been terminated as a result of an abend in Com-plete

Self-explanatory message.

This message is associated with TPF initialisation and indicates that the requested Adabas link module could not be loaded.

This message is associated with TPF initialisation and indicates that one of the access transaction has been incorrectly linked.

This message indicates that insufficient storage was available for TPF initialisation or (under CICS) for continuation of the access transaction.

This message is associated with TPF printout spooling under CICS and indicates that the spool transaction could not be started by the control transaction.

This message is associated with TPF printout spooling and indicates that the exec cics enq has failed (this should not occur).

This message is associated with TPF error recovery and indicates that an error or abend has occured in a TPF transaction.

This message is associated with TPF printout spooling and is output whenever the printout control transaction is started directly from a terminal device.

This message is purely informative.

This message is associated with TPF printout spooling and informs the user of how many spool tasks were started by the control transaction.

The indicated number of printout spool tasks have been started.

This message is informative.

This message is associated with TPF printout spooling. The spool transaction cannot be started on a terminal device.

The spool transaction terminates.

It is not possible to start the spool transaction directly from a terminal device. Use the control transaction instead.

This message is associated with TPF reverse access processing and indicates that the program name supplied as the continuation program is invalid or could not be loaded.

Ensure that the program specified in the reverse access call is both defined to and installed on the host CICS system.

This message is associated with TPF printout spooling and indicates that an intervention required condition has been detected on the indicated device.

This error is associated with TPF mainline processing and indicates that an error has occured during relocation of the access transaction.

This message is associated with TPF printout spooling and indicates that an error condition has been detected on the indicated device.

This message is associated with the TPF TSO host interface, it indicates that the module ADALNK could not be loaded.

This message is associated with TPF printout spooling initialisation and indicates that the printout spool transaction AB45 has been started via the PLT and will re-start in one minute.

This message is associated with the TPF Com-plete host module and indicates that the parameter area passed is invalid.

This message is associated with TPF CICS printout spooling and indicates that the control transaction has abnormally terminated.

This message is associated with the TPF CICS host system and indicates that a terminal CONVERSE has failed.

This message is associated with TPF CICS reverse access processing and indicates that the requested CICS program could not be loaded.

This message is associated with TPF CICS mainline termination and indicates that the requested continuation program could not be XCTLed.

This message is associated with TPF mainline processing and indicates that there was insuffient storage available to obtain communication buffers.

This message is associated with TPF mainline processing and indicates that storage was not available to obtain buffer space for Adabas communication.

This message is associated with TPF host initialisation and indicates that the requested ACSTAB module is invalid.

This message is associated with TPF host transaction initialisation and indicates that the user has specified an unknown target destination.

This message is associated with TPF host transaction initialisation and indicates that the destination table (ACSTBL) cannot be found.

This message is associated with TPF host transaction processing. It is not possible for a user to specify host and target to be the same node.

This message is associated with TPF transaction processing and indicates that the input read from the terminal device was too large for the buffer provided by the TPF host transaction.

This message is associated with TPF under TSO. The screen-to-hardcopy function is not available under ADABAS-TPF/TSO.

This message is associated with TPF transaction processing and indicates that the transmission of data from the host to the target TPF system obtained the indicated error response.

The TPF session is terminated.

Contact your system programmer.

The following codes are issued from Com-plete :

- 22 - Invalid command

- 40 - Access prefix invalid

- 50 - Record buffer (=screen size) too small for output

- 77 - No tib available

All other codes can be found in the ADABAS Errors and Codes Manual.

This message indicates that the requested target node is not currently known to the Adabas router SVC.

This message is associated with TPF transaction processing and indicates that the length of the data to be transmitted to the target node is incorrect.

This message is associated with TPF transaction processing and indicates that the data received from the target node was not intended for output on the current terminal device.

This message is associated with TPF CICS printout spooling. The indicated printer device is out of service for one of the reasons shown.

This message is associated with TPF CICS printout spooling. The indicated printer device is unavailable due to a permanent error condition.