Re: Trying to build CMSBAM segment
Hi, I just got the same problem today. Never had before... I am in zVM530 rsu 1001 and I would like to know if a ptf was brought in a rsu ? Alain
Re: Trying to build CMSBAM segment
We use PP 5648-A25 IBM COBOL for OS/390 VM 2.2.0, and 5668-910 IBM OS PL/I OPTIMIZING COMPILER V2.R3.M0 -- but no VSAM. Yah, probably should have been a bit clearer. AFAIK, CMS VSAM was the only method of doing direct access or similar things with anything but C or Fortran (both C and Fortran used the native CMS facilities for that). Sequential stuff _usually_ worked w/the default segments shipped with VM, mostly because the compilers used OS simulation, not DOS, which doesn't use those segments.
Re: Trying to build CMSBAM segment
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
Re: Trying to build CMSBAM segment
Let us know if IBM has a new solution. I'm doing VM5.3 too and will hit CMSBAM build problem again at some point. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Harland, Lawrence Sent: Wednesday, November 21, 2007 7:58 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trying to build CMSBAM segment 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
Re: Trying to build CMSBAM segment
Maybe you've got some minidisks with lots of files then. At the other hand, when I migrate from one VM level to another, I keep my spool. And, I know CMSDOS co are seldom changed... So, my CMSDOS,BAM,AMSVSAM date from december 2002. We now run 5.2 2007/11/21, Harland, Lawrence [EMAIL PROTECTED]: 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
Re: Trying to build CMSBAM segment
Gee, I'm glad now I was in a hurry, and just copied these segments from z/VM 3.1.0 to z/VM 5.3.0. I missed a headache there! And now I know to try building them second-level before I do anything in production. Thanks guys!!! -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: November 21, 2007 08:27 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trying to build CMSBAM segment Maybe you've got some minidisks with lots of files then. At the other hand, when I migrate from one VM level to another, I keep my spool. And, I know CMSDOS co are seldom changed... So, my CMSDOS,BAM,AMSVSAM date from december 2002. We now run 5.2 2007/11/21, Harland, Lawrence [EMAIL PROTECTED]: 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: Trying to build CMSBAM segment
I'm now having a problem submitting the PMR. Get the following error. An error has occurred: * An error occurred accessing the database: CPR1 201 I'll try it again later today then just wait til after the weekend. Happy Thanksgiving Larry Harland
Re: Trying to build CMSBAM segment
Is this a known problem and does everyone have it? I am on z/VM 5.3 for about two weeks. Ran all the RSU and PTFS before testing. AFAIK, it really only affects people who need DOS/VS emulation or who still care about CMS VSAM. Ordinary CMS and Linux use of VM really doesn't invoke any of these segments in normal life. Of course, if you still use any compilers other than C/C++ or VS Fortran on CMS, you *do* care... *sigh*.
Re: Trying to build CMSBAM segment
Hello Everyone, Is this a known problem and does everyone have it? I am on z/VM 5.3 for about two weeks. Ran all the RSU and PTFS before testing. Ed Martin Aultman Health Foundation 330-588-4723 [EMAIL PROTECTED] ext. 40441
Re: Trying to build CMSBAM segment
Hello David, Thanks. I am on z/VM 5.3 and we are using VSE/VSAM for VM. It is required for the UltraQuest report product. Ed Martin Aultman Health Foundation 330-588-4723 [EMAIL PROTECTED] ext. 40441 -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, November 21, 2007 2:07 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trying to build CMSBAM segment Is this a known problem and does everyone have it? I am on z/VM 5.3 for about two weeks. Ran all the RSU and PTFS before testing. AFAIK, it really only affects people who need DOS/VS emulation or who still care about CMS VSAM. Ordinary CMS and Linux use of VM really doesn't invoke any of these segments in normal life. Of course, if you still use any compilers other than C/C++ or VS Fortran on CMS, you *do* care... *sigh*.
Re: Trying to build CMSBAM segment
We use PP 5648-A25 IBM COBOL for OS/390 VM 2.2.0, and 5668-910 IBM OS PL/I OPTIMIZING COMPILER V2.R3.M0 -- but no VSAM. After first copying SEGBLIST EXC0 as a backup to SEGBLIST -EXC (Never change anything IBM sends you without leaving a trail of bread crumbs), I've been manually deleting CMSBAM and CMSDOS from SEGBLIST EXC0 for ages. And then just manually purging their appropriate NSSes. I also mark them DELETED in SEGBLIST SEGDATA -- there's a VMFsomethingorother command to do that, but the upshot is: ... :OBJNAME.CMSBAM :DEFPARMS.DELETED :OBJNAME.CMSDOS :DEFPARMS.DELETED ... :OBJNAME.DOSINST :DEFPARMS.DELETED ... Again, no CMS VSAM other uses, and nothing has been complaining and they never need to be re-built after service because they are not in the SEGBLIST EXC0 (he says without thoroughly looking through what he has done for a long time). :-) Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. David Boyes [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 01:06 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Trying to build CMSBAM segment Is this a known problem and does everyone have it? I am on z/VM 5.3 for about two weeks. Ran all the RSU and PTFS before testing. AFAIK, it really only affects people who need DOS/VS emulation or who still care about CMS VSAM. Ordinary CMS and Linux use of VM really doesn't invoke any of these segments in normal life. Of course, if you still use any compilers other than C/C++ or VS Fortran on CMS, you *do* care... *sigh*. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.
Re: Trying to build CMSBAM segment
Larry, Your MAINT user id might not have enough storage enter DEF STOR 256M Before you IPL 190 Also you might try purging CMSBAM segment before trying to re define it. good luck Bill Munson VM System Programmer Office of Information Technology State of New Jersey (609) 984-4065 President MVMUA http://www.marist.edu/~mvmua Harland, Lawrence 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 Harland Univ. of Connecticut - ipl 190 clear parm nosprof instseg no z/VM V5.3.02007-10-18 14:00 acc (noprof Ready; T=0.01/0.01 09:57:07 acc 5e5 b Ready; T=0.01/0.01 09:57:17 ac 51d d Ready; T=0.01/0.01 09:57:20 vmfppf segbld esasegs VMFPPF2760I VMFPPF processing started for SEGBLD ESASEGS VMFOVE2760I VMFOVER processing started VMFOVE1954I Locating ESASEGS tag in file SEGBLD $PPF on disk D2 VMFOVE2760I VMFOVER processing completed successfully VMFPPF2760I VMFPPF processing completed successfully for SEGBLD ESASEGS VMFPPF2760I VMFPPF processing completed successfully Ready; T=0.36/0.40 09:58:05 vmfbld ppf segbld esasegs (status VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=1.63/1.71 09:58:54 vmfview build Ready; T=0.06/0.06 10:01:55 vmfbld list segbld esasegs dosbam blddata (all VMFBLD2767I Reading DOSBAM BLDDATA * for list of objects to process VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I New build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment CMSDOS VMFBDS2115I Validating segment CMSBAM VMFBDS2002I A DEFSEG command will be issued for 2 segment(s). VMFBDS2219I Processing object CMSDOS.SEGMENT HCPNSS440I Saved segment CMSDOS was successfully saved in fileid 0208. RDR FILE 0018 SENT FROM MAINT53 PRT WAS 0018 RECS 0444 CPY 001 A NOHOLD NOKEEP DMSWGN715I DOSGEN COMPLETE VMFBDS2219I Processing object CMSBAM.SEGMENT DMSDCS1083E Saved segment $$DMY$$ does not exist DMSSET1101I 100K DOS partition defined at hexadecimal location 02 DMSSGN363R ENTER LOCATION WHERE CMSBAM WILL BE LOADED AND SAVED: DMSSGN366R ENTER NAME OF SYSTEM TO BE SAVED: DMSDCS343E Storage in range 00B0D000-00B37FFF for CMSBAM in use. DMSSGN239E Cannot build segment. ReIPL CMS, ACCESS (NOPROF, and rebuild segment. VMFBDS1965E The command, $BAMGEN$ B0D000 CMSBAM, failed with return code 41 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=4.91/5.40 10:02:42 d t00B0D000-00B37FFF R00B0D000 F4 ** R00B0D010 to 00B0 suppressed line(s) same as above R00B1 to 00B1 suppressed line(s) same as above R00B2 to 00B2 suppressed line(s) same as above R00B3 to 00B37FFF suppressed line(s) same as above Ready; T=0.01/0.04 10:03:03
Re: Trying to build CMSBAM segment
welcome to the can't build CMSBAM club, been happening for at least 2 years, seems to have stumped IBM support since they recommend even now I continue to use this workaround. Quick, easy workaround is based on knowledge CMSBAM hasn't changed and doesn't really need to be rebuilt, so lie to VMSES as follows: on Vm5.3 MAINT 51D edit VM SRVBLDS, locate line that begins like :BLDLIST.SEGBLIST :OBJECT.CMSBAM.SEGMENT :STAT. and edit it to look like :STAT,BUILT.yy/mm/dd.hh:mm:ss.blurb :BLDLIST.SEGBLIST :OBJECT.CMSBAM.SEGMENT :STAT.BUILT.03/30/06.11:42:47.JOHNR If you used SERVICE command then on MAINT 191 there's a recent SERVICE RESTART? or something file with 1 or more records. If only 1 record that refers to CMSBAM then delete the file, else delete that line. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Harland, Lawrence Sent: Tuesday, November 20, 2007 3:25 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Trying to build CMSBAM segment 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 Harland Univ. of Connecticut - ipl 190 clear parm nosprof instseg no z/VM V5.3.02007-10-18 14:00 acc (noprof Ready; T=0.01/0.01 09:57:07 acc 5e5 b Ready; T=0.01/0.01 09:57:17 ac 51d d Ready; T=0.01/0.01 09:57:20 vmfppf segbld esasegs VMFPPF2760I VMFPPF processing started for SEGBLD ESASEGS VMFOVE2760I VMFOVER processing started VMFOVE1954I Locating ESASEGS tag in file SEGBLD $PPF on disk D2 VMFOVE2760I VMFOVER processing completed successfully VMFPPF2760I VMFPPF processing completed successfully for SEGBLD ESASEGS VMFPPF2760I VMFPPF processing completed successfully Ready; T=0.36/0.40 09:58:05 vmfbld ppf segbld esasegs (status VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=1.63/1.71 09:58:54 vmfview build Ready; T=0.06/0.06 10:01:55 vmfbld list segbld esasegs dosbam blddata (all VMFBLD2767I Reading DOSBAM BLDDATA * for list of objects to process VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I New build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment CMSDOS VMFBDS2115I Validating segment CMSBAM VMFBDS2002I A DEFSEG command will be issued for 2 segment(s). VMFBDS2219I Processing object CMSDOS.SEGMENT HCPNSS440I Saved segment CMSDOS was successfully saved in fileid 0208. RDR FILE 0018 SENT FROM MAINT53 PRT WAS 0018 RECS 0444 CPY 001 A NOHOLD NOKEEP DMSWGN715I DOSGEN COMPLETE VMFBDS2219I Processing object CMSBAM.SEGMENT DMSDCS1083E Saved segment $$DMY$$ does not exist DMSSET1101I 100K DOS partition defined at hexadecimal location 02 DMSSGN363R ENTER LOCATION WHERE CMSBAM WILL BE LOADED AND SAVED: DMSSGN366R ENTER NAME OF SYSTEM TO BE SAVED: DMSDCS343E Storage in range 00B0D000-00B37FFF for CMSBAM in use. DMSSGN239E Cannot build segment. ReIPL CMS, ACCESS (NOPROF, and rebuild segment. VMFBDS1965E The command, $BAMGEN$ B0D000 CMSBAM, failed with return code 41 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=4.91/5.40 10:02:42 d t00B0D000-00B37FFF R00B0D000 F4 ** R00B0D010 to 00B0 suppressed line(s) same as above R00B1 to 00B1 suppressed line(s) same as above R00B2 to 00B2 suppressed line(s) same as above R00B3 to 00B37FFF
Re: Trying to build CMSBAM segment
Actually John is correct and I remember it happening on z/VM 4 systems too, now that I recollect. This is a good reason to back up NSS's before doing any service. I know we have had to reload theses segments from backup many times. DOSBAM, CMSDOS and CMSBAM munson Romanowski, John (OFT) wrote: welcome to the can't build CMSBAM club, been happening for at least 2 years, seems to have stumped IBM support since they recommend even now I continue to use this workaround. Quick, easy workaround is based on knowledge CMSBAM hasn't changed and doesn't really need to be rebuilt, so lie to VMSES as follows: on Vm5.3 MAINT 51D edit VM SRVBLDS, locate line that begins like :BLDLIST.SEGBLIST :OBJECT.CMSBAM.SEGMENT :STAT. and edit it to look like :STAT,BUILT.yy/mm/dd.hh:mm:ss.blurb :BLDLIST.SEGBLIST :OBJECT.CMSBAM.SEGMENT :STAT.BUILT.03/30/06.11:42:47.JOHNR If you used SERVICE command then on MAINT 191 there's a recent SERVICE RESTART? or something file with 1 or more records. If only 1 record that refers to CMSBAM then delete the file, else delete that line. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Harland, Lawrence Sent: Tuesday, November 20, 2007 3:25 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Trying to build CMSBAM segment 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 Harland Univ. of Connecticut - ipl 190 clear parm nosprof instseg no z/VM V5.3.02007-10-18 14:00 acc (noprof Ready; T=0.01/0.01 09:57:07 acc 5e5 b Ready; T=0.01/0.01 09:57:17 ac 51d d Ready; T=0.01/0.01 09:57:20 vmfppf segbld esasegs VMFPPF2760I VMFPPF processing started for SEGBLD ESASEGS VMFOVE2760I VMFOVER processing started VMFOVE1954I Locating ESASEGS tag in file SEGBLD $PPF on disk D2 VMFOVE2760I VMFOVER processing completed successfully VMFPPF2760I VMFPPF processing completed successfully for SEGBLD ESASEGS VMFPPF2760I VMFPPF processing completed successfully Ready; T=0.36/0.40 09:58:05 vmfbld ppf segbld esasegs (status VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=1.63/1.71 09:58:54 vmfview build Ready; T=0.06/0.06 10:01:55 vmfbld list segbld esasegs dosbam blddata (all VMFBLD2767I Reading DOSBAM BLDDATA * for list of objects to process VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I New build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment CMSDOS VMFBDS2115I Validating segment CMSBAM VMFBDS2002I A DEFSEG command will be issued for 2 segment(s). VMFBDS2219I Processing object CMSDOS.SEGMENT HCPNSS440I Saved segment CMSDOS was successfully saved in fileid 0208. RDR FILE 0018 SENT FROM MAINT53 PRT WAS 0018 RECS 0444 CPY 001 A NOHOLD NOKEEP DMSWGN715I DOSGEN COMPLETE VMFBDS2219I Processing object CMSBAM.SEGMENT DMSDCS1083E Saved segment $$DMY$$ does not exist DMSSET1101I 100K DOS partition defined at hexadecimal location 02 DMSSGN363R ENTER LOCATION WHERE CMSBAM WILL BE LOADED AND SAVED: DMSSGN366R ENTER NAME OF SYSTEM TO BE SAVED: DMSDCS343E Storage in range 00B0D000-00B37FFF for CMSBAM in use. DMSSGN239E Cannot build segment. ReIPL CMS, ACCESS (NOPROF, and rebuild segment. VMFBDS1965E The command, $BAMGEN$ B0D000 CMSBAM, failed with return code 41 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=4.91/5.40 10:02:42
Re: Trying to build CMSBAM segment
Larry, I've had this problem for several releases of z/VM. My solution was to use the DIRATTR command to make the directories in the VMSYS:MAINT. filespace dircontrol, including the base direct directory. The MAINT userid must be MACHINE XC in the VM directory to use dircontrol directories. My understanding is that the FST for files in a dircontrol directory reside in a dataspace and not the user virtual storage. For me, this sufficiently rearranged the usage of MAINT's virtual storage, such that the problem no longer occurs. The SFS server must have XCONFIG statements to use dataspaces, which it does on a default install. Robert Hodge From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Harland, Lawrence Sent: Tuesday, November 20, 2007 1:25 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Trying to build CMSBAM segment 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 Harland Univ. of Connecticut - ipl 190 clear parm nosprof instseg no z/VM V5.3.02007-10-18 14:00 acc (noprof Ready; T=0.01/0.01 09:57:07 acc 5e5 b Ready; T=0.01/0.01 09:57:17 ac 51d d Ready; T=0.01/0.01 09:57:20 vmfppf segbld esasegs VMFPPF2760I VMFPPF processing started for SEGBLD ESASEGS VMFOVE2760I VMFOVER processing started VMFOVE1954I Locating ESASEGS tag in file SEGBLD $PPF on disk D2 VMFOVE2760I VMFOVER processing completed successfully VMFPPF2760I VMFPPF processing completed successfully for SEGBLD ESASEGS VMFPPF2760I VMFPPF processing completed successfully Ready; T=0.36/0.40 09:58:05 vmfbld ppf segbld esasegs (status VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=1.63/1.71 09:58:54 vmfview build Ready; T=0.06/0.06 10:01:55 vmfbld list segbld esasegs dosbam blddata (all VMFBLD2767I Reading DOSBAM BLDDATA * for list of objects to process VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I New build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment CMSDOS VMFBDS2115I Validating segment CMSBAM VMFBDS2002I A DEFSEG command will be issued for 2 segment(s). VMFBDS2219I Processing object CMSDOS.SEGMENT HCPNSS440I Saved segment CMSDOS was successfully saved in fileid 0208. RDR FILE 0018 SENT FROM MAINT53 PRT WAS 0018 RECS 0444 CPY 001 A NOHOLD NOKEEP DMSWGN715I DOSGEN COMPLETE VMFBDS2219I Processing object CMSBAM.SEGMENT DMSDCS1083E Saved segment $$DMY$$ does not exist DMSSET1101I 100K DOS partition defined at hexadecimal location 02 DMSSGN363R ENTER LOCATION WHERE CMSBAM WILL BE LOADED AND SAVED: DMSSGN366R ENTER NAME OF SYSTEM TO BE SAVED: DMSDCS343E Storage in range 00B0D000-00B37FFF for CMSBAM in use. DMSSGN239E Cannot build segment. ReIPL CMS, ACCESS (NOPROF, and rebuild segment. VMFBDS1965E The command, $BAMGEN$ B0D000 CMSBAM, failed with return code 41 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=4.91/5.40 10:02:42 d t00B0D000-00B37FFF R00B0D000 F4 ** R00B0D010 to 00B0 suppressed line(s) same as above R00B1 to 00B1 suppressed line(s) same as above R00B2 to 00B2 suppressed line(s) same as above R00B3 to 00B37FFF suppressed line(s) same as above Ready; T=0.01/0.04 10:03:03
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
Re: Trying to build CMSBAM segment
The problem with saving the DOS/BAM segments is because of two things: (1) The DOS/BAM segments are still below the 16M line. (2) The directory, (FSTs), for every accessed CMS disk or SFS directory are also still below the 16M line. VMFBLD accesses a lot of disks/directories so when it went to save the BA M segment, the storage was in use. It released the disks before exiting so that's why the storage appeared to no longer be in use, (your CP DISPLAY command). I never used VMSES to manage my shared segments, I had my one procedure that I developed before VMSES had code to manage/mangle segments. :-) I think the following steps will work, (but I don't have a system to test it with): ipl 190 clear parm nosprof access (noprof segment reserve cmsbam/* Do this before anything else! */ access 5e5 b access 51d d vmfppf segbld esasegs vmfbld ppf segbld esasegs (status vmfsetup zvm cms/* This may not be necessary, but shouldn't hurt */ segment release cmsbam/* has to be done before saving segs */ vmfbld list segbld esasegs dosbam blddata (all nosetup Hopefully, this will work, if not, I'll let know how I did it without VMSES, that always worked! :-) The NOSETUP option on the last VMFBLD i s required to prevent VMSES from accessing disks, that's why the VMFSETUP command may be required. The SEGMENT RESERVE command will keep CMS from using the storage area where the DOS/BAM segments reside. If the SEGMENT RESERVE command fails, then that means the storage area for the segments is already in use. Another way around this problem is to have a special CMS nucleus/NSS that IPLs at a lower address, (for example 5-8M). Back when there were other products that used segments below the 16M line, I used this special low CMS to allow me to save segments that were right below where the high version of CMS started. Without a low CMS, I would not have been able to save segments in the megabyte immediately below CMS. -- Dale R. Smith There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another theory which states that this has already happened. - Douglas Adams On Tue, 20 Nov 2007 15:24:42 -0500, 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 Harland Univ. of Connecticut - ipl 190 clear parm nosprof instseg no z/VM V5.3.02007-10-18 14:00 acc (noprof Ready; T=0.01/0.01 09:57:07 acc 5e5 b Ready; T=0.01/0.01 09:57:17 ac 51d d Ready; T=0.01/0.01 09:57:20 vmfppf segbld esasegs VMFPPF2760I VMFPPF processing started for SEGBLD ESASEGS VMFOVE2760I VMFOVER processing started VMFOVE1954I Locating ESASEGS tag in file SEGBLD $PPF on disk D2 VMFOVE2760I VMFOVER processing completed successfully VMFPPF2760I VMFPPF processing completed successfully for SEGBLD ESASEGS VMFPPF2760I VMFPPF processing completed successfully Ready; T=0.36/0.40 09:58:05 vmfbld ppf segbld esasegs (status VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD2180I There are 3 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=1.63/1.71 09:58:54 vmfview build Ready; T=0.06/0.06 10:01:55 vmfbld list segbld esasegs dosbam blddata (all VMFBLD2767I Reading DOSBAM BLDDATA * for list of objects to process VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I New build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment CMSDOS VMFBDS2115I Validating segment CMSBAM VMFBDS2002I A DEFSEG command will be issued for 2 segment(s). VMFBDS2219I Processing object CMSDOS.SEGMENT HCPNSS440I Saved segment CMSDOS was successfully saved in fileid 0208. RDR FILE 0018 SENT FROM MAINT53 PRT WAS 0018 RECS 0444 CPY 001 A NOHOLD NOKEEP DMSWGN715I DOSGEN COMPLETE VMFBDS2219I Processing object CMSBAM.SEGMENT DMSDCS1083E Saved segment $$DMY$$ does not exist DMSSET1101I 100K DOS partition defined at hexadecimal location 02 DMSSGN363R ENTER LOCATION
