No, it's allocated exactly as it came from IBM.
Data Set Name . . . : SYS1.NUCLEUS
General Data Current Allocation
Volume serial . . . : TRES13 Allocated blocks . : 1,072
Device type . . . . : 3390 Allocated extents . : 1
Organization . . . : PO Maximum dir. blocks : 118
Record format . . . : U
Record length . . . : 0
Block size . . . . : 32760 Current Utilization
1st extent blocks . : 1072 Used blocks . . . . : 898
Secondary blocks . : 0 Used extents . . . : 1
Used dir. blocks . : 99
Number of members . : 578
Dates
Creation date . . . : 2011/11/18
Referenced date . . : 2014/03/04
Expiration date . . : ***None***
On Tue, Mar 4, 2014 at 10:37 AM, Jousma, David <[email protected]> wrote:
> You don't have SYS1.NUCLEUS allocated with secondary extents do you?
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Mark Pace
> Sent: Tuesday, March 04, 2014 9:54 AM
> To: [email protected]
> Subject: Re: Disabled wait
>
> Once I get the last of the maintenance I am working on applied, I'll go
> back and try to apply these again looking for any irregularities with
> SYS1.NUCLEUS.
>
>
> On Tue, Mar 4, 2014 at 9:25 AM, Staller, Allan <[email protected]
> >wrote:
>
> > UA69565 closes APAR OA42179
> > UA71730 closes APAR OA43690
> >
> > As of a few minutes ago, neither PTF was indicated as a PE.
> > I checked the cover letters for the z/OS 2.1 versions of those PTF's
> > (UA69566 and UA71731) and of the 2 I would consider UA71730 the most
> > likely culprit.
> >
> > I would check you apply run for failures during the application of
> > these PTF's, or bypass of a pre -req. Can you post the SMPOUT from your
> apply run?
> > I can't think of anything else that would cause this.
> >
> > <snip>
> > But through some slow application of maintenance I determined the 2
> > that PTFs that cause the DW are UA69565 and UA71730. I've no idea why
> > they cause an issue, but when I apply them I get the DW. To make it
> > even more odd is those PTFs are applied to other z/OS 1.13 systems I run.
> > </snip>
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to [email protected] with the message: INFO IBM-MAIN
> >
>
>
>
> --
> The postings on this site are my own and don't necessarily represent
> Mainline's positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to [email protected] with the message: INFO IBM-MAIN
>
> This e-mail transmission contains information that is confidential and may
> be privileged. It is intended only for the addressee(s) named above. If
> you receive this e-mail in error, please do not read, copy or disseminate
> it in any manner. If you are not the intended recipient, any disclosure,
> copying, distribution or use of the contents of this information is
> prohibited. Please reply to the message immediately by informing the sender
> that the message was misdirected. After replying, please erase it from your
> computer system. Your assistance in correcting this error is appreciated.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
The postings on this site are my own and don't necessarily represent
Mainline's positions or opinions
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
