🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: bit.listserv.l-vmctr
Article #793

Re: VMOPERATOR scheduling execs.

#793
From: Mike Karolchik
Date: Fri, 13 Mar 1992 20:56
65 lines
2759 bytes
>Hi,
>    What's the best way to schedule execs on the OPERATOR id?  Suppose
>I wanted to run a QTELNET exec every 20 min to display on the console
>and the log, the users who are telneting in.  I put QTELNET EXEC on the
>operators 191 disk.  Now what?  We do have VMSCHED.  Thanks for any help.
>                                                                   T.S.

There are several ways you could do this. Since you have VMSCHED it is
probably best to trigger the event(s) from there since most of your
other schduled activity will be managed by that program.

Every 20 minutes (if that's possible with VMSCHED) have VMSCHED send
an message to OPERATOR such as:

      CP MSG OPERATOR **QTELNET**

Then in your LOGTABLE for VMOPERATOR have a line that says:

      IGNORE NOLOG SPAWN DOQTEL MSG VMSCHED *1 * @1='**QTELNET**'

And finally, have a file called "DOQTEL VMOPER" on OPERATOR's A-disk
that looks something like this:

      /* Run the QTELNET exec */
      'TEST CMS EXEC QTELNET'
      Exit


Another way would be to have DOQTEL run all of the time with a
20 minute WAIT loop. Note that I have some code at the top of the
loop that supports a locally implemented "CANCEL" command. I don't
like to have a process in a perpetual loop that cannot be cancelled.

      /* Run the QTELNET exec */
      Do Forever
         /* See if we are being cancelled */
         'TEST CMS SET CMSTYPE HT'
         'TEST CMS STATE DOQTEL CANCEL A'
         xrc = rc
         'TEST CMS SET CMSTYPE RT'
         If xrc = 0 Then Do
            Say 'DOQTEL: Ending due to cancel.'
            'TEST CMS ERASE DOQTEL CANCEL A'
            Exit
         End

         /** Run the EXEC **/
         'TEST CMS EXEC QTELNET'

         /** Wait for 20 minutes **/
         'TEST PROCESS WAIT 1200'
      End
      Exit


If you opt to use the perpetual loop, you need to have a userid
running an IUCV-Connected console with "PROCESS DOQTEL" in their
list of processes.



Hope this helps.

-Mike Karolchik
WVNET
Technical Details
Message-ID: <L-VMCTR%92031315553020@VM1.CC.UAKRON.EDU>
Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!WVNVM.BITNET!MIKE

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe320,fc2de8004a17ece5
X-Google-Attributes: gidfe320,public
X-Google-ArrivalTime: 1992-03-13 13:04:40 PST
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!WVNVM.BITNET!MIKE
X-Acknowledge-To: <MIKE@WVNVM>
Message-ID: <L-VMCTR%92031315553020@VM1.CC.UAKRON.EDU>
Newsgroups: bit.listserv.l-vmctr
Date:         Fri, 13 Mar 1992 15:56:11 EST
Sender:       VMCENTER Components Discussion List <L-VMCTR@AKRONVM.BITNET>
From:         Mike Karolchik <MIKE@WVNVM.BITNET>
Subject:      Re: VMOPERATOR scheduling execs.
In-Reply-To:  Message of 03/13/92 at 12:11:29 from STOODT@NUACVM.BITNET