SWAP files usage

[Igor_Silc]

NonStop subject...

Is it somehow possible to monitor CPU memory pages usage in the SWAP files. I have in my mind the values which it can be seen with NSKCOM STATUS SWAPF command? The output of this command is similar to this one:

Status of $SYSTEM.ZSYSSWAP.CPU0A
CPU 0
CPU Pages: Total 51282 Reserved 43583 Available 7699
Peak CPU Pages ever reserved 43588
Threshold 43589 CPU pages

So I would like to use those values (numbers like CPU pages: Total, Reserved, Available, Ever Reserved) on Prognosis displays and especially I would like to use it within thresholds.

Thank you for any hint!

Regards,
Igor Silc

[GeraldC]

Hi Igor

There is no out-of-the-box record in Prognosis for those nskcom status swapfile metrics.
There is an alert in NonStopAlerts from an EMS event of Kernel Managed Swap File exceeding its threshold.
There are some interesting swap page related fields in NonStopCPU record, but they are not the same.

I suggest, if you have the ADI license key, you could try writing a command extractor for it or purchase one through IR Consulting.
HTH - Below are Help references of these 3 points.

Product Guides - Prognosis for Infrastructure - Prognosis for HP NonStop - System Monitoring - Tools - Prognosis Thresholds - NonStop Alerts
Technical - Records - Long Record Names - N - NonStopCpu

Product Guides - Prognosis for Infrastructure - Prognosis for HP NonStop - Application Development Interface - File Extractor - Overview
Product Guides - Prognosis for Infrastructure - Prognosis for HP NonStop - Application Development Interface - File Extractor - ..... (lots of useful articles)

[Igor_Silc]

Thank you Gerald!
I am aware of catching this EMS event and we already have it in place. But on other way, it would be very useful if we had any kind of information before the KMSF threshold is reached.

Has anyone tried or even already have the EXTRACT solution/sample for this topic? I appreciate it very much if anyone wants to share it.

[GeraldC]

Hi Igor, A similar sample extractor has been sent to you that should help you get started. A couple of things to note:
- Note that there are also 2 examples in Help in this location.
"Product Guides > Prognosis for Infrastructure > Prognosis for HP NonStop > Application Development Interface > File Extractor > Extractor Examples"
- Note, if your License has 'UserRecs 0' or UserRecs is too low, you'll need to enquire with IR to get a new license file with UserRecs increased for the new user defined record.
HTH

[Igor_Silc]

Thank you Gerald for an example. I have install it, but I really do have problem with our license.

but anyway, I have a questions ...

Our Prognosis processes are running under prognosi.manager (22,255) userid. Of course some of the processes are started under SuperID by default.
As I can see also extract servers are run under 22,255 userid:

$DATA03 PRGN 75> status *, prog irextcol
Process Pri PFR %WT Userid Program file Hometerm
$X3NR 0,785 100 001 22,255 $DATA03.PRGN.IREXTCOL $ZHOME {#FSCOL}
$X3P2 0,888 150 001 22,255 $DATA03.PRGN.IREXTCOL $ZHOME {#FSCOLNSK as I defined in UDEFSSRV}

My questions:
- Which userid is taken for Extractor COMMAND itself - does NSKST TACL macro runs under 22,255? The same as #FSCOLNSK?
This is a configuration in Extract subsys: EXTRACT COMMAND (FSCOLNSK, $DATA03.PRGNIGOR.NSKEXT, "RUN $$DATA03.PRGNIGOR.NSKST", 30)

- is there a way to specify other userid for #FSCOLNSK or at least for NSKST tacl macro?

I am asking that because our policy is to secure systems as much as possible, so also $system.sys.NSKCOM is secured that only super group has permission to run that object.

[GeraldC]

You're welcome. I can confirm that there is no configuration in Prognosis to specify a different user ID for IREXTCOL or its spawned TACL session command. The simplest option is to adjust NonStop to allow prognosi.manager (22,255) to run that TACL command.

Otherwise you may need to test other Prognosis features to see if there is an alternative that might work there, such as using a threshold to call a command that could write to a file for a file extractor to read it into Prognosis (user credentials stored in the PASSWORDS configuration). Here's some relevant Help articles about this threshold command feature.
- - Product Guides > Prognosis System > System Functions > Thresholds > Threshold Conditions Dialog Box > Message Destinations Tab > Command
- - Product Guides > Prognosis System > System Functions > Thresholds > Commands from Thresholds > Command Password Configuration

HTH