Re: PTF's Installed on Production Servers

I install on our development machine and let them run 4-6 weeks.  Then
install on production.  Besides that, I always wait for the cume PTF's
to be "seasoned" - I never order right them right away.  Not an option
with HIPERS, but that's just life.  If you don't do a *perm apply, you
can back them out.

I have to agree with the statement about the focus of the auditors on
this.  It's ridiculous beyond the extreme.  Our policy has a statement
to the effect that it is not feasible or cost effective to do QA on
vendor supplied software and we will rely on their testing.  

Have you shown them a list of PTF's included in a cume?  That may be a
reality check for them - or make your situation even worse!

Larry.Ketzes@xxxxxxx 09/07/2006 11:12:33 AM >>>

I am getting pounded by auditors on an issue, and I would like to know
what
other admin's are doing about this.  Our auditors are asking to see
testing
resulting from installing ptf's from IBM on our Production Servers.
Although I do have a test partition, I do not install every ptf I need
on
that partition first.  I do not have enough space on that partition for
all
testing of all applications just because I put on some ptf's!

What are other folks doing?  We do go through a change process procedure
that includes management approving the install of the ptf's.

Thanks, Larry

======================

Larry Ketzes
iSeries Senior System Administrator
American Life Insurance Company

One ALICO Plaza
600 King Street
Wilmington, DE 19801
Phone: 302-594-2146
Mobile: 302-559-1631

Fax: 302-830-4524


Email: larry.ketzes@xxxxxxx




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, September 07, 2006 2:06 PM
To: Midrange Systems Technical Discussion
Subject: RE: Verifying Existence of a File on a Server

I was afraid of that.  There's no way I'm going to ask my overworked 
system administrator to ensure everybody that can use this function

has 

an i.d. on the Windows server.

Ask your administrator for a single account on the Windows server -- one

that has access to the files you need to check for.  Create an iSeries 
profile with the same name and password as the Windows account.  When
you 
need to check existence, use the profile handle APIs to swap to that 
particular iSeries account, then check access, then swap back.  This way

all access to the Windows server is from that one particular ID.