Generally I would think that... but then automation suddenly decides
differently.
On 7/26/2020 9:45 AM, Seymour J Metz wrote:
The safe way to handle that is to have automation rules that prevent or delay
the start during test windows.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of Tom
Brennan [[email protected]]
Sent: Sunday, July 26, 2020 1:18 AM
To: [email protected]
Subject: Re: Started task stopping immediately. No error messages.
I used to type JCLERROR or similar at the top of a proc I didn't want
started. Like Steve said, this was typically because I was doing some
work on the task in the middle of the night and I didn't want another
sysprog (or more likely automation) starting it up until I was done.
Auditors were sleeping soundly.
On 7/25/2020 6:22 PM, Seymour J Metz wrote:
Your management tolerates that? The auditors didn't red flag it?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Steve Horein [[email protected]]
Sent: Friday, July 24, 2020 6:05 PM
To: [email protected]
Subject: Re: Started task stopping immediately. No error messages.
This. As an automation guy, I've encountered support folks changing
PGM=<legit thing> to PGM=IEFBR14 to keep <legit thing> from executing while
maintenance is being done, or when they're drafting the change task to
retire it. And who do you think the Operations staff calls when they can't
get the task to keep running? Three guesses...
On Fri, Jul 24, 2020 at 3:28 PM Charles Mills <[email protected]> wrote:
A started proc is just JCL that executes some program. Any program *might*
behave as you describe. IEFBR14 would behave as you describe. People would
probably need more specifics to be able to help.
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Skippy the Ancient
Sent: Friday, July 24, 2020 12:48 PM
To: [email protected]
Subject: Started task stopping immediately. No error messages.
Has anyone seeing a started task immediately after you start it? No ACF2
messages. No error codes.
Nothing.
Help?
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
