It all depends on if you have DirMaint up and running, or you’re still working from your original source directory.
From the source directory, run dirmap (I think; I no longer have a system to try on…) to map out the space on your volumes. On the volume where 500 is now, there’s likely free space at the end. Note the starting cylinder, and then go edit the source directory. Find your 500 minidisk. Duplicate the line, and change the address to 1500. Find the starting cylinder for the minidisk, and change it to the free one you found above. Change the minidisk size to the desired size. Save the file. Use DIRECTXA to put the source directory online. Link and format the new minidisk. Copy the contents of the old 500 to the new minidisk. Then go in to the source directory again, change 1500 to 500, and 500 to 1500. Put this directory online, and try deterse again to set up your maintenance. If all went well, then go back into your source directory yet again, and remove the MDISK statement that points to the old space, and put this online. -- Robert P. Nix | Sr IT Systems Engineer | Data Center Infrastructure Services 507-284-0844 | [email protected] <applewebdata://7C28AA03-E9D7-4519-A679-80B7EC6A010B/[email protected]> Mayo Clinic| 200 First Street SW | Rochester, MN 55905 Mayo Clinic, a mission-driven worldwide leader in health care for 150 years. http://150years.mayoclinic.org/ On 11/17/14, 3:27 PM, "Chu, Raymond" <[email protected]> wrote: >I love this idea. However, I am still learning z/VM system. If possible, >could you please show the steps. > >Thanks, >Ray > > > > >-----Original Message----- >From: Linux on 390 Port [mailto:[email protected]] On Behalf Of >Nix, Robert P. >Sent: Monday, November 17, 2014 4:15 PM >To: [email protected] >Subject: Re: Ran out of space when applying RSU > >Email sent from outside of PSEG. Use caution before using >links/attachments. > > >If you don¹t want to move the file(s) out of 500, what¹s the issue with >relocating 500 and making it bigger? I had to do that with several of the >default disks on systems throughout the years, and never ran into any >huge issues. > >Make a new, larger disk. Copy the contents of the old disk to the new >disk. Switch around the entries in the directory entry, and you have a >shiny new 500 minidisk that will hold the files you need it to hold. >-- >Robert P. Nix | Sr IT Systems Engineer | Data Center Infrastructure >Services >507-284-0844 | [email protected] ><applewebdata://7C28AA03-E9D7-4519-A679-80B7EC6A010B/[email protected]> >Mayo Clinic| 200 First Street SW | Rochester, MN 55905 > >Mayo Clinic, a mission-driven worldwide leader in health care for 150 >years. >http://150years.mayoclinic.org/ > > > > > >On 11/17/14, 3:04 PM, "Hodge, Robert L" <[email protected]> wrote: > >>It is RSU 1401. >> >>-----Original Message----- >>From: Linux on 390 Port [mailto:[email protected]] On Behalf Of >>Chu, Raymond >>Sent: Monday, November 17, 2014 2:00 PM >>To: [email protected] >>Subject: EXTERNAL: Re: Ran out of space when applying RSU >> >>It came with the z/VM installation. I ran the "q cplevel" command and >>had the following >> >>q cplevel >>z/VM Version 6 Release 3.0, service level 1302 (64-bit) Generated at >>08/07/13 11:42:58 UTC >> >>What I have now is second RSU in the year 2013. If I interpret >>"6302RSU1² correctly, it should be V6.3 Second RSU but do not know the >>year. >> >> >>-----Original Message----- >>From: Linux on 390 Port [mailto:[email protected]] On Behalf Of >>Dave Jones >>Sent: Monday, November 17, 2014 3:45 PM >>To: [email protected] >>Subject: Re: Ran out of space when applying RSU >> >>Email sent from outside of PSEG. Use caution before using >>links/attachments. >> >> >>Hi, Ray. >> >>Have you already applied the 630RSU1 to the system? If you have, then >>you can delete it from the 500 mdisk. >> >>Have a good one, too. >> >>DJ >> >>On 11/17/2014 02:29 PM, Chu, Raymond wrote: >>> Hi, >>> >>> This is the first time to apply RSU after having a z/VM SSI Cluster >>> system successfully built. When I logged on as maint630 and ran >>> several commands as shown below: >>> >>> q disk LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) >>> BLKS LEFT BLK TOTAL MNT191 191 A R/W 175 3390 4096 36 >>> 242-01 31258 31500 MNT5E6 5E6 B R/W 9 3390 4096 >>> 134 1304-80 316 1620 MNT500 500 C R/W 1200 >>> 3390 4096 1 97057-45 118943 216000 MNT51D 51D D >>> R/W 26 3390 4096 297 1823-39 2857 4680 >>> PMT551 551 E R/W 40 3390 4096 10 119-02 7081 >>> 7200 MNT190 190 S R/O 207 3390 4096 696 18085-49 >>> 19175 37260 MNT19E 19E Y/S R/O 500 3390 4096 1124 >>> 30404-34 59596 90000 Ready; T=0.01/0.01 20:16:42 >>> >>> listf * * c 6302RSU1 SERVLINK C1 >>> >>> The Maint630.500 has already been 45% full. I uploaded just one RSU >>> (RPTF01 servlink) and both of them occupied 79% full. Attempted to >>> run this "deterse RPTF01 SERVLINK C = = = (replace" command and the >>> disk >>> 500 was full. >>> >>> I would like to know whether the 630RSU1 servlink file can be >>> deleted to free up more space for detersing. Thanks, Ray >>> >>> >>> >>> ----------------------------------------- The information contained >>> in this e-mail, including any attachment(s), is intended solely for >>> use by the named addressee(s). If you are not the intended >>> recipient, or a person designated as responsible for delivering such >>> messages to the intended recipient, you are not authorized to >>> disclose, copy, distribute or retain this message, in whole or in >>> part, without written authorization from PSEG. This e-mail may >>> contain proprietary, confidential or privileged information. If you >>> have received this message in error, please notify the sender >>> immediately. This notice is included in all e-mail messages leaving >>> PSEG. Thank you for your cooperation. >>> >>> --------------------------------------------------------------------- >>> - >>> >>> >>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/ >>> >> >>-- >>Dave Jones >>V/Soft Software >>www.vsoft-software.com >>Houston, TX >>281.578.7544 >> >>---------------------------------------------------------------------- >>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/ >> >> >>----------------------------------------- >>The information contained in this e-mail, including any attachment(s), >>is intended solely for use by the named addressee(s). If you are not >>the intended recipient, or a person designated as responsible for >>delivering such messages to the intended recipient, you are not >>authorized to disclose, copy, distribute or retain this message, in >>whole or in part, without written authorization from PSEG. This e-mail >>may contain proprietary, confidential or privileged information. If you >>have received this message in error, please notify the sender >>immediately. This notice is included in all e-mail messages leaving >>PSEG. Thank you for your cooperation. > >---------------------------------------------------------------------- >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/ > > >----------------------------------------- >The information contained in this e-mail, including any attachment(s), is >intended solely for use by the named addressee(s). If you are not the >intended recipient, or a person designated as responsible for delivering >such messages to the intended recipient, you are not authorized to >disclose, copy, distribute or retain this message, in whole or in part, >without written authorization from PSEG. This e-mail may contain >proprietary, confidential or privileged information. If you have received >this message in error, please notify the sender immediately. This notice >is included in all e-mail messages leaving PSEG. Thank you for your >cooperation.
