For batch access, you can use FTP now, this is meant for when something happens 
in automation that requires someone to respond to something.  It provides the 
give and take part, plus it opens up the ability to send email to z/OS again, 
without CSSMTP.  The automation system already can send email on demand, but 
this gives a way to receive email. 

Brian

On Sun, 23 Aug 2026 06:12:00 +0000, Farley, Peter <[email protected]> 
wrote:

>FWIW, my honest opinion is that it just seems like a bit of a Rube Goldberg 
>way to get commands into automation software.  Interesting project for sure, 
>but why?
>
>Wouldn’t a REST API with appropriate SAF authentication be cleaner and more 
>secure?  Including both batch JCL (PGM=) and Unix Services CLI programs to 
>communicate to the API without programming?
>
>Or maybe an Ansible interface?  I admit to very small knowledge of Ansible 
>capabilities, but from what little I know it seems to be a reasonable pathway 
>from off-platform systems into Z-based software that accepts commands.
>
>Peter
>
>From: IBM MainframeiDiscussion List <[email protected]> On Behalf Of 
>Brian Westerman
>Sent: Saturday, August 22, 2026 3:09 AM
>To: [email protected]
>Subject: Odd idea?
>
>
>I was wondering.  Since IBM is unlikely to ever change CSSMTP to create the 
>ability to send email to the mainframe, what do you think about adding the 
>ability for sending email to our automation system to have it execute 
>functions and/or commands on the mainframe?  We have supported using FTP to do 
>that for many years, and have provided trigger commands, but this would be 
>creating the ability to send an email to what would be the "inbox" for talking 
>with the Syzygy automation system and having it confirm if the email sender 
>was authorized to issue commands and of what type, and then pass them on to 
>the automation system on the various LPARs that automation is executing on for 
>processing.
>
>
>
>I have a prototype created that I have been testing for a while and I am 
>looking for volunteers to try it out.  The only restriction is that you have 
>to be running the Syzygy Automation package, (shame on you if you aren't :).
>
>
>
>I'm trying to decide if the proce s needs to reflect back to the user that the 
>process was successful.  I current tell them if it wasn't, and there is no 
>reason that I couldn't tell them that it was as well, but can't decide if 
>that's necessary.
>
>
>
>I found that I could also ask automation to send the output of jobs in the 
>queue, but didn't know if that's something that would be useful because the 
>automation system already can send email when any job ends that contains the 
>output already.  So it could be a "feature" I keep to the side to add later.
>
>
>
>Even if (for some odd reason) you don't run the Syzygy Automation system, I 
>would be interested in your thoughts on this process.
>
>
>
>Brian
>
>--
>
>Tsis esssage 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

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

Reply via email to