Hi Radoslaw, >From your description, I understand that TGT1 and TGT2 are at the same fix >level and that is a different fix level than TGT3.
Several questions - Is the product working properly in your TGT1 and TGT2 environments? Do you usually keep these three target zones at the same fix level? If yes, then you might want to consider cloning from TGT1 or TGT2 to TGT3. It is extremely rare that I would ever BYPASS HOLDERROR. Only if I had fully researched the the APAR and fully understood the possible impact of that particular PE. After you RECEIVE the resolving fix, the HOLDERROR will be satisfied, assuming that the fix goes on properly. HOLDERROR is there to protect your system from a known problem. Your particular system might not be affected by that problem, depending on what it is. What I would do, is let the HOLDERROR do its job, and keep the PE from APPLYing. If you usually have all three of these zones at the same level, you can bypass the SOURCID for your RSU maint, as well as what ever else you got with that order that is also not on TGT1 and TGT2. Is that a great idea? It depends. YMMV. If your environments are the same and you install to TGT3 so that it is the same, it is probably okay. Would I do that? I have done that successfully with my system and the product that I was working with at the time. Since you want to put the product in without an IPL and you were able to do that from TGT1 and TGT2, you might be able to do that with TGT3. Maybe not, maybe you would need to bounce another product too. It depends on what you have running. Review the results of your APPLY CHECK and take a good look at the action HOLDs. HOLDDATA should always be as current as possible. Suppose today you install something, it seems fine. 3 weeks from now, you RECEIVE the new HOLDDATA and let's just say there was no new service RECEIVEd. But when you run the APPLY CHECK, you get a HOLDERROR. That would mean that a problem had been found between the time you downloaded that last HOLDDATA and the more current set. Maybe you didn't have any problems. That HOLDERROR tries to keep us from discovering every problem ourselves. If you haven't used the FIXCATs yet, they are pretty cool. Both Marne Walle and Greg Daynes have given several presentations at SHARE that include good information on FIXCATs. HTH, Linda ----- Original Message ----- From: "Jan Jakubek" <[email protected]> To: [email protected] Sent: Friday, June 20, 2014 4:53:41 PM Subject: Re: SMPE problem RECEIVE the latest HOLDDATA (goes into GLOBAL only). I always do this before any maintenance. Run ERRORSYSMOD report against TGT1 & TGT2. I'm sure the same PE/s or APAR/s against the product FMID/s/base will show up on this report. The new HOLDDATA should tell you if there is a fix or there is not for above APAR/s. If no fixing PTF/s is/are available - APPLY the product on TGT3 with BYPASS HOLDERROR(id/s from above ERRORSYSMOD rpt). You know what the error/s is/are. If product is already in use - I'm sure you can live with this. Hth... -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of R.S. Sent: Friday, June 20, 2014 6:17 PM To: [email protected] Subject: SMPE problem My SMP/E CSI consist of GLOBAL zone and several pairs of DLIB/Target, let's name it DLIB1/TGT1, DLIB2/TGT2, DLIB3, TGT3. An IBM product, downloaded from ShopzSeries (indirectly, using PC) was RECEIVEd. The product was ordered with a service (PTFs), based of SMP/E report. It happened in begining of April (several weeks ago), time is important here. The product was APPLied on TGT1 and TGT2, it was immediately after RECEIVE. Note: TGT3 was not touched. Few weeks passed. Recently (2 weeks ago) a service (RSU) was ordered, downloaded and received. PTFs + current HOLDDATA. Now I'm trying to APPLY the product on TGT3. And I'm getting error, because some HOLDERROR occurs. I can order and download missing PTFs, but I worry the PTFs need more requisities and finally some of them would require IPL or other disruptive action. And I need to APPLY the product without IPL, because the IPL is scheduled in far future. It was possible to APPLY the product with no IPL on TGT1 and TGT2, before new service was downloaded. My ideas how to solve it: 1. Simply BYPASS HOLDERROR. I don't like it, especially I'm not sure about further results of such bypass. 2. Replace HOLDDATA with older one or just reject newest HOLDDATA. Is it possible? How? Any clue? Please advise. -- Radoslaw Skorupka Lodz, Poland --- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: [email protected] Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2014 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.696.052 złote. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
