Title: RE: Problem when using API

hi,

But I can't compile the v3.7.1.0 API with the attached error.
<<run_err.txt>> <<compile_err.txt>>

Regards,
Kathy Lai
Outsourcing & Managed Services
Pacific Century CyberWorks
( 852-8101 2790
[EMAIL PROTECTED]

    -----Original Message-----
    From:   Thiha Than [SMTP:[EMAIL PROTECTED]]
    Sent:   Friday, November 09, 2001 12:53 AM
    To:     [EMAIL PROTECTED]
    Subject:        Problem when using API

    hi,

    Since the backups are done using V3.7.1 API, you must use the V3.7.1 API
    Sample program also.  Can you query the objects?  Make sure that query is
    fine before deleting.

    regards,
    Thiha


    >I can compile the API (v.3.1.0.6) now. But I can compile the API
    (v3.7.1.0).
    >Error as describe before.
    >In my environment, I have install Client (v3.1.0.6), Client API (3.7.1.0)
    >and TDPoracle (2.1.10). I want to use the API to delete a backup piece
    which
    >backup through TDPoracle. However, when I execute the sample API program
    >dapismp given the following input delete failed. Please HELP as I have
    many
    >backup pieces in the server which need to delete manually.

    >INPUT
    >Choose Utilities(7) and Backup Delete(1)
    >Filespace: /adsmorc
    >Highlevel: /*
    >Lowlevel: /<backup piece name>

    >OUTPUT
    >*** dsmGetNextQObj failed:
    >ANS1245E (RC122)  Format unknown

    >When I try again, sometimes I will have the following output.

    >*** dsmBeginQuery failed:
    >ANS1026E (RC136)  Session rejected: Communications protocol error

    >Should I use v3.7.1.0 version API to delete the backup object?

/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from
/usr/lib/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from /usr/li
b/libApiDS.sl
/usr/lib/dld.sl: Unresolved symbol: __pure_virtual_called (plabel)  from /usr/li
b/libApiDS.sl
/usr/lib/dld.sl: Unresolved module for symbol: dsmQueryApiVersionEx (code)  from
 ./dapismp
Abort(coredump)
        cc -I. -O -c dapiproc.c
        ar rv libApiSmp.a dapiproc.o
r - dapiproc.o
        cc -I. -O -c dapibkup.c
        ar rv libApiSmp.a dapibkup.o
r - dapibkup.o
        cc -I. -O -c dapiinit.c
        ar rv libApiSmp.a dapiinit.o
r - dapiinit.o
        cc -I. -O -c dapiqry.c
cc: "dapiqry.c", line 3386: warning 562: Redeclaration of "SortRestoreOrder"
with a different storage class specifier: "SortRestoreOrder"
will have internal linkage.
        ar rv libApiSmp.a dapiqry.o
r - dapiqry.o
        cc -I. -O -c dapipref.c
        ar rv libApiSmp.a dapipref.o
r - dapipref.o
        cc -I. -O -c dapipw.c
        ar rv libApiSmp.a dapipw.o
r - dapipw.o
        cc -I. -O -c dapirc.c
        ar rv libApiSmp.a dapirc.o
r - dapirc.o
        cc -I. -O -c dapint64.c
        ar rv libApiSmp.a dapint64.o
r - dapint64.o
        cc -I. -O -c dapiutil.c
        ar rv libApiSmp.a dapiutil.o
r - dapiutil.o
        cc -I. -O -c dapismp.c
        cc -I. -O -o dapismp dapismp.o libApiSmp.a -lApiDS
/usr/ccs/bin/ld: (Warning) At least one PA 2.0 object file (dapismp.o)
was detected. The linked output may not run on a PA 1.x system.


Reply via email to