× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Subsystem Creation
  • From: Buck Calabro/commsoft<mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 30 Mar 1999 14:17:03 -0500

On 03/30/99 02:02:45 PM "Gary Feinstein"  wrote:

>I need to create a separate subsystem in which to run my nightly 
operations.  I 
>will be bringing down QBATCH before everything runs.  Basically, I need to 
have 
>a duplicate of the QBATCH SBS.  Should I just copy the subsystem 
description to 
>create my new one?  I'm not all that well versed on Routing Entries and I 
>didn't want to run into any problems if my new sbs has the same Routing 
Entries 
>as Qbatch. 

Gary,
I'd create a new subsystem and add one job queueentry, one pool entry, and 
the *ANY routing entry.  You definitely do NOT want any autostart job 
entries and probably don't want any communication entries or prestart job 
entries.  It depends on whether you want communications-related jobs to run 
or not (and if they run in QBATCH rather than QCMN.)

Buck Calabro
Billing Concepts Inc (formerly CommSoft), Albany, NY
mailto:mcalabro@commsoft.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.