Sponsored Content
Operating Systems AIX Prerequisites for Infosphere v9.1 Post 302840967 by tostay2003 on Tuesday 6th of August 2013 07:52:16 PM
Old 08-06-2013
Thanks for the help. I am contact the admin team to have them installed the compiler and packages.
 

6 More Discussions You Might Find Interesting

1. Solaris

VxVM volume extending Prerequisites

Hellow Experts, Could anyone tell me the Prerequisites for extending a Volume on VxVM. (3 Replies)
Discussion started by: sudhan143
3 Replies

2. Solaris

Prerequisites for Solaris10 Branded Zone within Solaris 11 Express

Dear all, we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message: ***The image patch level is downrev for running in a solaris10 branded zone*** The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed. Does the... (0 Replies)
Discussion started by: xunil321
0 Replies

3. Programming

J2EE prerequisites

Hi guys, I'm going to start studding about J2EE in a couple of weeks. I have no idea about its technologies. what prerequisites do i need. I only know java and have basic knowledge about HTML. I have a solid knowledge on database. 1. Do i need java script or CSS knowledge for JSP and JSF? 2.... (1 Reply)
Discussion started by: majid.merkava
1 Replies

4. UNIX for Dummies Questions & Answers

Makefile prerequisites

In the makefile code below am I correct to say that the prerequisites are: 4thg 4thx 4thd 4thc lib4th OBJ4TH = errs_4th.o save_4th.o load_4th.o free_4th.o comp_4th.o \ name_4th.o dump_4th.o exec_4th.o open_4th.o hgen_4th.o cgen_4th.o all: lib4th.a 4th # 4thc 4thd 4thx 4thg lib4th.a:... (1 Reply)
Discussion started by: momhef4
1 Replies

5. AIX

Prerequisites for installing VIOS

Hello, I am trying to setup LPARs on a p7 system. There is an existing install of AIX 7.1 that we have been using for various tasks. Can I install VIOS on top of this existing OS without any other prep work? Or is it advisable to install a fresh copy of AIX before installing VIOS on it? ... (1 Reply)
Discussion started by: bstring
1 Replies

6. AIX

PreRequisites for Dynamic LPAR actions

Hello All, To perform Dynamic Operations from HMC in command Line (such as adding cpu to an lpar for example) in order to avoid stopping Applications, What PreRequisites are needed ? AIX version ? HMC version ? Filesets (applied/committed) ? and what else should I have to check ...? What is... (2 Replies)
Discussion started by: LoLo92
2 Replies
pkgrm(1M)																 pkgrm(1M)

NAME
pkgrm - remove a package from the system SYNOPSIS
pkgrm [-nv] [-a admin] [ [-A | -M] -R root_path] [-V fs_file] [pkginst... | -Y category[,category...]] pkgrm -s spool [pkginst... | -Y category[,category...]] pkgrm will remove a previously installed or partially installed package from the system. A check is made to determine if any other packages depend on the one being removed. If a dependency exists, the action taken is defined in the admin file. The default state for the command is in interactive mode, meaning that prompt messages are given during processing to allow the administra- tor to confirm the actions being taken. Non-interactive mode can be requested with the -n option. The -s option can be used to specify the directory from which spooled packages should be removed. Certain unbundled and third-party packages are no longer entirely compatible with the latest version of pkgrm. These packages require user interaction throughout the removal and not just at the very beginning. To remove these older packages (released prior to Solaris 2.4), set the following environment variable:NONABI_SCRIPTS=TRUE pkgrm permits keyboard interaction throughout the removal as long as this environment variable is set. The following options are supported: -a admin Use the installation administration file, admin, in place of the default admin file. pkgrm first looks in the current work- ing directory for the administration file. If the specified administration file is not in the current working directory, pkgrm looks in the /var/sadm/install/admin directory for the administration file. -A Remove the package files from the client's file system, absolutely. If a file is shared with other packages, the default behavior is to not remove the file from the client's file system. -M Instruct pkgrm not to use the $root_path/etc/vfstab file for determining the client's mount points. This option assumes the mount points are correct on the server and it behaves consistently with Solaris 2.5 and earlier releases. -n Non-interactive mode. If there is a need for interaction, the command will exit. Use of this option requires that at least one package instance be named upon invocation of the command. Certain conditions must exist for a package to be removed non-interactively or a non-restrictive admin file needs to be used. -R root_path Defines the full path name of a directory to use as the root_path. All files, including package system information files, are relocated to a directory tree starting in the specified root_path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -s spool Remove the specified package(s) from the directory spool. The default directory for spooled packages is /var/sadm/pkg. -v Trace all of the scripts that get executed by pkgrm, located in the pkginst/install directory. This option is used for debugging the procedural and non-procedural scripts. -V fs_file Specify an alternative fs_file to map the client's file systems. Used in situations where the $root_path/etc/vfstab file is non-existent or unreliable. -Y category Remove packages based on the value of the CATEGORY parameter stored in the installed or spooled package's pkginfo(4) file. No package with the CATEGORY value of system can removed from the file system with this option. The following operand is supported: pkginst Specifies the package to be removed. The format pkginst.* can be used to remove all instances of a package. The asterisk character (*) is a special character to some shells and may need to be escaped. In the C-Shell, "*" must be surrounded by single quotes (') or preceded by a backslash (). Example 1: Removing All instances of SUNWjunk From client1 The following example removes all instances of SUNWjunk from client1: example% pkgrm -R /export/root/client1 SUNWjunk* Note the caveat on the use of the -R option in the description of that option, above. The following exit values are returned: 0 Successful completion. 1 Fatal error. 2 Warning. 3 Interruption. 4 Administration. 10 Reboot after removal of all packages. 20 Reboot after removal of this package. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1), installf(1M), pkgadd(1M), pkgask(1M), pkgchk(1M), removef(1M), admin(4),pkginfo(4), attributes(5) 6 Apr 2005 pkgrm(1M)
All times are GMT -4. The time now is 10:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy