LU 6.2 API Application Programmer's Reference Guide (30294-90008)

Chapter 5 71
Intrinsic Descriptions
TPStarted
NOTE For remotely initiated TPs on MPE XL, the LocalTPName parameter of
the TPStarted intrinsic must match the
LocalTPName parameter of the
MCGetAllocate intrinsic.
The
TraceOn parameter can have four possible values. When you are
writing and debugging programs, it is useful to turn API intrinsic
tracing on by setting the
TraceOn parameter to 1. API intrinsic tracing
is documented in Chapter 7 , “Debugging.” It will help you diagnose
errors in your TP. Use
TraceOn values of 2 and 3 only when asked to do
so by your HP representative.
Since tracing can be turned on or off only during the execution of
TPStarted, you might want to write your TP so that it will accept an
info string that specifies the type of tracing to be performed. This would
save having to recompile the program to change the type of tracing.
Status Info Values
0 Successful Completion.
-1 Intrinsic called with parameter out of bounds.
-19 APPC subsystem is inactive.
-20 Not enough stack space for intrinsic to run.
-21 Insufficient memory space to allocate a conversation.
-90 An internal error in Presentation Services has occurred.
-95 Internal Error: Unable to create Transaction Program port.(MPE XL)
-1002 An internal error at the mapped conversation level has occurred.
-1003 Required parameter missing.
-1005 Insufficient Heap Space. (MPE V)
-1030 TPStarted request rejected.
-1033 Unable to open file specified in the 'TraceFile' parameter.
-1034 Out of range 'TraceSize' parameter specified in intrinsic call.
-1036 Out of range 'TraceOn' parameter specified in intrinsic call.
-1044 Multiple calls made to TPStarted.