Article View: bit.listserv.l-vmctr
Article #717VMSCHED Request xxx Reached FINAL RUN LIMIT.
From: Tim Stoodt
Date: Wed, 06 May 1992 14:40
Date: Wed, 06 May 1992 14:40
20 lines
1600 bytes
1600 bytes
Hi, I know I'm missing something basic here. I issue the following command to VMSCHED: 'VMSCHED EXEC TDSKMON VMWDMON TDSKMON MAXIDLE 9900 MAXTIME 9900 NODETACH', ' TESTUSER OPERATOR (AT 09:52:30 AGAIN DAILY TO 09:52:29 EVERY 00:30:00' This just sends the TDSKMON msgs to the OPERATOR's console every 30 min. I do this with TAPEMON also. The problem is about three weeks after I issue the command, the EXEC quits working. I look in VMRMAINT's rdr and I have a file that says: VMDRSH059I Request 'TDSKMON' reached final run limit. VMDAUT330I Local request 'TDSKMON' started normally on 04/30/92 17:52:30. VMDAUT064I Local request 'TDSKMON' executed normally on 04/30/92 17:52:39. VMDAUT069I Request 'TDSKMON' not rescheduled. The 059I message says the indicated job was scheduled with a run limit and has reached that limit. I didn't think I put a limit on it. What am I doing wrong? Thanks. T.S. We run VMSCHED 4.3A
Technical Details
Message-ID:
<L-VMCTR%92050610554803@VM1.CC.UAKRON.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!uvaarpa!darwin.sura.net!paladin.american.edu!auvm!NUACVM.BITNET!STOODTShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe320,44b501dc6985c755,start X-Google-Attributes: gidfe320,public X-Google-ArrivalTime: 1992-05-06 07:40:05 PST Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Path: arc1-ca.pugleaf.net!sparky!uunet!uvaarpa!darwin.sura.net!paladin.american.edu!auvm!NUACVM.BITNET!STOODT Message-ID: <L-VMCTR%92050610554803@VM1.CC.UAKRON.EDU> Newsgroups: bit.listserv.l-vmctr Date: Wed, 6 May 1992 09:40:05 CDT Sender: VMCENTER Components Discussion List <L-VMCTR@AKRONVM.BITNET> From: Tim Stoodt <STOODT@NUACVM.BITNET> Subject: VMSCHED Request xxx Reached FINAL RUN LIMIT. Lines: 20