SEGGEN also makes "fn PSEGMAP" and "fn LSEGMAP". Maybe the HELPSEG segment is full and HELPSEG PSEGMAP, or HELP LSEGMAP may contain error messages. In the past I often had to issue the failing SEGGEN command manually to see what went wrong.
2008/2/14, Ivica Brodaric <[EMAIL PROTECTED]>: > Your problem is here: > > > > > > > > ST:BLDSEG : DMSGEN1279E Error(s) occurred during SEGGEN processing. > > > ST:BLDSEG : VMFBDS1965E The command, SEGGEN HELPSEG PSEG A SYSTEM SEGID > > > ST:D2 ( NOTYPE, failed > > > ST:BLDSEG : with return code 32 > > > Return code 32 from SEGGEN is not very helpful (and neither is NOTYPE > option). It could be many things, but my first guess would be that you don't > have current SYSTEM SEGID file on MAINT 490. If you rearrange segments, you > must always copy SYSTEM SEGID file to *both* MAINT 190 and MAINT 490. Second > guess is that 'HELPSEG PSEG A' file is not on BLDSEG's A disk (is it full?). > > Ivica > -- Kris Buelens, IBM Belgium, VM customer support
