RE: PTF's Installed on Production Servers

We provide auditors with the OS level for each LPP (print screen from GO
LICPGM/10).  When they ask about updates, we provide a fresh screen
print.  Compared to the previous year/audit, it will show if the OS
version has changed.  If it has we provide the change management record
as well.  PTFs aren't a factor. 

That said, as a JDE shop, if pressed for PTF details we can point to the
IBM/Oracle APAR that notes current recommended PTF levels, which is
always the latest & greatest.  So we have vendor doc showing the app is
supported with our fix levels.  No testing required on our end.  And I
do a change management record when doing group PTFs.  The test plan is
basically "vendor has tested this release."

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ketzes, Larry
Sent: Thursday, September 07, 2006 1:13 PM
To: Midrange Systems Technical Discussion
Subject: PTF's Installed on Production Servers

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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
 
 

This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.