> Well the PROFILE EXEC is always run and the swap 201/202 are always > defined. > The PROFILE checks if the userid is disconnected and if so assumes it needs > to boot linux with what we have as IPL 100. > The swap dasd definitely is there and shows up in "lsdasd" - its also in > fstab.
OK, so far so good. The disks are getting defined, but somehow SWAPGEN isn't getting to process them. Is it possible the code in PROFILE EXEC is bypassing the SWAPGEN step if the id is logged on? Another possibility: If the vdisk is already defined and you rerun SWAPGEN, you need to add the FORCE parm to have SWAPGEN overwrite an existing vdisk. It assumes for safety reasons that if the vdisk at the specified vaddr already exists, it's not supposed to write the swap signature unless you tell it explicitly to do so. That would explain why it works if you log the id off -- the disks wouldn't exist at that point. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
