Dan, It does indeed appear from this that you are running on an 'A' side that is base V3R2 code. Cum package C8139320 (the TL98139) is not necessarily the only package that has been applied to this system, but none of the others shown on your list (other than the 'RE' PTF's that were part of V3R2 base code) show as Permanently Applied. (By the way, C8139320 was the LAST cum package issued for V3R2M0). We can tell that no previous cum packages were permanently applied to the A side because they all show Superseded, right back to TL96144 (cum package C6144320). If you had permanently applied previous cum packages the 'TL9nnnn' indicator PTF's would have show up as Permanently Applied, as TL97126 does in this example: Display PTF Status Syste Product ID . . . . . . : 5763999 IPL source . . . . . . : ##MACH#B Release . . . . . . . . : V3R2M0 Type options, press Enter. 5=Display PTF details 6=Print cover letter 8=Display cover PTF IPL Opt ID Status Action TL98139 Permanently applied None TL98048 Superseded None TL97322 Superseded None TL97231 Superseded None TL97126 Permanently applied None TL97063 Superseded None TL97014 Superseded None TL96317 Superseded None TL96282 Superseded None TL96233 Superseded None TL96219 Superseded None TL96191 Superseded None TL96165 Superseded None TL96144 Superseded None RE96102 Permanently applied None You need to scroll through the list to see if any of the 'MF' PTF's show as Permanently applied. They are the only ones that would be active when IPL'd from the 'A' side. I think there was also a question about group PTF's. These are refreshed on a regular basis so you always get the latest PTF's for a particular area (like Database, Fax, etc.). These PTF's may make their way onto a future cumulative PTF package, but they are more current. For example, you should have Database group PTF SF99105 available to apply after upgrading to V4R5. In some cases (like the Y2K fixes for V3R2) there were no future cumulative PTF's packages planned for that release, so the PTF's in the Group PTF package would never appear on a cum PTF package. As to whether you can apply additional PTF's at the same time as the cumulative PTF package, read the instructions for the cumulative package to see if that is allowed. Sometimes you are instructed to apply the cumulative package (OR maybe selected PTF/s from it) before applying additional PTF's. This usually occurs when there are PTF's to fix issued with the PTF application process itself. Neil Palmer DPS Data Processing Services Canada Ltd. 50 Acadia Avenue, Ste.102 AS/400~~~~~ Markham, Ontario, Canada. ____________ ___ ~ Phone:(905) 474-4890 x303 |OOOOOOOOOO| ________ o|__||= Cell.:(416) 565-1682 x303 |__________|_|______|_|______) Fax: (905) 474-4898 oo oo oo oo OOOo=o\ mailto:NeilP@DPSlink.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://www.DPSlink.com iSeries 400 The Ultimate Business Server D.BALE@handleman.com Sent by: firstname.lastname@example.org 2001/04/04 16:09 Please respond to MIDRANGE-L To: MIDRANGE-L@midrange.com cc: Subject: IPL source: ##MACH#A - Uh oh! After creating my original post on the cume & group PTFs, I came across an interesting (?) situation on our V3R2 development box. DSPPTF shows: Product ID . . . . . . : 5763999 IPL source . . . . . . : ##MACH#A Release . . . . . . . . : V3R2M0 Type options, press Enter. 5=Display PTF details 6=Print cover letter 8=Display cover PTF IPL Opt ID Status Action _ TL98139 Temporarily applied None _ TL98048 Superseded None _ TL97322 Superseded None _ TL97231 Superseded None _ TL97126 Superseded None _ TL97063 Superseded None _ TL97014 Superseded None _ TL96317 Superseded None _ TL96282 Superseded None _ TL96233 Superseded None _ TL96219 Superseded None _ TL96191 Superseded None _ TL96165 Superseded None _ TL96144 Superseded None _ RE97230 Permanently applied None _ RE96102 Permanently applied None _ MF19696 Save file only None _ MF18809 Temporarily applied None etc.... Note that the last IPL source shows ##MACH#A. If I interpret correctly that the TL* entries are the cume PTFs, would it not appear that this box is currently running on a totally non-cume'd bare V3R2 OS? No one here has any idea how long this box has been running in ##MACH#A; most likely since cume 98139 was applied. I suppose I should IPL to ##MACH#B and run that for a week or so before installing the latest/last cume (subject to the question of whether I should even bother - see last post). Again, all useful advice solicited. Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 D.Bale@Handleman.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) +--- | 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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.