Re: Automated shutdown

2008-01-18 Thread nounours
Hi Mark:
A real professional tool like *AutoMan* is virtually all you need. See *
www.exspans.com
*They use it in the USA and Germany as far as I'm aware.
Bob Ruwel

On Jan 16, 2008 3:53 PM, Mark Pace [EMAIL PROTECTED] wrote:

 Is there a way to automate the shutdown of z/OS?  I hate having to follow
 a
 script, typing all of the commands to stop tasks.

 Also, is there a command to stop syslogd, other than to cancel it?

 Thanks very much.

 --
 Mark Pace
 Mainline Information Systems

 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
 Search the archives at http://bama.ua.edu/archives/ibm-main.html



Yours as ever,
Bob Ruwel
Time flies like an arrow - Fruit flies like bananas.
Dogmas shut your mind.
Dogpas water hydrants.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Automated shutdown

2008-01-18 Thread Mark Pace
A tool would be nice.  But buying additional software is not an option.

-- 
Mark Pace
Mainline Information Systems

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Automated shutdown

2008-01-17 Thread Mark Yuhas
My installation let the Operations staff write and maintain the shutdown
procedure using our automation tool.  This was done a number of years
ago when the mainframe was the platform of choice.  Since then, the
mainframe has become the 'platform non grata' and the automation tool
has become an afterthought.

I tried to update and rewrite the shutdown procedure.  I found it
cumbersome and inadequate - both the procedure and the automation tool.

Consequently, I have written my own shutdown procedure, it consists of a
started task to initiate, monitor and facilitate the shutdown.  I also
use the WTO exit to assist in the monitoring and communication with the
started task.  Finally, I use an ECSA table that provides the
information the started task needs to perform its functions.

I am prejudiced but it works a lot better and is fault tolerant, e.g.
tasks that don't come down are cancelled after a specified period of
time.

Operator intervention is almost non-existent.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Automated shutdown

2008-01-17 Thread Brian Westerman
I hate to do marketing, but I need to mention that the company I work for
sells a very inexpensive product that allows you to perform automated
operations, IPL, Shutdown, and anything in-between.  You can get information
by going to www.SyzygyInc.net, but I'll also paste some of the marketing
stuff below.  You can try out any of our products for up to 60 days for free.

Basically SyzCmdz does what the big ticket automation products from the
likes of IBM and CA do, but is available at a VERY small fraction of the
cost.  There are over hundreds of users of our products, and this particular
one is my personal favorite.

Begin Marketing blurb: 

The SyzCmdz utility is designed to provide the authorized user with the
capability of executing simple or complex scripts of MVS, JES2, JES3,
CICS, DB/2, or Unix System Services (USS) commands from within a batch job
or started task. The command(s) can be issued from the PARM parameter on the
EXECute card or from the parameter script file both.

SyzCmdz can be used to automate the operating systems IPL, Shutdown,
controlling and monitoring CICS, DB/2 the TCP/IP or VTAM network, and almost
any operator function in between. The product can be called from within
authorized high level programs to execute commands and perform functions
that would otherwise not be possible.

SyzCmdz is not simply a dumb scripting facility for issuing commands, it
has a direct interface with your sites security system (RACF, ACF/2,
TOP/Secret) and will only allow authorized users to use the many special
features for determining what needs to be done and when. The utility
provides a very simple scripting language that allows the authorized user
to harness extremely powerful command logic, including nested IF/THEN/ELSE
logic.

Facilities are provided to allow authorized users to perform
script/command logic in instances such as only IF some task is active, or
not active, or only if (or if not) a certain day of the week, or time of day.

There are over 35 special internal logic commands built in to the SyzCmdz
facility with more under development.

Some features include:

Nested IF/THEN/ELSE capability (up to 8 levels)

IF logic for Whether or not a particular JOB/STC/TSO user is started (or
not), If specific VOLSERs or Units are ONLINE (or OFFLINE), Day of Week,
Time of day, LPAR ID (system ID), and more!!!

Cause the script to WAIT for a specific thing to happen, like for a
specific JOB to start, or a specific time of day, or any of many variable
items including (a Syzygy exclusive) for VTAM to not only be started but be
ready for work without requiring any VTAM changes to support this function.

Provide the ability to reply to outstanding messages without regard to their
reply-id's or even knowing the complete text or message ID of the message. 
You can reply to ANY outstanding message for a JOB/STC/USER, or to all
messages that are currently outstanding.

Pause from 1 second to  hours, or until a specific time of day.

and much more.

If you're interested, have a look at the web site, or drop me an offline
email and I'll get you a copy of the manuals, or a free trial.

Brian

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Automated shutdown

2008-01-16 Thread Mark Jacobs
Mark Pace wrote:
 Is there a way to automate the shutdown of z/OS?  I hate having to follow a
 script, typing all of the commands to stop tasks.

 Also, is there a command to stop syslogd, other than to cancel it?

 Thanks very much.

   
