Re: Creating a subsystem

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.

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.

>>> Zak_Metz@xxxxxx 04/04/03 07:41AM >>>
Happy Friday, list!

I'm working on the packaging of a software application. This app is
the
server side of a client/server system. It is a single, multi-threaded,
never-ending program that will be submitting secondary long-running,
resource-intensive jobs.

My initial reaction is that we should create our own subsystem to run
everything in. However, I don't really know how clients feel about
that.

Then it occurred to me that perhaps, since the NEP is a communication
job, it belongs in QCMN, QSERVER, QSYSWRK or some other existing
subsystem. I don't know how I would decide which, though. I would risk
losing my AJEs when the client upgrades. I'm not sure that adding an
AJE
to a standard SBS is a good thing to do. Perhaps the client won't want
to start the server automatically.

Then there's still the issue of the jobs that the NEP will be
submitting. Currently our software defaults to submitting to whatever
JOBQ is the default in the current user's USRPRF's JOBD, but this
isn't
an interactive application and will be running under our own
USRPRF/JOBD. It would give the client a lot of control if this were a
standalone subsystem, but it would also increase the complexity of
their
system.

How would you expect this sort of application to behave if you were
installing it on your system? What options would you want? What would
tick you off?

Thank you for helping me do this right the first time!

Zak Metz
Group 1 Software
iSeries Platform Specialist
IBM Certified Specialist - IBM eServer iSeries Technical Solutions
Implementer
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.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.