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



Okay.  I have looked at all the other replies to this note.  You guys have
all forgotten how to make a wheel with a stone axe.

Following is an easy way.  There are probably others that I haven't thought
of lately.  This technique requires the target job to agree to be probed.
There are other ways where this is not a requirement - see Peek/400.

When the target job starts, execute commands inside the target job.  first,
create a message queue in qgpl named q+job number.  Also in the target job,
assign a break message handler to the message queue.  The program to call
should look like this:

pgm (&mark)

dcl &mark *char 4
dcl &msg  *char 255

rcvmsg &mark &msg

call qcmdexec (&msg 255)

endpgm

If you try to compile this and it doesn't work, I won't be the least bit
surprised.  The last time I wrote this particular program was about 15 years
ago and the above is from memory.  If it turns out to work, it will be a
miracle on the same scale as the parting of the Red Sea.

Nevertheless, in order to get the DSPFD from the other job, send a break
message to qgpl/q+jobname.  The message should contain "dspfd qtemp/filename
... *print".  The spool file shows up in the target job.

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-----Original Message-----
From: owner-midrange-l@MIDRANGE.COM
[mailto:owner-midrange-l@MIDRANGE.COM]On Behalf Of Graves, Chuck
Sent: Monday, September 25, 2000 2:50 PM
To: 'MIDRANGE-L@midrange.com'
Subject: Another job's QTEMP


I think there's a way...I just don't know it...
How can I look at another jobs QTEMP...specifically to do a DSPFD of a file
in that job's QTEMP library

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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 subscribe to this list send email to MIDRANGE-L-SUB@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-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.