David,
see the below APAR details of the behaviour change and exact versions it
affects.
IC75871: AUTODEPLOY=NOREBOOT SET IN THE DEPLOYMENT SCHEDULE IS NOT HONORED
IF IT IS NOT SET IN THE CLIENT NODE
http://www.ibm.com/support/docview.wss?uid=swg1IC75871
Thank you for bringing this issue to our
I did try client autodeployment in the lab and, frankly, found it rather
disappointing - tricky to troubleshoot and no way of automating it from the
command line that we could work out. Didn't experience any random reboots
because we couldn't get the damn thing to work!
/David Mc
Sent from my
Hi David,
what phases of the deployment steps were you trying to automate via the
command line and did not work for you -- Scheduling the deployment ?
Observing the results?
So we can help you with that.
Regards/Pozdravi, Gergana
| | ~\\ ! //~
| | ( ( 'o . o' ) )Imagination can
I have tried the autodeploy feature and like it. Yes it has been problems,
mostly because IBM failed to keep the ftp-server compatible with the autodeploy
feature (wrong case in a file name and later a corrupt xml-file), but now it
works.
I recommend everyone to try it. It is easy to setup
