[COMMON] tpinit error

Q:总是tpinit出错，有什么需要特别注意的吗

A: zongyn,你说的没有问题，封装是可以的。你说的tpinit出错，应该跟配置有关系。你把ulog信息发上来，看后就知道错误在哪里？
一般tpinit错误，在于网络不通，另外就是你的client程序是否是WS方式编译的，如果是必须使用buildclient参数－w参数，另外设置WSNADDR环境变量。

你还是把ulog信息发上来看看。一般是不能连接WSH等信息。

Return Values Upon failure, tpinit() leaves the calling process in its original context, returns -1,
and sets tperrno to indicate the error condition. Also, tpurcode() is set to the value
returned by the AUTHSVR(5) server.
Errors Upon failure, tpinit() sets tperrno to one of the following values:
[TPEINVAL]
Invalid arguments were specified. tpinfo is non-NULL and does not point
to a typed buffer of type TPINIT.
[TPENOENT]
The client cannot join the application because of space limitations.
[TPEPERM]
The client cannot join the application because it does not have permission to
do so or because it has not supplied the correct application password.
Permission may be denied based on an invalid application password, failure
to pass application-specific authentication, or use of restricted names.
tpurcode() may be set by an application-specific authentication server to
explain why the client cannot join the application.
[TPEPROTO]
tpinit() has been called improperly. For example: (a) the caller is a server;
(b) the TPMULTICONTEXTS flag has been specified in single-context mode; or
(c) the TPMULTICONTEXTS flag has not been specified in multicontext mode.
[TPESYSTEM]
A BEA Tuxedo system error has occurred. The exact nature of the error is
written to a log file.
[TPEOS]
An operating system error has occurred.