ACC-ESS - Com-plete TP MONITOR COMMUNICATION

#### Search Results

Search

# ACC-ESS - Com-plete TP MONITOR COMMUNICATION

### Overview of Messages

`ACS1001 | ACS1002 | ACS1003 | ACS1004 | ACS1005 | ACS1006 | ACS1007 | ACS1008 | ACS2001 | ACS2002 | ACS2003 | ACS2004 | ACS2010 | ACS2020 | ACS4001 | ACS4002 | ACS4003 | ACS5001 | ACS5002 | ACS5003 | ACS5004 | ACS5005 | ACS5006 | ACS5007 | ACS5008 | ACS5009 | ACS5010 | ACS5011 | ACS5012 | ACS5013 | ACS5014 | ACS5020 | ACS5030 | ACS5031 | ACS5040 | ACS5042 | ACS5044 | ACS6101 | ACS6102 | ACS6201 | ACS6202 | ACS6203 | ACS6204 | ACS6301 | ACS6402 | ACS6501 | ACS6502 | ACS6503 | ACS6504 | ACS7101 | ACS7102`

ACS1001 | ACCESS node $1 is initialized
Explanation: | This message is output when ACCESS has successfully initialised.

ACS1002 | ACCESS error in startup phase
Explanation: | This message indicates that an error occurred during ACCESS initialisation, other messages will indicate the exact cause.
System action: | 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).
System programmer info: | Determine the reason for the error and re-start ACCESS.
Computer operator info: | Determine the reason for the error and re-issue the ACCESS START.

ACS1003 | ADAMPM Version is incorrect
Explanation: | This message indicates that the ADAMPM module loaded during ACCESS initialisation was found to be incorrect.
System action: | ACCESS initialisation is terminated.
System programmer info: | Check that the correct version of the ADABAS MPM module is included in the COMPLIB concatenation.
Computer operator info: | Contact the system programmer.

ACS1004 | ACCESS buffer allocation failed
Explanation: | This message indicates that insufficient storage was available to satisfy the GETMAIN request for access buffers.
System action: | Access initialisation is terminated.
System programmer info: | 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.
Computer operator info: | Contact the system programmer.

ACS1005 | ACCESS Sysparms are incomplete
Explanation: | This message indicates that at least one parameter required for ACCESS has not been specified.
System action: | Access initialisation is terminated.
System programmer info: | Check that the following sysparms have been specified correctly: - ACCESS-SVC - ACCESS-DBID - ACCESS-NCQE - ACCESS-NABS
Computer operator info: | Contact the system programmer.

ACS1006 | Error loading module $1
Explanation: | This message indicates that access initialisation was unable to load the indicated ADABAS interface module.
System action: | Access initialisation is terminated.
System programmer info: | Check that the indicated module is contained in the COMPLIB load library concatenation.
Computer operator info: | Contact the system programmer.

ACS1007 | ACCESS is already active
Explanation: | This message indicates that an ACCESS START command was issued when ACCESS was already active.
System action: | The command is ignored.
Computer operator info: | Before issuing an ACCESS START command, ACCESS must be terminated via an ACCESS STOP command.

ACS1008 | ADAMPM, ADALNK, and ADAIOR loaded successfully
Explanation: | This message indicates that the ADABAS interface modules have been loaded successfully.

ACS2001 | ACSBEG terminated abnormally
Explanation: | This message indicates that the Com-plete ACCESS printer program has abnormally terminated.
System action: | The task ACSBEG will be automatically re-started if it has been included in ULPGMTAB.
System programmer info: | Investigate the cause of the failure. ACSBEG should be included in ULPGMTAB so that it will be automatically re-started.
Computer operator info: | Contact the system programmer.

ACS2002 | Unexpected READ (TIB has no CQE)
Explanation: | This message indicates that an program running on an ACCESS terminal issued a READ and a valid session does not exist.
System action: | The thread task is terminated.
Terminal operator info: | Contact the system programmer.
System programmer info: | Contact SOFTWARE AG.

ACS2003 | Unexpected WRITE (TIB has no CQE)
Explanation: | This message indicates that a program running on an ACCESS terminal issued a WRITE and a valid session does not exist.
System action: | The thread task is terminated.
Terminal operator info: | Contact the system programmer.
System programmer info: | Contact SOFTWARE AG.

ACS2004 | Output too large for $1
Explanation: | 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.
System action: | The data transmitted is truncated to fit into the supplied request buffer and a response 53 is generated in the ACB.
Terminal operator info: | Contact your system programmer.
System programmer info: | The length of the request buffer generated is determined by the terminal definitions in the host system.

ACS2010 | Unable to reset printer $1
Explanation: | This message indicates that a request to reset a printer has been unsucessful.

ACS2020 | $1
Explanation: | Self-explanatory message.

ACS4001 | This ACCESS node is no longer active
Explanation: | This message is output access communication has been successfully terminated.

ACS4002 | This ACCESS node is no longer active
Explanation: | This message is output when access communication has been terminated as a result of an abend in Com-plete

ACS4003 | ACSBEG is active in TID $1 for $2
Explanation: | Self-explanatory message.

