Sponsored Content
Operating Systems AIX Install RPM from NIM LPP without smitty Post 302900637 by n.i.b on Thursday 8th of May 2014 02:12:22 AM
Old 05-08-2014
@ross.mather
Thanks, I will try that method also.

My buddy also found that install method from client:

Code:
CLIENT # nimclient -o cust -a lpp_source=RPMS_AIX53 -a  filesets=sudo-1.6.9p23-2noldap.aix5.3.ppc.rpm -a accept_licenses=yes -a  show_progress=yes

As for @bakunin method ... it also work, displays errors, but works, here are the results:

Before.

Code:
CLIENT # rpm -qa
AIX-rpm-7.1.1.15-1
tcl-8.4.7-3
tk-8.4.7-3
expect-5.42.1-3
bash-3.2-1

After.
Code:
CLIENT # rpm -qa
sudo-1.6.9p23-2noldap
tcl-8.4.7-3
tk-8.4.7-3
expect-5.42.1-3
bash-3.2-1
AIX-rpm-7.1.2.0-2

Commands from NIM.

Code:
NIM # nim -F -o allocate -a lpp_source="RPMS_AIX53" "CLIENT"
NIM # nim -F -o deallocate -a lpp_source="nim_script" "CLIENT"
NIM # nim -o cust -a lpp_source="RPMS_AIX53" -a filesets="sudo-1.6.9p23-2noldap 1.6.9p23-2noldap" "CLIENT"

Validating RPM package selections ...

Please wait...
sudo                        ##################################################

+-----------------------------------------------------------------------------+
                          RPM  Error Summary:
+-----------------------------------------------------------------------------+
The following packages were requested for installation 
but were not found on the media:
1.6.9p23-2noldap

0042-001 nim: processing error encountered on "master":
   0042-001 m_cust: processing error encountered on "CLIENT":
   0042-175 c_script: An unexpected result was returned by the "NIM:/export/nim/scripts/CLIENT.script" command:

0042-175 c_installp: An unexpected result was returned by the "/usr/sbin/installp" command:
See the log file:
        /var/adm/ras/nim.installp
for details or use the "showlog" operation.



NIM # cat /export/nim/scripts/CLIENT.script

#!/bin/ksh
CLIENT.script: END
# nim_script for CLIENT
result=success

export NIM_NON_41_MASTER=yes
export NIM_SHOW_PROGRESS=yes
export NIM_SCRIPT=yes
# lpp_source=RPMS_AIX53
/usr/lpp/bos.sysmgt/nim/methods/c_installp ${VERBOSE} \
        -afilesets="sudo-1.6.9p23-2noldap 1.6.9p23-2noldap" \
        -alpp_source=NIM:/export/PACKAGES/RPMS_AIX53
[[ $? != 0 ]] && result=failure

[[ ${result} = success ]] && exit 0 || exit 1

In other words, problem solved, thank You for help gentleman.

Last edited by n.i.b; 05-08-2014 at 05:42 AM..
 

10 More Discussions You Might Find Interesting

1. AIX

Linux install from NIM

Has anyone ever done this and is it easy to do with SLES9/10? All I can find so far is this link http://www-941.ibm.com/collaboration/wiki/display/Wikip5/16Jan07+Using+NIM+to+Install+VIO+and+Linux Can you still use all the feature of autoyast etc? TIA. (1 Reply)
Discussion started by: backslash
1 Replies

2. AIX

NIM install hangs on LED 0608

Hi guys, I am trying to install a new machine via nim but it is hanging on 0608 => it should be a network issue here the situation hoping you will be able to help: server NIM on a subnet/IP 10.36.12.64 client on 161.43.56.25 the ping test is successful but when I launch the isntall it... (9 Replies)
Discussion started by: touny
9 Replies

3. Shell Programming and Scripting

How to install expect rpm?

Hi , I am tryin to install expect rpm on my linux machine. I have the source file expect-5.42.1-1.src.rpm I am doin this rpm -ivh expect-5.42.1-1.src.rpm But I am gettin this error warning: expect-5.42.1-1.src.rpm: V3 DSA signature : NOKEY, key ID db42a60e error: cannot... (1 Reply)
Discussion started by: eamani_sun
1 Replies

