absolutely agree, my link list lib's are not SMS manged, but I'm the z/OS guy, some on the team are not sysprogs and allocate based on the vendor doc and my storage guy, likes to mis.... I mean manage everything, and they get burnt :( I just recently forwarded a health check issue to a teammate, her PDS was allocated with secondary space , SOMETIME THE VENDOR SUPPLIED in their allocation JCL, she got burnt because she compressed the library without knowing really what to do or without asking what to do first.
Carmen Vitullo ----- Original Message ----- From: "Steve Beaver" <[email protected]> To: [email protected] Sent: Tuesday, October 2, 2018 12:15:21 PM Subject: Re: S106 abends after copying into LINKLIST Never, ever let your LINKLST go into secondary's. Otherwise you will quickly learn how to Update your LNKLST dynamically. And never put your LNKLST datasets in SMS -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, October 2, 2018 12:10 PM To: [email protected] Subject: Re: S106 abends after copying into LINKLIST On Tue, 2 Oct 2018 15:34:44 +0000, Seymour J Metz wrote: >Alas, your allocation can still get another extent, but I'd prefer that nobody >explain how; >somebody might think that it was a good idea and cause the obvious problems. > Since I don't encourage integrity by obscurity, I'll ask the question that occurs to me. Can an overriding SPACE option in a DD statement allow allocation of a secondary extent to a data set initially allocated with zero secondary? >________________________________________ >From: I Carmen Vitullo >Sent: Monday, October 1, 2018 11:55 AM > >There's the key, in the allocation, if I allocate space for a linklist library >I DO NOT specify any secondary allocation, zero zilch! a secondary extend can >be taken to get my primary space if needed, but my PDS cannot get another >extend due to my initial allocation of 100,0 for example , SMS or not, (as >long as an SMS dataclass is not getting me in trouble) -- gil ---------------------------------------------------------------------- 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
