An SSH command line utility like PuTTY plink might work depending on what TSO command you need:
plink -ssh [email protected] tso -t delete foo.bar See: https://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter7.html you could also use the z/OSMF REST services API for TSO command services: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.izua700/izuprog_API_TSOServices.htm Kirk Wolf Dovetailed Technologies http://dovetail.com On Wed, Apr 27, 2016 at 1:39 AM, Martin Packer <[email protected]> wrote: > Naïve question (as one who does iOS, macOS, Linux) is SSH something an end > user can rely on to be there? Or is it something my Sysprogs (and I'm not > one of them) needs to set up. > > And compared to my PHP-driven FTP scripting would it be complementary or a > faster or slower replacement? > > (Mentioning my 3 client operating systems implies I can find an SSH client > for each.) > > Cheers, Martin > > Martin Packer, > zChampion, Principal Systems Investigator, > Worldwide Cloud & Systems Performance, IBM > > +44-7802-245-584 > > email: [email protected] > > Twitter / Facebook IDs: MartinPacker > > Blog: > https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker > > Podcast Series (With Marna Walle): > https://developer.ibm.com/tv/category/mpt/ > > > > From: Paul Gilmartin <[email protected]> > To: [email protected] > Date: 27/04/2016 03:54 > Subject: Re: TSO command from Microsoft Windows > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > On Tue, 26 Apr 2016 19:28:41 -0500, Steve Beaver wrote: > > >The problem with Windows Telenet is getting by the signon screen and any > messages that come out such as "Password Will Expire..." and all the > Broadcast messages. Plus if the LOGON is driven into ISPF you will have > to compensate for that. > > > >The next question, is what type of commands? > > > Yup. > > ssh is much nicer to you: > > o It's encrypted. > > o It doesn't require keyboard-interactive authentication. > > o The fluff goes to stderr, the payload to stdout, making it suitable > for a programmatic interface. > > A much abridged version of my bridge EXEC: > > user@OS/390.25.00: cat rtso2 > /* REXX */ signal on novalue; /* ****************************** > Doc: simple ssh network interface to TSO. > */ > trace Err > > address 'MVS' > > do L = 1 > 'EXECIO 1 DISKR 0 (stem S.' /* Read a command from terminal. */ > if RC<>0 then leave L /* Quit if end of file. */ > address 'TSO' S.1 /* Issue TSO command. */ > end L > > return( RC ) /* ****************************** */ > user@OS/390.25.00: > > o Surely needs allocation for SYSEXEC, etc. > > o Works alike with PuTTY and Cygwin. > > o I use something similar for batch-like ISPF. > > - gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > ---------------------------------------------------------------------- > 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
