Re: Determine the PDS a job was submitted from?

[CM Poncelet]

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 = (())
 SET DATE = +
 (4:6,)(1:3,)(7:8,)
 SET TIME = 
 ERROR GOTO EXIT
 ISREDIT FIND P'//@' 1 FIRST
 ERROR DO
   ISREDIT FIND P'//=' 1 LAST
   GOTO CONTINUE
   ENDO
 ISREDIT FIND P'//¬' 1 NEXT
CONTINUE: +
 ISREDIT (ROW) = CURSOR
 ERROR OFF
 ISREDIT LINE_BEFORE  = '//* '
 ISREDIT LINE_BEFORE  = +
 '(//* USER   :  , AT  ON )'
 ISREDIT LINE_BEFORE  = "//* DATASET: '' "
 ISREDIT LINE_BEFORE  = '//* '
 ISREDIT SUBMIT
 ISREDIT CURSOR = 1
 ISREDIT DELETE  (+3)
 ISREDIT LOCATE .ZLAST
 ISREDIT LOCATE 0
EXIT: +
 EXIT CODE(1)

I had no problem tracking jobs submitted by Control-M or ZEKE (or 
whatever else), either.


Just my ha'penny worth.

CP


Brian Westerman wrote:


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 capability of logging that 
data either via a parm or via an exit.  If the job were submitted from another 
batch job, you're going to see that in the syslog already.  If it comes via 
FTP, then you can't possibly care where the JCL came from because it's not 
anywhere you can get to and all that matters is that you know who sent it to 
you and when, it would be their job to know where they sent it from.  There 
just aren't that many ways to get jobs into the system that don't have exits to 
use to keep thing under observation.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


 



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Brian Westerman]

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 capability of logging that 
data either via a parm or via an exit.  If the job were submitted from another 
batch job, you're going to see that in the syslog already.  If it comes via 
FTP, then you can't possibly care where the JCL came from because it's not 
anywhere you can get to and all that matters is that you know who sent it to 
you and when, it would be their job to know where they sent it from.  There 
just aren't that many ways to get jobs into the system that don't have exits to 
use to keep thing under observation.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Sam Golob]

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 contains an IKJEFF10 TSO
 SUBMIT exit that originally came from PRC's CBT tape
 File 369.  It stopped working from z/OS 1.12 to 1.13
 because of a change in control blocks, and Jim found
 a different way to obtain the information, which,
 by the way, also works on old systems back to OS/390
 1.3 (the first Y2K compliant MVS release).  So (I
 think) you can use this version of the exit on older
 systems too.  (Works on z/OS 2.2 also.)

 The exit inserts a comment line in the JCL source,
 telling you where the JCL in the job came from.

 For example:

 //*ISPF EDIT OF SBGOLOB.B.ASM(IKJEFF1$)
 or
 //*JCL: SBGOLOB SUBMIT   'SBGOLOB.CBT484.FILE863(IKJEFF1$)'

 email:  james.r.calli...@salliemae.com

 email:  sbgo...@cbttape.org  or
 sbgo...@attglobal.net

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Lizette Koehler]

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 members.  May be that could 
be helpful if you knew the time/date/LPAR the job was submitted.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Brian Westerman
> Sent: Wednesday, June 08, 2016 7:59 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: 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 Com-PLETE and
> CICS as well.  When I was at PRC in Virginia many years ago, we had a COM-
> PLETE, CICS (although the program to submit was home grown as well) and a TSO
> exit (IKJEFF10 I believe) that put out a hardcopy message that was something
> like "submitted by name, from DSN at Terminal" where the DSN would sometimes
> be only the PDS name, not the actual member.  I remember fixing that problem,
> but can't remember what caused it.  I can't believe that TSO has changed that
> much to where it's no longer possible to do that.
> 
> Brian
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Brian Westerman]

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 Com-PLETE and 
CICS as well.  When I was at PRC in Virginia many years ago, we had a 
COM-PLETE, CICS (although the program to submit was home grown as well) and a 
TSO exit (IKJEFF10 I believe) that put out a hardcopy message that was 
something like "submitted by name, from DSN at Terminal" where the DSN would 
sometimes be only the PDS name, not the actual member.  I remember fixing that 
problem, but can't remember what caused it.  I can't believe that TSO has 
changed that much to where it's no longer possible to do that.

Brian

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Zahir Hemini]

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.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Ron Hawkins]

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 ,  and  are replaced 
with the UID, IP Addr, and password as required.

Thought this may be useful for you the SAS users out there.

Ron


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Tuesday, June 7, 2016 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] 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: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 editing the tailoring Macro.

>IIRC FTP will submit a job from either of those sources also.
> 
Or from a Windows file, if you're so afflicted.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Greg Shirey]

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 "captures" the 
JCL being submitted and manages it.   Also, given the proper authorities, you 
can modify an SQR to read a different PDS member, run the job, then delete the 
SQR, leaving no clue behind.  

Admittedly, the last two scenarios are rare, and perhaps not noteworthy for 
this discussion.

