What documentation do I need to provide for a High CPU condition?

Document ID : KB000055290
Last Modified Date : 14/02/2018
Show Technical Document Details

The following documentation is requested for diagnosing high CPU conditions:

  1. A screen print showing where the high CPU is noticed.

  2. All output (all files) from the region's started task.

  3. All output from the associated SSI region's started task.

  4. CPUMON output, see procedure below

  5. Output from issuing STATUS on the Command Entry Screen (=CMD) within Netmaster.

  6. Information such as: does the CPU usage spike or remain constant, if spiking does it occur on a regular interval basis, did the condition occur after invoking a specific screen in Netmaster, how long has the region been up, is the high CPU condition causing other issues on your system.

CPUMON - Customer Instructions for Diagnosing High CPU in Netmaster:

  1. Turn on CPU monitoring in the started task:

    • Add the following statement to the started task proc:
          PPREF='XOPT=(SDUMP,CPUMM,CPUPM,CPULM)
    • Bounce the started task region

  2. . Add the CPUMON procedure below to the TESTEXEC and call it member CPUMON
      ***************************** Top of Data **********
    $NMCP01Z HICPU=002.00 + LOCPU=001.00 + PMONDSN=hlq.##PMON.UNLOAD + HICOUNT=01 + -* DEFAULTS TO 2 PERIOD=05 + -* DEFAULTS TO 2 SITE=HIGHCPU + PREFIX=PN **************************** Bottom of Data ********
    NOTE: Change hlq to a valid High Level Qualifier(s)
    HICPU=the lowest value considered to be high CPU
    LOCPU=the value which is considered normal CPU

  3. Preallocate the PMONDSN above with the following attributes:
    hlq.##PMON.UNLOAD     Organization  . . . : PO        Record format . . . : VB       Record length . . . : 260      Block size  . . . . : 2600     1st extent cylinders: 2        Secondary cylinders : 1        Data set name type  : PDS
  4. In the product region go to the Command Entry Screen (=CMD) and enter command: CPUMON

    You should see response messages similar to:
      ,cpumon,  ,NMCP0110 Minute-Minder Listener started,   ,NMCP0111 Site ID = HIGHCPU_________,   ,NMCP0111 High CPU Value = 2,   ,NMCP0111 Low CPU Value = 1,   ,NMCP0111 High Count Threshold = 01,   ,NMCP0111 PMON Collection Period = 02,   ,NMCP0111 PMON Data Set Name = AUCM0.MICCY01.##PMON.UNLOAD,   ,NMCP0111 PMON Data Set Member Prefix = PN,   ,N02C03 EDS PROFILE ENABLED,   ,** END OF DELIVERED MESSAGES **, 
  5. This will execute the procedure and put messages similar to the following into your log every minute:
      11.28.40 N00M10 11.28.40 ET: 60.01 DC: 0.222401 TC: 193.525500 %A: 0.36  11.28.40 N00M20 11.28.40 ET: 60.01 DC: 0.222401 PC: 0.193901 ST: 4 EN: 3 TO: 87   11.28.40 N00M21 1 008437   MICCY01 ##HELP   N SE 15.43   0.031769 0.123555   11.28.40 N00M21 2 007142   WITAN01 $RMLK00S N -- 60.01   0.102767 0.102767   11.28.40 N00M21 3 008358   MICCY01 $CMDENT  N -- 60.01   0.025875 0.025875   11.28.40 N00M29 *END*   11.28.40 N00M30 11.28.40 ET: 60.01 DC: 0.222401 TC: 0.020510 ST: 2 EN: 2 TO: 13   11.28.40 N00M31 1 96       NM061    SE  0.04     0.005564 8.347391   11.28.40 N00M31 2 95       NM061    SE  0.10     0.008256 4.954425   11.28.40 N00M31 3 37       NM502    -- 60.01     0.005471 0.005471   11.28.40 N00M31 4 6        NM061    -- 60.01     0.000308 0.000308   11.28.40 N00M31 5 2        NM042    -- 60.01     0.000284 0.000284   11.28.40 N00M31 6 4        NM042    -- 60.01     0.000284 0.000284   11.28.40 N00M31 7 5        NM042    -- 60.01     0.000186 0.000186   11.28.40 N00M31 8 3        NM042    -- 60.01     0.000157 0.000157   11.28.40 N00M31 9 1        NM042    -- 60.01     0.000000 0.000000   11.28.40 N00M31 10 32      NM006011 -- 60.01     0.000000 0.000000   11.28.40 N00M31 11 33      NM020    -- 60.01     0.000000 0.000000   11.28.40 N00M31 13 79      NM0005I4 -- 60.01     0.000000 0.000000   11.28.40 N00M39 *END* 
  6. When the High CPU condition is met you will see the following message in the log:
        2.07.42 N14K01 ##PMON START COMMAND PROCESSED SUCCESSFULLY. 
    The data will be written to the hlq.##PMON.UNLOAD dataset that was defined above. The procedure will stop executing once the normal CPU threshold, as set above for LOCPU is met or at the conclusion of 5 minutes, whichever occurs first.

  7. When the data has completed writing to the dataset you will see the following messages:
    12.09.42 N14K80 MONITOR RUN 1 ENDED. 2007/08/23 12:07:42 TO 2007/08/23 12:09:4212.09.42 N14O10 MONITOR UNLOAD STARTING FOR ID: 1 TO DDNAME: PMONDD MEMBER: PNHHWM07 12.09.42 N14O11 MONITOR UNLOAD COMPLETE FOR ID: 1 TO DDNAME: PMONDD MEMBER: PNHHWM07 
    Note - the MEMBER name, in this case PNHHWM07 is the member in the dataset that contains the data.

  8. Go to the command entry screen (=CMD) and issue the following command to turn off the process:
    $NMCP01Z STOP

    This will be confirmed by messages:
    12.14.53 START $nmCP01Z STOP12.14.53 NMCP0198 Minute-Minder Listener stop requested 12.14.53 N14K01 ##PMON STOP COMMAND PROCESSED SUCCESSFULLY. 
  9. Send the Netmaster product region log, along with the data from the hlq.##PMON.UNLOAD dataset to us for diagnosis. Please TERSE and FTP the data in binary format.