Sponsored Content
Operating Systems AIX Cannot uninstall powerpath - bosboot issues Post 302366090 by dukessd on Wednesday 28th of October 2009 08:03:50 PM
Old 10-28-2009
Hi zxmaus,

Unlucky 13 - must be Halloween coming up soon...

Tricky one, should EMC sort it out because it is their code misbehaving, or IBM because it is their OS, as you found each will say it is the others problem and in a way they are right.

Probably best is to push IBM AIX support, they should be able to tell you how to manually remove the fileset install information from the ODM (and fix the bosboot) which should allow you to install the later level OK BUT obviously this will come with no guarantee because they have no real way of knowing exactly what the EMC code might have done to the system integrity.

AFAIK IBM and EMC actually have a fairly good relationship at the higher levels of support and obviously in development of the EMC device drivers so if you can push your local AIX support to push it far enough up the support chain you are likely to get a good solution eventually.

I've seen a few cases where an uninstall of third party drivers goes wrong and it can usually be overcome with a bit of careful ODM manipulation but this is always best done under the direction of IBM support.

HTH
Duke
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bosboot problem please help!

each time I try to do a bosboot or a mksysb the cpu says that he doesn't find /unix... I don't understand cause the kernel is here on the computer and at this exact place with the right name. I tried to force with -k /unix but it doesn't do anything. He doesn't find it and it is here... Do you... (6 Replies)
Discussion started by: jericho
6 Replies

2. Solaris

Perl - How to uninstall? Will pkgrm uninstall all versions?

Hello, I'm working on a Solaris 9/Sparc machine and it has the Solaris 10 version of Perl (5.8.8) installed on it, which always requires all kinds of library files that Solaris 9 doesn't come with. I think the best way to do is to uninstall this wrong version and install the correct Solaris 9... (1 Reply)
Discussion started by: alanlh
1 Replies

3. AIX

installp -C error: 'bosboot verification failed'

Hi, I'm a noob with AIX, can anybody help me solve this issue I'm stuck with on an 5.3 box. bash# installp -C 0503-409 installp: bosboot verification starting... 0503-497 installp: An error occurred during bosboot verification processing. Thanks. (4 Replies)
Discussion started by: thebytegrill
4 Replies

4. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

5. AIX

bosboot issue

bosboot -ad hdisk0 give the following error .. malloc failed 0301-177 A previous bosdebug command has changed characteristics of this boot image. Use bosdebug -L to display what these changes are. 0301-106 /usr/lib/boot/bin/mkboot_chrp: The malloc call failed for size: 216174592 ... (1 Reply)
Discussion started by: b_manu78
1 Replies

6. Solaris

change SP value in powerpath

How to change the following values in power path from SP B to SP A ? Owner: default=SP B, current=SP B this is excerpt from powermt display dev=all (3 Replies)
Discussion started by: fugitive
3 Replies

7. Solaris

Solaris 10 with Veritas and PowerPath

Hello, I have an issue with veritas volume manager version 5.0 in combination with EMC powerpath version 5.2.0 running on Solaris10(Sparc). This server is fiber connected to a EMC Clariion CX3-40 SAN. This is the situation : Server is a SUN Enterprise M5000 OS = Solaris10 Sparc Veritas... (1 Reply)
Discussion started by: chipke2005
1 Replies

8. AIX

bosboot issue

Hi i wanted to know for what reasons, bosboot fails with the error below.? # /usr/sbin/bosboot.dp -a -p /usr/lib/boot/chrp.disk.proto -d /dev/ipldevice dd: 0511-053 The write failed. : There is a request to a device or address that does not exist. 65893+1 records in. 1029+1 records out. ... (1 Reply)
Discussion started by: gnakul
1 Replies

9. Solaris

One emc powerpath failed

It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies

10. AIX

Problem with bosboot

This is my problem: I couldn't create boot image for hdisk7 test02:/]lspv hdisk2 00c8ac36cfdf99b4 old_rootvg hdisk5 00c8abd6d05f83ca newvg active hdisk6 00c8abd6d4ad141f rootvg active... (4 Replies)
Discussion started by: bobochacha29
4 Replies
PERLOS400(1)						 Perl Programmers Reference Guide					      PERLOS400(1)

NAME
README.os400 - 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 com- piled 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 -Dpre- fix=/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 imple- mented 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.8.9 2007-11-17 PERLOS400(1)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy