Sponsored Content
Full Discussion: multibos with aix53 hacmp45
Operating Systems AIX multibos with aix53 hacmp45 Post 302227686 by shockneck on Thursday 21st of August 2008 05:23:15 PM
Old 08-21-2008
HACMP 4.5 is not supported with AIX 5.3. So I believe you mean HACMP 5.4.

You don't need to use multibos. However it is a good idea to have some means to return to the former software levels in case you end up with some AIX-RSCT-HACMP combination that does not work as expected. Using multibos or alt_disk_install makes your life much easier if you don't have a testserver.

Remember that you will have to do a full clustertest after the upgrade.
 

3 More Discussions You Might Find Interesting

1. AIX

install apar on aix53

Hi All, I was installing apar CVE-2008-0122 on my freshly test aix53. I followed the ibm site and run this 'installp -a -d libc_ifix -X all' and got this +-----------------------------------------------------------------------------+ Pre-installation... (1 Reply)
Discussion started by: itik
1 Replies

2. AIX

multibos and hacmp

Hi All, Is multibos and hacmp compatible? Anyone who have work/experience with both technology. Thanks for any idea. (0 Replies)
Discussion started by: itik
0 Replies

3. AIX

Restore previous update w/o multibos

Hi All, How do I restore previous state if my current update failed w/o multibos? Is that possible? Thanks in advance for any idea. (3 Replies)
Discussion started by: itik
3 Replies
update(n)						       Tcl Built-In Commands							 update(n)

__________________________________________________________________________________________________________________________________________________

NAME
update - Process pending events and idle callbacks SYNOPSIS
update ?idletasks? _________________________________________________________________ DESCRIPTION
This command is used to bring the application "up to date" by entering the event loop repeatedly until all pending events (including idle callbacks) have been processed. If the idletasks keyword is specified as an argument to the command, then no new events or errors are processed; only idle callbacks are invoked. This causes operations that are normally deferred, such as display updates and window layout calculations, to be performed imme- diately. The update idletasks command is useful in scripts where changes have been made to the application's state and you want those changes to appear on the display immediately, rather than waiting for the script to complete. Most display updates are performed as idle callbacks, so update idletasks will cause them to run. However, there are some kinds of updates that only happen in response to events, such as those triggered by window size changes; these updates will not occur in update idletasks. The update command with no options is useful in scripts where you are performing a long-running computation but you still want the applica- tion to respond to events such as user interactions; if you occasionally call update then user input will be processed during the next call to update. EXAMPLE
Run computations for about a second and then finish: set x 1000 set done 0 after 1000 set done 1 while {!$done} { # A very silly example! set x [expr {log($x) ** 2.8}] # Test to see if our time-limit has been hit. This would # also give a chance for serving network sockets and, if # the Tk package is loaded, updating a user interface. update } SEE ALSO
after(n), interp(n) KEYWORDS
event, flush, handler, idle, update Tcl 7.5 update(n)
All times are GMT -4. The time now is 11:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy