Sponsored Content
Full Discussion: System event on AIX
Top Forums UNIX for Advanced & Expert Users System event on AIX Post 302783367 by big123456 on Wednesday 20th of March 2013 11:06:15 AM
Old 03-20-2013
System event on AIX

Hi,
on AIX 6,
are the system events historicized ? I want to know how was the performance on 18th of march. Is there any way ?

thanks and regards.
 

6 More Discussions You Might Find Interesting

1. Solaris

rsh commands not getting executed from Solaris 10 System to AIX System

Hi Friends, I am trying to execute rsh commands from Solaris 10 system to AIX system. When I give; Solaris10# rsh <hostname> ls -l , it gives me an error rshd : 0826-826 The host name for your address is not known At the same time, Solaris10# rsh <hostname> ---- gives me remote shell of... (25 Replies)
Discussion started by: jumadhiya
25 Replies

2. AIX

How to apply aix 5.3 TL8 properly on ML5 aix system ?

Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ? Is the TL8 installation not totally safe ? thank you. (6 Replies)
Discussion started by: astjen
6 Replies

3. AIX

AIX Printers moved to anothere AIX system

AIX Printers need to be moved to another system Guy's We have two servers old AIX 5.2 and new AIX 6.1 the old server has more than 300 printers installed with different configurations I'd like to move all the printers from the old server to the new server with fast steps it's... (1 Reply)
Discussion started by: ITHelper
1 Replies

4. Shell Programming and Scripting

Help me fixing event handling in csh on AIX

Hi All, I have problem with a csh script. This script simply search for a certail process id and kill that using simple kill -5 <pid>. Everything is okay untill there is valid process id trapped. But if the process id is already cleaned before the execution of the kill command, but script ends... (2 Replies)
Discussion started by: sraj142
2 Replies

5. AIX

Accessing files on AIX system from Linux system

I have a following requirement in production system 1 : LINUX User: abcd system 2: AIX (it is hosting a production DB) Requirement user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies

6. Infrastructure Monitoring

Event processing & machine learning in monitoring system

Hello! For a couple of years I'm developing an IT infrastructure monitoring system in the research group in my university. And now we would like to use some nontrivial methods in this area. So, I decided to contact with experienced users on the subject. My questions would be: Do existing... (3 Replies)
Discussion started by: pyalxx
3 Replies
cpc_npic(3CPC)					    CPU Performance Counters Library Functions					    cpc_npic(3CPC)

NAME
cpc_npic, cpc_caps, cpc_cciname, cpc_cpuref, cpc_walk_events_all, cpc_walk_generic_events_all, cpc_walk_events_pic, cpc_walk_generic_events_pic, cpc_walk_attrs - determine CPU performance counter configuration SYNOPSIS
cc [ flag... ] file... -lcpc [ library... ] #include <libcpc.h> uint_t cpc_npic(cpc_t *cpc); uint_t cpc_caps(cpc_t *cpc); const char *cpc_cciname(cpc_t *cpc); const char *cpc_cpuref(cpc_t *cpc); void cpc_walk_events_all(cpc_t *cpc, void *arg, void (*action)(void *arg, const char *event)); void cpc_walk_generic_events_all(cpc_t *cpc, void *arg, void (*action)(void *arg, const char *event)); void cpc_walk_events_pic(cpc_t *cpc, uint_t picno, void *arg, void (*action)(void *arg, uint_t picno, const char *event)); void cpc_walk_generic_events_pic(cpc_t *cpc, uint_t picno, void *arg, void (*action)(void *arg, uint_t picno, const char *event)); void cpc_walk_attrs(cpc_t *cpc, void *arg, void (*action)(void *arg, const char *attr)); DESCRIPTION
The cpc_cciname() function returns a printable description of the processor performance counter interfaces, for example, the string Ultra- SPARC III+ & IV. This name should not be assumed to be the same as the name the manufacturer might otherwise ascribe to the processor. It simply names the performance counter interfaces as understood by the system, and thus names the set of performance counter events that can be described by that interface. The cpc_cpuref() function returns a string that describes a reference work that should be consulted to (allow a human to) understand the semantics of the performance counter events that are known to the system. The string returned might be substantially longer than 80 charac- ters. Callers printing to a terminal might want to insert line breaks as appropriate. The cpc_npic() function returns the number of performance counters accessible on the processor. The cpc_caps() function returns a bitmap containing the bitwise inclusive-OR of zero or more flags that describe the capabilities of the processor. If CPC_CAP_OVERFLOW_INTERRUPT is present, the processor can generate an interrupt when a hardware performance counter overflows. If CPC_CAP_OVERFLOW_PRECISE is present, the processor can determine precisely which counter overflowed, thereby affecting the behavior of the overflow notification mechanism described in cpc_bind_curlwp(3CPC). The system maintains a list of performance counter events supported by the underlying processor. Some processors are able to count all events on all hardware counters, while other processors restrict certain events to be counted only on specific hardware counters. The sys- tem also maintains a list of processor-specific attributes that can be used for advanced configuration of the performance counter hardware. These functions allow applications to determine what events and attributes are supported by the underlying processor. The reference work pointed to by cpc_cpuref() should be consulted to understand the reasons for and use of the attributes. The cpc_walk_events_all() function calls the action function on each element of a global event list. The action function is called with each event supported by the processor, regardless of which counter is capable of counting it. The action function is called only once for each event, even if that event can be counted on more than one counter. The cpc_walk_events_pic() function calls the action function with each event supported by the counter indicated by the picno argument, where picno ranges from 0 to the value returned by cpc_npic(). The system maintains a list of platform independent performance counter events known as generic events (see generic_events(3CPC)). The cpc_walk_generic_events_all() function calls the action function on each generic event available on the processor. The action function is called for each generic event, regardless of which counter is capable of counting it. The action function is called only once for each event, even if that event can be counted on more than one counter. The cpc_walk_generic_events_pic() function calls the action function with each generic event supported by the counter indicated by the picno argument, where picno ranges from 0 to the value returned by cpc_npic(). The system maintains a list of attributes that can be used to enable advanced features of the performance counters on the underlying pro- cessor. The cpc_walk_attrs() function calls the action function for each supported attribute name. See the reference material as returned by cpc_cpuref(3CPC) for the semantics use of attributes. RETURN VALUES
The cpc_cciname() function always returns a printable description of the processor performance counter interfaces. The cpc_cpuref() function always returns a string that describes a reference work. The cpc_npic() function always returns the number of performance counters accessible on the processor. The cpc_caps() function always returns a bitmap containing the bitwise inclusive-OR of zero or more flags that describe the capabilities of the processor. If the user-defined function specified by action is not called, the cpc_walk_events_all(), cpc_walk_events_pic(), cpc_walk_attrs(), cpc_walk_generic_events_pic(), and cpc_walk_generic_events_pic() functions set errno to indicate the error. ERRORS
The cpc_walk_events_all(), cpc_walk_events_pic(), cpc_walk_attrs(), cpc_walk_generic_events_pic(), and cpc_walk_generic_events_pic() func- tions will fail if: ENOMEM There is not enough memory available. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
cpc_bind_curlwp(3CPC), generic_events(3CPC), libcpc(3LIB), attributes(5) SunOS 5.11 8 Oct 2008 cpc_npic(3CPC)
All times are GMT -4. The time now is 08:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy