NI System Monitor. PXI chassis info? Where?

I am trying to update my system to LV 14 from 12. However I used the NI System Monitor to read various temperatures and items from my PXI chassis. It seems that the installer for NI System Monitor only works up through LV 12? Is there a replacement? Has this useful tool just been dropped? Did NI just forget to update it for 2 years?
http://www.ni.com/download/ni-system-monitor-1.2.0/3550/en/
Solved!
Go to Solution.

Jeff·Þ·Bohrer wrote:
I'm with the blue bars on this Scott. The system configuration API is the way to go.
I am fine with the "Blue Bars". Or any decent bar or brew pub, but the Documentation then should mention that for newer versions the functionality have been superseded or replaced with the "System Configuration" API. I don't mind switching API, but a little pointer on the road map goes a long way in helping one stay on track. Especially for those of us who sometims leap frog versions!

Similar Messages

Timers do and communication not working on RT system on PXI chassis

I am having problems with my application when I "Install it to a real-time target". When I run the program in debug mode everything works fine.
I have two programs. One runs on a real-time OS on a PXI chassis Controller (Client). The other runs on my Windows 7 PC (host).
When I run the Client application in debug mode (Run->Debug Project) everything works fine. When I run the Client application in the release mode (Run->Install Program to Real-time execution target) things do not work.
It appears that the timers do do start. The Client application does receive communication sent from the Host application but is not able to send communication from the Client to the Host.
I have been fighting this for a while and have tried to get help through emailing the support but have not had much luck that way. I think I need a phone call with an application engineer.

It is not LabView. I am developing software with LabWindows\CVI. I've seemed to narrow things down a bit. When I send a message to my application on the PXI Controller it is calling a function PostDeferredCall(...). The deferred function is never called. Not sure why it works when I am running the code in Debug Mode but not when I install it on the target. In my while loop in my RTmain() function it looks like this:
while (!RTIsShuttingDown () && !gDone)
  /* Your code. */
  /* Sleep for some amount of time to give the desired loop rate */
  /* and to allow lower priority threads to run.                 */
  SleepUS (1000);
  ProcessSystemEvents ();
I thought the deferred function was supposed to be called in the Main thread? Not sure where it is hanging up yet.

System Monitor for PXI 4-Slot Chassis

Hi all,
I have PXI 4-Slot and PXIe 5-Slot system, which are currently being used for continuous monitoring of some power parameters. Recently, there's a requirement for us to actually monitor the status and health of these PXI systems. I was told that PXI-8250 and NI System Monitor can only work with 8-Slot chassis. Is there a solution smaller chassis? Please advice.
Shazlan

I got the same problem and started a thread in the Idea Exchange:
http://forums.ni.com/t5/LabVIEW-Real-Time-Idea-Exchange/Update-and-extend-NI-System-Monitor/idi-p/17...
Hopefully NI will update the System Monitor soon.

Computing Requirements in Multiple PXI Chassis System

I have acquired a two PXI Chassis system, each with their own embedded controller (PXIe-8108 and PXIe-8130). I would like to control all instruments (simultaneously) in both chassis from a central location (either a laptop or one of the embedded controllers). What is the best configuration for this and will using one controller have enough power to drive two fully populated PXIe-1065 chassis?
(I am aware of the different configurations for control (MXI, etc.) and am more concerned with instrument performance, data buffers become full quickly etc., in using one PC controller)
THANKS!

Hi JMU_ISAT,
The PXIe-1065 chassis uses a four link configuration where there is an x4 link going to slots 7, one to slot 8, another to slots 9-14. There are also an x1 link converted to PXI that goes to slots 2-7 and another x1 link converted to PXI that goes to slots 11-13 and 15-18. Each x4 link gives 1 GB/s of bandwidth and each x1 link converted to PXI will provide 125 MB/s of bandwidth. These bandwidths are theoretical maximums where overhead and chip design reduces the bandwidth somewhat.
The PXI-8130 has four x4 links with the four link configuration so it will be able to get the full chassis bandwidth. The PXIe-8108 has four x1 links which will limit the bandwidth to 250 MB/s for slot 7, slot 8, and slot 9-14.
To synchronize the measurements across both chassis you will need a timing and synchronization module such as the PXIe-6672 in the timing slot of each chassis. This will allow you to route the clock of one timing module to the other and then use that clock to override the backplane reference clock of each chassis. Now each module can use the 10 MHz reference clock to synchronize to each other.
In order to control both chassis from one controller, you can run windows on one controller and LabVIEW RealTime on the other controller allowing you to distribute code from the windows controller to the LabVIEW RealTime controller. The other method would be to run a MXI connection from one chassis to the other to daisy chain the chassis. Since the most you can get out of a single slot of the PXIe-1065 is an x4 link, this would limit the total bandwidth of the daisy chained chassis to 1 GB/s theoretical maximum.
I hope this information is helpful!
Andy K.
Applications Engineer
National Instruments

HELP! I need to be able to remove power from a PXI chassis and replace a card without rebooting the whole system

I do not have particulars on the controller, but I am sure it's an NI chassis
and NI regular controller that has a serial cable leading back to the PC.
I am making this PXI rack into a debug rack for instrument cards,
so I need to be able to remove power from just the PXI chassis
and then replace the card with another one
or the same one and then turn the power back on and restart a
diagnostic test on the card WITHOUT
having to reboot the PC.
Is there a PCIe bridge setup that would allow me to do this?
Is there software that I need that can accomplish this?

Yes
The Chassi is a NI PXI 1045
and the controller is a NI-PXI-8331
Let me re-enumerate my requirements:
Background:
I have a number of NI cards as well as other manufactured cards in the system.
One of these cards in the NI system is considered to be a UUT.
That is, I am using the NI card cage system and other cards in the system to test a CARD
during a manufacturing test of said UUT CARD.
The UUT uses a PLX 9030 for it's PCI interfacing.
This UUT is not designed for hot swap, and I do not bieleve it is plug and play.
Requirement:
1. I need to be able to shut off the chassis and remove the UUT when the test finishes, replace the tested UUT
with a unknown UUT, re-apply power and then test the new UUT WITHOUT having to reboot the PC.
I have tried several things, such as disabling the PCIe busses in the windows control panel, and then removing power
replacing the UUT with the next one, re-applying chassis power and then re-enabling the bus and SOMETIMES it works.
I need a very robust way to do this.
I also bought a CHROMA PXI-52906-E extender card with bus switches on it, so that I can remove power to the UUT
without shutting off the chassis. The card is supposedley designed so that when power is re-applied to the UUT, the necessary
signals to boot the PXI PCI interface is conducted, but I think something else has to be written to the card's PCI registers.
I am by no means an expert in PCI/PXI,
but I seem to have exhausted all of my reserach online in how to meet my requirements.
Perhaps there is a way for the NI8331 controller to capture PCI configuration data to the card's on system boot,
and then "replay it" to my UUT after I re-apply power to the UUT?
Or perhaps PLX makes such a tool?
Any ideas?

PXI Chassis recognition issues

Hello all,
I am using LV 8.2, XP, PXI chassis 1024Q, PXI-5122 digitizers, PCI-6259
I had a complete system error (very nasty virus) and needed to wipe the computer and re-install all labview drivers. Previously I had been using my system for about 1 year with no problems. Upon re-installing everything I am having trouble recognizing my DAQ cards and PXI Chassis Digitizers. I have attached a .jpg of what my DAQ card hierarchy looks like in MAX. Before the re-install my PCI card was in the NI-DAQmx devices as Dev 1, and my digitizer cards where in the PXI System section, as Dev2, slot 2, slot 3 etc. Now MAX tells me that my PXI system is undefined and also includes my PCI card in the PXI section. I can not communicate with any of my devices even though MAX tells me all devices are working properly. Does anyone have any ideas on how I can fix this problem? Does the device installation sequence matter?
Thanks,
Azazal
Azazel
Pentium 4, 3.6GHz, 2 GB Ram, Labview 8.5, Windows XP, PXI-5122, PCI-6259, PCI-6115
Attachments:
MAX.jpg ‏35 KB

You have only one 6259, right? The 6259's entries are indicative of having moved the card into a different slot from the last time MAX looked at the configuration. Assuming you have one 6259, delete the one with the X through it.
And I always give my cards an alias instead of leaving the default "DEV 1", etc.
Message Edited by Bill@NGC on 07-16-2007 06:56 PM
“A child of five could understand this. Send someone to fetch a child of five.”
― Groucho Marx

