RE: WRKACTJOB annoyance -- MIDRANGE-L

× 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.

Subject: RE: WRKACTJOB annoyance
From: "Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>
Date: Mon, 1 Apr 2002 12:08:11 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Mike,

Short of renaming all of your subsystems so that QBATCH comes first
alphabetically :), would the WRKSBSJOB (Work with subsystem jobs)
command do what you want?  It provides similar output to WRKACTJOB, but
only for one subsystem.

WRKSBSJOB QBATCH

Andy

> Subject: WRKACTJOB annoyance
>
> One thing I don't like about WRKACTJOB is that I can't position it so
I
> can
> see what is all running in QBATCH. Is there a better way to view this?
>
> Mike

As an Amazon Associate we earn from qualifying purchases.

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.