Re: Determine the PDS a job was submitted from?

This might be OTT, but I have used the following "JS" Clist edit macro since the 1980's when submitting jobs to record when and from where (and by whom) a job was submitted: ISREDIT MACRO CONTROL: + CONTROL MAIN END(ENDO) ISREDIT (DSN) = DATASET ISREDIT (MEM) = MEMBER IF () ¬= THEN SET DSN

Re: Determine the PDS a job was submitted from?

If the job came through the INTRDR from TSO the exit will see it, if it comes via a scheduling product, then you already know where the JCL came from:) JOB scheduling packages aren't all that smart about where they get the JCL from. Plus I would imagine that every one of them has the

Re: Determine the PDS a job was submitted from?

Hi Folks, You can look at the code in IKJEFF10 which is in File 863 of the CBT collection www.cbttape.org and see how it gets its results. Below is the File 001 (doc) entry for CBT File 863. Use it in good health... Sincerely, Sam FILE 863 is from Jim Callihan and

Re: Determine the PDS a job was submitted from?

That would work for TSO Submitted work. But it would not work for jobs submitted by other means, like INTRDR. Hence, the need for scheduling software. It manages the submission from its files. But not from jobs that are not submitted by it. However, there is information in SMF Type42 on PDS

Re: Determine the PDS a job was submitted from?

I didn't see this whole thread, so I don't know how much of this applies (to anything), but wouldn't the TSO submit exit be where you could check to see where the data being submitted came from and put it out as a SYSLOG entry or insert a comment into the submitted JCL? You can do that from

Re: Determine the PDS a job was submitted from?

Among the tasks that I am now responsible for maintaining, there is a suite of programs written in Assembler that manufacture jobs, by building the text and writing them directly to the internal reader. There is never any PDS member or source involve.

Re: Determine the PDS a job was submitted from?

Charles, We generate JCL from SAS programs on Windows and write them direct to JES with FTP. filename jesftp0ftp '.submit' USER="" host="" PASS="" rcmd='site file=jes' passive; The sample is from within a SAS macro, so

Re: Determine the PDS a job was submitted from?

Yes, that's the standard way of doing it in Zeke - you define the schedule time and/or the conditions that must be satisfied and also the member name and library that is the source of the job. However, Zeke also allows for dynamically created schedule queue records (SQRs), whereby Zeke

Re: Determine the PDS a job was submitted from?

Caveat: daily digestion implies response delays... As was discussed extensively on IBM-Main before (Jan, Feb?), for all other methods besides 'automation' submission, you're outta luck. 'specially in a sysplex environment where conversion and xeq'tion could occur in different locations. For

Re: Determine the PDS a job was submitted from?

Don't know. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: 07 June, 2016 16:36 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Determine the PDS a job was submitted from? On 2016-06-07, at 08:18, Vernooij, CP

Re: Determine the PDS a job was submitted from?

On 2016-06-07, at 08:18, Vernooij, CP (ITOPT1) - KLM wrote: > With IOF you can select a job that has run, edit the input JCL and submit it > again. This job is exactly the job from your production JCL library, but > doesn't come from there. > Does it preserve RECFM and LRECL of SYSINs? --

Re: Determine the PDS a job was submitted from?

With IOF you can select a job that has run, edit the input JCL and submit it again. This job is exactly the job from your production JCL library, but doesn't come from there. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of

Re: Determine the PDS a job was submitted from?

On Tue, 7 Jun 2016 08:26:41 -0500, Tom Marchant wrote: >On Mon, 6 Jun 2016 16:08:30 -0500, Paul Gilmartin wrote: > >>a programmer might >>have typed JCL from scratch in an editor then SUBMIT on the command >>line. > >I sometimes do that from within SDSF using line command SJ. >And I frequently

Re: Determine the PDS a job was submitted from?

On Tue, 7 Jun 2016 09:21:40 -0400, Charles Mills wrote: >> Or from a Windows file, if you're so afflicted. > >Really? Without first copying it to a mainframe file or dataset? > Sure.: ftp zos user password quote site filetype=JES put JCL somename quit (Haven't actually

Re: Determine the PDS a job was submitted from?

On Tue, Jun 7, 2016 at 8:46 AM, Charles Mills wrote: > Ah! You're right. But the job goes off into never-never land. I have only > used GET which submits a local JCL (on the FTP server mainframe) file or > dataset and retrieves the SYSOUT back to the submitting FTP client. >

Re: Determine the PDS a job was submitted from?

Ah! You're right. But the job goes off into never-never land. I have only used GET which submits a local JCL (on the FTP server mainframe) file or dataset and retrieves the SYSOUT back to the submitting FTP client. BTW, I *think* you mean quote SITE filetype=jes Charles -Original

Re: Determine the PDS a job was submitted from?

On Tue, Jun 7, 2016 at 8:21 AM, Charles Mills wrote: > > Or from a Windows file, if you're so afflicted. > > Really? Without first copying it to a mainframe file or dataset? > ​Sure. Use ftp ftp zos quote filetype=jes​ put myjob.jcl > > Charles > > -- The unfacts, did we

Re: Determine the PDS a job was submitted from?

> Or from a Windows file, if you're so afflicted. Really? Without first copying it to a mainframe file or dataset? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, June 06, 2016 8:12 PM To:

Re: Determine the PDS a job was submitted from?

On Mon, 6 Jun 2016 16:08:30 -0500, Paul Gilmartin wrote: >a programmer might >have typed JCL from scratch in an editor then SUBMIT on the command >line. I sometimes do that from within SDSF using line command SJ. And I frequently resubmit a job the same way. -- Tom Marchant

Re: Determine the PDS a job was submitted from?

Yes... I recall some discussion awhile back with the consensus being a “likely no”. I wanted to make sure I was not missing something. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: Determine the PDS a job was submitted from?

We discussed this a few months ago. General answer: no. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Ten Eyck Sent: 06 June, 2016 21:09 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Determine the PDS a job was submitted from?

Re: Determine the PDS a job was submitted from?

On Mon, 6 Jun 2016 17:30:07 -0400, Charles Mills wrote: >Or copied to INTRDR from a non-PDS or (gasp!) a UNIX file. > I do that regularly. ISPF 3.17; View with tailoring Initial Macro; Submit; Cancel. I rarely SAVE; I make systematic changes to the family of jobs (most often DSN HLQ) by

Re: Determine the PDS a job was submitted from?

Did ZEKE actually submit the job or did it submit a "launcher" job that then submitted the one you are really interested in? I have never used ZEKE but surely it did not just up and decide to submit a job. Some form of input to ZEKE must have specified "when this condition occurs then "

Re: Determine the PDS a job was submitted from?

I think tracking a job back to a JCL source file is hopeless. Besides the submit methods mentioned, we get jobs submitted via NDM (Connect Direct) or FTP/REXEC. You could insist on some kind of doc format, but ad hoc submissions would be an endless guessing game. I don't think anyone would try

Re: Determine the PDS a job was submitted from?

Or copied to INTRDR from a non-PDS or (gasp!) a UNIX file. IIRC FTP will submit a job from either of those sources also. I am no JES or job exit expert. Could an exit limit INTRDR to specific sources or stick a PDS name somewhere? A member name would fit in SMF30UIF. Charles -Original

Re: Determine the PDS a job was submitted from?

On Mon, 6 Jun 2016 14:08:33 -0500, Peter Ten Eyck wrote: >Does anyone have suggestions on how to determine the PDS a job was submitted >from? In this case the ZEKE scheduler was used. I would interested in comments >with and without scheduler. > Without scheduler? Not a chance. In the

Determine the PDS a job was submitted from?

Does anyone have suggestions on how to determine the PDS a job was submitted from? In this case the ZEKE scheduler was used. I would interested in comments with and without scheduler. -- For IBM-MAIN subscribe / signoff /