Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ?
Is the TL8 installation not totally safe ?
thank you. (6 Replies)
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Hi all,
I am trying to exchange hostname and IP address of two AIX machines.
But i am confused as how to change it ?
do i need to use "smitty mktcpip" or "smitty tcpip" ?
what is the difference between smitty mktcpip and smitty tcpip ?
Also anymore steps to follow or just updating... (3 Replies)
Hello,
I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior.
for example
1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert.
2) disk usage alerts
3)... (5 Replies)
I am new to AIX but not new to unix.
I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs
From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT FREEBSD
s390_sthyi
S390_STHYI(2) System Calls Manual S390_STHYI(2)NAME
s390_sthyi - emulate STHYI instruction
SYNOPSIS
#include <asm/unistd.h>
int s390_sthyi(unsigned long function_code, void *resp_buffer,
uint64_t *return_code, unsigned long flags);
DESCRIPTION
The s390_sthyi() system call emulates the STHYI (Store Hypervisor Information) instruction. It provides hardware resource information for
the machine and its virtualization levels. This includes CPU type and capacity, as well as the machine model and other metrics.
The function_code argument indicates which function to perform. The following code(s) are supported:
0 Return CP (Central Processor) and IFL (Integrated Facility for Linux) capacity information.
The resp_buffer argument specifies the address of a response buffer. If the system call returns 0, the response buffer will be filled with
CPU capacity information. Otherwise, the response buffer's content is unchanged.
The return_code argument stores the return code of the STHYI instruction, using one of the following values:
0 Success.
4 Unsupported function code.
For further details about return_code, function_code, and resp_buffer, see the reference given in NOTES.
The flags argument is provided to allow for future extensions and currently must be set to 0.
RETURN VALUE
On success (that is: emulation succeeded), the return value of s390_sthyi() matches the condition code of the STHYI instructions, which is
a value in the range [0..3]. A return value of 0 indicates that CPU capacity information is stored in *resp_buffer. A return value of 3
indicates "unsupported function code" and the content of *resp_buffer is unchanged. The return values 1 and 2 are reserved.
On error, -1 is returned, and errno is set appropriately.
ERRORS
EFAULT The value specified in resp_buffer or return_code is not a valid address.
EINVAL The value specified in flags is nonzero.
ENOMEM Allocating memory for handling the CPU capacity information failed.
EOPNOTSUPP
The value specified in function_code is not valid.
VERSIONS
This system call is available since Linux 4.15.
CONFORMING TO
This Linux-specific system call is available only on the s390 architecture.
NOTES
Glibc does not provide a wrapper for this system call, use syscall(2) to call it.
For details of the STHYI instruction, see <https://www.ibm.com/support/knowledgecenter/SSB27U_6.3.0/com.ibm.zvm.v630.hcpb4/hcpb4sth.htm>.
SEE ALSO syscall(2)COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux Programmer's Manual 2018-02-02 S390_STHYI(2)