I'm having to send support savediag after savediag. It seems like it's getting to be a weekly routine.

I saw once that there is a way to run savediag with a single command line with parameters. But for the life of me I can't locate it now.

Does anyone have the documentation or examples?

OK I did find the command line args. However it still doesn't work...

edastart -?s
This shows....
-savediag Interactive Save Diagnostic option allowing to
save diagnostic information and post it to IBI
special site for analysis (non interactive if
running from JCL) as an archive.
-savediag [] []
Silent mode for Save Diagnostic option
is [[-sdir] []] [-app []]
default is sd under EDASHARE
default is all directories under APPROOT
if -app is not supplied, baseapp will be copied.
is -post
-sdir combination allows to post a
saved earlier diagnostic information.

- SYSTEM ADMINISTRATION -


I've tried the following script.

CASE_NBR=12345678
LOG_DIR=/var/ibi/log/savediag/sd$(date "+%Y%m%d_%H%M%S")

mkdir ${LOG_DIR}

/opt/ibi/srv71/wfs/bin/edastart -savediag -sdir ${LOG_DIR} -app baseapp

This goes as far as showing the system information, but never copies the logs dir, edatemp dir, followed by taring the contents.

I add the arguments to post to the site...
/opt/ibi/srv71/wfs/bin/edastart -savediag -sdir ${LOG_DIR} -app baseapp -post ${CASE_NBR} cssftp anonymous -sdir ${LOG_DIR}

Still no copy of log or edatemp files. It does create a tar file(blank). Then it asks for confirmation to proceed. (It's supposed to be "silent") And where to I get the uid/pw for the ftp server.

So I try to trick it and do the following.. Create everything but don't post it. I'll try posting later :-(

echo N | /opt/ibi/srv71/wfs/bin/edastart -savediag -sdir ${LOG_DIR} -app baseapp -post ${CASE_NBR} cssftp anonymous -sdir ${LOG_DIR}

Now I get as far as...
07/09/2007 14:58:21 Post Action was not confirmed.
07/09/2007 14:58:21 Savediag information was not posted...

Good I don't get an interactive message for a silent utility. But again no files copied which means a blank tar file is created.

Any help from anyone is appreciated.

This message has been edited. Last edited by: Michael Simon,