Thanks again Sri.  After reading those posts, I do see the issue.  That would 
be the "Don't break existing jobs" mantra.

I would instead have said "Go ahead and break them in QA so we can fix the 
broken ones", but I don't pay the bills and "breaking them in QA" AssUMes that 
QA batch initiator classes are distinct from Production batch initiator 
classes, which isn't true at any large shop where I have worked.

But I agree with Gil's final post in that thread - it should have been 
implemented as a new JCL option (similar to EXPORT SYMLIST) rather than an 
initiator class parameter.  Positive opt-in for jobs that want to use it, leave 
the others alone.  Perhaps a global parameter for the JCL interpreter to allow 
or disallow the new JCL option during the initial transition so shops could 
choose to allow or disallow use of the new JCL option to prevent accidental 
breakage by too-eager programmers until automated SDLC rules for JCL are 
updated and enforced.

Water under the proverbial bridge now.  At least we have EZACFSM1 as an 
alternative, so that's good.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Sri 
h Kolusu
Sent: Wednesday, June 15, 2022 1:32 PM
To: [email protected]
Subject: Re: SFTP JOB Data parameter

>>> But that raises the question why NOT always allow system symbols in 
>>> every batch initiator?  Allowing them just seems like a no-brainer 
>>> to me

Peter,

There have been several discussions on IBM-MAIN about SYSSYM=ALLOW and here is 
a post which explains one of the reason.

https://www.mail-archive.com/[email protected]/msg62638.html 

Thanks,
Kolusu
--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to