Job cards are dead easy to code: //MYJOB JOB
What can be simpler? I personally add a notify: //MYJOB JOB NOTIFY=&SYSUID Now if SUB could use, say, the PDS/PDSE member name as the job name and add a NOTIFY=&SYSUID then that could be great as well! Related question: We don't specify NOTIFY on production JCL because the scheduler is not a "user" and doesn't need this anyway. If we did specify NOTIFY, however, would there be a way (other than an assembler exit, please!) to suppress it's function for certain users? Frank ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Wayne Bickerdike <[email protected]> Sent: Wednesday, June 28, 2017 2:44 PM To: [email protected] Subject: Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) - I think in my days at IBM we had job name standards that were enforced as UID + 1 char. This may explain why many times I never bother coding a job card for trivial jobs and once the job has run, I perform an SJ command, cut ALL and paste ALL back into the JCL library to have a syntactically correct job card. Lots of people struggle to code a job card and when I say "just delete the darn thing and submit", they don't know about the 1 char jobname dodge. On Thu, Jun 29, 2017 at 6:34 AM, Jesse 1 Robinson <[email protected]> wrote: > I've worked in half a dozen shops but never encountered any onerous > jobname restrictions. I suppose if you absolutely had to depend on the > OUTPUT command and did not want to customize IKJEFF53, the restriction > could be justified in those terms. But spool display tools like the old > QUEUE command, SDSF, and EJES make the TSO OUTPUT command absurdly archaic. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > [email protected] > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Wednesday, June 28, 2017 1:11 PM > To: [email protected] > Subject: (External):Re: Sources of message: IKJ56700A ENTER JOBNAME > CHARACTER(S) - > > On Wed, 28 Jun 2017 15:36:25 -0400, Farley, Peter x23353 wrote: > > >All well and good when the shop standard does not mandate TSO userid as > job name for *all* non-privileged users, no exceptions allowed. > > > >Some of us do not get to make the rules ourselves, or even have any input > on what the rules are. > > > http://mistupid.com/people/page058.htm > > My sympathies. (I know; I've posted it before.) > > And one of my employers' user ID standards practically guaranteed that > Cheng K. Fu, of San Diego, would never become an employee. (Real name; > found in a targeted white pages search.) > > -- gil > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
