been deleted,
the system was ready for student work.
Chris Mason
- Original Message -
From: John S. Giltner, Jr. [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Friday, 01 September, 2006 3:44 AM
Subject: Re: IPL intervals
As others have stated
[mailto:[EMAIL PROTECTED] On Behalf
Of Jon Brock
Sent: 01 September 2006 22:59
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IPL intervals
I was thinking the same thing. I have managed to avoid doing this (to
date), but we have had more than one operator activate/deactivate the wrong
image by mistake
I was thinking the same thing. I have managed to avoid doing this (to date),
but we have had more than one operator activate/deactivate the wrong image by
mistake.
Before PRSM/HPLF/MDF, I had occasion to go to the wrong service console and
stop the wrong machine.
Also, I remember when MDF
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL
Sent: Friday, September 01, 2006 10:16 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IPL intervals
I was thinking the same thing. I have managed to avoid
doing this (to date
I was thinking the same thing. I have managed to avoid doing this (to
date), but we have had more than one operator activate/deactivate the
wrong image by mistake.
We keep the DISRUPIVE TASKS lock on to avoid an accidental IPL.
Daniel McLaughlin
ZOS Systems Programmer
Crawford
This issue has been discuss in multiple places but never in one place.
After a series of human errors in following procedures during an IPL, we
are changing our weekly IPL to semi-annual.
Is there a check list of parameters that I would need to change to
accommodate fewer or no IPLs? Are there
Gee, Norman wrote:
This issue has been discuss in multiple places but never in one place.
After a series of human errors in following procedures during an IPL, we
are changing our weekly IPL to semi-annual.
Is there a check list of parameters that I would need to change to
accommodate fewer
Norman,
You may want to peruse Redbook z/OS Planned Outage Avoidance Checklist
published Aug. 21.
HTH, Paul
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message:
On 8/31/2006 11:40 AM, Gee, Norman wrote:
This issue has been discuss in multiple places but never in one place.
After a series of human errors in following procedures during an IPL, we
are changing our weekly IPL to semi-annual.
Is there a check list of parameters that I would need to
On Thursday, 08/31/2006 at 05:48 ZE2, R.S.
[EMAIL PROTECTED] wrote:
We *never* do IPLs on scheduled basis. Of course we do IPL when a need
arise.
From our Book of Experience, volume 59, p.843, it says:
What about IPLing less frequently?
- Use strong Change Management procedures. The longer
If you are running a parallel sysplex, you will probably have an easier time of
this.
Yes, you could have an issue with spool space and long-running jobs; you can
use the SPIN capability of JES to avoid this problem, though.
The more human involvement in your IPL procedures, the more trouble
In a message dated 8/31/2006 10:41:32 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Is there a check list of parameters that I would need to change to
accommodate fewer or no IPLs? Are there control blocks I would need to
be concern with? Will I now run into spool space issues
I'll second Jon's comments. I made a lot of use of two automation tools
from the CBT tape. AUTO and COMMAND were the tools. I mostly used COMMAND,
which lets you issue a series of commands by putting them in a PDS member.
If you have some automation software that can key on messages, that is
Six months is the life cycle of new releases.
NOT since 1.4 came out.
When in doubt.
PANIC!!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN
On Thu, 31 Aug 2006 08:40:31 -0700, Gee, Norman [EMAIL PROTECTED]
wrote:
This issue has been discuss in multiple places but never in one place.
After a series of human errors in following procedures during an IPL, we
are changing our weekly IPL to semi-annual.
Is there a check list of
My entire IPL process is automated. The procedures was to wait for the
IPL process to complete with the message that IPL has completed prior to
bringing up applications. We use commercial automation products.
The OPS initiated the command to start up all application at the
beginning of the IPL
. The inability to follow a written procedure is not a
technical issue, it is a management issue.
HTH
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Gee, Norman
Sent: Thursday, August 31, 2006 10:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: IPL intervals
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Hal Merritt
Sent: Thursday, August 31, 2006 2:43 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IPL intervals
You may run into RACF issues if you auto revoke ID's after x days. The
long
On 8/31/2006 3:43 PM, Hal Merritt wrote:
You may run into RACF issues if you auto revoke ID's after x days. The
long running task ID's may revoke, and that may or may not cause issues.
You should make sure that the IDs assigned to your started tasks are
PROTECTED (defined as NOPASSWORD),
Assuming, of course, that the site is reasonably up to date on their
maintenance :-)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Walt Farrell
Sent: Thursday, August 31, 2006 3:24 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IPL intervals
On 8
As others have stated, automating your IPL process will help alot.
Our shutdown and IPL process are automated. We use NetView for system
automation.
When we need to IPL the operators execute a clist from a system console
on the system they want to shutdown, a WTOR is issued to which they
21 matches
Mail list logo