Trans-receiver system using PXI

Hi,
I need to build a trans-receiver system using PXI. For the transmission part I can use a PXI 5652 to generate a single tone continuous waveform.
For the receiver part, I need an antenna to capture the signal transmitted by 5652 (which will have a transmission antenna ). The received signal will then be down converted by PXI 5601 (RF OUT of 5652 is connected to LO IN of 5601). The intermediate frequency will be then digitized by PXI 5622 (IF OUT of 5601 is connected to IF IN of 5622).
But my question is these connections are already there between the slots/chassis.(The next stage has I/Q demodulation but I want to get clear on this part first). But there is not output port on the PXI 5622, so how can I check the digitized output?
I have attached a file for reference.
Thanks,
Sharmi
Attachments:
Ref.docx ‏689 KB

Hi Sharmi,
To address your questions:
Is the data, after it is down converted and digitized by the 5622 is automatically sent to 5450?
No, the data is not automatically sent to the 5450. The digitized data is sent to the backplane and can be accessed on your controller/laptop through LabVIEW or the RFSA Soft Front Panel. The 5450 is used to take digital signals generated by LabVIEW and turn them into an analog signal. It is not used in any part of the downconversion process.
If you want to take the data that you receive from your 5663 VSA and send it to your 5673 VSG, you will need to do so using software. There are RFSA and RFSG examples that ship with the driver that you can use as a starting point on how to acquire a signal and send a signal using LabVIEW. These examples can be found by going to Start » All Programs » National Instruments » NI-RFSA (or NI-RFSG for generation examples) » Examples.
5450 has “400 MS/s I/Q Signal Generator” written on it, so does it generate I and Q channel data separately?
The 5450 does generate IQ data on 2 separate channels. LabVIEW is used to generate an IQ bit stream. The IQ data is combined after being upconverted with the 5611.
Also 5611 has “I/Q Vector Modulator” written. So, can it demodulate a signal (after it is split into I and Q components by 5450) and then combine the resultant output?
The 5611 is an upconverter and is used to take the IQ signals generated by the 5450, combine them, upconvert them from some IF frequency to an RF frequency and transmit them. It can be used to do some basic types of modulation, but not demodulation. The NI RF Signal Generators Help ( Start » All Programs » National Instruments » NI-RFSG » Documentation) has a section about the 5611 that includes the hardware block diagram and a more detailed explanation about each part of the block diagram. This is where you can find out more about what basic types of modulation the 5611 is capable of performing.
Let me know if you have more questions, I'd be happy to help.
Sarah Y
SDR Product Manager
National Instruments | Ettus Research

Problems with the link between PXI chassis and PC via MXI-4

MAX display the chassis with a yellow exclamation point, and the MXI-4 conection monitor indicates taht the connection to the chassis has timed out.
Under the windows device manager appears PCI std PCI-to-PCI bridge and MXI-4 connection monitor working properly.
The system has bben working properly for one year and suddenly start to fail.
I've tried to uninstall fromn device manager and reinstall again, and teh problem continues. When the PC starts detect new hardware and reinstall from CD with MXI-4 software for windows v 1.0
Only the led PWR lights. The link indicator remains always off, from power up continuously. The cable connection has benn checked ok.
The chassis is powered up in the proper sequence, first the PXI chassis, and the the PC.
Operating system windows XP service pack 2; latest update KB835732 30/12/2004 (V 6.2)
labwindows/cvi (fds) 7.0
ivi compliance oackage 2.1.2
max 3.1
ni-daq 7.3
visa 3.1
chassis pxi-1000b with PXI-8331.

Hello,
it could it be an incompatibility with the desktop PC (maybe?). I know of cases in which the PCI board can be incompatible with a certain PC for various reasons (PCI bus not 100% compliant to PCI standards, PCI power rails, PCI bus-master capabilities, motherboard/chipset issues, etc..).
I mean, has the PC been changed?
Wich PC model/brand is it?
Have you tested it on another of PC (another model)?
In case you have already tested your mxi-4 in other PCs and the behavior is the same, I suggest you to contact your local NI office for assistance.
Regards,
Jorge M.

System monitoring - alert email notification

Hello Sapers,
I already set up system monitoring in our Solution Manager but i would like to receive mail if any alert occur. Unfortunatelly I did not find any way how to do it through Solution Manager. I guess there must be something like edit -> Automatic email transmission where I set up sending Earlywatch and SL reports to my mailbox, but how to set up alert email notification?
I also tried another way - setting up CEN (in our sollution manager) in RZ20, there i created monitor where i have desired alerts from all remote systems configured in SMSY (i have not used sapccm4x or any other ccms agent), also tried autoreaction method on local and it is working fine (SCOT is set up) but when i tried create and assign central autoreaction method (sapnote 429265) during assigning i receive error "no ccms agent avalable for system" and it is not working. Do I really need configure SAPCCM4X on all remote systems when i want to use central autoreaction? I dont feel very confortable with this solution. I think there must be some other smarter way (maybe in solution manager).
We also tried to connect our RZ20 monitor set to nagios (used in our company to monitor non sap servers and email notification), but we are not able to compile the ccms nagios plugin uder 64bit. AIX 5.3.
I also heard little bit about ALM (Alert management) but dont know anything about forwarding alerts from RZ20 to ALM and transmitting email from there. But I think this sollution would be the most difficult from all mentioned above.
Thank you very much for any help

Josef,
Somewhat chasing the point here - when you have the Solman and you look in your CCMS and you can see the other systems - it is all RFC data and not actually on the Solution Manager (the only local MTE's are those tha belong to the Solution Manager). For the Solution Manager to Centrally Auto-React to threasholds (act as the CEN System), the information needs to be passed to the Central System through the agents.
If you want to do email threasholds on your remote systems, you can configure it on each of the systems individually without agents as this is a CCMS Function that any SAP System can do - but this is not Central Auto-Reaction. This is just actions taken on individual systems based on local MTE's.
To Centrally Auto-React - you have to add the agents so the information is passed to the CEN to react on.
I hope that this has clarified the situation a bit more. If this answers your question, please set this thread to answered.

System Monitoring - add SAP PI 711 system

All,
I'm facing problems when I want to add the ABAP stack of my SAP PI 7.11 system...
I use Monitoring Setup Guide (CEN SAP NetWeaver 7.0 EhP 1, SPS 08) to do my setup --> Entering Monitored ABAP Systems with Release SAP NetWeaver 7.1 in ST03G.
Using transaction RZ21--> technical infrastructure --> Configure central system --> create remote monitoring entry.
Next, I choose for DualStack for the component type to be monitored. I fill in all the necessary data and save the entry.
Nothing happens and I do not see the system appearing in the system overiew list.
For single-stack ABAP systems, no problems appear and I can add them.
Please advice.
Thanks.

Dear Dimitri,
The problem is that these products
01200314690800000134 -- 9 -- I -- C
01200314690800000134 -- 34 -- I -- C
These products will need to be reverted to S ( SAP BASIS) from C (NON_SAP BASIS)
Since these are primary keys, you will need to copy and change the + existing record, and then delete the old one.
Once this is done, you will have to perform the following:
Call transaction SMSY. Chose System Groups and Logical Components.
Expand 'Logical Components' - 'SAP NETWEAVER'. Expand the product
instances 'Mobile Infrastructure' and 'Process Integration'. For all
logical components that have systems repeat the following procedure.
1. Check if the logical component is used in solutions using the where
    used button. If no, you can continue with the next one.
2. If yes, note which systems are assigned to which role.
3. Go to change mode and remove the systems from the logical component
     by selecting system SPACE with the value help.
4. Save. Check if a warning says that System monitoring is active.
5. Add the same systems again.
6. Save.
7. If system monitoring was active in a solution the customer should
    run the system monitoring setup for the solution again.
If you are not comfortable making these changes, you can raise a message with SAP.
However once this is done, then the SIDs will be offered and selectable.
Regards,
Paul

System Monitoring - Solman 7 EHP1

Hi
Solution Manager 7.0 EHP1 / Windows 2008 / Oracle
Satellite System R/3 Enterprise extn set 110 / Solaris on Sparc / Oracle
I am having trouble configuring System monitoring on solution Manager. Here is what I have done
Added the satellite system to SLD, Configured data collector (RZ70) in the satellite system, Pushed data from SLD to SMSYS (automatic transfer).
Installed CCMS agent + CCMSPING agent in satellite system. Checked connectivity in solman with RZ21. Connectivity is fine.
Created Monitor sets and monitors in CCMS for monitoring satellite system. Client data is visible in CCMS.
Created a solution in DSWP. Created logical component in SMSY. Assigned the logical component to the solution. Now I can see the data in DSWP.
Here are my questions
==================
1. In DSWP, everytime I have to view data, I have to click on "Setup System Monitoring" to view the alerts in the satellite system
I see a red alert reading for instance availability. Similarly,
In the system monitoring workcenter, I see the status of both the solution manager and the satellite system greyed out with a cross. When I move my mouse over it, it reads, no CCMSPING data available.
Any idea as to why this happens?
2. For what I see after I click on "Setup System Monitoring" I have parameters which I can configure. I see default values for these parameters. Is there like a recommendation or a template which can be used to setup these monitoring parameter values?
3. I have configured the ccmsping in the solution manager (for the solution manager) however the ccmsping service refuses to run. It throws a error reading "The system could not find the file specified". The ccmsping exe file is present in the location stated. Are there other files that this is looking for?
4. While registering the agent in the satellite system, I first registered with the CSMREG id. It failed with the message,
INFO: [SMG:040:CSMREG] connected to SMG, host sapsm.NA.XXX.NET, System Nr. 00, traceflag [ ]
INFO: SMG release is 701 , (kernel release 701 )
        RFC Error Info:
         message:
         status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
         intstat:
      Go Ahead anyway? n/[y] :
INFO: handling destination SAPCCM4X.SAPR3PR1.00
ERROR: can't register at SMG. RfcRc = 2, AUTHORITY_NOT_AVAILABLE
RFC Error Info for SALF_CSM_AGENT_REGISTER
message:
status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
intstat:
I then did this with a dialog user. That worked. Agent was registered in solution manager. Any idea on why this error would show up with the CSMREG? I am concerned about issues which can come up when the password for the dialog user changes.
I am not sure how to upload screenshots of what i see, probably if i do that, it will be easy to relate to the issue which I am mentioning here. Is there a way I can do that?
Let me know if you need any more information from my side to understand this.
Ideas will be appreciated.
thanks
Ravi

Hello Ravi,
Additionally you will want to look at SAP Note 1175058 - Problems with CCMSPING in SAP Solution Manager, especially
c) Ensure that the message server host name in the monitoring options of CCMSPING and the message server of the corresponding main instance of the relevant system is the same in the SAP Solution Manager landscape
(SMSY). Important: The monitoring options of CCMSPING must not be configured using an IP address.
Regards,
Paul

Solution manager system monitoring configuration

Hi
I am configuring system monitoring in solution manager (Oracle / Solman 7.0 EHP1 / Windows 2008 / VM)
I have added a satellite system to solution manager thru CCMS and CCMSPING agents. These are visible in RZ21 / Technical infrastructure / Overview. This has also been added in SMSY, SMSY when refreshed pulls out data from the satellite system. However I am having trouble with the transaction SOLUTION_MANAGER. This is where I setup system monitoring.
Here I find the solution maanger system however am not able to find the satellite system which I had added.
Thoughts?
thanks
Ravi

Hi,
Have you defined and added corresponding logical systems for the respective satellite systems?
Here is the sequence of steps you've to do:
in SMSY:
1) Define server, DB, Systems
2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
3) define logical systems and assign the satellite system to it
in Solution_Manager:
1) define new solution
2) add the logical system into the solution
If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
Have you already done these steps?
After performing these steps:
Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
Your system will then appear.
Does this help any way?

System Monitoring with Solution Manager Ehp1

Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.

Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
               with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
          with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key:   10 Pool
            Size configured.....:   642000000 ( 612.3 MB)
            Size min. estimated.:   637597428 ( 608.1 MB)
            Advised Size........:   640000000 ( 610.4 MB)
Key:   40 Pool for database buffers
            Size configured.....: 1048000000 ( 999.4 MB)
            Size min. estimated.: 1468229308 (1400.2 MB)
            Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key:        1 Size:        2500 (   0.0 MB) System administration
