10-09-2013
I've had a good read, but there is nothing I've spotted on how to choose which to boot from. I presume that one would get to SMS and select it there. Has anyone actually done this? I wouldn't want to just leap in without knowing what to do and I guess neither would any other reputable system manager.
Does this affect a mksysb by the way, or does that only make an image of what is the running OS?
Thanks again,.
Robin
10 More Discussions You Might Find Interesting
1. AIX
Hi guys
I have joined a new department and one of my tasks is to investigate the feasibility of upgrading our current AIX v 4.3 to V5.3.
I do not know anything about AIX and any actual work will be done by an outside consultant until such time as I have built up my own knowledge.
The system we... (3 Replies)
Discussion started by: JDM
3 Replies
2. UNIX for Dummies Questions & Answers
Hello everyone, I have to do a ML upgrade on AIX 5.2 from 01 to 09
this is the first time iam going to do it.
are there any command i have to keep in mind??
thanks! (1 Reply)
Discussion started by: karthikosu
1 Replies
3. UNIX for Dummies Questions & Answers
Does anyone know any gotcha's on upgrading AIX from 5.1 to 5.3? Any interim steps on needs to do or ??? (3 Replies)
Discussion started by: capeme
3 Replies
4. AIX
I have an IBM P520 that I need to upgrade from 5.2 to 5.3. My background in Unix is from 15 years ago so I don't remember much. IBM documentation is hard to find. Any help would be appreciated. (1 Reply)
Discussion started by: bashtonmcse
1 Replies
5. AIX
We are going from UDB DPF 8.2 to 9.5 and changing HW from P4+ to P6 and moving from 5.2 to 5.3. Anyone out there gone through this upgrade? Any words of wisdom, warnings, or other gotchas you could pass on. TIA.
ART (0 Replies)
Discussion started by: ArtF
0 Replies
6. AIX
Hello Folks,
i am facing some weired issues.
case is like this :-
initially i was on AIX 5.3
i have installed filesets related to my application and those were in APPLY state.(COMMIT is set as NO)
Then i have taken lslpp -l| grep -i <apps name>
in that i confirmed whether the filesets are... (1 Reply)
Discussion started by: harsh_mulay
1 Replies
7. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
8. AIX
i upgrade aix ml 5.3.2.1 to 5.3.2.2 but when running commnd #oslevel -r
shows out put, again 5.3.2.1-- where should i chek???
2-can any one tell me when mknfs command run which files get updated?? (2 Replies)
Discussion started by: nayyer
2 Replies
9. Emergency UNIX and Linux Support
Hello Team,
Am trying to upgrade the AIX 6.1 TL 7 to TL 8. My rootvg is mirrored so i have unmirrored and taken out the secondary disk and trying to install the update via smitty alt_clone.
The filesets has been installed and finally when making the updated disk as bootable bosboot... (6 Replies)
Discussion started by: gowthamakanthan
6 Replies
10. AIX
Hi all,
I'm getting errors while booting AIX 7.1 after upgrade
I have used FLRT tool for the process with the following input values shown in the attached photo. titled FLRT
After reboot for the upgrade process system hangs and no response as shown in screenshot named AIX7.1-NormalBoot
I... (13 Replies)
Discussion started by: h@foorsa.biz
13 Replies
LEARN ABOUT MOJAVE
time2posix
TIME2POSIX(3) BSD Library Functions Manual TIME2POSIX(3)
NAME
time2posix, posix2time -- convert seconds since the Epoch
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <time.h>
time_t
time2posix(time_t t);
time_t
posix2time(time_t t);
DESCRIPTION
IEEE Std 1003.1-1988 (``POSIX.1'') legislates that a time_t value of 536457599 shall correspond to "Wed Dec 31 23:59:59 GMT 1986." This
effectively implies that POSIX time_t's cannot include leap seconds and, therefore, that the system time must be adjusted as each leap
occurs.
If the time package is configured with leap-second support enabled, however, no such adjustment is needed and time_t values continue to
increase over leap events (as a true `seconds since...' value). This means that these values will differ from those required by POSIX by the
net number of leap seconds inserted since the Epoch.
Typically this is not a problem as the type time_t is intended to be (mostly) opaque--time_t values should only be obtained-from and passed-
to functions such as time(3), localtime(3), mktime(3) and difftime(3). However, IEEE Std 1003.1-1988 (``POSIX.1'') gives an arithmetic
expression for directly computing a time_t value from a given date/time, and the same relationship is assumed by some (usually older) appli-
cations. Any programs creating/dissecting time_t's using such a relationship will typically not handle intervals over leap seconds cor-
rectly.
The time2posix() and posix2time() functions are provided to address this time_t mismatch by converting between local time_t values and their
POSIX equivalents. This is done by accounting for the number of time-base changes that would have taken place on a POSIX system as leap sec-
onds were inserted or deleted. These converted values can then be used in lieu of correcting the older applications, or when communicating
with POSIX-compliant systems.
The time2posix() function is single-valued. That is, every local time_t corresponds to a single POSIX time_t. The posix2time() function is
less well-behaved: for a positive leap second hit the result is not unique, and for a negative leap second hit the corresponding POSIX time_t
does not exist so an adjacent value is returned. Both of these are good indicators of the inferiority of the POSIX representation.
The following table summarizes the relationship between time_t and its conversion to, and back from, the POSIX representation over the leap
second inserted at the end of June, 1993.
DATE TIME T X=time2posix(T) posix2time(X)
93/06/30 23:59:59 A+0 B+0 A+0
93/06/30 23:59:60 A+1 B+1 A+1 or A+2
93/07/01 00:00:00 A+2 B+1 A+1 or A+2
93/07/01 00:00:01 A+3 B+2 A+3
A leap second deletion would look like...
DATE TIME T X=time2posix(T) posix2time(X)
??/06/30 23:59:58 A+0 B+0 A+0
??/07/01 00:00:00 A+1 B+2 A+1
??/07/01 00:00:01 A+2 B+3 A+2
[Note: posix2time(B+1) => A+0 or A+1]
If leap-second support is not enabled, local time_t's and POSIX time_t's are equivalent, and both time2posix() and posix2time() degenerate to
the identity function.
SEE ALSO
difftime(3), localtime(3), mktime(3), time(3)
BSD
September 11, 2005 BSD