Sponsored Content
Full Discussion: Versioned WPAR's
Operating Systems AIX Versioned WPAR's Post 302915737 by bakunin on Thursday 4th of September 2014 12:18:18 PM
Old 09-04-2014
Quote:
Originally Posted by firefox111
The problem is, one of our customers needs to run old AIX5.2 and 5.3 Systems on P7 Hardware (applications do not run on AIX6 or AIX7). The only way to do this is to use the versioned WPAR's. And after all he wants these applications to be highly available
OK. I could say i pity you but my compassion wouldn't help you at all.

AIX 5.3 (ML12) LPARs definitely run natively on P7 hardware if you activate "Power6-compatibility mode" (or something such, can't remember). I have had exactly this some 2 years ago, when we migrated LPARs from some P5-systems to a p795.

In the meantime this is not mentioned any more because 5.3 reached its end of life, but whatever you do, you won't reach any supported state at all anyways. Not with 5.3 and even less so with 5.2 (which was, along with 5.1, a big PITA even back then when it was supported - if i were to decide between 5.1 and 5.2 at the point of a gun, i'd prefer pulling the trigger).

My suggestion is to create LPARs and try starting them with 5.3 and 5.2 respectively and see how far it gets you. If HACMP comes into play anyways this is an additional reason not to use WPARs. I couldn't even imagine building a cluster from WPAR nodes.

Another question: why don't you try to get some P6- or P5-hardware which ran AIX 5.x for years? What is the reason for needing a P7? I suppose you don't have performance problems when the software is built for AIX version 5.2, have you? It must have run with a p690 ("Regatta"), which was the high end back then when AIX 5.2 was modern, no?

I hope this helps.

bakunin
 

9 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

snmpget not working on AIX shared wpar

Hi, I have a shared AIX wpar configured. I have started snmpd process on shared AIX wpar. But when i tried to query a MIB id using the following command /opt/OV/bin/snmpget -d -v 1 -c public -p <hostname> .1.3.6.1.2.1.1.7.0 i get the following error message #... (0 Replies)
Discussion started by: avazeer
0 Replies

2. AIX

Unexpected Behaviour with WPAR

Hello, We have a system running AIX 6.1.7.1. We have created a Workload Partition(wpar) on this system with wpar specific routing enabled. On wpar, we are running DNS (UDP/53) and syslog (UDP/514). en0: 1.1.1.1/255.255.255.0 NOT assigned to any wpar en1:... (0 Replies)
Discussion started by: 03sep2011
0 Replies

3. AIX

Virtualization: WPAR vs LPAR

seems to be WPAR is quite easy to set up..without additional licenses.. If I don't need Linux and all my legacy and new apps are happy in AIX 7.1 (the latest OS), I could save all troubles and use WPAR. Can someone comment on this ?? One copy of OS to maintain, so to speak.. ... (4 Replies)
Discussion started by: ppchu99
4 Replies

4. Shell Programming and Scripting

WPAR monitoring shell script suggestions needed

Hi All, This is for WPAR monitoring shell script, earlier opened thread was closed, had to open a new thread, as suggested I have used script as below, But am trying to get the output in below format, need suggestions with it. Below is the lswpar output, required output format. ... (7 Replies)
Discussion started by: aix_admin_007
7 Replies

5. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies

6. AIX

Wpar network,i'm confused

Hi. I've setup a wpar on aix mkwpar -h ibmunix2 -i -r -N interface=en0 address=10.6.0.1 netmask=255.255.255.0 -n ibmunix2 When i log into ibmunix2 it can't ping any external host,include the ibm host. How to set route for network please? I've set ibmunix2 with a different subnet. ... (7 Replies)
Discussion started by: Linusolaradm1
7 Replies

7. AIX

How to Load a CICS IPC Kernel Extension in a versioned "rootvg" WPAR ?

Anyone running CICS TX in a WPAR ? In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue). Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
Discussion started by: The Doctor
4 Replies

8. AIX

No iscsi available in newly created AIX wpar

AIX 7.1 New to WPAR, hopefully just missing something simple here. Creating the WPAR like this..... (The box where the WPAR is hosted does have an iscsi protocol device) mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D... (0 Replies)
Discussion started by: TomR
0 Replies

9. AIX

Error doing clogin into a wpar

