On Wednesday 06 April 2005 10:14 am, James Melin wrote: >The flexibility requirement really requires us to have the ability to have Linux trigger events on z/OS.
To schedule jobs from our job scheduler on remote Solaris platforms we've been using SSH. Basically, scheduler runs a batch job that logs in via SSH (using public/private keys so no passwords are sent in the clear) to run scripts. Scripts set a return code that gets picked up by the job scheduler. So scheduling stuff on our Solaris boxes looks like a simple batch job to our scheduler.
To go the other way, i.e. trigger something on OS/390 (yes, our production is still OS/390 -- we're working on upgrading), we run syslogd on the mainframe which sends stuff to /dev/console. This shows up as regular console messages and our automation product picks up on them to trigger an event.
-Stephen
-- -- ----------------------------------------------------------------------- Stephen Y. Odo Senior Systems Programmer phone: (808)956-2383 Information Technology Services FAX: (808)956-2412 University of Hawai'i e-mail: [EMAIL PROTECTED] ....................................................................... Region Registrar home phone: (808)847-1076 American Youth Soccer Organization Honolulu Region 178 e-mail: [EMAIL PROTECTED] -----------------------------------------------------------------------
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
