You need to tel DIRMAINT how big your emulated 9336 is in EXTENT CONTROL. DIRM SEND EXTENT CONTROL RDRLIST/RECEIVE/XEDIT DIRM FILE EXTENT CONTROL DIRM RLDE
Kris, IBM Belgium, VM customer support > I'm attempting some things and was hoping someone else out there has done > this before. Now, first of all, I know IBM recommends connecting Open > systems data directly to the linux image. BUT, what we have is a 50gig lun > and the system coming in will require only 5gig, maybe at most a max of > 10gig. I do NOT want to waste this lun. SO, what I'm attempting is to > emulate this device under vm, tried to use DIRM AMDISK commands to assign > what I need from it but this doesn't work due to it not being in EXTENT > CONTROL. Can't seem to add it there as 9336 isn't understood. So I did a > DIRM for LINUX3 get lock, updated it manually, and did a DIRM replace > thinking I'll keep track of it manually. It took it but NOT all the cyls > seem to show. I later found out that my allocation appears to be in blocks, > NOT cyls and when I boot the image and use YAST to format it, YAST comes > back with a failed message exit code 0. I've put some info below to help, > but I guess the main question is can I take this lun and then somehow give > different linux images large chunks of it? Otherwise it seems I have to > waste the entire amount on one image. > cp set edev 5702 ty fba attr 2105 fcp_dev f100 wwpn xxxxxxxxxxxxxxxx lun > xxxxxxxxxxxxxxxx > cp vary on 5702 > cp attach 5702 maint > I then did a CPFMTXA 0 to end. Format was in pages I noticed. > Detached it from maint and attached it to system. > q 5702 > DASD 5702 CP SYSTEM BIGBOY 1 > q edev 5702 > EDEV 5702 TYPE FBA ATTRIBUTES 2105 > q edev 5702 details > EDEV 5702 TYPE FBA ATTRIBUTES 2105 > PATHS: > FCP_DEV: F100 WWPN: xxxxxxxxxxxxxxxx LUN: xxxxxxxxxxxxxxxx > > q dasd details 5702 > 5702 CUTYPE = 6310-80, DEVTYPE = 9336-10, VOLSER = BIGBOY, CYLS = 125683 > BLKS = 97656256 > > This is the minidisk line I added to linux2 direct file. > MDISK 0104 9336 1 6676 BIGBOY > And what a dirm dirmap shows after I did the dirm replace. > BIGBOY 9336 0 0 1 Gap > LINUX3 0104 * 1 6676 6676 > 6677 920114 913438 Gap > > The 913438 + 6676 is far short of the 125683 shown under q dasd details. > Brian W. France > Systems Administrator (Mainframe) > Pennsylvania State University > Administrative Information Services - Infrastructure/Sysarc > Rm 25 Shields Bldg., University Park, Pa. 16802 > 814-863-4739 > [EMAIL PROTECTED]
