Re: Set JobId on Submit..
And if you populate your RACF TSO segment you can also affect the outcome of submitting something without a JOBCARD. On Thu, 19 Jun 2008 13:27:31 EDT, Ed Finnell <[EMAIL PROTECTED]> wrote: > >In a message dated 6/19/2008 11:32:27 A.M. Central Daylight Time, >[EMAIL PROTECTED] writes: > >Wait a minute, guys. Isn't there something in ISPF SUBMIT that, if your JCL >member does not contain a jobcard, the "default jobcard" stored in ISPF >Settings somewhere is automatically inserted on top of your JCL? I seem to > >>> >There's that, there's also the native TSO/E behavior documented in the >user's guide. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
On Thu, 19 Jun 2008 10:05:26 -0400, Jerry Fuchs <[EMAIL PROTECTED]> wrote: >The IKJEFF10 TSO submit exit would be used to change the job name to the >TSO user's ID. > Might I guess from the prefix that this applies only to the TSO SUBMIT command, and not to jobs submitted otherwise, such as by FTP? I believe I have seen earlier discussion in this list that there is an exit for the reader (or similar) that properly processes all submitted jobs. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
In a message dated 6/19/2008 11:32:27 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: Wait a minute, guys. Isn't there something in ISPF SUBMIT that, if your JCL member does not contain a jobcard, the "default jobcard" stored in ISPF Settings somewhere is automatically inserted on top of your JCL? I seem to >> There's that, there's also the native TSO/E behavior documented in the user's guide. If the job name consists of only your user ID, the system prompts you for one or more characters to complete the job name. This allows you to change job names without re-editing the data. For example, you may submit the same job several times, and supply a different character for the job name each time you are prompted. If the first JCL statement of your data set is not a JOB statement, the system generates the following JOB statement when you submit the job with the SUBMIT command: //userid JOB accounting info, // userid, ** JOB STATEMENT GENERATED BY SUBMIT ** // NOTIFY=userid, // MSGLEVEL=(1,1) TSO/E prompts you for a character to complete the job name. The job accounting information is the information specified by the user when logging on to the system. With no JOB statement in the data set, the security label assigned to the job (if your installation uses security labels) is the security label you are logged on at. **Gas prices getting you down? Search AOL Autos for fuel-efficient used cars. (http://autos.aol.com/used?ncid=aolaut000507) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
Wait a minute, guys. Isn't there something in ISPF SUBMIT that, if your JCL member does not contain a jobcard, the "default jobcard" stored in ISPF Settings somewhere is automatically inserted on top of your JCL? I seem to remember something like that ... Isn't that the solution to what ails you? Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Chase, John Sent: Thursday, June 19, 2008 09:00 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Set JobId on Submit.. > I'd really LOVE for IBM to allow something like: > > //&SYSUID.A JOB ...,NOTIFY=&SYSUID Now that could make a couple of USERMODs go away. :-) -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of McKown, John > > > -Original Message- > > From: IBM Mainframe Discussion List On Behalf Of Michael Knigge > > > > All, > > > > I'm currently working on a new system and I miss a great > feature(tm). > > On the systems I've been working so far the Jobid of a JCL was > > automatically set to my UserId when I've submitted the Job. > > > > i. e.: > > > > //ABCXYZPQ JOB 999830010T,'SPUFI',CLASS=A,NOTIFY=&SYSUID, > > // MSGCLASS=H,MSGLEVEL=(1,1),&SYSUID > > > > Here "ABCXYZP" was replace with my userid FOOBAA0, resulting to the > > jobname FOOBAA0Q... > > > > could anyone tell what I have to do to get this great feture back? > > That was likely an "in house" function. There is no such > function as distributed by IBM. If you are talking about > submitting from TSO, then I'd bet it was done via the > IKJEFF10 submit exit. Basically, you're likely out of luck. > > I'd really LOVE for IBM to allow something like: > > //&SYSUID.A JOB ...,NOTIFY=&SYSUID Now that could make a couple of USERMODs go away. :-) -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
On Thu, 19 Jun 2008 10:36:42 -0500, John P Kalinich <[EMAIL PROTECTED]> wrote: >Mark Zelden of the IBM Mainframe Discussion List >wrote on 06/19/2008 10:13:49 AM: > >> The best way to do that would be to build the entire >> job card based on site specific standards instead of trying to account >for >> all the different combinations of userid length and where the "JOB" is >> placed. >> > >See the JC macro on CBT file 078. > >Regards, >John K > Didn't look, but that is what I was referring to. Most shops I've been at have one of these (at least the ones that don't use submit exits). JC seems to be a common name. Go Figure. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
Mark Zelden of the IBM Mainframe Discussion List wrote on 06/19/2008 10:13:49 AM: > The best way to do that would be to build the entire > job card based on site specific standards instead of trying to account for > all the different combinations of userid length and where the "JOB" is > placed. > See the JC macro on CBT file 078. Regards, John K -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
Paul Gilmartin wrote: On Thu, 19 Jun 2008 15:55:29 +0200, Michael Knigge wrote: All, I'm currently working on a new system and I miss a great feature(tm). On the systems I've been working so far the Jobid of a JCL was automatically set to my UserId when I've submitted the Job. could anyone tell what I have to do to get this great feture back? I couldn't resist trying the obvious, if only to verify that I got the expected (WAD) failure: 1 //&SYSUID JOB &SYSUID,'Paul Gilmartin', JOB02946 // MSGLEVEL=(1,1),REGION=0M,MSGCLASS=R //* IEFC653I SUBSTITUTION JCL - SPPG,'Paul Gilmartin',MSGLEVEL=(1,1),REGION=0M,MSGCLASS=R ... STMT NO. MESSAGE 1 IEFC662I INVALID LABEL Why, why, why?! I hate JCL! From the JCL reference, chapter 5, section on JCL symbols, the rules include: 4. Do not use symbols to change the identifier field, name field, or operation field of a JCL statement So you can't use symbols in the name field of a JCL statement; I admit it would be nice, but you can't. Lobby for change. Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com z/OS Application development made easier * Our classes include + How things work + Programming examples with realistic applications + Starter / skeleton code + Complete working programs + Useful utilities and subroutines + Tips and techniques ==> Check out the Trainer's Friend Store to purchase z/OS <== ==> application developer toolkits. Sample code in four<== ==> programming languages, JCL to Assemble or compile, <== ==> bind and test. <== ==> http://www.trainersfriend.com/TTFStore/index.html<== -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
On Thu, 19 Jun 2008 09:44:54 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote:
>On Thu, 19 Jun 2008 09:31:13 -0500, Mark Zelden wrote:
>>
>>/* REXX */
>>/* */
>>/* AUTHOR: Mark Zelden */
>>/* */
>>Address ISREDIT
>>"MACRO"
>>uid= sysvar('SYSUID')
>>ulen = Length(uid)
>>"(data1) = LINE 1"
>>data1 = Overlay(uid,data1,3,ulen)
>>"LINE 1= (data1)"
>>"SUBMIT"
>>
>But be careful of the initial formatting of the JOB statement. If it
>is initially the very legal:
>
>//NAME JOB account-stuff
>
>won't the above result in the not very legal:
>
>//ZELDENOB account-stuff
>
>... ? (I have a tester's mentality.)
>
My code was just a 60 second throw together sample of what could be done
based on the OP. It wasn't meant to be "works in all environments all
the time" code. The best way to do that would be to build the entire
job card based on site specific standards instead of trying to account for
all the different combinations of userid length and where the "JOB" is
placed.
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
On Thu, 19 Jun 2008 15:55:29 +0200, Michael Knigge wrote: >All, > >I'm currently working on a new system and I miss a great feature(tm). On >the systems I've been working so far the Jobid of a JCL was >automatically set to my UserId when I've submitted the Job. > >could anyone tell what I have to do to get this great feture back? > I couldn't resist trying the obvious, if only to verify that I got the expected (WAD) failure: 1 //&SYSUID JOB &SYSUID,'Paul Gilmartin', JOB02946 // MSGLEVEL=(1,1),REGION=0M,MSGCLASS=R //* IEFC653I SUBSTITUTION JCL - SPPG,'Paul Gilmartin',MSGLEVEL=(1,1),REGION=0M,MSGCLASS=R ... STMT NO. MESSAGE 1 IEFC662I INVALID LABEL Why, why, why?! I hate JCL! -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
This is from the early 90's, published in TSO Times, courtesy yours truly. http://www.tsotimes.com/quicktips/sp95qt1.html Todd > -Original Message- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Knigge > Sent: Thursday, June 19, 2008 8:55 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Set JobId on Submit.. > > All, > > I'm currently working on a new system and I miss a great feature(tm). On > the systems I've been working so far the Jobid of a JCL was > automatically set to my UserId when I've submitted the Job. > > i. e.: > > //ABCXYZPQ JOB 999830010T,'SPUFI',CLASS=A,NOTIFY=&SYSUID, > // MSGCLASS=H,MSGLEVEL=(1,1),&SYSUID > > Here "ABCXYZP" was replace with my userid FOOBAA0, resulting to the > jobname FOOBAA0Q... > > could anyone tell what I have to do to get this great feture back? > No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.4.0/1509 - Release Date: 6/19/2008 8:00 AM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
On Thu, 19 Jun 2008 09:31:13 -0500, Mark Zelden wrote:
>
>/* REXX */
>/* */
>/* AUTHOR: Mark Zelden */
>/* */
>Address ISREDIT
>"MACRO"
>uid= sysvar('SYSUID')
>ulen = Length(uid)
>"(data1) = LINE 1"
>data1 = Overlay(uid,data1,3,ulen)
>"LINE 1= (data1)"
>"SUBMIT"
>
But be careful of the initial formatting of the JOB statement. If it
is initially the very legal:
//NAME JOB account-stuff
won't the above result in the not very legal:
//ZELDENOB account-stuff
... ? (I have a tester's mentality.)
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
As others have said... an exit.
If you have your own clist/rexx library concatenated to SYSPROC/SYSEXEC,
you can easily create a submit edit macro that does it for you. Or perhaps
talk someone into putting the macro in a common library. Then you can type
something like "MYSUB" instead of SUBmit:
/* REXX */
/* */
/* AUTHOR: Mark Zelden */
/* */
Address ISREDIT
"MACRO"
uid= sysvar('SYSUID')
ulen = Length(uid)
"(data1) = LINE 1"
data1 = Overlay(uid,data1,3,ulen)
"LINE 1= (data1)"
"SUBMIT"
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
On Thu, 19 Jun 2008 10:05:26 -0400, Jerry Fuchs wrote: >The IKJEFF10 TSO submit exit would be used to change the job name to the >TSO user's ID. > >Maybe this was missed when you went to a new release? > In days of yore, I recall using the TSO SUBMIT command and being prompted for the jobname suffix character. Was that being done by the IKJEFF10 exit? And that TSO OUTPUT would retrieve only job named as user ID + one character. Various places in ISPF there are JOB statement templates. Are these effective only if the file being SUBMITted has no JOB statement? Regardless, I abandoned prefixing my job names with my user ID shortly after SDSF became available. I found it more useful to filter my SDSF displays by OWNER and use the full 8 characters of the job name for other meaningful information. Try it; it's liberating (although many of my colleagues find greater comfort in the legacy of user ID prefixing job names). I believe Flasher and EJES also provide filtering by owner ID. Installation standards may have inertia that binds you to the legacy naming conventions. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
I'd bet it was done via the IKJEFF10 submit exit. Basically, you're likely out of luck. Ahhh, yes And I also found some on the CBT-Tape that will do the job! Thank you! I'd really LOVE for IBM to allow something like: //&SYSUID.A JOB ...,NOTIFY=&SYSUID And I always thought I'm too stupid ;) Now I know it really doesn't work ;-) Bye & Thanks, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
Michael, If you cannot locate your IKJEFF10 exit I can send ours to you. Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
Michael Knigge wrote: I'm currently working on a new system and I miss a great feature(tm). On the systems I've been working so far the Jobid of a JCL was automatically set to my UserId when I've submitted the Job. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4B480/5.8.3 -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
The IKJEFF10 TSO submit exit would be used to change the job name to the TSO user's ID. Maybe this was missed when you went to a new release? Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Set JobId on Submit..
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Knigge > Sent: Thursday, June 19, 2008 8:55 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Set JobId on Submit.. > > All, > > I'm currently working on a new system and I miss a great > feature(tm). On > the systems I've been working so far the Jobid of a JCL was > automatically set to my UserId when I've submitted the Job. > > i. e.: > > //ABCXYZPQ JOB 999830010T,'SPUFI',CLASS=A,NOTIFY=&SYSUID, > // MSGCLASS=H,MSGLEVEL=(1,1),&SYSUID > > Here "ABCXYZP" was replace with my userid FOOBAA0, resulting to the > jobname FOOBAA0Q... > > could anyone tell what I have to do to get this great feture back? > > > Thanks, > Michael That was likely an "in house" function. There is no such function as distributed by IBM. If you are talking about submitting from TSO, then I'd bet it was done via the IKJEFF10 submit exit. Basically, you're likely out of luck. I'd really LOVE for IBM to allow something like: //&SYSUID.A JOB ...,NOTIFY=&SYSUID -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Set JobId on Submit..
All, I'm currently working on a new system and I miss a great feature(tm). On the systems I've been working so far the Jobid of a JCL was automatically set to my UserId when I've submitted the Job. i. e.: //ABCXYZPQ JOB 999830010T,'SPUFI',CLASS=A,NOTIFY=&SYSUID, // MSGCLASS=H,MSGLEVEL=(1,1),&SYSUID Here "ABCXYZP" was replace with my userid FOOBAA0, resulting to the jobname FOOBAA0Q... could anyone tell what I have to do to get this great feture back? Thanks, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
