Re: Running a command in another job

Dave, Dieter

Thanks for the ideas. I'll mull them over and try to decide which approach to take.

Dean

On 2/22/2018 10:42 AM, dlclark-hrkKUNNHk/rME/82e/C8hg@xxxxxxxxxxxxxxxx wrote:

"MIDRANGE-L" <midrange-l-bounces-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx> wrote on 02/22/2018
09:54:44 AM:

Thanks for the pointer. Mark Waterbury had responded to me offline
and sent me the code for this command. I'll probably use this approach.

Regarding having my web service receive a special parameter to shut
down, it can't reclaim the activation group because the program
itself specifies the activation group to run in. And since the
program is still running, the RCLACTGRP command fails. As far as
closing the program, *INLR works as long as *NOMAIN isn't specified

correct?


The way I handled this is to have a two-level process in its own
subsystem -- the job is a CL program that calls an RPG program to perform
the actual processing. The CL is in the default activation group and the
RPG is in a named activation group.

I coded a call to %SHTDN in the RPG program so that it would
self-end on any shutdown request (job, subsystem, or system). Then, the
CL program determines which type of shutdown was requested and, if "only"
a job shutdown then RCLACTGRP is issued for the RPG's named activation
group and loop back to call the RPG program again. The other shutdown
types would cause the CL program to self-end and, therefore, the whole
job.

This way another program I wrote queries the system to find the
job in question, by name, and sends a *CTRLD shutdown request to that job.
Voila!


Sincerely,

Dave Clark

______________________________________________________________________
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.