HP Guardian Errors Manual page 76

Procedure errors and messages manual
Table of Contents

Advertisement

Cause An invalid signal value was found. Either an invalid value was specified to
TMF_WRITE_SIGNAL_ or an invalid buffer was specified to TMF_INTERPRET_SIGNAL_.
Effect The operation is not performed.
Recovery Determine why the invalid signal value was used or why the TMF sub-system thinks the
buffer is invalid.
719
Cause An attempt was made to write branch or resource manager data, but the amount of data
specified would cause the allowable limits on the data to be exceeded.
Effect In the case of branch data (TMF_WRITE_TX_DATA_) the transaction is aborted. In the case
of resource manager data (TMF_WRITE_RM_DATA_), the operation fails and the resource manager
data is not updated.
Recovery Fix the application to not generate more than the allowable amount of branch or resource
manager data. Branch data is limited to 1.5K (1024) bytes per branch, or a total of 12K (12288)
bytes per transaction. Resource manager data is limited to 1K (1024) bytes per resource manager.
721
Cause The TMF_RESUME_ procedure was called before the BEGINTRANSACTION processing for
the specified transaction is complete. This could occur because the BEGINTRANSACTION procedure
does not wait for the processing to complete before returning to the caller and the caller could
subsequently call TMF_SUSPEND_ and send the tid off to another process to resume before the
processing is complete.
Effect The TMF_RESUME_ fails.
Recovery Delay for a few seconds and try the TMF_RESUME_ again.
722
Cause An attempt was made to open a resource manager file, but the gateway process' local CPU
has run out of available resource manager control blocks.
Effect The resource manager open fails.
Recovery The number of resource manager control blocks allocated per CPU can be configured
through the subsystem management interface. If this error is consistently being returned, that value
can be increased. Another possible recovery is to distribute the gateway processes across other
CPUs where the limit has not been reached.
723
Cause An attempt was made to export or import a transaction branch, but the limit of the number
of branch control blocks per CPU has been exceeded.
Effect The operation fails.
Recovery The number of branches per resource manager can be configured through the subsystem
management interface. If this error is consistently being returned, that value should be increased.
Another possible recovery is to add more resource managers to the directory and distribute the
load of transaction branches across them.
724
76
File-System Errors
(%1317)
FEDATASIZEEXCEEDED
(%1321)
FEBEGINTXNOTCOMPLETED
(%1322)
FENOMORERMCBS
(%1323)
FENOMOREBCBS
(%1324)
FENOTNOWAITTFILE

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Guardian

Table of Contents