Creating a subsystem

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.