Hi,
Is anyone aware of a way to internally change the identifier of a Started Task
after the task starts?. For instance, If someone starts a task called "MYTASK"
via "S MYTASK.bob" and I would like it to be something other than "BOB" that I
can issue a modify command to the STC "MYTASK", is th
I have wondered the same thing. Would be interested in any answers.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Brian Westerman
Sent: Monday, August 14, 2017 3:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: changing the STC
, 2017 14:47
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: changing the STC identifier
>
> I have wondered the same thing. Would be interested in any answers.
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTS
On Mon, Aug 14, 2017 at 7:55 AM, Vernooij, Kees (ITOPT1) - KLM <
kees.verno...@klm.com> wrote:
> The only way I can think of is update the CSCB of that particular Address
> Space. Make sure you have the right one, e.g. by ASID.
>
This is how I have seen in done. Once ... a _long_ time ago under
That worked perfectly. Thank you very much. It has saved me a lot of time and
opened up some great possibilities now that I can alter the ID. I found that I
can change it as many times as I want through the course of the task and even
interrogate it and treat it as a run-time "parameter" now.
Brian Westerman wrote:
>That worked perfectly. Thank you very much.
What worked? Or please be kind to post what method or which person's advice you
used for your project.
Thanks in advance.
Groete / Greetings
Elardus Engelbrecht
--
There is surely no supported way.
But there is no way to stop a key 0 user from doing whatever it wants.
Peter Relson
z/OS Core Technology Design
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
The field at +8 into the CSCB is field I needed to change. As it turns out, I
only need to change it when it's left to default to the unit address of the
IEFRDER DD. In my code, I already know the unit address that the IEFRDER file
is on (or if it is Inline), so if I compare them and they are
You're quite right, it's not supported but it's actually quite safe (in this
case). It's our code that makes up both the STC and the script that it uses.
I have a series of checks that we do during startup and I also made sure there
won;t be any timing issues between tasks. Originally I had (
Brian Westerman wrote:
>The field at +8 into the CSCB is field I needed to change. As it turns out, I
>only need to change it when it's left to default to the unit address of the
>IEFRDER DD. In my code, I already know the unit address that the IEFRDER file
>is on (or if it is Inline), so if
IEFRDER/unitaddr was originally for unit record tasks (readers & writers) which
would never be shared. (Also worked for tape drives.)
It enables start/stop/modify commands to be issued against the unit address.
What's odd is why you're using it in this day and age for shareable devices.
If
Way back in the 70s, our SVS and MVT systems had 2! started tasks,
Master and HASP. Occasionally, an external writer. STCs only later
were expanded to other purposes, and obviously there's quite a few
these days.
J R's question is a good one. //IEFRDER allows for some convenience
overrides on a
No, all that needs to be changed is that field. It takes immediate effect.
I'm actually pretty impressed with the results (so far). There is still a
great deal of beta testing to be conducted, but it seems to work fine.
Brian
--
The code was originally created back in 1987 and using IEFRDER allowed a lot of
flexibility (at the time). The code now supports alternate DD's for sequential
script command input, and even dynamically generating the DD (which is what
most of the 400 current users use), but enough people still
14 matches
Mail list logo
