× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Gary

I sent a post on this recently. Essentially, you can set an environment variable, in order to get the job names. (I also have job QP0ZSPWP.)

ADDENVVAR ENVVAR(QIBM_CHILD_JOB_SNDINQMSG) VALUE(2)

sends inquiry messages (CPAA980) with the qualified job name - you can get the job name, then respond with 'G' to keep going. This required 2 RCVMSG commands. The VALUE(2) is the number of messages sent, and I see 2 jobs.

You can try it interactively - execute this command first:

CHGMSGQ MSGQ(*usrprf) DLVRY(*BREAK)

More info on these environment variables is in the QShell docs under Programming->Shells in InfoCenter.

HTH

Vern

At 10:15 AM 6/19/2003 -0700, you wrote:
I'm running a CL in batch that uses job description JOBD1.  It specifies
LOG(4 0 *SECLVL) which is what I want for my batch job.

The CL executes two STRQSH commands every five minutes, each specifying a
command to execute in the CMD parameter.  Each of these STRQSH commands in
my CL spawns a QZSHSH job of type BATCHI.  The QZSHSH job inherits JOBD1
from by batch job running the CL containing the STRQSH commands.  This
results in joblogs hanging around for the numerous QZSHSH jobs that are
getting created.

Is there a way to prevent these job logs from being retained or to cause the
shell command to be executed from a thread inside my batch job, preventing
the creation of the QZSHSH job in the first place?

We are on v5r1.

Many thanks in advance,
Gary



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.