13.12.2012 Views

Adabas Transaction Manager Messages and Codes - Software AG ...

Adabas Transaction Manager Messages and Codes - Software AG ...

Adabas Transaction Manager Messages and Codes - Software AG ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Adabas</strong> Response <strong>Codes</strong><br />

124<br />

Subcode Meaning<br />

85<br />

86<br />

87<br />

88<br />

89<br />

90<br />

91<br />

92<br />

93<br />

94<br />

A file involved in the replay was inactive at the beginning of the replay or deactivated<br />

while the replay was running.<br />

Action: Reactivate the deactivated file <strong>and</strong> rerun the replay process for the<br />

subscriptions involved in the replay that get data from the file.<br />

Invalid format buffer was specified for destination-type <strong>Adabas</strong> update comm<strong>and</strong>s.<br />

Action: Correct the format buffer.<br />

An unexpected message sequence number was encountered.<br />

Action: Contact your <strong>Software</strong> <strong>AG</strong> support representative.<br />

An unrecognized eye-catcher was encountered in control block following the URBH.<br />

Action: Contact your <strong>Software</strong> <strong>AG</strong> support representative.<br />

The same subscription name was specified more than once for an <strong>Adabas</strong> automated<br />

replay (defined using the <strong>Adabas</strong> Event Replicator Subsystem or Event Replicator<br />

Administration).<br />

Action: Verify that a subscription is specified only once in an automated replay, <strong>and</strong><br />

try again.<br />

The same destination name was specified more than once for an <strong>Adabas</strong> automated<br />

replay (defined using the <strong>Adabas</strong> Event Replicator Subsystem or Event Replicator<br />

Administration).<br />

Action: Verify that a destination is specified only once in an automated replay, <strong>and</strong><br />

try again.<br />

The replay start date <strong>and</strong> time were not supplied for an automated replay (defined<br />

using the <strong>Adabas</strong> Event Replicator Subsystem or Event Replicator Administration)<br />

or for multiple destination open/close client requests.<br />

Action: Verify that a destination is specified only once in an automated replay or in<br />

multiple destination open/close client requests <strong>and</strong> try again.<br />

The timeout parameter specified for an automated replay was too high.<br />

Action: Reduce the timeout parameter value <strong>and</strong> try again.<br />

PLOG information was not recorded in the Event Replicator Server system file.<br />

Action: Contact your <strong>Software</strong> <strong>AG</strong> support representative.<br />

The AI/BI format buffer was used also for the key. An attempt was made to<br />

decompress a key value, but the related format buffer is for data storage <strong>and</strong> not<br />

for a key.<br />

Action: Contact your <strong>Software</strong> <strong>AG</strong> support representative.<br />

<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!