|
Usually I run on side B and only permanently apply PTF just before putting up a new Cum CD. Or a new release. I see no problems running on the B side. Russ Popeil IBM Certified Specialist - RPG Programmer & AS/400 Sales Associate Avnet Computer - Integrated Solutions. Bottom-Line Results. Office: 516-677-9346, Fax: 516-677-0296, Beeper: 516-786-5846 eMail: Russ.popeil@avnet.com http://www.avnetcomputer.com -----Original Message----- From: Jim Welsh [mailto:jimwelsh@ix.netcom.com] Sent: Monday, July 06, 1998 10:03 PM To: MIDRANGE-L@midrange.com Subject: Managing PTF's...Strategy? You Guru's I'd like to start a discussion dealing with the management of PTF's and Client Access upgrades. My own thoughts on this are to keep current and perm apply after a week or so if all is well. IPLSRC A, B....? I've not been involved in operations that much as I've mainly been application programming for the last 10 years. Being in a two person shop now where the manager appears to know less than I do about *managing* the 400 I'd like some feedback on some *best practices* approaches... Is it normal to run off IPLSRC B everyday ? Is it not more effecient to perm apply your ptf's ? How many have been burned by a perm applied ptf that was bad ? What was the solution ? How about tape backup management, isn't it a bit risky to take backup tapes home with you escpecially when your not keeping them in a safe ? Everyplace else i've worked has had there tapes picked up by a service company ( not sure what exactly they do with them ) : ) I'd like to see the two of us run an organized shop with good practices in place but right now I think we have much room for improvement. I can't make these decisions but I can make suggestions. Perhaps after hearing about what others are doing I'll have even better suggestions to make. Oh where Oh where will I find a well managed IS dept... tia -- Jim I'm surprised anything works at all http://www.netcom.com/~jimwelsh/welcome/welcome.html mailto:jimwelsh@ix.netcom.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.