HMC - tracking dlpar

10 More Discussions You Might Find Interesting

1. AIX

LPAR RMC state for DLPAR

Hello, I have checked the state of rmc on the HMC as below: HMC1:~> lssyscfg -r lpar -m Server-xxx -F lpar_id,state,rmc_state,rmc_ipaddr,os_version,dlpar_mem_capable,dlpar_proc_capable,dlpar_io_capable --filter "lpar_ids=4" 4,Running,inactive,10.176.x.x,VIOS 2.2.6.51,0,0,0 HMC1:~> lssyscfg...

2. AIX

AIX: DLPAR VFC - HMC v9

Hey All, I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS. In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the...

3. AIX

DLPAR capable with IVM - checks to do

I cannot find the post with the comment that DLPAR capability was not working with IVM. The two commands that need to be run are (as root, padmin does not know this command): VIOS: lsrsrc IBM.MngNode CLIENTS: lsrsrc IBM.MCP Examples: # lsrsrc IBM.MngNode Resource Persistent Attributes for...

4. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ???

5. Red Hat

Tracking Process to a particular

I've tried to see what I can find on my own but I'm coming up with goose eggs. Basically I was wondering if there was a way of querying the scheduler (or something similar) to track a process back to a particular CPU it's executing on at the time of the command. ps has a "cpu" output option but...

6. AIX

DLPAR Error

Hello, This is the foll error wen i try doin DLPAR from my VIO after adding the virtual adpaters on my clients: HSCL294C DLPAR ADD Virtual I/O resources failed: com.ibm.hsc.common.exceptions.PIHscClientException: HSCL294C DLPAR ADD Virtual I/O...

7. UNIX for Advanced & Expert Users

Tracking down the problem

Is there a way to track down what process is sending to a certain port? I have some thing pounding the network with requests to a multicast IP that doesn't exist. I have shut down all comms related processes and yet it is still there. Need a way to track the port or IP back to the process. Thanks...

8. UNIX for Advanced & Expert Users

Tracking user

dear all, I'm facing problem that is i have noticed from few days back that some body is deleting and making changes in the file from developement server where i'm working(in unix) so i want to track that who is using the server, what performancr they are doing and each every thing which r...

9. UNIX for Advanced & Expert Users

Command Tracking

Hi, OS: Solaris9, SPARC Is there any way I can track the commands run by users from the shell prompt? Example: Somebody is deleting files from the system. Who it is is a mystery. That person obviously does not use bash prompt so there is no history. Is there anyway I can find out who...

10. AIX

Dlpar

Hi, Anybody had a problem trying to rmdev a scsi device and get the following error : root@:/> rmdev -dlscsi3 -R Method error (/usr/lib/methods/ucfgncr_scsi): 0514-062 Cannot perform the requested function because the specified device is busy. I can't...

LEARN ABOUT MOJAVE

tklib_history

history(n)					       Provides a history for Entry widgets						history(n)

__________________________________________________________________________________________________________________________________________________

NAME

       history - Provides a history for Entry widgets

SYNOPSIS

       package require Tcl  8.4

       package require Tk  8.4

       package require history	?0.1?

       ::history::init pathName ?length?

       ::history::remove pathName

       ::history::add pathName text

       ::history::get pathName

       ::history::clear pathName

       ::history::configure pathName option ?value?

       bell

_________________________________________________________________

DESCRIPTION

       This package provides a convenient history mechanism for Entry widgets.	The history may be accessed with the up and down arrow keys.

       ::history::init pathName ?length?
	      Arranges	to  remember  the  history of the named Entry widget. An optional length determines the number of history entries to keep.
	      This may be changed later with ::history::configure. History entries must be added with the ::history::add command before  they  can
	      be seen.

       ::history::remove pathName
	      Forgets all history entries for the Entry pathName and removes the history bindings.

       ::history::add pathName text
	      This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
	      called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).

       ::history::get pathName
	      This command returns a list containing the history entries for the Entry pathName

       ::history::clear pathName
	      This command clears the history list for the named Entry.

       ::history::configure pathName option ?value?
	      This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
	      mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
	      the history, it defaults to

       bell

       entry .e
       bind .e <Return> [list ProcessEntry %W]
       ::history::init .e
       pack .e

       proc ProcessEntry {w} {
	   set text [$w get]
	   if {$text == ""} { return }
	   ::history::add $w $text
	   puts $text
	   $w delete 0 end
       }

KEYWORDS

       entry, history

history 								0.1								history(n)

AIX