4. SuSE

How to install .src.rpm ? ( source rpm )

Hi, I have got few RPM's from rpmfind.net ( mainly gcc ). But it seems to be src files instead of the image. so I think we have to build the src files according to target machine using rpmbuild. Can any one help me with 1) Various options of rpm build that have to be taken care 2)... (3 Replies)
Discussion started by: Sivaswami
3 Replies

5. AIX

AIX 5.1 install bos.sysmgt.nim.master failed

I was trying to install bos.sysmgt.nim.master on AIX 5.1 with a mounted NFS source, but it failed: # installp -agXd /nfs/aix51cd1 bos.sysmgt.nim.master installp: APPLYING software for: bos.sysmgt.nim.master 5.1.0.50 restore: 0511-123 The volume on... (0 Replies)
Discussion started by: ezlee
0 Replies

6. UNIX for Dummies Questions & Answers

RPM uninstall/install

Running FC5 on a Dell desktop. When I compile a LaTex file, it goes fine but only outlines blank boxes where figs should be. When I send the figs.eps and Tex file to a friend, his compiles and imbeds the fig. in the text of the DVI output using my files without add'nl control cards. I conclude... (1 Reply)
Discussion started by: blann
1 Replies

7. UNIX for Dummies Questions & Answers

RPM install problem

I'm trying to install mysql on a server, but I keep getting an error. Can anyone offer any help? Below I've listed a bunch of info that you might find helpful. Here are the commands I'm using. $ ls MySQL-client-community-5.1.35-0.rhel3.i386.rpm... (2 Replies)
Discussion started by: wsetchell
2 Replies

8. AIX

OS install from NIM fails

Hi Guys, The ping is failing SMS menu on the client to the interface for a network boot from NIM. I checked the cables, they are plugged in and lights are blinking. this is the error i am getting when I am pushing the OS on NIM Command: OK stdout: yes stderr: no ... (2 Replies)
Discussion started by: ithinksgreen
2 Replies

9. AIX

NIM - install up-to-date VIOS ?

Hello, Is it possible to install up-to-date vios in one NIM operation ? For example I have vios v2.1 DVD and current vios version is v2.2.1.3(we update to fixpack v2.2.1.1_FP25 and apply service pack 2.2.1.3-FP25-SP01) I know it's possible if we install AIX using NIM - we just update... (0 Replies)
Discussion started by: vilius
0 Replies

10. AIX

Install software in another directory with smitty install

Hello, I would like to ask if someone knows if is possible to install sofware via smitty or installp in another directorie , or we have to accept the default location? i would like to intall in /opt folder , but smitty installed it in /usr Thanks in advance (4 Replies)
Discussion started by: prpkrk
4 Replies
DB(3pm) 						 Perl Programmers Reference Guide						   DB(3pm)

NAME
DB - programmatic interface to the Perl debugging API SYNOPSIS
package CLIENT; use DB; @ISA = qw(DB); # these (inherited) methods can be called by the client CLIENT->register() # register a client package name CLIENT->done() # de-register from the debugging API CLIENT->skippkg('hide::hide') # ask DB not to stop in this package CLIENT->cont([WHERE]) # run some more (until BREAK or another breakpt) CLIENT->step() # single step CLIENT->next() # step over CLIENT->ret() # return from current subroutine CLIENT->backtrace() # return the call stack description CLIENT->ready() # call when client setup is done CLIENT->trace_toggle() # toggle subroutine call trace mode CLIENT->subs([SUBS]) # return subroutine information CLIENT->files() # return list of all files known to DB CLIENT->lines() # return lines in currently loaded file CLIENT->loadfile(FILE,LINE) # load a file and let other clients know CLIENT->lineevents() # return info on lines with actions CLIENT->set_break([WHERE],[COND]) CLIENT->set_tbreak([WHERE]) CLIENT->clr_breaks([LIST]) CLIENT->set_action(WHERE,ACTION) CLIENT->clr_actions([LIST]) CLIENT->evalcode(STRING) # eval STRING in executing code's context CLIENT->prestop([STRING]) # execute in code context before stopping CLIENT->poststop([STRING])# execute in code context before resuming # These methods will be called at the appropriate times. # Stub versions provided do nothing. # None of these can block. CLIENT->init() # called when debug API inits itself CLIENT->stop(FILE,LINE) # when execution stops CLIENT->idle() # while stopped (can be a client event loop) CLIENT->cleanup() # just before exit CLIENT->output(LIST) # called to print any output that API must show DESCRIPTION
Perl debug information is frequently required not just by debuggers, but also by modules that need some "special" information to do their job properly, like profilers. This module abstracts and provides all of the hooks into Perl internal debugging functionality, so that various implementations of Perl debuggers (or packages that want to simply get at the "privileged" debugging data) can all benefit from the development of this common code. Currently used by Swat, the perl/Tk GUI debugger. Note that multiple "front-ends" can latch into this debugging API simultaneously. This is intended to facilitate things like debugging with a command line and GUI at the same time, debugging debuggers etc. [Sounds nice, but this needs some serious support -- GSAR] In particular, this API does not provide the following functions: o data display o command processing o command alias management o user interface (tty or graphical) These are intended to be services performed by the clients of this API. This module attempts to be squeaky clean w.r.t "use strict;" and when warnings are enabled. Global Variables The following "public" global names can be read by clients of this API. Beware that these should be considered "readonly". $DB::sub Name of current executing subroutine. %DB::sub The keys of this hash are the names of all the known subroutines. Each value is an encoded string that has the sprintf(3) format "("%s:%d-%d", filename, fromline, toline)". $DB::single Single-step flag. Will be true if the API will stop at the next statement. $DB::signal Signal flag. Will be set to a true value if a signal was caught. Clients may check for this flag to abort time-consuming operations. $DB::trace This flag is set to true if the API is tracing through subroutine calls. @DB::args Contains the arguments of current subroutine, or the @ARGV array if in the toplevel context. @DB::dbline List of lines in currently loaded file. %DB::dbline Actions in current file (keys are line numbers). The values are strings that have the sprintf(3) format "("%s00%s", breakcondition, actioncode)". $DB::package Package namespace of currently executing code. $DB::filename Currently loaded filename. $DB::subname Fully qualified name of currently executing subroutine. $DB::lineno Line number that will be executed next. API Methods The following are methods in the DB base class. A client must access these methods by inheritance (*not* by calling them directly), since the API keeps track of clients through the inheritance mechanism. CLIENT->register() register a client object/package CLIENT->evalcode(STRING) eval STRING in executing code context CLIENT->skippkg('D::hide') ask DB not to stop in these packages CLIENT->run() run some more (until a breakpt is reached) CLIENT->step() single step CLIENT->next() step over CLIENT->done() de-register from the debugging API Client Callback Methods The following "virtual" methods can be defined by the client. They will be called by the API at appropriate points. Note that unless specified otherwise, the debug API only defines empty, non-functional default versions of these methods. CLIENT->init() Called after debug API inits itself. CLIENT->prestop([STRING]) Usually inherited from DB package. If no arguments are passed, returns the prestop action string. CLIENT->stop() Called when execution stops (w/ args file, line). CLIENT->idle() Called while stopped (can be a client event loop). CLIENT->poststop([STRING]) Usually inherited from DB package. If no arguments are passed, returns the poststop action string. CLIENT->evalcode(STRING) Usually inherited from DB package. Ask for a STRING to be "eval"-ed in executing code context. CLIENT->cleanup() Called just before exit. CLIENT->output(LIST) Called when API must show a message (warnings, errors etc.). BUGS
The interface defined by this module is missing some of the later additions to perl's debugging functionality. As such, this interface should be considered highly experimental and subject to change. AUTHOR
Gurusamy Sarathy gsar@activestate.com This code heavily adapted from an early version of perl5db.pl attributable to Larry Wall and the Perl Porters. perl v5.16.2 2012-10-11 DB(3pm)
All times are GMT -4. The time now is 07:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy