• SYSBUSY version

    From Stefan Barfred@21:1/5 to All on Thu Aug 17 06:51:30 2023
    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS version or TSNX version or a similar utility to show CPU busy?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Randall@21:1/5 to Stefan Barfred on Thu Aug 17 11:47:37 2023
    On Thursday, August 17, 2023 at 9:51:32 a.m. UTC-4, Stefan Barfred wrote:
    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS version or TSNX version or a similar utility to show CPU busy?

    There is PEEK and VIEWSYS. Those might help.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Honaker@21:1/5 to Stefan Barfred on Thu Aug 17 13:55:05 2023
    On Thu, 17 Aug 2023 06:51:30 -0700 (PDT), Stefan Barfred <stefan.barfred@gmail.com> wrote:

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS version or TSNX version or a similar utility to show CPU busy?

    4 years ago, this utility was available from third data, but their website is not active now.
    One person said that there was a Code 100 version which might work, but recognize that
    Measures continues to change with new hardware so it may not work.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JShepherd@21:1/5 to All on Thu Aug 17 23:15:50 2023
    In article <9b8b98cb-f4a8-4081-a33a-b46542e45d33n@googlegroups.com>, stefan.barfred@gmail.com says...

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the
    OLD TNS version or TSNX version or a similar utility to show CPU busy?


    This is the copy we have on x86
    I dont know if the author built an x86 native version


    $SYSTEM.SYSTOOLS.SYSBUSY
    Binder timestamp: 10DEC2014 16:55:14 (creator's LCT)
    Version procedure: T0700D48_28MAY2014_SYSBUSY_V4_1
    Target CPU: UNSPECIFIED
    AXCEL timestamp: 10DEC2014 16:56:09 (creator's LCT)
    OCAX timestamp: 17SEP2019 14:19:09 (creator's LCT)


    https://www.dropbox.com/scl/fi/p2xtoenbsno6j2wx00u15/SYSBUSY.100? rlkey=eixpk21wkgdg3e01wh7rb1sva&dl=1

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JShepherd@21:1/5 to All on Thu Aug 17 23:28:55 2023
    In article <e4rsdilmhvp58tp556iahfeilm0emj583f@4ax.com>, no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 06:51:30 -0700 (PDT), Stefan Barfred <stefan.barfred@gmail.c
    wrote:

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS ver
    sion or TSNX version or a similar utility to show CPU busy?

    4 years ago, this utility was available from third data, but their website
    is no
    t active now.
    One person said that there was a Code 100 version which might work, but recogniz
    e that
    Measures continues to change with new hardware so it may not work.


    It does not appear that sysbusy uses measure

    External Procedures from Code Space 00
    Procedure Name #Ref Calling Procedure ---------------------------------- ---- ------------------------
    ABEND 7
    17439 - ENV_WRITELOG
    12739 - ENV_SHUTDOWN
    12749 - ENV_SHUTDOWN
    2765 - SYSBUSY
    2750 - SYSBUSY
    2735 - SYSBUSY
    2720 - SYSBUSY
    ALLOCATESEGMENT 1
    14406 - UTIL_ALLOCATESEGMENT
    FNAMECOLLAPSE 4
    17246 - UTIL_FNAMECOLLAPSE
    16297 - ENV_FNAME
    10043 - UTIL_FORMAT
    10273 - UTIL_FORMAT
    MYPID 6
    10012 - UTIL_FORMAT
    10991 - UTIL_FORMAT
    11007 - UTIL_FORMAT
    10165 - UTIL_FORMAT
    10388 - UTIL_FORMAT
    9995 - UTIL_FORMAT

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JShepherd@21:1/5 to All on Thu Aug 17 23:41:38 2023
    In article <ubmafn$3um0j$2@dont-email.me>, invalid@nowhere.com says...

    In article <e4rsdilmhvp58tp556iahfeilm0emj583f@4ax.com>, >no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 06:51:30 -0700 (PDT), Stefan Barfred ><stefan.barfred@gmail.c
    wrote:

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD
    TNS
    ver
    sion or TSNX version or a similar utility to show CPU busy?

    4 years ago, this utility was available from third data, but their website >is no
    t active now.
    One person said that there was a Code 100 version which might work, but >recogniz
    e that
    Measures continues to change with new hardware so it may not work.





    Sorry, that last list was incomplete,

    It does not appear that sysbusy uses measure

    External Procedures from Code Space 00
    Procedure Name #Ref Calling Procedure ---------------------------------- ---- ------------------------
    ABEND 7
    17439 - ENV_WRITELOG
    12739 - ENV_SHUTDOWN
    12749 - ENV_SHUTDOWN
    2765 - SYSBUSY
    2750 - SYSBUSY
    2735 - SYSBUSY
    2720 - SYSBUSY
    ALLOCATESEGMENT 1
    14406 - UTIL_ALLOCATESEGMENT
    AWAITIO 1
    17103 - ENV_INITIALIZER_
    AWAITIOX 4
    17750 - TERM_CONVMODE
    17635 - TERM_FUNC
    15732 - TERM_FLUSH
    15325 - TERM_BLOCKMODE
    CPUTIMES 1
    11672 - CPU_SAMPLE
    CREATE 1
    14352 - UTIL_ALLOCATESEGMENT
    DEFINEINFO 1
    16174 - ENV_FNAME
    DNUMIN 5
    16605 - UTIL_DOUBLE
    16533 - UTIL_IPADDR
    16492 - UTIL_IPADDR
    16452 - UTIL_IPADDR
    16414 - UTIL_IPADDR
    DNUMOUT 14
    9617 - UTIL_FORMAT
    10823 - UTIL_FORMAT
    1559 - TIME8
    1529 - TIME8
    1493 - TIME8
    1461 - TIME8
    1419 - TIME8
    1387 - TIME8
    1347 - TIME8
    1304 - TIME8
    1272 - TIME8
    1228 - TIME8
    1165 - TIME8
    1126 - TIME8
    FILEINFO 6
    14399 - UTIL_ALLOCATESEGMENT
    14362 - UTIL_ALLOCATESEGMENT
    14208 - UTIL_ALLOCATESEGMENT
    9937 - UTIL_FORMAT
    10130 - UTIL_FORMAT
    9710 - UTIL_FORMAT
    FILENAME_COMPARE_ 1
    18126 - UTIL_SAMEFILE
    FILENAME_DECOMPOSE_ 2
    17304 - UTIL_MYSWAPVOLUME
    1795 - PRINTTABLE
    FILE_CLOSE_ 6
    18304 - LCONF_READ_
    17216 - ENV_INITIALIZER_
    12875 - TERM_CLOSE
    12836 - ENV_SHUTDOWN
    12854 - ENV_SHUTDOWN
    12818 - ENV_SHUTDOWN
    FILE_GETINFO_ 19
    18274 - LCONF_READ_
    18297 - LCONF_READ_
    18174 - TERM_FUNC_NW
    18109 - UTIL_SAMEFILE
    18089 - UTIL_SAMEFILE
    17764 - TERM_CONVMODE
    17730 - TERM_CONVMODE
    17695 - TERM_CONVMODE
    17649 - TERM_FUNC
    17346 - ENV_WRITELOG
    17411 - ENV_WRITELOG
    17088 - ENV_INITIALIZER_
    17113 - ENV_INITIALIZER_
    15746 - TERM_FLUSH
    15712 - TERM_FLUSH
    15339 - TERM_BLOCKMODE
    15305 - TERM_BLOCKMODE
    15270 - TERM_BLOCKMODE
    14473 - TERM_OPEN
    FILE_GETRECEIVEINFO_ 1
    16834 - ENV_INITIALIZER_
    FILE_OPEN_ 6
    18253 - LCONF_READ_
    17200 - ENV_INITIALIZER_
    14454 - TERM_OPEN
    14121 - ENV_STARTUP
    14039 - ENV_STARTUP
    14072 - ENV_STARTUP
    FNAMECOLLAPSE 4
    17246 - UTIL_FNAMECOLLAPSE
    16297 - ENV_FNAME
    10043 - UTIL_FORMAT
    10273 - UTIL_FORMAT
    FNAMEEXPAND 2
    16286 - ENV_FNAME
    12214 - UTIL_GETSYSTEMNUMBER
    HEAPSORTX_ 1
    2381 - NEXTPROCESSLIST
    INTERPRETINTERVAL 1
    10794 - UTIL_FORMAT
    INTERPRETTIMESTAMP 1
    10837 - UTIL_FORMAT
    KEYPOSITIONX 1
    18264 - LCONF_READ_
    MYPID 6
    10012 - UTIL_FORMAT
    10991 - UTIL_FORMAT
    11007 - UTIL_FORMAT
    10165 - UTIL_FORMAT
    10388 - UTIL_FORMAT
    9995 - UTIL_FORMAT
    MYPROCESSTIME 1
    12730 - ENV_SHUTDOWN
    MYSYSTEMNUMBER 3
    12247 - UTIL_GETSYSTEMNUMBER
    10107 - UTIL_FORMAT
    10193 - UTIL_FORMAT
    NODENUMBER_TO_NODENAME_ 1
    2678 - SYSBUSY
    NUMIN 1
    12237 - UTIL_GETSYSTEMNUMBER
    NUMOUT 14
    11096 - UTIL_FORMAT
    10883 - UTIL_FORMAT
    10215 - UTIL_FORMAT
    10935 - UTIL_FORMAT
    10868 - UTIL_FORMAT
    10851 - UTIL_FORMAT
    10918 - UTIL_FORMAT
    10314 - UTIL_FORMAT
    10965 - UTIL_FORMAT
    11108 - UTIL_FORMAT
    10905 - UTIL_FORMAT
    10948 - UTIL_FORMAT
    10239 - UTIL_FORMAT
    10229 - UTIL_FORMAT
    PROCESSHANDLE_DECOMPOSE_ 1
    1773 - PRINTTABLE
    PROCESSINFO 6
    11016 - UTIL_FORMAT
    10105 - UTIL_FORMAT
    10173 - UTIL_FORMAT
    10022 - UTIL_FORMAT
    10005 - UTIL_FORMAT
    11000 - UTIL_FORMAT
    PROCESSORTYPE 3
    12485 - CPU_INIT
    10375 - UTIL_FORMAT
    10394 - UTIL_FORMAT
    PROCESS_GETINFOLIST_ 1
    2101 - FETCHINFO
    PROCESS_GETINFO_ 4
    17284 - UTIL_MYSWAPVOLUME
    16846 - ENV_INITIALIZER_
    14102 - ENV_STARTUP
    1742 - PRINTTABLE
    PROCESS_GETPAIRINFO_ 1
    16866 - ENV_INITIALIZER_
    READUPDATE 1
    17078 - ENV_INITIALIZER_
    READX 2
    18287 - LCONF_READ_
    18160 - TERM_FUNC_NW
    REMOTEPROCESSORSTATUS 1
    12421 - CPU_INIT
    REMOTETOSVERSION 1
    12492 - CPU_INIT
    REPLY 2
    17138 - ENV_INITIALIZER_
    17125 - ENV_INITIALIZER_
    SETMODE 3
    17681 - TERM_CONVMODE
    15256 - TERM_BLOCKMODE
    14486 - TERM_OPEN
    SETPARAM 2
    17798 - TERM_CONVMODE
    15366 - TERM_BLOCKMODE
    STOP 2
    12860 - ENV_SHUTDOWN
    2993 - SYSBUSY
    USERIDTOUSERNAME 1
    11035 - UTIL_FORMAT
    USESEGMENT 1
    11970 - KLD_STARTUP
    WRITEREADX 2
    17716 - TERM_CONVMODE
    15698 - TERM_FLUSH
    WRITEX 4
    17397 - ENV_WRITELOG
    17332 - ENV_WRITELOG
    15676 - TERM_FLUSH
    15291 - TERM_BLOCKMODE

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Barfred@21:1/5 to All on Fri Aug 18 01:35:43 2023
    So cool.. it works great on TNSX :) Thanks for the help...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Honaker@21:1/5 to JShepherd on Fri Aug 18 11:17:49 2023
    On Thu, 17 Aug 2023 23:41:38 -0000 (UTC), invalid@nowhere.com (JShepherd) wrote:

    In article <ubmafn$3um0j$2@dont-email.me>, invalid@nowhere.com says...

    In article <e4rsdilmhvp58tp556iahfeilm0emj583f@4ax.com>, >>no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 06:51:30 -0700 (PDT), Stefan Barfred >><stefan.barfred@gmail.c
    wrote:

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD >TNS
    ver
    sion or TSNX version or a similar utility to show CPU busy?

    4 years ago, this utility was available from third data, but their website >>is no
    t active now.
    One person said that there was a Code 100 version which might work, but >>recogniz
    e that
    Measures continues to change with new hardware so it may not work.





    Sorry, that last list was incomplete,

    It does not appear that sysbusy uses measure

    External Procedures from Code Space 00
    Procedure Name #Ref Calling Procedure >---------------------------------- ---- ------------------------
    ABEND 7
    17439 - ENV_WRITELOG
    12739 - ENV_SHUTDOWN
    12749 - ENV_SHUTDOWN
    2765 - SYSBUSY
    2750 - SYSBUSY
    2735 - SYSBUSY
    2720 - SYSBUSY
    ALLOCATESEGMENT 1
    14406 - UTIL_ALLOCATESEGMENT
    AWAITIO 1
    17103 - ENV_INITIALIZER_
    AWAITIOX 4
    17750 - TERM_CONVMODE
    17635 - TERM_FUNC
    15732 - TERM_FLUSH
    15325 - TERM_BLOCKMODE
    CPUTIMES 1
    11672 - CPU_SAMPLE
    CREATE 1
    14352 - UTIL_ALLOCATESEGMENT
    DEFINEINFO 1
    16174 - ENV_FNAME
    DNUMIN 5
    16605 - UTIL_DOUBLE
    16533 - UTIL_IPADDR
    16492 - UTIL_IPADDR
    16452 - UTIL_IPADDR
    16414 - UTIL_IPADDR
    DNUMOUT 14
    9617 - UTIL_FORMAT
    10823 - UTIL_FORMAT
    1559 - TIME8
    1529 - TIME8
    1493 - TIME8
    1461 - TIME8
    1419 - TIME8
    1387 - TIME8
    1347 - TIME8
    1304 - TIME8
    1272 - TIME8
    1228 - TIME8
    1165 - TIME8
    1126 - TIME8
    FILEINFO 6
    14399 - UTIL_ALLOCATESEGMENT
    14362 - UTIL_ALLOCATESEGMENT
    14208 - UTIL_ALLOCATESEGMENT
    9937 - UTIL_FORMAT
    10130 - UTIL_FORMAT
    9710 - UTIL_FORMAT
    FILENAME_COMPARE_ 1
    18126 - UTIL_SAMEFILE
    FILENAME_DECOMPOSE_ 2
    17304 - UTIL_MYSWAPVOLUME
    1795 - PRINTTABLE
    FILE_CLOSE_ 6
    18304 - LCONF_READ_
    17216 - ENV_INITIALIZER_
    12875 - TERM_CLOSE
    12836 - ENV_SHUTDOWN
    12854 - ENV_SHUTDOWN
    12818 - ENV_SHUTDOWN
    FILE_GETINFO_ 19
    18274 - LCONF_READ_
    18297 - LCONF_READ_
    18174 - TERM_FUNC_NW
    18109 - UTIL_SAMEFILE
    18089 - UTIL_SAMEFILE
    17764 - TERM_CONVMODE
    17730 - TERM_CONVMODE
    17695 - TERM_CONVMODE
    17649 - TERM_FUNC
    17346 - ENV_WRITELOG
    17411 - ENV_WRITELOG
    17088 - ENV_INITIALIZER_
    17113 - ENV_INITIALIZER_
    15746 - TERM_FLUSH
    15712 - TERM_FLUSH
    15339 - TERM_BLOCKMODE
    15305 - TERM_BLOCKMODE
    15270 - TERM_BLOCKMODE
    14473 - TERM_OPEN
    FILE_GETRECEIVEINFO_ 1
    16834 - ENV_INITIALIZER_
    FILE_OPEN_ 6
    18253 - LCONF_READ_
    17200 - ENV_INITIALIZER_
    14454 - TERM_OPEN
    14121 - ENV_STARTUP
    14039 - ENV_STARTUP
    14072 - ENV_STARTUP
    FNAMECOLLAPSE 4
    17246 - UTIL_FNAMECOLLAPSE
    16297 - ENV_FNAME
    10043 - UTIL_FORMAT
    10273 - UTIL_FORMAT
    FNAMEEXPAND 2
    16286 - ENV_FNAME
    12214 - UTIL_GETSYSTEMNUMBER
    HEAPSORTX_ 1
    2381 - NEXTPROCESSLIST
    INTERPRETINTERVAL 1
    10794 - UTIL_FORMAT
    INTERPRETTIMESTAMP 1
    10837 - UTIL_FORMAT
    KEYPOSITIONX 1
    18264 - LCONF_READ_
    MYPID 6
    10012 - UTIL_FORMAT
    10991 - UTIL_FORMAT
    11007 - UTIL_FORMAT
    10165 - UTIL_FORMAT
    10388 - UTIL_FORMAT
    9995 - UTIL_FORMAT
    MYPROCESSTIME 1
    12730 - ENV_SHUTDOWN
    MYSYSTEMNUMBER 3
    12247 - UTIL_GETSYSTEMNUMBER
    10107 - UTIL_FORMAT
    10193 - UTIL_FORMAT
    NODENUMBER_TO_NODENAME_ 1
    2678 - SYSBUSY
    NUMIN 1
    12237 - UTIL_GETSYSTEMNUMBER
    NUMOUT 14
    11096 - UTIL_FORMAT
    10883 - UTIL_FORMAT
    10215 - UTIL_FORMAT
    10935 - UTIL_FORMAT
    10868 - UTIL_FORMAT
    10851 - UTIL_FORMAT
    10918 - UTIL_FORMAT
    10314 - UTIL_FORMAT
    10965 - UTIL_FORMAT
    11108 - UTIL_FORMAT
    10905 - UTIL_FORMAT
    10948 - UTIL_FORMAT
    10239 - UTIL_FORMAT
    10229 - UTIL_FORMAT
    PROCESSHANDLE_DECOMPOSE_ 1
    1773 - PRINTTABLE
    PROCESSINFO 6
    11016 - UTIL_FORMAT
    10105 - UTIL_FORMAT
    10173 - UTIL_FORMAT
    10022 - UTIL_FORMAT
    10005 - UTIL_FORMAT
    11000 - UTIL_FORMAT
    PROCESSORTYPE 3
    12485 - CPU_INIT
    10375 - UTIL_FORMAT
    10394 - UTIL_FORMAT
    PROCESS_GETINFOLIST_ 1
    2101 - FETCHINFO
    PROCESS_GETINFO_ 4
    17284 - UTIL_MYSWAPVOLUME
    16846 - ENV_INITIALIZER_
    14102 - ENV_STARTUP
    1742 - PRINTTABLE
    PROCESS_GETPAIRINFO_ 1
    16866 - ENV_INITIALIZER_
    READUPDATE 1
    17078 - ENV_INITIALIZER_
    READX 2
    18287 - LCONF_READ_
    18160 - TERM_FUNC_NW
    REMOTEPROCESSORSTATUS 1
    12421 - CPU_INIT
    REMOTETOSVERSION 1
    12492 - CPU_INIT
    REPLY 2
    17138 - ENV_INITIALIZER_
    17125 - ENV_INITIALIZER_
    SETMODE 3
    17681 - TERM_CONVMODE
    15256 - TERM_BLOCKMODE
    14486 - TERM_OPEN
    SETPARAM 2
    17798 - TERM_CONVMODE
    15366 - TERM_BLOCKMODE
    STOP 2
    12860 - ENV_SHUTDOWN
    2993 - SYSBUSY
    USERIDTOUSERNAME 1
    11035 - UTIL_FORMAT
    USESEGMENT 1
    11970 - KLD_STARTUP
    WRITEREADX 2
    17716 - TERM_CONVMODE
    15698 - TERM_FLUSH
    WRITEX 4
    17397 - ENV_WRITELOG
    17332 - ENV_WRITELOG
    15676 - TERM_FLUSH
    15291 - TERM_BLOCKMODE



    JShepahrd,

    It may have changed, but the PROCESS BUSY counters in Measure are used in the PROCESS_GETINFO_ calls when it's requested.
    In the past, if a measurement wasn't started that included that process, no values are avaialble.

    Using those calls does make the code portable between Measure versions so if the source is avaiable (or a code 100), it should work.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JShepherd@21:1/5 to All on Fri Aug 18 21:06:57 2023
    In article <386vdipgs4o12kfi64vfq1p9aa5cha17j3@4ax.com>, no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 23:41:38 -0000 (UTC), invalid@nowhere.com (JShepherd) wrote:

    In article <ubmafn$3um0j$2@dont-email.me>, invalid@nowhere.com says...

    In article <e4rsdilmhvp58tp556iahfeilm0emj583f@4ax.com>, >>>no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 06:51:30 -0700 (PDT), Stefan Barfred >>><stefan.barfred@gmail.c
    wrote:

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD >>TNS
    ver
    sion or TSNX version or a similar utility to show CPU busy?

    4 years ago, this utility was available from third data, but their
    website
    is no
    t active now.
    One person said that there was a Code 100 version which might work, but >>>recogniz
    e that
    Measures continues to change with new hardware so it may not work.







    JShepahrd,

    It may have changed, but the PROCESS BUSY counters in Measure are used in
    the PR
    OCESS_GETINFO_ calls when it's requested.
    In the past, if a measurement wasn't started that included that process, no valu
    es are avaialble.

    Using those calls does make the code portable between Measure versions so if the
    source is avaiable (or a code 100), it should work.




    So if measure is not running you can't get process busy time ?

    meascom
    stop meassubsys
    status meassubsys
    MEAS 3219 MEASURE subsystem is not currently running
    exit

    pstate $TMP
    [snip]

    Process Creation Time: May 1, 2019 12:21:58.653163 (LCT)
    Process Execution Time: 3:7:16.714161

    status $TMP, detail

    Pid: 0,12 ($TMP) Primary
    PRIV
    Priority: 204
    Wait State: %007 (LDONE, LTMF, LREQ)
    Userid: 255,255 (SUPER.SUPER)
    Myterm: $YMIOP.#CLCI
    Program File Name: $SYSTEM.SYS00.TMFTMP
    Swap File Name: $SYSTEM.#0
    Process Time: 3:7:16.741

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Honaker@21:1/5 to JShepherd on Fri Aug 18 18:47:11 2023
    On Fri, 18 Aug 2023 21:06:57 -0000 (UTC), invalid@nowhere.com (JShepherd) wrote:

    In article <386vdipgs4o12kfi64vfq1p9aa5cha17j3@4ax.com>, >no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 23:41:38 -0000 (UTC), invalid@nowhere.com (JShepherd) >wrote:

    In article <ubmafn$3um0j$2@dont-email.me>, invalid@nowhere.com says...

    In article <e4rsdilmhvp58tp556iahfeilm0emj583f@4ax.com>, >>>>no_spam_bhonaker__@x_i_d.com says...

    On Thu, 17 Aug 2023 06:51:30 -0700 (PDT), Stefan Barfred >>>><stefan.barfred@gmail.c
    wrote:

    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD >>>TNS
    ver
    sion or TSNX version or a similar utility to show CPU busy?

    4 years ago, this utility was available from third data, but their >website
    is no
    t active now.
    One person said that there was a Code 100 version which might work, but >>>>recogniz
    e that
    Measures continues to change with new hardware so it may not work.







    JShepahrd,

    It may have changed, but the PROCESS BUSY counters in Measure are used in >the PR
    OCESS_GETINFO_ calls when it's requested.
    In the past, if a measurement wasn't started that included that process, no >valu
    es are avaialble.

    Using those calls does make the code portable between Measure versions so if >the
    source is avaiable (or a code 100), it should work.




    So if measure is not running you can't get process busy time ?

    meascom
    stop meassubsys
    status meassubsys
    MEAS 3219 MEASURE subsystem is not currently running
    exit

    pstate $TMP
    [snip]

    Process Creation Time: May 1, 2019 12:21:58.653163 (LCT)
    Process Execution Time: 3:7:16.714161

    status $TMP, detail

    Pid: 0,12 ($TMP) Primary
    PRIV
    Priority: 204
    Wait State: %007 (LDONE, LTMF, LREQ)
    Userid: 255,255 (SUPER.SUPER)
    Myterm: $YMIOP.#CLCI
    Program File Name: $SYSTEM.SYS00.TMFTMP
    Swap File Name: $SYSTEM.#0
    Process Time: 3:7:16.741


    In my defense (if I need it), I did start the post with "It may have changed, but..."
    Waaay back when, the counters bump code didn't do anything if there wasn't an active measurement
    looking for data to be stored somewhere. Could be they changed that so PROCESS_GETINFO_LIST_ can use it without starting a meas.

    Thanks for checking.

    The rest of my post, "if the source is avaiable (or a code 100), it should work.", still applies.
    Bill

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rob Lesan@21:1/5 to Stefan Barfred on Thu Aug 24 07:43:15 2023
    On Thursday, August 17, 2023 at 9:51:32 AM UTC-4, Stefan Barfred wrote:
    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS version or TSNX version or a similar utility to show CPU busy?

    I have an Itanium copy of SYSBUSY (code 800). Email me and I can send it to you.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rob Lesan@21:1/5 to Rob Lesan on Thu Aug 24 07:45:06 2023
    On Thursday, August 24, 2023 at 10:43:17 AM UTC-4, Rob Lesan wrote:
    On Thursday, August 17, 2023 at 9:51:32 AM UTC-4, Stefan Barfred wrote:
    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS version or TSNX version or a similar utility to show CPU busy?
    I have an Itanium copy of SYSBUSY (code 800). Email me and I can send it to you.

    FYI, SYSBUSY does not use Measure...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rob Lesan@21:1/5 to Rob Lesan on Thu Aug 24 07:49:03 2023
    On Thursday, August 24, 2023 at 10:45:08 AM UTC-4, Rob Lesan wrote:
    On Thursday, August 24, 2023 at 10:43:17 AM UTC-4, Rob Lesan wrote:
    On Thursday, August 17, 2023 at 9:51:32 AM UTC-4, Stefan Barfred wrote:
    Hi, we just got a brand new TNSX server.
    I have utility SYSBUSY in Itanium version, does anybody have the an OLD TNS version or TSNX version or a similar utility to show CPU busy?
    I have an Itanium copy of SYSBUSY (code 800). Email me and I can send it to you.
    FYI, SYSBUSY does not use Measure...

    And I just found a CISC (code 100) version 2 copy of SYSBUSY as well....

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)