|
You know, by making the "e" small in cume, it illuminates the fact even moreso that the first three letters could be perceived as naughty by some. If you do a CHGIPLA to restricted *YES, you don't have to change startup programs. -- Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert - System i Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Larry Bolhuis Sent: Tuesday, June 27, 2006 8:25 AM To: Midrange Systems Technical Discussion Subject: Re: V5r4 Upgrade, IPL required between Cume and Group PTF installs The CUMe / IPL / Groups / IPL tactic will work always and is the safe way, albeit a tad longer. I think we can all agree on that. If you routinely apply each CUMe and occasionally adding HIPER and others between them, doing Groups / CUMe / IPL will not be a problem. If you wait a year or 18 months between PTFs though, you'd better go back to 'The Safe Way'. Here's a time saving tip to help speed up 'the safe way': Before the IPL to apply the CUMe, change sysval QSTRUPPGM to *NONE and CHGIPLA to NOT start TCP or Printers but YES to start to restricted state. On some systems this can save more than 30 minutes of starting things up and shutting them back down between Groups. When ready to IPL to apply the Groups then put these values back where you had them. - Larry rob@xxxxxxxxx wrote:
Did anyone suggest applying a group first before a cume? I didn't see
that. In theory, Tom, if you put on a cume but do not IPL, and then put on some groups then the prereq's and coreq's should be there. I do this on all cumes, after the first cume from the upgrade, and do not have any problems. However I still recommend putting on the cume, IPL, then groups, etc for immediately after an upgrade. Rob Berendt
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.