Alan, SEGMENT RESERVE/RELEASE didn't help. A few more details. I defined vstor at 256m. We installed to mdisk, not SFS. I have backups of the old SDF files and can restore if necessary. We are running 5.1 and are trying to get to 5.3 since 5.1 is unsupported. I'll open a PMR with that information and provide the console listings.
Thanks, Larry -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, November 20, 2007 5:38 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trying to build CMSBAM segment On Tuesday, 11/20/2007 at 03:32 EST, "Harland, Lawrence" <[EMAIL PROTECTED]> wrote: > We are installing zVM 5.3 and need to recreate the CMSDOS and CMSBAM segments > on the current spool. I issued the following (results listed below) from the > Service Guide and received this error for CMSBAM: > > "DMSDCS343E Storage in range 00B0D000-00B37FFF for CMSBAM in use." > > I displayed storage for this range and it showed nothing in that area of > storage. > > We keep the same spool packs between releases and rename the segments. We > are using the default names for 5.3 so I thought this would be easy. I'm > trying this from the MAINT id on a second level 5.3 system. Any help on what > I might try or what I might be doing wrong would be appreciated. Larry, please open a PMR so that we can look at your problem in more detail. This usually shows up when you've installed into SFS - the memory occupied by file descriptors (FSTs) in the accessed directories is bumping into the memory used by CMSBAM. A possible workaround: Immediately after IPL CMS and ACC (NOPROF, try SEGMENT RESERVE CMSBAM. Then, right before you issue the VMFBLD for the segment, issue SEGMENT RELEASE CMSBAM. And add the NOSETUP option to VMFBLD. E.g. segment release cmsbam Ready; vmfbld list segbld esasegs dosbam blddata (all nosetup No guarantees, but worth a try. Alan Altmark z/VM Development IBM Endicott
