Just remember to add it to MSTRJCL asIEFJOBS.
Michael
At 10:39 AM 12/16/2022, Carmen Vitullo wrote:
Content-Transfer-Encoding: 8bit
I'm not sure this was a question or a statement
but yes, I use SYS1.STCJOBS and place jobcards
for STC's I want to add, accounting info or
change the msgclass or any other valid jobcard parms.
I learn something almost daily, I didn't know about &SYSJOBNM, good to know
Carmen
On 12/16/2022 10:32 AM, Jay Maynard wrote:
You can now put a JOB statement in an STC PROC?!
On Fri, Dec 16, 2022 at 10:10 AM Steve Smith <sasd...@gmail.com> wrote:
Well, I've only used the new &SYSJOBNM for batch jobs, as the old &JOBNAME
seems to work well for STCs. However! I found (in MVS System Commands)
the following description of the rabbit hole that is names of STCs:
The job name for a given started task can be assigned based on a variety of
inputs. These inputs are examined in the following order, so that if item
#1 is not specified, item #2 is used. If neither #1 nor #2 is specified,
then #3 is used, and so on.
1. The job name specified in the JOBNAME= parameter of the START
command
or
The identifier specified on the START command.
2. The job name specified on the JOB JCL statement within the member.
3. The device number specified on the START command, or the device
number associated with the device type specified on the START command
or
The device number associated with the device type specified on the
START command.
4. The device number associated with the IEFRDER DD statement within
the member.
5. The member name.
IBM® recommends that you use the JOBNAME parameter rather than an
identifier. If you use the JOBNAME parameter, SMF records, messages, and
automated programs can reflect or react to job status; identifiers can
only
be viewed at a console.
Note: JOBNAME and identifier are mutually exclusive; you cannot specify
both parameters on the START command.
Nothin's simple. It would be interesting to see how all the options affect
both variables.
sas
On Fri, Dec 16, 2022 at 9:37 AM Colin Paice <colinpai...@gmail.com> wrote:
Wth
S OMPROUTE.OMP4 &SYSJOBNM gives OMROUTE
S OMPROUTE,JOBNAME=OMP4 gives OMP4
I can live with this
Colin
On Fri, 16 Dec 2022 at 14:31, Colin Paice <colinpai...@gmail.com> wrote:
Thank you .. I'll raise some doc comments, as it is not well
documented.
It is only mentioned in the
*what's changed in 2.3 *
Colin
On Fri, 16 Dec 2022 at 13:04, Steve Smith <sasd...@gmail.com> wrote:
This was asked and answered before. &SYSJOBNM
sas
On Fri, Dec 16, 2022 at 4:07 AM Colin Paice <colinpai...@gmail.com>
wrote:
If I start OMPROUTE.OMP1, or issue Start OMPROUTE,JOBNAME=OMP1, can
I
get
the
OMP1 as a JCL symbol so I can use it to pick up different
configuration
members?
I can crawl around the control blocks and create a symbol - but
want a
supported solution.
If I use &JOBNAME I get JES2.
Colin
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
--
Carmen
----------------------------------------------------------------------
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
