× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks for the offer. I'll let "My Guy" at the cloud provider do it, just
want to make sure he agrees.

The ol' light bulb went on in Mr. Obvious head here. If I delete level 16
followed by UPDPTFINF prior to the IPL for MF99207 I won't have any issue.

Never run UPDPTFINF before. Is it a long running command?

Thanks.


On Tue, Dec 3, 2019 at 3:49 PM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Ok. Larry posted the steps earlier with more detail but basically you
delete the save file that has 16 in it. Then UPDPTFINF.

Now apply as normal.

I get the fear, if you want some help, I can assist tomorrow.

Jim Oberholtzer
Agile Technology Architects



On Dec 3, 2019, at 2:21 PM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

Jim - I'm sorry if I'm being dense and confused, but I am :)

I do SNDPTFORD, so no image catalog.

- both 16 and 17 are on my system as Not Applied
- DSPPTFCVR *NOTAPY shows *ONLY* MF99207 set to apply at IPL
- I cannot set any more to apply right now because I get "PTF
5770999-MF99207 V7R3M0 requires IPL"

Is this my course of action:

- Do an IPL so MF99207 applies
- then do INSPTF LICPGM((*ALL)) INSTYP(*DLYALL) which will get every
other
PTF set to apply
- do another IPL which will then do both level 16 and 17

I'm asking because in earlier emails both you and Larry said to NOT do
that
with both 16 and 17 there, then in this latest email you suggest because
17
is there, I'll be OK,

My system is in the cloud, so the cloud provider is in the loop. I'd
like
for this group and the cloud provider to agree.

Sorry to be so anal-retentive, but the stakes are pretty high.

Thanks.


On Tue, Dec 3, 2019 at 2:46 PM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

IF 17 is on already you should be past the problem entirely.

How to you apply these that it would be not applied? Did not IPL from
the
image catalog?

In any case, IPL and it should be OK because 17 is there.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jeff
Crosby
Sent: Tuesday, December 3, 2019 1:34 PM
To: Midrange Systems Technical Discussion <
midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: i7.3 DB Group 16 ** Do NOT Install **

How do I discard it? WRKPTFGRP and option 4=Delete it? I've never done
that before.

On Tue, Dec 3, 2019 at 2:11 PM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

Don't attempt to apply 16, that will cause issues. Discard it. Apply
17.

The only way 16 does not cause issues is if you are very current on
HIPER and DB groups to start with, mainly the HIPER. It's best just to
avoid it.

17 has the co/pre requisite table corrected so the process will work
as expected.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jeff Crosby
Sent: Tuesday, December 3, 2019 12:43 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: i7.3 DB Group 16 ** Do NOT Install **

Like you Paul I have both level 16 and 17 as Not Applied.

If I do DSPPTFCVR SELECT(*NOTAPY), those 2 level 16 PTFs do not show.

Do a:

DSPPTF LICPGM(5770SS1) SELECT(SI71241) DSPPTF LICPGM(5770SS1)
SELECT(SI71254)

and both show as Superseded.

I wonder if Larry still thinks it is dangerous to apply both 16 and 17
at the same time . . .



--


Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.