|
At 15:46 05/12/1999 , David Gibbs wrote: >Can anyone point me to a resource on setting up prestart & autostart jobs >and what they are good for? Well, I can take a whack at what they're good for. Autostart jobs are great for things like subsystem monitors and data queue monitors - any job that needs to start when a subsystem starts and execute autonomously. An autostart job entry will start exactly one job. Prestart jobs are more suited to servers that will be used exclusively by a single user, but may be needed by multiple users simultaneously (like Telnet, FTP or ODBC). You can start a predetermined number of them so that a user can attach to an idle server without waiting for program initialization to complete. The system will manage the number of active jobs on a prestart job entry so that if there aren't enough, or if there are too many, the active job count is adjusted. There's some stuff in the work management guide about them. I suppose you could call that a "resource". Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | 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 mailing list archive is Copyright 1997-2025 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.