LIBTUX 1321, 1322, ... ?

Question

On my development machine, my testing program (some tuxedo client)
started complaining about the errors like
NLS:6: Message not found, catalog LIBTUX_CAT, set 1, num 1321
(after tpgetrply, tperrno=11, tperrordetail=0, I am fairly sure
that it should be 'TPESVCFAIL - application level service
failure')
NLS:6: Message not found, catalog LIBTUX_CAT, set 1, num 1322
(after tpinit when TUXCONFIG variable points to non-existant file
or the file of stopped application, tperrno=12, tperrordetail=0)
What is worth noting, there are no errors like LIBTUX 1321 or LIBTUX
1322 (at least according to the docs).
What could be going on? Apart from this problem, the program works as
expected (executes tpcalls, gets replies...) TUXDIR, PATH, TUXCONFIG
are set correctly.
And there is more: if I get the same program, put its main as a
service, boot as server (using the same environment) and call the
service to make it running - the problem disappears.
This is not very problematic for me, but ...
(unpatched Tuxedo 7.1, Linux)

Answer 1

When the catalog messages don't print, it is because Tuxedo can not find
the catalogs. This is usually caused when you have LANG set to something
other than 'C', or NLSPATH does not include your TUXEDO/locale
directory.
But you can always look in the text files under locale/C. The messages
1321 and 1322 in LIBTUX.text are the descriptive strings for the
TPESVCFAIL and TPESYSTEM errors, and are returned when you call
tpstrerror().
     Scott Orshan
Marcin Kasperski wrote:
>
On my development machine, my testing program (some tuxedo client)
started complaining about the errors like
NLS:6: Message not found, catalog LIBTUX_CAT, set 1, num 1321
(after tpgetrply, tperrno=11, tperrordetail=0, I am fairly sure
that it should be 'TPESVCFAIL - application level service
failure')
NLS:6: Message not found, catalog LIBTUX_CAT, set 1, num 1322
(after tpinit when TUXCONFIG variable points to non-existant file
or the file of stopped application, tperrno=12, tperrordetail=0)
What is worth noting, there are no errors like LIBTUX 1321 or LIBTUX
1322 (at least according to the docs).
What could be going on? Apart from this problem, the program works as
expected (executes tpcalls, gets replies...) TUXDIR, PATH, TUXCONFIG
are set correctly.
And there is more: if I get the same program, put its main as a
service, boot as server (using the same environment) and call the
service to make it running - the problem disappears.
This is not very problematic for me, but ...
(unpatched Tuxedo 7.1, Linux)