|
I'm not arguing the point for normal operations, but in this specific case, the PTFs would be on as *PERM for a few hours to a few days tops. 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 Al Barsa Sent: Thursday, April 28, 2005 8:48 AM To: Midrange Systems Technical Discussion Subject: RE: GO Save Option 21 When you come to a point that a *PERM applied PTF drives you into a bridge abutment, and you have to reload the entire OS, you won't take this so lightly anymore. Temp applied PTFs were an expensive luxury on the System/38 and early CISC boxes, IMHO they are just fine today. At one point or another, I have to invest the disk space (getting less and less expensive by the day), every time I save a reload of a current release (and I've personally done it 3 times) by removing a *TEMP applied PTF, I thank my lucky stars. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Jones, John \(US\)" <John.Jones@xxxxx To l.com> "Midrange Systems Technical Sent by: Discussion" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 04/28/2005 08:15 RE: GO Save Option 21 AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> You know, though, if you've been running at that PTF level for a while without any issues, and since in this case it's applying them perm immediately before an OS upgrade which should replace all that code anyway, I don't see any harm in doing the apply other than the downtime for the (probably necessary) IPL to do the apply. 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 MWalter@xxxxxxxxxxxxxxx Sent: Thursday, April 28, 2005 7:05 AM To: Midrange Systems Technical Discussion Subject: Re: GO Save Option 21 You're preaching to the choir, brother. But she's old school. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 04/27/2005 04:36 cc PM Subject Re: GO Save Option 21 Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> It's not only not necessary, it can be downright dangerous, but I've said enough on that on some of my recent posts. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com MWalter@xxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/27/2005 03:32 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: GO Save Option 21 That looks like the plan right now. We're planning our upgrade to V5R3, and I always like to get a 21 save before. Just in case. Plus my boss insists on applying all of the PTFs *perm before the upgrade. I don't think it's necessary any more, but I do what I'm told. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com Scott Klement <midrange-l@scott klement.com> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 04/27/2005 04:21 Subject PM Re: GO Save Option 21 Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Hi Mark, There's a field that you can set on the SAVE 21 screen to make it delay until a certain time. So, you could just sign on to the system console on Friday before you leave the office and tell it to wait. If that doesn't do the job, you can also edit the source code. Use RTVCLSRC on program QMNSAVE to get the source code, then you can add delays or whatever you need. (I wouldn't actually change the IBM-supplied object, but you could make your own copy and use that...) I don't know if it'll work as a batch job, or if it needs to be interactive -- but, at least for us, the system console can just be left on over the weekend, so we can set it up with a DLYJOB or two and then I don't have to make a special trip into the office. --- Scott Klement http://www.scottklement.com On Wed, 27 Apr 2005 MWalter@xxxxxxxxxxxxxxx wrote: > At V5R2, can GO SAVE option 21 be submitted as a batch job to QCTL? > I'd like to do a complete system save, then an IPL, but I don't want > to have to > come in on a Saturday Night at midnight. Who does? -- 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 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 the future then please respond to the sender to this effect. -- 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 the future then please respond to the sender to this effect.
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.
midrange.com
