This problem sounds like APAR IC29355. Here is the
pertinent text of that APAR:

----- BEGIN APAR TEXT -----
ABSTRACT:
ABSTRACT:
TSM HP CLIENT DISPLAYS ACC RUNTIME ERROR MESSAGE

ERROR DESCRIPTION:
TSM HP client shows aCC runtime ERROR: _main()not called
message every time user is issuing a command from BA command
line (e.g. incremental or query backup). This does not produce
any errors or affect normal operations.

LOCAL FIX:
The only way to avoid this message is not to have new HPUX
patches installed (PHSS_21906 or PHSS_22217). These new
patches updates aCC compiler to later version which hasmore
strict checking of calling descructors/constructors.

PROBLEM SUMMARY: The 4.1.1. client was a mixture of C and C++ co
de and the module containg main() was compiled as C. This leads
to non-initialization of C++ static constructors and maybe core
dumps. Newer versions of system libraries since HP UX 11.04 leve
l and higher recognize the problem and print out a warning about
 _main not called.
PROBLEM CONCLUSION: The code in 4.1.2. was compiled as C++ in to
tal. So be changing this the problem removed without any code ch
anges.
TEMPORARY FIX: The problem is already fixed with 4.1.2. So if a
customer upgrades its HP and run into the problem he has to use
PTF 4.1.2. to avoid this situation.
----- END APAR TEXT -----
Regards,
Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: araibeck AT tivoli DOT com
"The only dumb question is the one that goes unasked."


Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>@VM.MARIST.EDU> on 04/05/2001
08:03:49 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  HP-UX client 3.7.2.16



We recently installed fix test 3.7.2.16 on a number of HP-UX systems
because of recurrent backup failures resulting from a bug in the
client software. As far as I can tell, the fix test client code is
consistently generating an error messages on all of these systems
when a dsm, dsmc, or dsmadmc command ends. The error message is as
follows:

aCC runtime: ERROR: _main() not called.

As far as I tell, the error is not preventing the commands from
carrying out their normal functions. A co-worker responsible for
SQL-BackTrack installation just reported seeing the same error
message after backing up an Oracle database using SQL-BackTrack and
its interface to TSM, which is based on the TSM API.

Is this a known problem? Can anyone confirm that it is not interferring
with the functioning of the various commands?