Re: z/OS PTFs

Meganen Naidoo - BCX - RO JHB wrote:
Hi All,

We are currently running z/OS 1.7 service level 0705 on 11 production
Lpars for different clients - not in a sysplex.
We just received the latest recommended and critical ptfs from Shop
zSeries - 0710.
The PTF's are a staggering 7524 in total. Our current fix strategy is to
just smp receive all the PTF's and
use the 'fix on fail' approach if we require a fix. We have a good SMPE
rollout strategy - SMP dddefs point to copied system volumes
and we IPL of the 'SMP applied' set....etc. Our reason for not applying
all the fixes is that we run many different non-IBM 3rd party products
on the different lpars and are concerned that the fixes may cause
problems.

We would like to know what strategy's other companies use to install
these system fixes. How often do you receive/apply system fixes...etc

Kind Regards,
Meganen Naidoo



You are correct in saying that IBM service can effect ISV software
products but I assume you have a process to test the environments before
production rollout however.

Fix on fail is one method of applying service, its not the one we use
but it is a valid method however. The problem with "fix on fail" is that
you always run the risk of hitting a problem that has already been fixed
and could have been prevented if the service had been applied already.

I generally apply the all available RSU's and available HIPERs not yet
assigned an RSU identifier on a bi-monthly basis (6 times a year).

Yes I sometimes get hit by being too aggressive but I can better defend
my decision when that happens than having a system or subsystem outage
due to not fixing a known problem.

It's a balancing act with no right answer.

--
Mark Jacobs
Time Customer Service
Tampa, FL
------

Everything is theoretically impossible, until it is done. One
could write a history of science in reverse by assembling the
solemn pronouncements of highest authority about what could not
be done and could never happen.

Robert A. Heinlein - The Rolling Stones (1952)

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

Relevant Pages

  • Re: COBOLs Influence on C
    ... environment that relies on having scads of libraries that must be ... Deployment to production is controlled by a third group: ... Then fix the real problem rather than ranting about how it is everyone ... third party, which calls C from another third party. ...
    (comp.lang.cobol)
  • Re: Splitting an DFSMShsm environment
    ... I once worked at a company where they had 3 LPARs, named Prod, Dev and Test. ... MIM controlled dataset access and tape drive sharing across all LPARs. ... DFHSM on Prod ran all the main activities: ... recall a migrated production dataset ... ...
    (bit.listserv.ibm-main)
  • Re: Does NIM pay for small deployments?
    ... micropartitioned LPARs + 1 or more testing or other non-production LPARS ... The p510 is production and not partitioned. ... and then use NIM to install all the other AIX ... I think that implies a single Virtual I/O Server partition ...
    (comp.unix.aix)
  • z/OS PTFs
    ... We are currently running z/OS 1.7 service level 0705 on 11 production ... Lpars for different clients - not in a sysplex. ... rollout strategy - SMP dddefs point to copied system volumes ... all the fixes is that we run many different non-IBM 3rd party products ...
    (bit.listserv.ibm-main)
  • Re: Tale of debugging and programming logic in c#/sql
    ... > and I pushed it to production. ... I was anxious to find a fix, ... The login page does ... > user authenticates or creates a new login name -- it is based on an ID ...
    (microsoft.public.dotnet.languages.csharp)