I have this error when I'm trying to do clogin from AIX 7200-00-00-0000 into a wpar with AIX 5.2 abanksPaDesa2:/> clogin AbanksBDPA_wpar exec: A file or directory in the path name does not exist somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from... (2 Replies)
Discussion started by: sandra25350
2 Replies
PERLOS400(1)						 Perl Programmers Reference Guide					      PERLOS400(1)

NAME
perlos400 - Perl version 5 on OS/400 DESCRIPTION
This document describes various features of IBM's OS/400 operating system that will affect how Perl version 5 (hereafter just Perl) is compiled and/or runs. By far the easiest way to build Perl for OS/400 is to use the PASE (Portable Application Solutions Environment), for more information see <http://www.iseries.ibm.com/developer/factory/pase/index.html> This environment allows one to use AIX APIs while programming, and it provides a runtime that allows AIX binaries to execute directly on the PowerPC iSeries. Compiling Perl for OS/400 PASE The recommended way to build Perl for the OS/400 PASE is to build the Perl 5 source code (release 5.8.1 or later) under AIX. The trick is to give a special parameter to the Configure shell script when running it on AIX: sh Configure -DPASE ... The default installation directory of Perl under PASE is /QOpenSys/perl. This can be modified if needed with Configure parameter -Dprefix=/some/dir. Starting from OS/400 V5R2 the IBM Visual Age compiler is supported on OS/400 PASE, so it is possible to build Perl natively on OS/400. The easier way, however, is to compile in AIX, as just described. If you don't want to install the compiled Perl in AIX into /QOpenSys (for packaging it before copying it to PASE), you can use a Configure parameter: -Dinstallprefix=/tmp/QOpenSys/perl. This will cause the "make install" to install everything into that directory, while the installed files still think they are (will be) in /QOpenSys/perl. If building natively on PASE, please do the build under the /QOpenSys directory, since Perl is happier when built on a case sensitive filesystem. Installing Perl in OS/400 PASE If you are compiling on AIX, simply do a "make install" on the AIX box. Once the install finishes, tar up the /QOpenSys/perl directory. Transfer the tarball to the OS/400 using FTP with the following commands: > binary > site namefmt 1 > put perl.tar /QOpenSys Once you have it on, simply bring up a PASE shell and extract the tarball. If you are compiling in PASE, then "make install" is the only thing you will need to do. The default path for perl binary is /QOpenSys/perl/bin/perl. You'll want to symlink /QOpenSys/usr/bin/perl to this file so you don't have to modify your path. Using Perl in OS/400 PASE Perl in PASE may be used in the same manner as you would use Perl on AIX. Scripts starting with #!/usr/bin/perl should work if you have /QOpenSys/usr/bin/perl symlinked to your perl binary. This will not work if you've done a setuid/setgid or have environment variable PASE_EXEC_QOPENSYS="N". If you have V5R1, you'll need to get the latest PTFs to have this feature. Scripts starting with #!/QOpenSys/perl/bin/perl should always work. Known Problems When compiling in PASE, there is no "oslevel" command. Therefore, you may want to create a script called "oslevel" that echoes the level of AIX that your version of PASE runtime supports. If you're unsure, consult your documentation or use "4.3.3.0". If you have test cases that fail, check for the existence of spool files. The test case may be trying to use a syscall that is not implemented in PASE. To avoid the SIGILL, try setting the PASE_SYSCALL_NOSIGILL environment variable or have a handler for the SIGILL. If you can compile programs for PASE, run the config script and edit config.sh when it gives you the option. If you want to remove fchdir(), which isn't implement in V5R1, simply change the line that says: d_fchdir='define' to d_fchdir='undef' and then compile Perl. The places where fchdir() is used have alternatives for systems that do not have fchdir() available. Perl on ILE There exists a port of Perl to the ILE environment. This port, however, is based quite an old release of Perl, Perl 5.00502 (August 1998). (As of July 2002 the latest release of Perl is 5.8.0, and even 5.6.1 has been out since April 2001.) If you need to run Perl on ILE, though, you may need this older port: <http://www.cpan.org/ports/#os400> Note that any Perl release later than 5.00502 has not been ported to ILE. If you need to use Perl in the ILE environment, you may want to consider using Qp2RunPase() to call the PASE version of Perl. AUTHORS
Jarkko Hietaniemi <jhi@iki.fi> Bryan Logan <bryanlog@us.ibm.com> David Larson <larson1@us.ibm.com> perl v5.16.2 2012-10-11 PERLOS400(1)
All times are GMT -4. The time now is 09:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy