Do you mean that the NSH Script Job waits until the Patch Download job completes?
yes. the NSH Script Job waits until the Patch Download completes.
so the nsh job will run too long time.
so you don't want the nsh script to wait for the download job to finish?
how are you running the download job? (the blcli command)
why are you running it via nsh?
can you post the script you are using ?
thanks for you reply,bill:
yes,i don't want the nsh script to wait for the download job to finish
i created a NSH Script Job by the bladelogic console,the script is:
sh /opt/bmc/downland/aix_downloader.sh -configFile /opt/bmc/downland/aix-config.xml
we need to Automatically download the patch Once a month.
so when the nsh job run,start download the patch,but the NSH Script Job will finish waits until the Patch Download completes.the process of NSH Script Job will in the "tasks in process" too long time.
this is my way to downland the patch,or have you get another good way to downland the patch?
i'm not really sure why this is an issue - don't you want to know if the download was successful or not? if the script job finishes before the download finishes you'll never know if the download is complete. what if one copy of the download is still running when you kick off another one. that will cause problems.
what is the problem w/ the nsh script running for 'too long' ? the job is running, it will be in tasks in progress until it's done.
you can background the run like:
sh /opt/bmc/downland/aix_downloader.sh -configFile /opt/bmc/downland/aix-config.xml > download1.log 2>&1 &
but i would advise against doing that as it will likely cause you more headache if there are problems w/ the download.
thank you very muck bill.