× 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: What job is using a device
  • From: bdietz@xxxxxx
  • Date: Fri, 20 Feb 1998 18:34:54 -0500

You can use the API QDCRCFGS.
It uses the device name and returnes a verity of information including the
job information you need

Bryan  Dietz
3X Corp.





mcrump@ballfoster.com on 02/20/98 03:06:45 PM

Please respond to MIDRANGE-L@midrange.com

To:   Midrange-L@midrange.com
cc:    (bcc: Bryan Dietz/Columbus/3X Corp)
Subject:  What job is using a device




I may have slipped and bumped my head but
I am trying to come up with an easy to get the
information (Job name,user, and number) of the
job using a specific device.  By easy I mean easy
programming and from a resource standpoint.
I have situations where I may have a device failure
and the program is attempting to recover on it's own.
When it doesn't I will get a job that loops.  While
pursuing the issue of why it won't recover I want to
be able to control the looping job - specifically I want
to end the job.
I will know the name of the device in question, but not
necessarily the job name.  Other than working with
locks (I'm concerned there may not be any..), what is
the easiest way to say I have device DSPMINE and want
to end whatever job is xxxxxx/YYYYYYYYYY/DSPMINE?
Most things I can think of will create a generic list which I
could process against.  I want to avoid doing this because
I want to get at it quick - I'd rather only have one job name
to process instead of checking multiple jobs.
I'm pretty sure there is a way and I'm sure I've read or looked
at it before but for the life of me can't remember (must be
V4R2 pricing shock).
Sorry for the rambling but does anyone have any suggestions?
Michael Crump
Technical Project Leader

(from

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---






+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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