GDSX Manual

Service Routines
Extended General Device Support (GDSX) Manual–134303
8-7
^ABORTTRANSACTION
^ABORTTRANSACTION
This procedure cancels the current TMF transaction associated with the calling user task.
Canceling a transaction assumes that a successful call to ^BEGINTRANSACTION
occurred from the user task calling ^ABORTTRANSACTION. See Appendix D for an
example of using this procedure.
A trace record is written after a successful call to ^ABORTTRANSACTION if bit 3 of
trace^control^flags in DCCBDECS is set to 1. The trace records contain the calling task
number of the user task and the TMF transaction identifier. See “Tracing GDSX” on
page 2-77 for more information.
The syntax, condition code settings, and considerations regarding this procedure are the
same as the TMF counterpart in the NonStop TM/MP Application Programmer’s Guide.
ADD^TRACE^DATA
If the trace file is open, this procedure collects the specified trace data and copies it into
the trace data pool at the next available address. The USER^OPEN^TRACE^FILE
procedure may be used to open the trace file.
During execution of the following user exits, the GDSX process is not completely
initialized and, therefore, ADD^TRACE^DATA should not be called:
•
PROCESS^ASSIGNS
•
PROCESS^USER^PARAMS
•
USER^INIT^CONFIG^PARAMS
•
USER^VERSION
Once TSCODE has called the USER^INITIALIZE user exit (which is called after
USER^VERSION in either the primary or backup process), USCODE may generate
trace entries by calling ADD^TRACE^DATA or ADD^TRACE^DATA^INT.
Trace entries generated by these procedure calls are merged with any trace entries that
you specify to be generated by TSCODE.
type input
INT:value
CALL ADD^TRACE^DATA ( type !
i
,data1 !
i
,bytes1 !
i
,[ data2 , bytes2 ]
,[ data3 , bytes3 ]
,[ data4 , bytes4 ]
,[ data5 , bytes5 ]
,[ data6 , bytes6 ] );