RE: Accessing Another Job's QTEMP

My DUMPQTEMP works fine for jobs at a MSGW status. Have you checked the failing joblog and compared it against a successful completion?



-----Original Message-----
From: dlclark@xxxxxxxxxxxxxxxx [mailto:dlclark@xxxxxxxxxxxxxxxx]
Sent: Thursday, May 10, 2018 2:07 PM
To: Midrange-L <midrange-l@xxxxxxxxxxxx>
Subject: Accessing Another Job's QTEMP

I followed the thread on this subject with interest. We often have a need for this when a job goes to a MSGW. So, I tried the STRSRVJOB/TRCJOB method and it appears not to work if the other job is in a wait state. Meaning, I set an RDi service entry point for both the command CL and the exit program CL and the exit program never gets invoked. If that is so, then what real case use is this method?

CALL PGM(QSNDDTAQ) PARM(&SNDDTAQ 'QGPL' &CMDLEN +
&CMDSTR)

STRSRVJOB JOB(&JOBNUMB/&JOBUSER/&JOBNAME)
TRCJOB SET(*ON) MAXSTG(1024) EXITPGM(&EXITPGM)
CALL PGM(QRCVDTAQ) PARM(&RCVDTAQ 'QGPL' &LEN &MSG +
&WAIT)
DLYJOB DLY(2)
TRCJOB SET(*END) MAXSTG(1024)
ENDSRVJOB


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331



*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.
*********************************************************************************************