Regards,
Greg Shirey
Ben E. Keith Company 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of retired mainframer
Sent: Monday, June 06, 2016 5:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 "  ZEKE should have some kind of report that allows you to see 
the active directives.  The relevant directive must tell ZEKE where to find the 
job.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Neil Duffee]

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 'automated' submission, I suspect most products have an exit that will 
insert whatever text you desire into the job such as the JCL source.  Our ESP 
set-up has the following text:

//* THIS IS JOB SMSSGRP.ARCMAINT
//*
//* SUBMITTED BY ESP AT 09.21.50 ON TUESDAY JUNE 7TH, 2016
//* SYSTEM , SUBSYSTEM ESP
//* REQUESTED BY EVENT OPS.ARCHIVE_DAILY
//* JCL COPIED TO SYSTEMS.ESP.JCLCPY
//* JCL FROM SYSTEMS.STGADM.REPORTS.CNTL(SGRPT01)
//* JOB IS IN APPLICATION ARCMAINT, GENERATION 3399

>  signature = 8 lines follows  <
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585  fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
“How *do* you plan for something like that?”  Guardian Bob, Reboot
“For every action, there is an equal and opposite criticism.”
“Systems Programming: Guilty, until proven innocent”  John Norgauer 2004
"Schrodinger's backup: The condition of any backup is unknown until a restore 
is attempted."  John McKown 2015

-Original Message-
From: retired mainframer [mailto:ret..-ma...@q...com] 
Sent: June 6, 2016 18:06
Subject: 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?  [snip]

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Peter Ten Eyck
> Sent: Monday, June 06, 2016 12:09 PM
> Subject: 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 / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Vernooij, CP (ITOPT1) - KLM]

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 (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?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Paul Gilmartin]

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?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Vernooij, CP (ITOPT1) - KLM]

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 Paul Gilmartin
Sent: 07 June, 2016 16:08
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 resubmit a job the same way.
> 
Repair typo; SUBmit; CANcel.

Too often I forget that quietly truncates SYSINs to 80 columns.  That ought
to be regarded as a data integrity flaw.  At least it should issue a warning
and require confirmation.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Paul Gilmartin]

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 resubmit a job the same way.
> 
Repair typo; SUBmit; CANcel.

Too often I forget that quietly truncates SYSINs to 80 columns.  That ought
to be regarded as a data integrity flaw.  At least it should issue a warning
and require confirmation.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Paul Gilmartin]

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 tried it from Windows; from OS X, Solaris, or Linux it works.)
"quote site" may not be obvious on a GUI client.
Can also specify JESRECFM and JESLRECL.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[John McKown]

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

​never-never land? When I do it, it goes into the SPOOL [grin/].​ I can
monitor it using ftp's "ls" command. Then get the output (if in HELD) via
the "get" command. I don't actually _do_ this because I have installed
Dovetailed Technologies' Co:Z series of (freely licensed) products. There
is a "todsn" command which can be used to submit a job. "lsjes" to list
jobs in the SPOOL. And, lastly, "fromdsn" to fetch the output. Much easier
to use in scripts (Oh, I run a Linux desktop and use it instead of my
Windows desktop).



>
> BTW, I *think* you mean quote SITE filetype=jes
>

​You're right. My mistake.​


>
> Charles
>
>
-- 
The unfacts, did we have them, are too imprecisely few to warrant our
certitude.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Charles Mills]

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 Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John McKown
Sent: Tuesday, June 07, 2016 9:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[John McKown]

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 have them, are too imprecisely few to warrant our
certitude.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Charles Mills]

> 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: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 editing the tailoring Macro.

>IIRC FTP will submit a job from either of those sources also.
> 
Or from a Windows file, if you're so afflicted.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Tom Marchant]

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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Peter Ten Eyck]

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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Vernooij, CP (ITOPT1) - KLM]

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?

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 / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Paul Gilmartin]

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 editing the tailoring Macro.

>IIRC FTP will submit a job from either of those sources also.
> 
Or from a Windows file, if you're so afflicted.

>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.
>
It's doubtful.  Probably too many jobs and started tasks depend on submitting
other jobs directly to INTRDR.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[retired mainframer]

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 "  ZEKE should have some kind of report that allows you to see 
the active directives.  The relevant directive must tell ZEKE where to find the 
job.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Ten Eyck
> Sent: Monday, June 06, 2016 12:09 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: 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 / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Jesse 1 Robinson]

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 to circumvent 
a standard; there would just be too many omissions in practice. 

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Monday, June 06, 2016 2:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):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 Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, June 06, 2016 5:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 extreme, a programmer might have 
typed JCL from scratch in an editor then SUBMIT on the command line.

Is it possible to prohibit all use of INTRDR except by an authorized scheduler? 
 (Is it practical?)

-- gil


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Charles Mills]

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 Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, June 06, 2016 5:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 extreme, a programmer might have 
typed JCL from scratch in an editor then SUBMIT on the command line.

Is it possible to prohibit all use of INTRDR except by an authorized scheduler? 
 (Is it practical?)

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Determine the PDS a job was submitted from?

[Paul Gilmartin]

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 extreme, a programmer might
have typed JCL from scratch in an editor then SUBMIT on the command
line.

Is it possible to prohibit all use of INTRDR except by an authorized
scheduler?  (Is it practical?)

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN