Re: Is there a simple way for a CL program to determine whether a given subsystem is active?

[Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>]

 +10 Scott!
And, James, this API:    https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/qwdrsbsd.htm ; 

exists all the way back to V2R1, so as far back as you might ever care to go ...  ;-)
All the best,
Mark S. Waterbury

    On Tuesday, March 2, 2021, 2:47:48 PM EST, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:  
 
 Rob,

Literally... this is all you have to do to check if a subsystem is active:


     DCL VAR(&SBS)       TYPE(*CHAR) LEN(20)  VALUE('QSYS QINTER')
     DCL VAR(&RCVVAR)    TYPE(*CHAR) LEN(80)
     DCL VAR(&RCVVARLEN) TYPE(*INT)  LEN( 4) VALUE(80)
     DCL VAR(&STATUS)    TYPE(*CHAR) LEN(10)

     CALL PGM(QWDRSBSD) PARM(&RCVVAR &RCVVARLEN SBSI0100 &SBS +
                             X'0000000000000000')
     CHGVAR VAR(&STATUS) VALUE(%SST(&RCVVAR 29 10))

     /* AT THIS POINT, &STATUS WILL CONTAIN '*ACTIVE' IF THE +
        SUBSYSTEM IS ACTIVE. */


I can understand someone wanting something simpler... but is this whole 
idea of installing new user space commands, creating the space, running 
QShell and outputting to the space, etc business really simpler than 
just calling an API?

-SK


On 3/2/2021 1:16 PM, Rob Berendt wrote:
> Well, if you really want to twist your head around something you can try this:
> QSH CMD('db2 "SELECT COUNT(*) FROM qsys2.subsystem_info where status = ''ACTIVE'' and subsystem_description = ''QBATCH''" > /QSYS.LIB/ROB.LIB/ROBSQL.USRSPC')
>
> Then install these commands to get RTVUSRSPC:
> https://www.ibm.com/support/pages/creatingchangingretrieving-user-space-usrspc-ibm%C2%AE-iseries%E2%84%A2-family-servers
>
> Too bad I couldn't get a pipe to a data area to work.
>
> or this
> QSH CMD('db2 "CREATE TABLE ROB.IFACTIVE AS(SELECT COUNT(*) AS JOBCOUNT FROM qsys2.subsystem_info where status = ''ACTIVE'' and subsystem_description = ''QBATCH'') WITH DATA"')
> Then read that file with cl
> Could not get the qtemp.ifactive to work.  I suspect that qsh is spawned as a different job with it's own qtemp.
>
> CL is such a kludge.
>
> Rob Berendt