People will say whatever they say whether the product is bullet-proof or not 
and whether it's true or not.  People who don't want to use it just won't use 
it, and those that want to use it will.    It's not like we will activate the 
process by default.  

Believe it or not, I have been in meetings where there are actually people who 
say "wait, Syzygy Automation is less than 10% of the cost of XYZ's automation, 
that means it can't be any good".  You can't stop people from saying or 
thinking things like that.  Luckily for us, the software really is just as 
good, and better in most parts, especially overhead, and sales have not been 
harmed by people complaining about "not paying enough".  :)

Brian 

On Sun, 23 Aug 2026 16:42:30 -0500, Charles Mills <[email protected]> wrote:

>Speaking as a guy who designed and product managed two successful mainframe 
>commercial products, actual security is only half of the battle. The other 
>half is prospect perception of security. If prospects say "we would never 
>allow people to email commands to our mainframe" then it does not matter how 
>bulletproof your security actually is. You may be worse off having the feature 
>at all, even if is completely controlled by a global parameter. You don't want 
>someone -- who just happens to be the guy who favors procuring your 
>competitor's product -- sitting in the staff meeting going "Syzygy -- that's 
>the one that lets people email commands into the mainframe." Explaining that 
>the feature can be disabled does not help. The sales guys say "when you 
>explain, you lose."
>
>CM
>
>----------------------------------------------------------------------
>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

Reply via email to