Thanks Richard for the GUI limitation.
About the retrieve of the mksysb, let say server A is down.
- first we retrieve the stored mksysb from A onto server B,
- then declare a NIM client for the server A,
- then bootp on server A (the retrieve mksysb is used).
Thats all ! no more mksysb going first to a central server via NFS (slow)!
Yours
Ren� LAMBELET
NESTEC SA
GLOBE - Global Business Excellence
Central Support Center
Information Technology
Av. Nestl� 55 CH-1800 Vevey (Switzerland)
t�l +41 (0)21 924 35 43 fax +41 (0)21 703 30 17 local
UBS-Nestec, Bussigny
mailto:[EMAIL PROTECTED]
This message is intended only for the use of the addressee
and may contain information that is privileged and confidential.
-----Original Message-----
From: Richard Sims [mailto:[EMAIL PROTECTED]
Sent: Tuesday,25. March 2003 14:43
To: [EMAIL PROTECTED]
Subject: Re: Archive objects from Tsm API not displayed in GUI client
>we recently developped a C++ script to directly send AIX mksysb's into TSM.
>The TSM API is used to archive the output of mksysb, block by block. Using
>dsmc, we can query and retrieve the archive objects without any problem.
>
>Now, using the tsm GUI, no archive file will appear, the file systems seem
to
>be empty !
>
>Is it normal ? Is the GUI only able to display objects sent by the base tsm
b/a
>client ?
Rene - Refer to the Understanding Interoperability chapter of the TSM API
manual.
It promises only CLI - not GUI - visibility of API-stored objects.
I think we're all curious how you intend to ultimately use the TSM-stored
mksysb
data, given the chicken-and-egg scenario.
Richard Sims, BU
