Re: RUNJOBCMD

If I follow correctly and you are using the RUNJOBCMD to get the job running, this seems like a band-aid solution.
I believe you need to find a "root cause" solution.
you seem to have a handle on the work management steps for this job, so it should be easy to make a permanent fix.

Bryan

Gad Miron wrote on 3/21/2023 8:17 AM:

Thanks dieter, Jim, Rob

I cheated a little, Actually it was not a batch job but a job evoked by
a MagicXPI IBMi agent (EASYCOM MAGIC400) called from an external
MagicXPI process.

This nvoked job uses a special user profile that automatically adds (INLPGM)
all required libraries to the Job's *LIBL

It has been working fine for the last 10 years but this time, the job was
invoked
right after (or perhaps during the last stages of) an IPL and the Library
list was not set correctly.

So a pinpoint operation , adding a missing library seemed to be the right
way.

What say you?

TIA
Gad

1. RUNJOBCMD (Gad Miron)
2. Re: RUNJOBCMD (Dsternb)
3. Re: RUNJOBCMD (Jim Oberholtzer)
4. Re: IFS Directory Authority (Rob Berendt)
5. Re: RUNJOBCMD (Rob Berendt)
6. Shared output queues (Michael Quigley)


----------------------------------------------------------------------

message: 1
date: Tue, 21 Mar 2023 07:55:49 +0200
from: Gad Miron <gadmiron@xxxxxxxxx>
subject: RUNJOBCMD

Hello All

Lately a Batch job "bombed" because of a library list issue

Googling for a solution I ran across RUNJOBCMD CMD
but could not download code or explanations
Nor could I find whether the A/M CMD is 7.4 tolerant.

Does anyone know?

TIA
Gad