Key:        4 Size:      523648 (   0.5 MB) statistic area
Key:        7 Size:       14838 (   0.0 MB) Update task administration
Key:        8 Size:    67108964 ( 64.0 MB) Paging buffer
Key:        9 Size:   134217828 ( 128.0 MB) Roll buffer
Key:       11 Size:      500000 (   0.5 MB) Factory calender buffer
Key:       12 Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
Key:       13 Size:   200500000 ( 191.2 MB) Alert Area
Key:       16 Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17 Size:     2672386 (   2.5 MB) Roll administration
Key:       30 Size:       37888 (   0.0 MB) Taskhandler runtime admin.
Key:       31 Size:     4806000 (   4.6 MB) Dispatcher request queue
Key:       33 Size:    39936000 ( 38.1 MB) Table buffer, part.buffering
Key:       34 Size:    20480000 ( 19.5 MB) Enqueue table
Key:       51 Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52 Size:       40000 (   0.0 MB) Message Server buffer
Key:       54 Size:    20488192 ( 19.5 MB) Export/Import buffer
Key:       55 Size:        8192 (   0.0 MB) Spool local printer+joblist
Key:       57 Size:     1048576 (   1.0 MB) Profilparameter in shared mem
Key:       58 Size:        4096 (   0.0 MB) Enqueue ID for reset
Key:       62 Size:    85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key:        2 Size:    31168040 ( 29.7 MB) Disp. administration tables
Key:        3 Size:   114048000 ( 108.8 MB) Disp. communication areas
Key:        6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key:       14 Size:    28600000 ( 27.3 MB) Presentation buffer
Key:       19 Size:    90000000 ( 85.8 MB) Table-buffer
Key:       42 Size:    13920992 ( 13.3 MB) DB TTAB buffer
Key:       43 Size:    43422392 ( 41.4 MB) DB FTAB buffer
Key:       44 Size:     8606392 (   8.2 MB) DB IREC buffer
Key:       45 Size:     6558392 (   6.3 MB) DB short nametab buffer
Key:       46 Size:       20480 (   0.0 MB) DB sync table
Key:       47 Size:    13313024 ( 12.7 MB) DB CUA buffer
Key:       48 Size:      300000 (   0.3 MB) Number range buffer
Key:       49 Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key:       18 Size:     1792100 (   1.7 MB) Paging adminitration
Key:       41 Size:    25010000 ( 23.9 MB) DB statistics buffer
Key:       63 Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64 Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65 Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002 Size:      400000 (   0.4 MB) Performance monitoring V01.0
Key: 58900130 Size:        4096 (   0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....:         73
System-imposed number of shared memories.:       1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB,   99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool:   34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................:    1
Warnings detected................:    9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
      additional CENTRAL system y/[n] ?   :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
      CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
      compiled at   Jun 28 2010
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    patch collection 2010/1, OSS note 1304480
      patchno       335
INFO Runtime:
      running on    saptqa01 AIX 3 5 00069A8FD600
      running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
      alert/MONI_SEGM_SIZE = 200000000
      alert/TRACE          = 1
      SAPSYSTEM            = 30
      SAPSYSTEMNAME        = TQA
      SAPLOCALHOST         = saptqa01
      DIR_CCMS             = /usr/sap/ccms
      DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
      DIR_PERF             = /usr/sap/tmp
INFO:
      pid           4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
        segment status     ENABLED
        segment started at Tue Sep 14 09:35:56 2010
        segment version    20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
       Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
       Please change configuration with profile parameters
           ipc/shm_psize_01 = -<different pool nr>
       xor
           ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1

(Help) system classpath -Vs- the place where weblogic looks for classes

The following is my app's hierarchy.
myapp
|
|__myjsp.jsp
|
|__WEB-INF
|
|__classes
|_ MyClass.class
I am not able to use MyClass within myjsp.jsp
i.e. a scriplet like that shown below gives an error stating that MyClass isnt found
<% MyClass obj; %>
I've tried setting the system classpath, but to no avail.
Is there a difference between the system classpath and the place where weblogic looks for classes?
(I am running my app by creating a myapp.war file and placing it in autodeploy folder)

Try moving your class to a named package and use the appropriate import statement in your JSP. Loading it from WEB-INF/classes/packagename should be fine so you might want to remove the other classpath mods you made to eliminate that uncertainty.
Here's a snippet from http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rweb_jsp_migration.html:
"As of JSP 2.0, referring to any classes from the unnamed or default package is not allowed. This can result in a translation error on some containers, specifically those that run in a JDK 1.4 or greater environment which will also break compatibility with some older JSP applications. However, as of JDK 1.4, importing classes from the unnamed package is not valid. See Java 2 Platform, Standard Edition Version 1.4.2 Compatibility with Previous Releases for details. Therefore, for forwards compatibility, applications must not rely on the unnamed package. This restriction also applies for all other cases where classes are referenced, such as when specifying the class name for a tag in a Tag Library Descriptor (TLD) file."
HTH,
Mike
Weblogic/J2EE Security Blog: http://monduke.com

System monitor for awesome

Im currently using awesome, its great except for one thing, there is no system monitor, like gnome-system-monitor for example. though I want something that dosent depend on gnome and displays remainning laptop battery time, aswell as mounted file systems, ram/cpu/network usage and a list of prosesses.

Here's what I'm using with dwm - probably good for dzen as well:
dwm-mystats.sh
#!/bin/zsh
# vim:ft=zsh ts=4
# (c) 2007 by Robert Manea
# Date format as recognized by standard system 'date'
SDATE_FORMAT='%Y-%m-%d %H:%M'
sdate() {
date +${SDATE_FORMAT}
sdfree() {
print -n `df -h / /home` | awk '{verf1=$11; part1=$13; verf2=$17; part2=$19}; END {print "["part1"] -"verf1" [~] -"verf2}'
smemused() {
awk '/MemTotal/ {t=$2}; /MemFree/ {f=$2}; END {print t-f " " t}' /proc/meminfo | dbar -w 6 -s '='
swapused() {
awk '/SwapTotal/ {t=$2}; /SwapFree/ {f=$2}; END {print t-f " " t}' /proc/meminfo | dbar -w 6 -s '='
sload() {
print -n ${(@)$(</proc/loadavg)[1,3]}
scpu() {
vmstat | awk '/0/ {print 100-$15}' | dbar -w 6 -s '='
snetabs() {
local iface
iface=`ifconfig | grep "Ethernet" | awk '{print $1}'`
if [ $iface != "" ] ; then
print -n "$iface: `mesure -l -i $iface -avK -c 2`||"
fi
snetbar() {
mesure -aK -c 2 -l -i `ifconfig | grep "Ethernet" | awk '{print $1}'` | dbar -nonl -w 6 -s '=' -min 0 -max 270
sac() {
case `awk '{print $2}' /proc/acpi/ac_adapter/AC/state` in
on-line)
print -n "yep"
print -n "no"
esac
sbatt() {
local STATE
STATE=`cat /proc/acpi/battery/BAT0/state /proc/acpi/battery/BAT0/info`
case `echo $STATE | awk '/present:/{print $2}' - | tail -n 1` in
no)
print -n "no"
echo $STATE | awk '/design capacity:/ {f=$3}; /remaining capacity:/ {r=$3}; END {print 100*r/f"%"}' -
esac
sgov() {
< /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
sfreq() {
awk '{print $1/1000}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
stemp() {
awk '{print $2}' /proc/acpi/thermal_zone/THRC/temperature
supdates() {
grep pkg.tar.gz /var/log/updates.log | wc -l
# Main
while true; do
upd=$(supdates)
if [ $upd = 0 ] ; then
print " AC: $(sac) | Batt: $(sbatt) || $(sdfree) || CPU:$(scpu) ($(sload)) | $(sgov) / $(sfreq) MHz -> $(stemp)° || $(sdate)"
else
print " AC: $(sac) | Batt: $(sbatt) || $(sdfree) || CPU:$(scpu) ($(sload)) | $(sgov) / $(sfreq) MHz -> $(stemp)° || $upd UPD. || $(sdate)"
fi
# change polling frequency in AC/BATT mode
case $(sac) in
yep)
sleep 8
no)
sleep 1m
esac
done
You can play around a bit with the functions that get called/displayed in the main loop. It depends on zsh and makes use of this cronjob (in /etc/cron.hourly/pacsync):
#!/bin/dash
pacman -Syup --noprogressbar > /var/log/updates.log

NI System Monitor. PXI chassis info? Where?

Similar Messages

Maybe you are looking for