Would you want a really weird idea? This is to communicate from Linux to
z/OS only. Although it would work the other way as well.
On z/OS, set up the UNIX syslog daemon. What I have in my "/etc/rc" file
is:
# Start the syslog daemon
_BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -c -u &
This starts up the UNIX syslog daemon on z/OS.
Dedicate a facility such as "local0.crit" in this daemon (in
"/etc/syslog.conf") . On the Linux side, send these messages to z/OS
with a entry such as:
local0.crit @zos.ip.address
This will send all Linux syslog messages which are "local0.crit" to the
z/OS system. On the z/OS system, set up the daemon similar to:
local0.crit /dev/console
This will send all messages coming into the syslog daemon with the
"local0.crit" to the z/OS console. I send the message:
Apr 6 05:02:56 LIH1/BPXROOT OSNMPD snmpagent[16777234]:
[EMAIL PROTECTED](1548):
using:
echo "Apr 6 05:02:56 LIH1/BPXROOT OSNMPD snmpagent[16777234]:
[EMAIL PROTECTED](1548):" >/dev/console
and on the z/OS syslog saw:
4000000 LIH1 05096 10:57:48.82 STC02546 00000094 BPXF024I (TSH009)
Apr 6 05:02:56 LIH1/BPXROOT OSNMPD snmpagent 167
645
645 00000094 77234 :
[EMAIL PROTECTED](1548):
You could set up your z/OS automated operator to key off of the BPXF024I
message and parse out what to trigger on z/OS. Perl is very easy to use
to send this sort of thing.
HTH,
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology
This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of James Melin
> Sent: Wednesday, April 06, 2005 9:15 AM
> To: [email protected]
> Subject: Are there any NJE/NRJE interoperability tools for
> Linux to submit jobs to z/OS?
>
>
> We're trying to develop a methodology where our
> scheduling system
> controls deployment of applications to our WebSphere production
> environment. We are using the Stonebranch universal command
> client to talk
> to our z/Linux guests from z/OS. We can query WebSphere,
> start and stop
> servers, and other tasks from a single ISPF interface that
> allows us to
> talk to several Linux guests. More to the point, it gives our
> operators a
> familiar interface into Linux that we control the scope and
> content for.
>
> For the production WebSphere environment, deployments
> are planned. We
> know when an application is going in. We can schedule it. We
> have a process
> that looks at the schedule batch deployments and determines what, if
> anything, needs to run 'today' and generates JCL to run Linux
> scripts that
> are kept in a highly secured PDS and submitted to Linux to
> execute via the
> Stonebranch universal command interface (Tivoli workload
> scheduler, which
> we also have, requires us to build an windows box in order to
> interface to
> z/Linux. This of course is unacceptable)
>
> For our development systems it is conceivable that
> there could be 5-6
> deploys per day during an active development period. We don't want to
> 'batch schedule' that but we still want to use the scripting
> tools we've
> developed for prod. The flexibility requirement really
> requires us to have
> the ability to have Linux trigger events on z/OS.
>
> What I've come up with proposal wise so far is not
> something I really
> like... and that is to ftp a generated JCL stream to z/OS
> directly into
> JES2 and issue a message to trigger an System Automation
> event. I only like
> this idea If it were possible to set it up so that this could
> be only done
> from a specific IP address (hipersocket) AND a specific user
> (which had no
> dataset access authority)
> If there were an NJE/RJE interface that Linux could
> exploit, this
> would perhaps be better. Is anyone aware of anything that has NJE/NRJE
> interoperability for z/Linux? Failing that, something in VM
> that could be
> triggered via CPINT somehow?
> The only other possibility is that I've read that
> system automation
> can treat a VM guest like an LPAR. In LPAR mode, the z/OS
> automation tool
> (last known to me as SA/390) uses the HMC to talk to the
> target LPAR. I can
> only presume that this will be the interface of choice for system
> automation to talk to a Linux guest. I'm still gathering information.
>
> Bottom line: Failing an NJE/NRJE interoperability
> solution, is there
> a recommended way to get two way command and control
> communication between
> z/OS and Linux under VM?
>
> ----------------------------------------------------------------------
> 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
>
----------------------------------------------------------------------
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
