Antwort: Re: Memo: RE: wadminep [ep_name] send_file

Check your destination directory. I bet the file ended up in 
.../lcf/dat/1.

Hth, Lothar





Jason Shamroski <jason_shamroski-9LkaxTQlAnxWk0Htik3J/w@xxxxxxxxxxxxxxxx>
Gesendet von: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
23.02.2005 15:25
Bitte antworten an tme10

 
        An:     tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
        Kopie: 
        Thema:  Re: Memo:  RE: [tme10] wadminep [ep_name] send_file


I just tested from a Linux TMR to a Windows 2003 endpoint, this format 
worked fine.
Framework v4.1.1 base, ep version 41100

 wadminep GBSLABW2K3 send_file tecmon.sh c:\tecmon.sh

Jason Shamroski
Gulf Breeze Software
www.gulfsoft.com
Office = 919-386-0534

Home of the OpenESM Project
www.sourceforge.net/projects/gulfsoft



yasseralkhathlan-esVVGgHqjCI@xxxxxxxxxxxxxxxx wrote:

>Lothar,
>I was doing this before with the same user! I doubt it is a permission
>problem.
>
>Loren,
>Actually, even with Software distribution it is not guaranteed to get the
>file installed in the other end. I experienced this in Tivoli SWD. It is
>showing that the package was successfully installed and when you check in
>the target; you don't find the file!!  I know this maybe rarely happens 
but
>it is fact and we can't help it.  With wadminep send_file, in most cases 
it
>works fine and smooth beside it is very fast. I never worked with ITCM 
and
>I don't know what are the requirements for that?
>If possible, please help me with some information and I'll be grateful.
>
>
>Regards.
>
>
>
>
>"Loren Cain" <loren.cain-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx on 23 Feb 
>2005 15:12>
>
>Sent by:    owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
>
>
>
>To:    <tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx>
>cc:
>Subject:    RE: [tme10] wadminep [ep_name] send_file
>
>
>I agree with Gary about not using wadminep. It is
>handy for one-off tasks from the command line, but
>I would not use it in an automated script. There
>really is no reliable way to tell if it actually
>worked or not, which makes error checking problematic.
>
>Because ITCM has become such a behemoth we are not
>using it for this project (under 100 stable endpoints
>being managed). I still had a requirement to move a
>few files around, however, so I tried to use wadminep,
>but I kept running into situations where the command
>produced no error messages and gave a return code of 0,
>but no files were transferred. Even using view_directory
>to see if the files arrived was not reliable, since
>sometimes that command returns no information (permission
>problems on the directory, I reckon).
>
>I ended up using a task to invoke an ssh/scp client on
>the endpoint(s), which then downloaded or uploaded the
>files. So far, so good.
>
>Loren Cain
>Digicon
>
>
>-----Original Message-----
>From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx 
>[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
>On Behalf Of Gary Hamilton
>Sent: Wednesday, February 23, 2005 4:55 AM
>To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
>Subject: Re: [tme10] wadminep [ep_name] send_file
>
>
>This probably has to do with the mdist1 settings of your repeater. One
>of
>the e-mail responses suggested checking the wmdist settings, but I think
>the wrpt settings are more likely to be the relevant ones. Either
>disk_dir
>is too small or has restrictions. The difference being that wmdist
>controls
>mdist2 settings, while wprt controls the mdist1settings.
>
>On another note, I'd recommend using data moving instead of wadminep. I
>have seen a few customer create file moving solutions around wadminep
>commands and cause instability in their environment. Data moving is a
>more
>scalable alternative.
>
>
>Gary R. Hamilton
>Team Leader
>Senior Software Engineer
>IBM Software Group - Tivoli Software (UK)
>Global Response Team - Europe/Middle East/Africa
>+44(0)1753-780-988
>mobile: +44(0)780-820-3714
>e-mail:hamilgar-ygUJEDcBm8rQT0dZR+AlfA@xxxxxxxxxxxxxxxx
>____________________________________________
>AskTivoli -  http://www-3.ibm.com/software/sysmgmt/products/support/
>Web PMR submission - http://www-3.ibm.com/software/support/probsub.html
>
>
>
>
>             yasseralkhathlan@
>
>             sabb.com
>
>             Sent by:
>To
>             owner-tme10@lists         
> tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
>
>             .us.ibm.com
>cc
>
>
>
>Subject
>             23/02/2005 08:39          [tme10] wadminep [ep_name]
>
>                                       send_file
>
>
>
>             Please respond to
>
>                   tme10
>
>
>
>
>
>
>
>
>
>
>
>Hello List,
>I'm trying to send a file to a number of endpoints using the command
>wadminep. I've written a script that sends the same file to different
>endpoints but unfortunately, I couldn't get the command work. I used the
>following syntax:
>
>wadminep $my_ep send_file me.class C:\me.class
>
>It gives the following error:
>
>
>" Performing administrative mode 'send_file' on endpoint 'Test_ep'
>Sending file to endpoint 'Test_ep'
>send_file failed on endpoint 'Test_ep'
>FRWTE0017E Wed Feb 23 10:48:01 SAUST 2005 (17): system problem:
>`disk_dir
>create failure' ".
>
>
>Thanks in advance.
>
>
>Yasser
>
>
>
>
>This message and any attachments are confidential to the ordinary
>user of the e-mail address to which it was addressed and may also
>be privileged. If you are not the addressee you may not copy,
>forward, disclose or use any part of the message or its
>attachments and if you have received this message in error, please
>notify the sender immediately by return e-mail and delete it from
>your system.
>
>Internet communications cannot be guaranteed to be secure or
>error-free as information could be intercepted, corrupted, lost,
>arrive late or contain viruses. The sender therefore does not
>accept liability for any errors or omissions in the context of
>this message which arise as a result of Internet transmission.
>
>Any opinions contained in this message are those of the author and
>are not given or endorsed by the Saudi British Bank or office
>through which this message is sent unless otherwise clearly
>indicated in this message and the authority of the author to so
>bind the SABB entity referred to is duly verified.
>
>************************************************************************
>******
>
>
>
>
>
>
>
>
>*****************************************************************************
>
>This message originated from the Internet. Its originator may or
>may not be who they claim to be and the information contained in
>the message and any attachments may or may not be accurate.
>
>*****************************************************************************
>
>
>
>
>
>
>
>
>This message and any attachments are confidential to the ordinary
>user of the e-mail address to which it was addressed and may also 
>be privileged. If you are not the addressee you may not copy, 
>forward, disclose or use any part of the message or its 
>attachments and if you have received this message in error, please 
>notify the sender immediately by return e-mail and delete it from 
>your system.
>
>Internet communications cannot be guaranteed to be secure or 
>error-free as information could be intercepted, corrupted, lost, 
>arrive late or contain viruses. The sender therefore does not 
>accept liability for any errors or omissions in the context of 
>this message which arise as a result of Internet transmission.
>
>Any opinions contained in this message are those of the author and 
>are not given or endorsed by the Saudi British Bank or office 
>through which this message is sent unless otherwise clearly 
>indicated in this message and the authority of the author to so 
>bind the SABB entity referred to is duly verified.
>
>******************************************************************************
>
>
> 
>