Hello Ann,
I have been looking at your statements. Let me see if I have
this right.
You have a first level system that has two DASD 163C and 165F that you
want to make MDISKs on VMTEST.
MDISK 163C 3390 000 10017 LX163C MR
MDISK 165F 3390 000 3338 LX165F MR
But you get these messages when you logon to VMTEST
HCPLNM108E VMTEST 163C not linked; volid LX163C not mounted
HCPLNM108E VMTEST 165F not linked; volid LX165F not mounted
If you want to have user MDISK statements on VMTEST, you will
need these two volumes ATTACHed to the system.
ATT 163C SYSTEM LX163C
ATT 165F SYSTEM LX165F.
Then re-logon to VMTEST.
And you intend to have WVLNX30 run under VMTEST, right?
Your DED statement should have 163C on attached to WVLNX30 as 0A81 on
VMTEST only.
I hope I explained this well enough.
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 Anne Crabtree
> Sent: Friday, June 22, 2007 8:50 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: DASD second level
>
> I didn't quite state that right. I'm signed onto VMTEST on first
level
> when I did the queries. Linux directory entry is in USER DIRECT on
> VMTEST 191 and looks like this:
> USER WVLNX30 WVLNX30 512M 1024M G
> IPL CMS PARM AUTOCR
> IUCV ANY
> IUCV ALLOW
> MACHINE ESA
> SPECIAL 3000 HIPERS 3
> CONSOLE 009 3215 T
> SPOOL 00C 2540 READER *
> SPOOL 00D 2540 PUNCH A
> SPOOL 00E 1403 A
> LINK MAINT 190 190 RR
> LINK MAINT 19E 19E RR
> LINK MAINT 19F 19F RR
> LINK MAINT 19D 19D RR
> LINK TCPMAINT 198 198 RR
> LINK TCPMAINT 592 592 RR
> MDISK 191 3390 7981 050 510RST MR READ WRITE MULTIPLE
> DEDICATE 0A81 163C
> DEDICATE 067E 165F
>
> VMTEST's USER DIRECT on first level:
> USER VMTEST VMTEST 64M 128M BG
> MACHINE ESA 2
> OPTION TODENABLE
> ACCOUNT 1 VMTEST
> IPL CMS
> *HIPERSOCKETS
> DEDICATE 3000 920
> DEDICATE 3001 921
> DEDICATE 3002 922
> DEDICATE 3004 980
> DEDICATE 3005 981
> DEDICATE 3006 982
> * CTC TO 2ND LEVEL
> SPECIAL 2000 CTCA TCPIP
> SPECIAL 2001 CTCA TCPIP
> SPECIAL 400 3270
> SPECIAL 401 3270
> SPECIAL 402 3270
> SPECIAL 403 3270
> SPECIAL 404 3270
> SPECIAL 405 3270
> CONSOLE 009 3215 T
> SPOOL 00C 2540 READER *
> SPOOL 00D 2540 PUNCH A
> SPOOL 00E 1403 A
> LINK MAINT 0190 0190 RR
> LINK MAINT 019D 019D RR
> LINK MAINT 019E 019E RR
> MDISK 191 3390 217 0070 510W01 MR
> MDISK 163C 3390 000 10017 LX163C MR
> MDISK 165F 3390 000 3338 LX165F MR
>
> .
> .
> .
>
>
>
> Anne D. Crabtree
> System Programmer
> WV Dept of Administration - OT
> 304-558-5914 ext 8885
> Fax 304-558-1351
>
> >>> [EMAIL PROTECTED] 6/22/2007 8:44 AM >>>
> Based on the messages "not linked" it would seem you are not using
> DEDICATE statements in the Linux directory entries, but LINK
> statements.
> You would either need to change those statements, or attach those
> volumes to SYSTEM so that the link statements can work.
>
> David Wakser
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
> On
> Behalf Of Anne Crabtree
> Sent: Friday, June 22, 2007 8:40 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: DASD second level
>
> I have a directory entry VMTEST for a second level VM. (z/vm v5r1) I
> am
> trying to put a Linux guest on second level. I have DEDICATE
> statements
> for the dasd it needs but second level does not "see" this
> dasd:
>
> HCPLNM108E VMTEST 163C not linked; volid LX163C not mounted HCPLNM108E
> VMTEST 165F not linked; volid LX165F not mounted
>
> I've tried putting a MDISK statement for these in VMTEST directory
> entry
> and I've tried adding them to the User_Volume_List on second level.
> Neither has seemed to resolve the problem.
>
> On second level, if I 'q dasd' I don't see these volumes. However, if
> I
> do 'q 163c' I get this:
> q 163c
> Ready; T=0.01/0.01 08:34:02
> DASD 163C LX163C
>
> So, my question is: What is the correct way to "define" dasd so that
> second level VM can see it and Linux can "own" it?
>
>
>
>
>
>
> Anne D. Crabtree
> System Programmer
> WV Dept of Administration - OT
> 304-558-5914 ext 8885
> Fax 304-558-1351
