Sponsored Content
Full Discussion: HMC - tracking dlpar
Operating Systems AIX HMC - tracking dlpar Post 302720707 by mk8570 on Wednesday 24th of October 2012 02:10:19 PM
Old 10-24-2012
HMC - tracking dlpar

I am trying to generate a report to track dlpar operation performed on a MS and was wondering if anyone has done this before.

I can get history from HMC using lssvcevents , but this does not give me details as to what quantity was added or removed .

Any thoughts ?

Thanks
 

10 More Discussions You Might Find Interesting

1. 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... (1 Reply)
Discussion started by: stumpy
1 Replies

2. 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... (5 Replies)
Discussion started by: mahatma
5 Replies

3. 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... (5 Replies)
Discussion started by: panknil
5 Replies

4. 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... (3 Replies)
Discussion started by: mattmanuel
3 Replies

5. 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... (0 Replies)
Discussion started by: lildudesaif
0 Replies

6. 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... (1 Reply)
Discussion started by: thmnetwork
1 Replies

7. 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

8. 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... (2 Replies)
Discussion started by: MichaelFelt
2 Replies

9. 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... (1 Reply)
Discussion started by: aixkidbee
1 Replies

10. 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 Replies)
Discussion started by: Phat
2 Replies
EXPIRE(8)						      System Manager's Manual							 EXPIRE(8)

NAME
expire - Usenet article and history expiration program SYNOPSIS
expire [ -d dir ] [ -e ] [ -f file ] [ -g file ] [ -h file ] [ -i ] [ -l ] [ -n ] [ -p ] [ -q ] [ -r reason ] [ -s ] [ -t ] [ -v level ] [ -w number ] [ -x ] [ -z file ] [ expire.ctl ] DESCRIPTION
Expire scans the history(5) text file /var/lib/news/history and uses the information recorded in it to purge old news articles. OPTIONS
-d If the ``-d'' flag is used, then the new history file and database is created in the specified directory, dir. This is useful when the filesystem does not have sufficient space to hold both the old and new history files. When this flag is used, expire leaves the server paused and creates a zero-length file named after the new history file, with an extension of ``.done'' to indicate that it has successfully completed the expiration. The calling script should install the new history file and un-pause the server. The ``-r'' flag should be used with this flag. -e If the ``-e'' flag is used, then as soon as the first cross posting of the article expires, all copies of it are removed. -f To specify an alternate history file, use the ``-f'' flag. -g If the ``-g'' flag is given, then a one-line summary equivalent to the output of ``-v1'' and preceeded by the current time, will be appended to the specified file. -h To specify an alternate input text history file, use the ``-h'' flag. Expire uses the old dbz(3z) database to determine the size of the new one. -i To ignore the old database, use the ``-i'' flag. -l Expire normally just unlinks each file if it should be expired. If the ``-l'' flag is used, then all articles after the first one are treated as if they could be symbolic links to the first one. In this case, the first article will not be removed as long as any other cross-posts of the article remain. -n If innd is not running, use the ``-n'' flag and expire will not send the ``pause'' or ``go'' commands. (For more details on the commands, see ctlinnd(8)). Note that expire only needs exclusive access for a very short time -- long enough to see if any new articles arrived since it first hit the end of the file, and to rename the new files to the working files. -p Expire makes its decisions on the time the article arrived, as found in the history file. This means articles are often kept a lit- tle longer than with other expiration programs that base their decisions on the article's posting date. To use the article's post- ing date, use the ``-p'' flag. -q Expire normally complains about articles that are posted to newsgroups not mentioned in the active file. To suppress this action, use the ``-q'' flag. -r Expire normally sends a ``pause'' command to the local innd(8) daemon when it needs exclusive access to the history file, using the string ``Expiring'' as the reason. To give a different reason, use the ``-r'' flag. The process ID will be appended to the reason. When expire is finished and the new history file is ready, it sends a ``go'' command. -s If the ``-s'' flag is used, then expire will print a summary when it exits showing the approximate number of kilobytes used by all deleted articles. -t If the ``-t'' flag is used, then expire will generate a list of the files that should be removed on its standard output, and the new history file will be left in history.n and history.n.dir and history.n.pag. This flag be useful for debugging when used with the ``-n'' and ``-s'' flags. Note that if the ``-f'' flag is used, then the name specified with that flag will be used instead of his- tory. -v The ``-v'' flag is used to increase the verbosity of the program, generating messages to standard output. The level should be a number, where higher numbers result in more output. Level one will print totals of the various actions done (not valid if a new history file is not written), level two will print report on each individual file, while level five results in more than one line of output for every line processed. -w Use the ``-w'' flag to ``warp'' time so that expire thinks it is running at some time other then the current time. The value should be a signed floating point number of the number of days to use as the offset. -x If the ``-x'' flag is used, then expire will not create any new history files. This is most useful when combined with the ``-n'', ``-s'', and ``-t'' flags to see how different expiration policies would change the amount of disk space used. -z If the ``-z'' flag is used, then articles are not removed, but their names are appended to the specified file. See the description of expirerm in news.daily(8). If a filename is specified, it is taken as the control file and parsed according to the rules in expire.ctl(5). A single dash (``-'') may be used to read the file from standard input. If no file is specified, the file /etc/news/expire.ctl is read. HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 1.19, dated 1996/10/29. SEE ALSO
ctlinnd(8), dbz(3z), expire.ctl(5), history(5), innd(8), inndcomm(3). EXPIRE(8)
All times are GMT -4. The time now is 03:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy