Mazel tov! I've always used FORTGTZONES just because. Never dreamed of possible problems in omitting it. The idea of trying to give you 'everything' for an empty zone seems wickedly bizarre, but you have to play the same game as your opponent. Er, benefactor.
. . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Jürgen Kehr <kehrjuer...@t-online.de> To: IBM-MAIN@listserv.ua.edu Date: 06/14/2012 02:06 PM Subject: Re: Problem with SMP/E RECEIVE ORDER - SOLVED Sent by: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> Dear Kurt, good news, the FORTGTZONES parameter solved the problem. I didn't use it first, because there is only one target zone existing. But in some way, similar to what is described in APAR IO04020 there must be some more other FMIDs in GLOBAL, I didn't check for the details yet. So because there are in fact no PTFs in this (non-existing) target zone, SMP/E tries to collect ALL PTFs for these FMIDs, which leads to such a large amount of data. When I use the FORTGTZONES parameter, everything works as expected. From my point of view, from now on we will always use FORTGTZONES in future, because then we're sure not to receive unwanted PTFs for any additional (unused) FMID in GLOBAL zone. Thanks again for your comment. Am 14.06.2012 16:23, schrieb Kurt Quackenbush: >> ... AFAIK using parameters like >> FORFMID or EXCLUDE etc. will not help, because I think they are >> recognized after the package is transfered on the client side, what is >> too late here. > > Correct. FORTGTZONES however can be used to limit the scope of the > order, but this is only helpful if you have several different target > zones managed from your global zone. For your z/OS global zone, you > may only have one target zone, therefore, FORTGTZONES may not help. > >> So again my question is, is it possible to identify the very large PTFs >> somewhere to order them seperately? > > Unfortunately no, it is not possible for you to identify the culprits. > I dare say even for IBM it would not be a simple task to identify the > very large PTFs in your order. Certainly its not something Level 2 > can manage, and they would need to find the right people at the > production center to manually gather that information. > > In any case I agree with others that you should try to receive Java > PTFs separately, maybe also WebSphere/MQ if you have that, then try > RECOMMENDED again. > > Kurt Quackenbush -- IBM, SMP/E Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
