Not exactly, Alan.
It was project where I realised*parallel data processing.
Usualy I use SBMJOB and data exchange through dataquee.
I developed project with spawn, but had to refuse spawn in future. Because
of our admins they require to run such process in qbatch.
*
Regards, Alex.
*
*
26.05.2016, 17:16, "Alan Campin" <alan0307d@xxxxxxxxx>:
Alex, normally you would not be using spawn to run jobs in QBATCH. Spawn
is
used to connect to pre-start jobs.
You define a subsystem with pre-start jobs and then you use Spawn to
take
over one of these jobs. This is not something that you would want to do
in
QBATCH.
Having said that I have an open source project that I have been working
on.
that consists of a socket server spawning socket worker jobs. One part
of
that project is a service program XVSPWN that wraps up the spawn
interface
to make it easy to use.
Could I know what you are planning to use the spawn api for. It sounds
like
you might be looking for pre-start jobs.
On Thu, May 26, 2016 at 3:34 AM, Scott Klement
<[1]rpg400-l@xxxxxxxxxxxxxxxx>
wrote:
*Hello Alex,
*On 5/26/2016 2:09 AM, [2]amunra@xxxxxx wrote:
*****Speaking about not CL technique.
*****Does anybody use spawn() API to create a separate jobs?
*****Some years ago I tried to use it, but I didn't find the way to
create
*job
*****in different subsystems.
*****Does anyone know if there is a way to run jobs in QBATCH
subsystem?
*I use the spawn() API quite often. But it is important to understand
that
*it does not simply submit a new job -- instead it creates a "child
*process". Your job that calls spawn() is considered it's parent.
*Due to the nature of a child process, it must always be in the same
*subsystem as the parent job. So spawn() cannot cause a job to run in
a
*different subsystem.
*There are other things about child processes that are different,
too...
*for example, even after the child process ends, some memory from it
is kept
*around until the parent process calls wait or waitpid to get it's
exit
*status, etc. Also, child processes inherit a number of things from
the
*parent. For details on all these things, see the manual for spawn()
in the
*IBM Knowledge Center.
*For what you are doing, you might consider using the SBMJOB command
*instead of the spawn() API.
*-SK
*--
*This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L)
*mailing list
*To post a message email: [3]RPG400-L@xxxxxxxxxxxx
*To subscribe, unsubscribe, or change list options,
*visit: [4]
http://lists.midrange.com/mailman/listinfo/rpg400-l
*or email: [5]RPG400-L-request@xxxxxxxxxxxx
*Before posting, please take a moment to review the archives
*at [6]
http://archive.midrange.com/rpg400-l.
*Please contact [7]support@xxxxxxxxxxxx for any subscription related
*questions.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: [8]RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [9]
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [10]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [11]
http://archive.midrange.com/rpg400-l.
Please contact [12]support@xxxxxxxxxxxx for any subscription related
questions.
References
Visible links
1. mailto:rpg400-l@xxxxxxxxxxxxxxxx
2. mailto:amunra@xxxxxx
3. mailto:RPG400-L@xxxxxxxxxxxx
4.
http://lists.midrange.com/mailman/listinfo/rpg400-l
5. mailto:RPG400-L-request@xxxxxxxxxxxx
6.
http://archive.midrange.com/rpg400-l
7. mailto:support@xxxxxxxxxxxx
8. mailto:RPG400-L@xxxxxxxxxxxx
9.
http://lists.midrange.com/mailman/listinfo/rpg400-l
10. mailto:RPG400-L-request@xxxxxxxxxxxx
11.
http://archive.midrange.com/rpg400-l
12. mailto:support@xxxxxxxxxxxx
midrange.com
