RE: Creating a subsystem

["Metz, Zak" <Zak_Metz@xxxxxx>]

Hey Tom, thanks for your comments!

Inline...

> -----Original Message-----
> From: Tom Jedrzejewicz @ San Pedro [mailto:TJedrzejewicz@xxxxxxxxxxxx]
> IMHO --
> 
> By default, isolate your program.  This in not likely the 
> best approach
> from a performance point of view, but is the most "polite" and least
> likely to disrupt the existing system.
> -- The never ending job (sockets communication perhaps?) should have
> it's own subsystem.  You can then have the subsystem description
> autostart whatever processes necessary.
> -- The submitted jobs should go to ANOTHER new subsystem that you
> create.

Ok, so perhaps something like a G1COMM *SBSD for the sockets program
(you were right!) with an AJE for the server job, and a G1BATCH *SBSD
for the batch work. Makes sense. All of this would be optional, with
install-time options for using an existing subsystem for either.


> You should provide clear instructions for:
> -- Submitted jobs to job queue/subsystem of customers choice
> -- NEP in existing subsystem, such as QSYSWRK
> -- the various startup options (job scheduler, QSTRUP pgm, SBS
> autostart, etc)
> 
> That would be ideal for the implementing of a new package.

Excellent, and I hadn't thought of the JOBSCDE.


Now I got a hankerin' for some seafood...


Kind regards,
Z
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.