Er, that is what an automated operations product does. It knows whats up
and how to shut everything down. One command to the product and it
should be able to (if setup correctly) to shut everything down the
correct way and in the correct order.

-- 
Mark Jacobs
Time Customer Service
Tampa, FL


Riley: Find the next number in the sequence: 313, 331, 367, ...? what?

The Doctor: 379. It's a sequence of happy primes, 379.

Martha: Happy what?

The Doctor: Just enter it!

Riley: Are you sure? We only get one chance.

The Doctor: Any number that reduces to one when you take the sum of 
the square of its digits and continue iterating until it yields 1 is 
a happy number, any number that doesn't, isn't. A happy prime is 
both happy and prime. 

Doctor Who episode 42

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Automated shutdown

2008-01-16 Thread Mark Zelden
On Wed, 16 Jan 2008 09:53:24 -0500, Mark Pace [EMAIL PROTECTED] wrote:

Is there a way to automate the shutdown of z/OS?  I hate having to follow a
script, typing all of the commands to stop tasks.


Of course there are automation products that you can by to take care of
this.  There some free ones on the CBT also. TSSO, COMMAND.  Even
though we have an automation product, all my sandbox LPARs use 
COMMAND from CBT file 19 (http://www.cbttape.org).  I start the scripts
from an STC that runs SUB=MSTR so it can even shutdown JES2 and
issue V XCF,sysname,OFFLINE.   I use COMMAND on my sandbox LPARs
for 2 reasons.  One:  the automation group controls the automation 
products.  Two: less overhead - quick, simple, easy to change.



Also, is there a command to stop syslogd, other than to cancel it?



On Wed, 16 Jan 2008 09:28:28 -0600, Stephen Wolf [EMAIL PROTECTED] wrote:

The CBT tape has many MPF exit examples for automation and of course
the AUTO command.

For syslogd shutdown look at IBM site for the z/OS UNIX tools for BPXSTOP.

While BPXSTOP could still be used, it's better these days to use 
F BPXOINIT,SHUTDOWN= commands or to shutdown OMVS completely
with F OMVS,SHUTDOWN.  See the Unix System Services Planning manual
for details.   I think BPXSTOP would cause a problem in a share HFS / zFS
environment also.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Automated shutdown

2008-01-16 Thread David Logan
ADCD also comes with startup/shutdown STCs. Mine for example, looks like
this (and as you can see uses a control file out of PARMLIB):

BROWSEADCD.ZOSV1R5.PROCLIB(SHUTDOWN) - 01.00 Line  Col 001
080 
 Command ===  Scroll ===
CSR  
* Top of Data
**
//SHUTDOWN PROC M=SHUTDOWN,PREFIX=NONE   == Change as required

//VTAMAPPL EXEC PGM=VTAMAPPL,PARM='COMMANDPREFIX=PREFIX',

// REGION=512K,TIME=1440

//STEPLIB  DD  DSN=ADCD.ZOSV1R5.LINKLIB,DISP=SHR

//PARMLIB  DD  DSN=ADCD.ZOSV1R5.PARMLIB(M),DISP=SHR

//SYSABEND DD  SYSOUT=H,HOLD=YES


David Logan

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Mark Zelden
Sent: Wednesday, January 16, 2008 9:24 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Automated shutdown

On Wed, 16 Jan 2008 09:53:24 -0500, Mark Pace [EMAIL PROTECTED] wrote:

Is there a way to automate the shutdown of z/OS?  I hate having to follow a
script, typing all of the commands to stop tasks.


Of course there are automation products that you can by to take care of
this.  There some free ones on the CBT also. TSSO, COMMAND.  Even
though we have an automation product, all my sandbox LPARs use 
COMMAND from CBT file 19 (http://www.cbttape.org).  I start the scripts
from an STC that runs SUB=MSTR so it can even shutdown JES2 and
issue V XCF,sysname,OFFLINE.   I use COMMAND on my sandbox LPARs
for 2 reasons.  One:  the automation group controls the automation 
products.  Two: less overhead - quick, simple, easy to change.



Also, is there a command to stop syslogd, other than to cancel it?



On Wed, 16 Jan 2008 09:28:28 -0600, Stephen Wolf [EMAIL PROTECTED]
wrote:

The CBT tape has many MPF exit examples for automation and of course
the AUTO command.

For syslogd shutdown look at IBM site for the z/OS UNIX tools for BPXSTOP.

While BPXSTOP could still be used, it's better these days to use 
F BPXOINIT,SHUTDOWN= commands or to shutdown OMVS completely
with F OMVS,SHUTDOWN.  See the Unix System Services Planning manual
for details.   I think BPXSTOP would cause a problem in a share HFS / zFS
environment also.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html