X-no-Archive:yes
Jeff Vance and Bob Schlosser discuss what ALTPROC will and will not do
versus what is documented, and  John Hornberger states that this should be
run from an OP or SM user. There is another wrinkle to this.

If I understand HELP ALTPROC OPERATION correctly ("The USER option, which is
the default, alters
only processes matching the user's name"), OP and SM are not required. One
would want a pair of jobs that runs under the MGR.NSD user (the same as the
JOBPAK job), and issues an ALTPROC JOB=MGR.NSD;PRI=pri. The effect will be
limited in its scope to jobs running under the MGR.NSD id, because of the
specific JOB argument. It would seem from HELP that one could use JOB=@J,
and that would just affect jobs under the current user, except for one
important detail: MGR.NSD has OP, so it can affect ALL jobs or sessions.
Jeff's recommendation of testing with SHOWPROC bears this out; SHOWPROC
JOB=J@ shows all procs in all jobs.

Other options would include ALTPROC just the executable, JP02SXL.JPAK. Or,
since this job is normally started from your SYSSTART routines, the job
number itself should be the same, if you don't mind living just a little
dangerously.

Also, instead of creating jobs, you could create single-line XEQs, and run
them from JobPak, configured in CONFIGIX.JPAK as job-specific XEQs tied to
the jobs at the beginning and end of your either your online or your batch
processing windows.

Greg Stigers
http://www.cgiusa.com