Has anyone considered a generalized REXX (Regina) routine that can start
processes and handle the return codes? Ok, I know Perl should be used,
but I come from the VM world where REXX rulesG.
Right now, I don't have much of a need for this type of
autostarting
But, I see the need in a few
On May 8, 2006, at 10:19 AM, Tom Duerbusch wrote:
Has anyone considered a generalized REXX (Regina) routine that can
start
processes and handle the return codes? Ok, I know Perl should be
used,
but I come from the VM world where REXX rulesG.
Right now, I don't have much of a need for this
I think someone did... And yes, it's a good starting point. The catch
is that startServer.sh (and the various other scripts) in WAS don't
nicely fit the mold with the way they do messages and return codes. And
of course there's no doc on the WAS scripts...
Lee
Bruce Hayden wrote:
Hi Lee,
I
Hi Lee,
I don't think anyone mentioned that SUSE supplies the file
/etc/init.d/skeleton as a starter for creating your own
startup/shutdown files. Also, see man init.d for their
documentation on the process. You use the insserv or chkconfig
command to add or remove the links to the startup
Hi...
What are people doing to automatically start things like WAS, DB2, MQ
etc.? Stuffing it at the end of /etc/inittab? Writing your own
start/stop script for /etc/init.d? What's the best place to stick it?
One of our clients was told have someone logon and issue... -- by
someone at IBM
On May 3, 2006, at 1:07 PM, Lee Stewart wrote:
Hi...
What are people doing to automatically start things like WAS, DB2, MQ
etc.? Stuffing it at the end of /etc/inittab? Writing your own
start/stop script for /etc/init.d? What's the best place to
stick it?
One of our clients was told have
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Lee Stewart wrote:
Hi...
What are people doing to automatically start things like WAS, DB2, MQ
etc.? Stuffing it at the end of /etc/inittab? Writing your own
start/stop script for /etc/init.d? What's the best place to stick it?
Hi, Lee.
On May 3, 2006, at 11:38 AM, Grega Bremec wrote:
And if you're delegating, why
not leave it to the System-V init process, which has matured to the
point where we're even talking about dependency-aware parrallel
startups
now?
And if you're interested in dependency-aware parallel startups for
When we installed it it installed at th eend of inittab. Works good. Then we
put together scripts to b/u and shutdown the processes.
Mace
Lee Stewart [EMAIL PROTECTED] wrote:
Hi...
What are people doing to automatically start things like WAS, DB2, MQ
etc.? Stuffing it at the end of
cooperation.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Lee Stewart
Sent: Wednesday, May 03, 2006 11:08 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Starting WAS, MQ, DB2, etc...
Hi...
What are people doing to automatically start things like
We have DB2 Connect Gateway (not the database) running on Lin-z. We wrote
our own startup script. DB2 Connect wants to use the fault monitor but
that took a lot of cpu, so we don't use it. We comment out the statement
that it puts in inittab. (Every fixpak tries to put it back in.)
tom
- - -
OK, this is what I thought -- and agree with...
Now I have to really grumble at IBM... Am I missing something or isn't
that missing what should be a key part of the product? Is it really
reasonable that every single shop has to write their own init.d
script Every shop expected to
Re:
Starting WAS, MQ, DB2, etc...
Please respond to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
OK, this is what I thought -- and agree with...
Now I have to really grumble at IBM... Am I
Stewart
Sent: Wednesday, May 03, 2006 4:10 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Starting WAS, MQ, DB2, etc...
OK, this is what I thought -- and agree with...
Now I have to really grumble at IBM... Am I missing something or isn't
that missing what should be a key part of the product
What are people doing to automatically start things like WAS, DB2, MQ
etc.? Stuffing it at the end of /etc/inittab?
God, no! Please, stamp this sort of thing out whenever you see it.
Writing your own
start/stop script for /etc/init.d? What's the best place to stick
it?
Init.d. And
@VM.MARIST.EDU
Subject: Re: Starting WAS, MQ, DB2, etc...
OK, this is what I thought -- and agree with...
Now I have to really grumble at IBM... Am I missing something or isn't
that missing what should be a key part of the product? Is it really
reasonable that every single shop has to write their own
Subject
Re:
Starting WAS, MQ, DB2, etc...
Please respond to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
OK, this is what I
Lee,
If you'll send me the commands and options, I'll produce a template for
you.
Now I have to really grumble at IBM... Am I missing something or
isn't
that missing what should be a key part of the product? Is it really
reasonable that every single shop has to write their own init.d
On 5/3/06, Lee Stewart [EMAIL PROTECTED] wrote:
I'd be happy with a template! I easily accept some tailoring. But
trying to take WAS's oddball scripts and what they return and fit that
into the /etc/init.d/skeleton pattern can be done, but it's not for a
novice... (And yes, David's Oracle
Here's the problem with IBM writing your startup script for you -
WebSphere changes over time. Servers are added. Servers are removed.
Server names
can change. All of this must be reflected in your startup script.
Easy. That's what /etc/sysconfig files are for.
Define one init.d instance
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 05/03/2006 05:17:20
PM:
snip
The only thing that inittab does right now that /etc/init.d scripts
can't do is automatically respawn a failed application if it dies. We'd
just need to write a spawner application that initialized, forked a
I, being a mainframe dinosaur, just wrote a script that checks for the
processes' existence. If it ain't there, it starts it. I cron it
every 5
to 15 mins based on how important the task is. (Actually, it does a
netstat and checks for the port.) Samples available for the asking.
Yeah,
Rob van der Heij wrote:
On 5/3/06, Lee Stewart [EMAIL PROTECTED] wrote:
I'd be happy with a template! I easily accept some tailoring. But
trying to take WAS's oddball scripts and what they return and fit that
into the /etc/init.d/skeleton pattern can be done, but it's not for a
novice...
I concede that your way is better, but my way works most of the time and I
did it with very limited knowledge of the *nix world.
tomS
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 05/03/2006 06:19:05
PM:
I, being a mainframe dinosaur, just wrote a script that checks for the
processes'
Now I have to really grumble at IBM... Am I missing something or isn't
that missing what should be a key part of the product? Is it really
reasonable that every single shop has to write their own init.d
script Every shop expected to reinvent that wheel? Surely they
might anticipate
Rick Troth wrote:
Now I have to really grumble at IBM... Am I missing something or isn't
that missing what should be a key part of the product? Is it really
reasonable that every single shop has to write their own init.d
script Every shop expected to reinvent that wheel? Surely they
Just for the record, I have written them for a couple of products
(probably poorly as I'm still fairly new to bash). And I've changed
them over and over as IBM changes names or directory structures etc..
And I've helped customers with it. And I've helped them try to complain
to IBM (to no
On Thursday, 05/04/2006 at 09:32 ZE8, John Summerfied
[EMAIL PROTECTED] wrote:
Better, users forking out dollars for the product (or seriously thinking
of doing so) should whinge and grip to their official IBM contacts.
If you have a support contract, then you should take it up with the
28 matches
Mail list logo
