• Subject: RE: File created in Qtemp
  • From: Tim McCarthy <TimM@xxxxxxxxxxxxxxxxxx>
  • Date: Mon, 26 Jul 1999 23:41:07 -0400

If it was running interactively it wouldn't be another job! The
suggestions posted mostly cited STRSRVJOB (which won't let you look at
the remote jobs QTEMP) and the obvious program changes. But there are
some alternatives - how badly do you need to do this? One solution that
I posted was to change the routing entry in the subsystem the job will
run in to create a Trojan horse. The routing entry will call a CL
program that you write that parses out the request data and uses QCMDEXC
to run the requested function. QTEMP is thus open to the shell job. A
more difficult option is to write an MI program to tap into the other
jobs QTEMP objects but this won't work if you're at security level 40 or
above. Finally you should also be able to use a combination of DMPSYSOBJ
and STRSST to find and dump the QTEMP object to say a spool file. I have
to admit I've never dumped a file this way.

> -----Original Message-----
> From: Roger Boucher [SMTP:RBoucher@stanpac.com]
> Sent: Monday, July 26, 1999 2:18 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: File created in Qtemp
> 
> Is it running interactively?  If in batch, can you run it
> interactively?  Do
> you know debug?  If the answer to all these is yes then you can run it
> and
> put it in debug and when it stops you can access a command line and
> take a
> look at the file.  If it is running in batch I believe the final
> answer was
> that you would have to modify the program to copy the file somewhere
> you can
> look at it later.
> 
> 
> -----Original Message-----
> From: Chanh Le [mailto:Chanh_Le@countrywide.com]
> Sent: Monday, July 26, 1999 11:37 AM
> To: MIDRANGE-L@midrange.com
> Subject: File created in Qtemp
> 
> 
> Could you show how to look at a file created in QTEMP by another job.
> I
> think there was a discussion about this topic, but I forgot.
> 
> 
> 
> Thanks.
> 
> 
> +---
> | 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
> +---
+---
| 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 thread ...


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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].