An FYI from a z/VM 6.1 1002 system. listf vmlink * * (iso FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE TIME VMLINK EXEC S2 F 1024 304 76 2009-03-22 16:04:36 VMLINK SEXEC S2 V 130 4114 42 2009-03-20 14:17:09 Ready; T=0.01/0.01 10:59:38 vmlink maint 190 <+1 a-z rr> (type DMSACC048E Invalid filemode S Ready(02024); T=0.01/0.01 11:00:17
On Wed, Jun 9, 2010 at 10:51 AM, Frank M. Ramaekers <[email protected]>wrote: > Surprised, especially since my VMLINK EXEC is dated 2008-06-10: > > LISTFILE VMLINK EXEC * (ISO > > FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE > TIME > VMLINK EXEC S2 F 1024 304 76 2008-06-10 > 09:41:15 > Ready; T=0.01/0.01 09:49:23 > > execmap vmlink > > Name Type Usage Records Bytes Attribute > Segname > VMLINK EXEC 5 304 313784 SHARED > CMSINST > Ready; T=0.01/0.01 09:49:33 > > vmlink maint 190 <+1 a-z rr> (type > > DMSVML2060I MAINT 190 linked RR as 0001 file mode E > > Ready; T=0.01/0.01 09:49:51 > > LISTFILE VMLINK * * (ISO > > FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE > TIME > VMLINK NAMES A1 V 35 15 1 2009-08-19 > 14:47:57 > VMLINK EXEC E2 F 1024 304 76 2008-06-10 > 09:41:15 > VMLINK SEXEC E2 V 130 4114 42 2008-06-10 > 07:27:50 > VMLINK EXEC S2 F 1024 304 76 2008-06-10 > 09:41:15 > VMLINK SEXEC S2 V 130 4114 42 2008-06-10 > 07:27:50 > VMLINK NAMES X1 V 35 15 1 2009-08-19 > 14:47:57 > Ready; T=0.01/0.01 09:50:48 > > > Frank M. Ramaekers Jr. > > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[email protected]] On > Behalf Of Mike Walter > Sent: Wednesday, June 09, 2010 9:47 AM > To: [email protected] > Subject: Re: VMLINK behavior > > Could you issue a: LISTFILE VMLINK * * (ISO > and: EXECMAP VMLINK > right before issuing (again) that: vmlink maint 190 <+1 a-z rr> (type > > That would ensure that you have no other VMLINK EXEC somewhere in your > search order, > > I, too, am surprised that it would not be just as broken at 0903 as it > is > in 0901 and 1001. > > Mike Walter > Hewitt Associates > The opinions expressed herein are mine alone, not my employer's. > > > > "Frank M. Ramaekers" <[email protected]> > > Sent by: "The IBM z/VM Operating System" <[email protected]> > 06/09/2010 09:33 AM > Please respond to > "The IBM z/VM Operating System" <[email protected]> > > > > To > [email protected] > cc > > Subject > Re: VMLINK behavior > > > > > > > Really? I'm surprised that it fails in 0901 and 1001 but not in 0903? > > > Frank M. Ramaekers Jr. > > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[email protected]] On > Behalf Of Mike Walter > Sent: Wednesday, June 09, 2010 9:11 AM > To: [email protected] > Subject: Re: VMLINK behavior > > Not that it matters much since IBM will need to resolve it for every > release and RSU, but it happens here for: > z/VM 5.4.0 CP service level 0901 and 1001, with CMS Level 24 at service > > level 901 and 001 > > Mike Walter > Hewitt Associates > The opinions expressed herein are mine alone, not my employer's. > > > > "Frank M. Ramaekers" <[email protected]> > > Sent by: "The IBM z/VM Operating System" <[email protected]> > 06/09/2010 07:56 AM > Please respond to > "The IBM z/VM Operating System" <[email protected]> > > > > To > [email protected] > cc > > Subject > Re: VMLINK behavior > > > > > > > Does not work that way here: > > q search > MNT191 191 A R/W > MNT5E5 5E5 B R/W > - DIR C R/W VMSYSA:MAINT.CONFIG > MNT51D 51D D R/W > MNT190 190 S R/O > MNT19D 19D U R/O > DFS1B5 121 V R/O > - DIR W R/W VMSYSA:MAINT.SPECIAL > - DIR X R/W VMSYSA:MAINT.COMMON > MNT19E 19E Y/S R/O > TCM592 120 Z R/O > Ready; T=0.01/0.01 07:55:53 > vmlink maint 190 <+1 a-z rr> (type > DMSVML2060I MAINT 190 linked RR as 0001 file mode E > Ready; T=0.01/0.01 07:55:57 > q search > MNT191 191 A R/W > MNT5E5 5E5 B R/W > - DIR C R/W VMSYSA:MAINT.CONFIG > MNT51D 51D D R/W > MNT190 001 E R/O > MNT190 190 S R/O > MNT19D 19D U R/O > DFS1B5 121 V R/O > - DIR W R/W VMSYSA:MAINT.SPECIAL > - DIR X R/W VMSYSA:MAINT.COMMON > MNT19E 19E Y/S R/O > TCM592 120 Z R/O > Ready; T=0.01/0.01 07:56:22 > q cplevel > z/VM Version 5 Release 4.0, service level 0903 (64-bit) > Generated at 01/18/10 14:15:11 CDT > IPL at 02/07/10 16:48:22 CDT > Ready; T=0.01/0.01 07:56:32 > q cmslevel > CMS Level 24, Service Level 903 > Ready; T=0.01/0.01 07:56:35 > > > Frank M. Ramaekers Jr. > > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[email protected]] On > Behalf Of Alain Benveniste > Sent: Wednesday, June 09, 2010 3:32 AM > To: [email protected] > Subject: VMLINK behavior > > Hi, > > q disk > LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT > BLK TOTAL > OWN191 191 A R/W 100 3390 4096 315 4296-24 13704 > 18000 > DFS1B5 001 B R/O 50 3390 4096 142 7988-89 1012 > 9000 > TCM592 002 C R/O 56 3390 4096 902 10043-99 37 > 10080 > HID191 003 D R/O 50 3390 4096 67 3865-43 5135 > 9000 > HID201 004 E R/O 20 3390 4096 1068 3086-86 514 > 3600 > CMS65A 005 F R/O 25 3390 4096 656 1303-29 3197 > 4500 > VMR193 006 G R/O 25 3390 1024 67 714-06 11661 > 12375 > MNT190 190 S R/O 100 3390 4096 703 15296-85 2704 > 18000 > MNT19E 19E Y/S R/O 212 3390 4096 1817 38098-99 62 > 38160 > Ready; T=0.01/0.01 10:04:24 > > vmlink maint 19e <+1 a-z rr> (type > DMSVML2060I MAINT 19E linked RR as 019E file mode Y/S > > Ready; T=0.01/0.01 10:04:53 > q disk > LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT > BLK TOTAL > OWN191 191 A R/W 100 3390 4096 315 4296-24 13704 > 18000 > DFS1B5 001 B R/O 50 3390 4096 142 7988-89 1012 > 9000 > TCM592 002 C R/O 56 3390 4096 902 10043-99 37 > 10080 > HID191 003 D R/O 50 3390 4096 67 3865-43 5135 > 9000 > HID201 004 E R/O 20 3390 4096 1068 3086-86 514 > 3600 > CMS65A 005 F R/O 25 3390 4096 656 1303-29 3197 > 4500 > VMR193 006 G R/O 25 3390 1024 67 714-06 11661 > 12375 > MNT190 190 S R/O 100 3390 4096 703 15296-85 2704 > 18000 > MNT19E 19E Y/S R/O 212 3390 4096 1820 38098-99 62 > 38160 > Ready; T=0.01/0.01 10:05:05 > > vmlink maint 190 <+1 a-z rr> (type > DMSACC048E Invalid filemode S > > Ready(02024); T=0.01/0.01 10:06:42 > q disk > LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT > BLK TOTAL > OWN191 191 A R/W 100 3390 4096 315 4296-24 13704 > 18000 > DFS1B5 001 B R/O 50 3390 4096 142 7988-89 1012 > 9000 > TCM592 002 C R/O 56 3390 4096 902 10043-99 37 > 10080 > HID191 003 D R/O 50 3390 4096 67 3865-43 5135 > 9000 > HID201 004 E R/O 20 3390 4096 1068 3086-86 514 > 3600 > CMS65A 005 F R/O 25 3390 4096 656 1303-29 3197 > 4500 > VMR193 006 G R/O 25 3390 1024 67 714-06 11661 > 12375 > MNT19E 19E Y/S R/O 212 3390 4096 1820 38098-99 62 > 38160 > Ready; T=0.01/0.01 10: > > I agree with the first response of vmlink command. Not with the second. > I > lost my 190... I dare a question... why ? > > Regards > Alain Benveniste > > _____________________________________________________ > > This message contains information which is privileged and confidential > and > is solely for the use of the > > intended recipient. If you are not the intended recipient, be aware that > > any review, disclosure, > > copying, distribution, or use of the contents of this message is > strictly > prohibited. If you have > > received this in error, please destroy it immediately and notify us at > [email protected]. > > > > > > > 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. > > _____________________________________________________ > > This message contains information which is privileged and confidential > and > is solely for the use of the > > intended recipient. If you are not the intended recipient, be aware that > > any review, disclosure, > > copying, distribution, or use of the contents of this message is > strictly > prohibited. If you have > > received this in error, please destroy it immediately and notify us at > [email protected]. > > > > > > > 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. > > _____________________________________________________ > This message contains information which is privileged and confidential and > is solely for the use of the > intended recipient. If you are not the intended recipient, be aware that > any review, disclosure, > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > received this in error, please destroy it immediately and notify us at > [email protected]. > -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
