I've always set it at the outq level.

That environment variable is a new one to me. Interesting though.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
Phn: (612) 315-1745
------------------------------

message: 6
date: Wed, 13 Nov 2019 16:53:15 +0000
from: "(WalzCraft) Jerry Forss" <JForss@xxxxxxxxxxxxx>
subject: RE: Spool Management - QEZJOBLOG

It has *NONE.

I thought by adding the environment variable all spool files would be added ADDENVVAR ENVVAR(QIBM_NOTIFY_CRTSPLF) VALUE('*DTAQ Lib/DataQ') LEVEL(*SYS)

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rich Loeber
Sent: Wednesday, November 13, 2019 10:47 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Spool Management - QEZJOBLOG

Jerry,

When you do a WRKOUTQ for QEZJOBLOG and press F21, what do you see specified for the data queue for the output queue?

Rich Loeber - @richloeber
Kisco Information Systems
http://www.kisco.com
------------------------------------------------------------------------

On 11/13/2019 11:27 AM, (WalzCraft) Jerry Forss wrote:
Hi All,

I created a spool file management system that manages all spool files created on the system.
It archives to the IFS, Emails and prints when wanted.

Works great.

I added the environment variable that adds to my DtaQ when a spool file is created.
However, when a job log is created in QEZJOBLOG or QEZDEBUG, it does not add it to my DtaQ.

I would like to eliminate the process where I interrogate the QEZJOBLOG outq and add entries to my DtaQ every few minutes.

What am I missing?



Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change specifications without notice.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 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.