RE: Job submitted in Qstrup

midrange-l-request@xxxxxxxxxxxx wrote:

>   7. RE: Job submitted in Qstrup (Jim Damato)
>
>You can get entirely around the issues of programs with adopted QPGMR
>authority vs. granting *USE authority to QPGMR by setting up an autostart
>job entry in one of your subsystems.

Jim:

This is a perfectly good idea, but needs some discussion so others know more of 
the issues.

An auto-start job will have the same issue if QPGMR is the profile named on the 
auto-start job description. You must specify a profile for an auto-start jobd.

If QPGMR isn't appropriate, one might as well change the QSTRUPJD jobd to a 
profile that works or use a different jobd altogether.

Perhaps the major problem with an auto-start job would be determining which 
subsystem description it should be associated with. This becomes important if 
the jobd request needs services that haven't started yet. If the request needs 
TCP/IP and TCP/IP isn't active yet for some reason, then the subsystem with the 
auto-start job shouldn't be started yet. This is somewhat equivalent to placing 
SBMJOB commands in QSTRUP at a point after services are verified as started. In 
short, don't issue STRSBS for that subsystem until the proper time.

Also keep in mind that auto-start jobs don't necessarily run only at IPL or 
return from restricted state. The jobs are started every time that subsystem 
starts, regardless of whether they _should_ be one-time or not.

Tom Liotta

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com


__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge.  Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455