ACS5001 | The ADABAS link module $1 could not be loaded
Explanation: | This message is associated with TPF initialisation and indicates that the requested Adabas link module could not be loaded.

ACS5002 | ACCESS has not been linked properly
Explanation: | This message is associated with TPF initialisation and indicates that one of the access transaction has been incorrectly linked.

ACS5003 | Insufficient storage for initialisation / continuation
Explanation: | This message indicates that insufficient storage was available for TPF initialisation or (under CICS) for continuation of the access transaction.

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

ACS5005 | Program already enqueued, this SHOULD NOT OCCUR...
Explanation: | This message is associated with TPF printout spooling and indicates that the exec cics enq has failed (this should not occur).

ACS5006 | C.I.C.S error/abend
Explanation: | This message is associated with TPF error recovery and indicates that an error or abend has occured in a TPF transaction.

ACS5007 | ACSBEG45 started from terminal
Explanation: | This message is associated with TPF printout spooling and is output whenever the printout control transaction is started directly from a terminal device.
Terminal operator info: | This message is purely informative.

ACS5008 | ACSBEG45 $1 tasks started
Explanation: | This message is associated with TPF printout spooling and informs the user of how many spool tasks were started by the control transaction.
System action: | The indicated number of printout spool tasks have been started.
Terminal operator info: | This message is informative.

ACS5009 | ACSSPOOL not allowed from terminal
Explanation: | This message is associated with TPF printout spooling. The spool transaction cannot be started on a terminal device.
System action: | The spool transaction terminates.
Terminal operator info: | It is not possible to start the spool transaction directly from a terminal device. Use the control transaction instead.

ACS5010 | Continuation program-id invalid
Explanation: | 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.
Appl. programmer info: | Ensure that the program specified in the reverse access call is both defined to and installed on the host CICS system.

ACS5011 | Intervention required for $1
Explanation: | This message is associated with TPF printout spooling and indicates that an intervention required condition has been detected on the indicated device.

ACS5012 | ACCESS program has been relocated
Explanation: | This error is associated with TPF mainline processing and indicates that an error has occured during relocation of the access transaction.

ACS5013 | Printer error for printer $1
Explanation: | This message is associated with TPF printout spooling and indicates that an error condition has been detected on the indicated device.

ACS5014 | Unable to load 'ADALNK'
Explanation: | This message is associated with the TPF TSO host interface, it indicates that the module ADALNK could not be loaded.

ACS5020 | ACSBEG45 will start in 1 minute
Explanation: | 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.

ACS5030 | Common area address invalid
Explanation: | This message is associated with the TPF Com-plete host module and indicates that the parameter area passed is invalid.

ACS5031 | ACSBEG45 terminated abnormally
Explanation: | This message is associated with TPF CICS printout spooling and indicates that the control transaction has abnormally terminated.

ACS5040 | Converse for STRTFIELD failed
Explanation: | This message is associated with the TPF CICS host system and indicates that a terminal CONVERSE has failed.

ACS5042 | Pgmiderr for NCALL transparency
Explanation: | This message is associated with TPF CICS reverse access processing and indicates that the requested CICS program could not be loaded.

ACS5044 | XCTL return program-id invalid
Explanation: | This message is associated with TPF CICS mainline termination and indicates that the requested continuation program could not be XCTLed.

ACS6101 | Insufficient storage for input buffers
Explanation: | This message is associated with TPF mainline processing and indicates that there was insuffient storage available to obtain communication buffers.

ACS6102 | Insufficient storage for SVC buffers
Explanation: | This message is associated with TPF mainline processing and indicates that storage was not available to obtain buffer space for Adabas communication.

ACS6201 | The module named ACSTAB is invalid
Explanation: | This message is associated with TPF host initialisation and indicates that the requested ACSTAB module is invalid.

ACS6202 | An unknown destination was requested
Explanation: | This message is associated with TPF host transaction initialisation and indicates that the user has specified an unknown target destination.

ACS6203 | The destination table is unavailable
Explanation: | This message is associated with TPF host transaction initialisation and indicates that the destination table (ACSTBL) cannot be found.

ACS6204 | Recursive ACCESS path is not allowed
Explanation: | 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.

ACS6301 | The input buffer is too small
Explanation: | 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.

ACS6402 | Screen-to-hardcopy not supported under Com-plete for TSO
Explanation: | This message is associated with TPF under TSO. The screen-to-hardcopy function is not available under ADABAS-TPF/TSO.

ACS6501 | Cross memory failure: $1
Explanation: | 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.
System action: | The TPF session is terminated.
Terminal operator info: | Contact your system programmer.
System programmer info: | 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.

ACS6502 | The requested node is not active
Explanation: | This message indicates that the requested target node is not currently known to the Adabas router SVC.

ACS6503 | The input transmission length is invalid
Explanation: | 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.

ACS6504 | Userid modified since last access
Explanation: | 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.

ACS7101 | Printer $1 not available ( ATI-, Out-of-service-, No-session error)
Explanation: | This message is associated with TPF CICS printout spooling. The indicated printer device is out of service for one of the reasons shown.

ACS7102 | Printer $1 not available (Terminal error)
Explanation: | This message is associated with TPF CICS printout spooling. The indicated printer device is unavailable due to a permanent error condition.