Re: SEGGEN failure
On the advice of a respected member of the list, I tried adding a LOT of virtual storage to MAINT, but even with 512M I get the same result. This makes sense, since the error message is not mentioning any problem loading the content of the segment. This is happening in VMFBDSEG EXEC at lines 2169-2170. The first is the SEGMENT RESERVE command, the second is the invocation of SEGGEN MODULE, which fails. Just for fun I commented out the RESERVE, since SEGGEN is apparently complaining about it, but (no surprise!) SEGGEN did not work then either. The difference was that there was no message explaining WHY it failed. So, here I am stuck, even with 512M, and no segment being built. Oh, the details of the segment are the defaults, 3M beginning at 20M: cp q nss name instseg map FILE FILENAME FILETYPE MINSIZE BEGPAG ENDPAG TYPE CL #USERS PARMREGS VMGROUP 0005 INSTSEG DCSS N/A01400 016FF SR A 00021 N/A N/A 0074 INSTSEG DCSS N/A01400 016FF SR S 0 N/A N/A And catching the SEGMENT RESERVE with an interactive trace, shows: 'QUERY SEGMENT *' Space Name Location LengthLoaded Attribute INSTSEG INSTSEG 0140 0030 NO USER Any ideas? ! ! ! NEWS FLASH ! ! != For some reason I happened to look at CMSINST LSEGMAP D on the 51D disk, and *IT* had the answer to the problem!!! One of the files I had listed in the build list for the segment was a mistake, and did not exist! So, instead of nicely putting out a RC=28 and saying the file was missing, it hid this message in a file NOT on my A-disk, and expected me to guess the problem. :-( Anyway, I made that correction, and then just for fun I reset storage to 64M before the build. It worked fine! Oh... the message about the segment already being reserved is a red herring, I got that message on the successful run too! VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved HCPNSS440I Saved segment INSTSEG was successfully saved in fileid 0076. VMFBLD1851I (1 of 1) VMFBDSEG completed with return code 0 VMFBLD2180I There are 0 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=3.73/4.02 12:17:07 So I sent all this to the list in case someone else also gets these messages: DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 Thank you all kindly for your attention :-) Shimon
Re: SEGGEN failure
Search your A-disk for LSEGMAP and PSEGMAP files, they may tell the segment storage is full. VMSES's SEGGEN usage is an area for improvement: all debugging information is missing. 2009/3/17 Shimon Lebowitz shimon...@gmail.com: On the advice of a respected member of the list, I tried adding a LOT of virtual storage to MAINT, but even with 512M I get the same result. This makes sense, since the error message is not mentioning any problem loading the content of the segment. This is happening in VMFBDSEG EXEC at lines 2169-2170. The first is the SEGMENT RESERVE command, the second is the invocation of SEGGEN MODULE, which fails. Just for fun I commented out the RESERVE, since SEGGEN is apparently complaining about it, but (no surprise!) SEGGEN did not work then either. The difference was that there was no message explaining WHY it failed. So, here I am stuck, even with 512M, and no segment being built. Oh, the details of the segment are the defaults, 3M beginning at 20M: cp q nss name instseg map FILE FILENAME FILETYPE MINSIZE BEGPAG ENDPAG TYPE CL #USERS PARMREGS VMGROUP 0005 INSTSEG DCSS N/A01400 016FF SR A 00021 N/A N/A 0074 INSTSEG DCSS N/A01400 016FF SR S 0 N/A N/A And catching the SEGMENT RESERVE with an interactive trace, shows: 'QUERY SEGMENT *' Space Name Location LengthLoaded Attribute INSTSEG INSTSEG 0140 0030 NO USER Any ideas? ! ! ! NEWS FLASH ! ! != For some reason I happened to look at CMSINST LSEGMAP D on the 51D disk, and *IT* had the answer to the problem!!! One of the files I had listed in the build list for the segment was a mistake, and did not exist! So, instead of nicely putting out a RC=28 and saying the file was missing, it hid this message in a file NOT on my A-disk, and expected me to guess the problem. :-( Anyway, I made that correction, and then just for fun I reset storage to 64M before the build. It worked fine! Oh... the message about the segment already being reserved is a red herring, I got that message on the successful run too! VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved HCPNSS440I Saved segment INSTSEG was successfully saved in fileid 0076. VMFBLD1851I (1 of 1) VMFBDSEG completed with return code 0 VMFBLD2180I There are 0 build requirements remaining VMFBLD2760I VMFBLD processing completed successfully Ready; T=3.73/4.02 12:17:07 So I sent all this to the list in case someone else also gets these messages: DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 Thank you all kindly for your attention :-) Shimon -- Kris Buelens, IBM Belgium, VM customer support
Re: SEGGEN failure
Shimon, VMSES/E is a great tool, but the clarity is not quite the best at some times It seems that error message from building segments is a particular weak point to me, too. One command that has helped me understand VMSES/E a lot better (until I forget again!) is one I use after any VMSES/E command failure, and when trying to better understand what files it has just changed: LISTFILE * * * (TODAY If you are (perhaps rightly) concerned about changed files on disk that are no longer accessed, but still LINKed, then the FILEFILE EXEC which I've posted here before can perform the same quick search function on even those disks not currently accessed via: FINDFILE * * * (TODAY ISO All the changed files (on accessed disks) will show right up, making the detective work somewhat less tedious. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. 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. E-mails 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 e-mail.
Re: SEGGEN failure
On Tuesday, 03/17/2009 at 11:01 EDT, Mike Walter mike.wal...@hewitt.com wrote: VMSES/E is a great tool, but the clarity is not quite the best at some times It seems that error message from building segments is a particular weak point to me, too. Please report problems with servicing/installing z/VM to the Support Center. If there is message whose documentation is unclear or there is no way to determine the cause of an error, we need to know. Alan Altmark z/VM Development IBM Endicott
Re: SEGGEN failure
Yes, note SEGGEN, it has been painful since day one. I no longer had problems since the day I had my own front-end (BLDSEG EXEC), it releases most minidisks and segments 'PIPE (end ?)', 'Command QUERY ACCESSED|Drop 1', '| NFind S|NFind Y|NFind A|NFind B|NFind D'||, '| Spec W4 1 1-* 5', '|F: Find DIR|Spec /ACCESS/ 1 W6 nw W2 nw', '|J: Faninany |STEM ACC.|SPEC /RELEASE/ 1 W3 nw.1|COMMAND|CONS', '?F:|Spec /ACCESS/ 1 W1 nw W2 nw|J:' /* Can not execute drops and releases from within pipe as we destroy PIPE itself... */ 'PIPE (end ?) COMMAND NUCXMAP|DROP|NFIND EAGRTPRC|NFIND CMSRTPRC', '|NFIND LINEWRT|NFIND TYPLIN' ||, '|SPECS /NUCXDROP/ 1 W1 NW|STACK', '?COMMAND QUERY SEGMENT|DROP 1|NFIND REXX370', '|SPEC /SEGMENT RELEASE/ 1 W2 NW|STACK' do queued() ; parse pull cmd ; say cmd ; cmd ; end ... at the end: 'PIPE STEM ACC.|COMMAND|CONS' 2009/3/17 Alan Altmark alan_altm...@us.ibm.com: On Tuesday, 03/17/2009 at 11:01 EDT, Mike Walter mike.wal...@hewitt.com wrote: VMSES/E is a great tool, but the clarity is not quite the best at some times It seems that error message from building segments is a particular weak point to me, too. Please report problems with servicing/installing z/VM to the Support Center. If there is message whose documentation is unclear or there is no way to determine the cause of an error, we need to know. Alan Altmark z/VM Development IBM Endicott -- Kris Buelens, IBM Belgium, VM customer support
SEGGEN failure
I am trying to rebuild CMSINST, following the directions in 3.17.1 Rebuild the Saved Segments of the 5.3.0 service guide. I 190 CL parm nosprof instseg no AC ( NOPROF AC 5E6 B AC 51D D vmfbld ppf segbld esasegs segblist instseg type (serviced VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 1 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=3.73/3.98 21:13:33 The reason I added the type option, was the advice in the manual for catching errors, and in fact, that line about already reserved was what showed up. So I ran through the steps again, and added Q SEGMENT * after the two ACCesses, before running vmfbld. The result was: q segment * DMSDCT357I No segment spaces exist Ready(00028); T=0.01/0.01 21:16:19 vmfbld ppf segbld esasegs segblist instseg type (serviced VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 1 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=3.67/3.90 21:16:49 So, why does it say already reserved if it isn't? Help, anybody? Thanks very much!! Shimon
Re: SEGGEN failure
Shimon, problem 1 do a Q NSS and you will find an instesg that has been defined/reserved you will need to delete that one before you try it again problem 2 what ever you changed in your instseg has made it too large to load in the instseg space you are defining/reserving. you will need to enlarge the defseg for instseg but I do not remember off hand how to do it. I am sure you can do it from the VMF segment panel screens good luck Bill Munson Sr. z/VM Systems Programmer Brown Brothers Harriman CO. 525 Washington Blvd. Jersey City, NJ 07310 201-418-7588 President MVMUA http://www2.marist.edu/~mvmua/ Shimon Lebowitz shimon...@gmail.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/16/2009 03:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject SEGGEN failure I am trying to rebuild CMSINST, following the directions in 3.17.1 Rebuild the Saved Segments of the 5.3.0 service guide. I 190 CL parm nosprof instseg no AC ( NOPROF AC 5E6 B AC 51D D vmfbld ppf segbld esasegs segblist instseg type (serviced VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 1 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=3.73/3.98 21:13:33 The reason I added the type option, was the advice in the manual for catching errors, and in fact, that line about already reserved was what showed up. So I ran through the steps again, and added Q SEGMENT * after the two ACCesses, before running vmfbld. The result was: q segment * DMSDCT357I No segment spaces exist Ready(00028); T=0.01/0.01 21:16:19 vmfbld ppf segbld esasegs segblist instseg type (serviced VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 1 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=3.67/3.90 21:16:49 So, why does it say already reserved if it isn't? Help, anybody? Thanks very much!! Shimon *** IMPORTANT NOTE* The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman Co., its subsidiaries and affiliates (BBH). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus.
Re: SEGGEN failure
Shimon, Look in appendix E of the Service Guide. munson 201-418-7588 Shimon Lebowitz shimon...@gmail.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/16/2009 03:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject SEGGEN failure I am trying to rebuild CMSINST, following the directions in 3.17.1 Rebuild the Saved Segments of the 5.3.0 service guide. I 190 CL parm nosprof instseg no AC ( NOPROF AC 5E6 B AC 51D D vmfbld ppf segbld esasegs segblist instseg type (serviced VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 1 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=3.73/3.98 21:13:33 The reason I added the type option, was the advice in the manual for catching errors, and in fact, that line about already reserved was what showed up. So I ran through the steps again, and added Q SEGMENT * after the two ACCesses, before running vmfbld. The result was: q segment * DMSDCT357I No segment spaces exist Ready(00028); T=0.01/0.01 21:16:19 vmfbld ppf segbld esasegs segblist instseg type (serviced VMFBLD2760I VMFBLD processing started VMFBLD1851I Reading build lists VMFBLD2182I Identifying new build requirements VMFBLD2182I No new build requirements identified VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC0 D, target is BUILD 51D (D) VMFBDS2115I Validating segment INSTSEG VMFBDS2002I A DEFSEG command will be issued for 1 segment(s). VMFBDS2219I Processing object INSTSEG.SEGMENT DMSDCS358E Skeleton segment INSTSEG has already been reserved DMSGEN1279E Error(s) occurred during SEGGEN processing. VMFBDS1965E The command, SEGGEN INSTSEG PSEG A SYSTEM SEGID D2 ( TYPE, failed with return code 32 VMFBLD1851E (1 of 1) VMFBDSEG completed with return code 100. Some objects were not built VMFBLD2180I There are 1 build requirements remaining VMFBLD2760I VMFBLD processing completed unsuccessfully Ready(8); T=3.67/3.90 21:16:49 So, why does it say already reserved if it isn't? Help, anybody? Thanks very much!! Shimon *** IMPORTANT NOTE* The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman Co., its subsidiaries and affiliates (BBH). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus.
