Re: Install of SUSE Linux on IBM z LPAR

[Alan Altmark]

On Tuesday, 02/03/2015 at 03:46 EST, Steve P 
wrote:
> So for the FTP  file server I can use the hmc enable FTP access to mass
> storage media giving the installer the IP address of the hmc. And giving
> the lpar IP address to the hmc FTP facility (for lack of a
> better name/word).  I just want to know for sure If this is valid option
> for me.   If not then I will abandon it and move to other options.

Yes, using the HMC as an FTP server is a valid option.

> > If it helps, know that there are special instructions that must be
used to
> > read the data from the DVD from inside the LPAR.  The LPAR is still
> > authorized to use those instructions (like VM TCP/IP does), but
without
> > that removable media device driver, the authorization does it no good.
> >
> >
> The special instructions you're talking about is the proverbial device
> driver that IBM is yet to develop/allow. Correct?  So for now an IP
network
> is best?

Correct, the special instructions would be used by a DVD device driver. So
for now, an IP network your best (only) choice.  The only question is how
much control you have over the environment.

If you wanted to, you could set up an FTP server on your own workstation,
put the DVD into your workstation's DVD drive, tell the HMC to Load from
FTP Server.   Then point to the installer to your FTP server.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Alan Altmark]

On Tuesday, 02/03/2015 at 06:25 EST, Rick Troth
 wrote:
> On 02/02/2015 07:19 PM, Alan Altmark wrote:
> > The protection is in place because of the allocation map.  Unlike
other
> > files on the disk, it is in a fixed location since it is written
during
> > FORMAT and its size never changes, as that size is based on the size
of
> > the disk.  But if you add more cylinders, you add more blocks.  And as
you
> > do that, the allocation map has to grow.  But it can't grow.  It's
> > surrounded by other data.
>
> Am not quite following since you changed ADTMCYL, Mike calls it
> malleable, and Ray once had a mod for.

Hence my comment about revisiting DMSFOR and DMSAUD.   So instead of
trying to modify the disk such that is is large when subsequently
accessed, I went the route of tricking the RECOMP code.  But I still
believe that the allocation map was never intended to physically move, but
switches locations along with the DIRECTOR file each time the DOP is
"flopped."

But it's going to take someone with more patience than I have to perform
more experiments.   I would first write several files to the disk, THEN
expand it, THEN fill the disk.  My intuition is telling me that the newly
RECOMPed allocation map will gladly overlay those first files and create a
mess.

But as I say, some more experiments are needed.  Or Ray's code.  :-)

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Donald J.]

If you use a z/OS FTP server, there is a bug in 1.13 which will not allow the 
FTP server to work.
A PTF is available for z/OS 2.1.   For a quickie workaround I modified a sample 
FTP exit to get
around the bug, but still couldn't get the FTP server method to work with z/OS.

If you have NFS server running on z/OS, that is the easiest way to go, using 
the repo=nfsiso option.
This avoids any ascii/ebcdic issues.  You can also later NFS mount the OMVS 
directory containing
the .iso on z/Linux and then do a loopback mount on the .iso file and use that 
for a yum repository.

--
  Donald J.
  dona...@4email.net

On Tue, Feb 3, 2015, at 01:03 PM, Steve P wrote:
> By the way. If I go the route of the network FTP server. Is there any
> setting in the hmc that needs to be addressed to allow access to a network
> FTP server?
>
> Thanks


--
http://www.fastmail.com - A fast, anti-spam email service.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Mark Post]

Lets go back to the beginning, and the basics, again.  Today, there is no other 
option to install Linux in an LPAR than using a network installation server.  
Period.

That network installation server can be any system that serves up one of the 
following protocols:
- FTP
- HTTP
- NFS
- SMB
AS LONG AS the TCP/IP traffic from the LPAR can traverse any and all firewalls 
and routers to get to that server.  Note that the ability to connect is 
_outbound_ from the LPAR and _inbound_ to the installation server.  That's 
important, since it is the Linux installer that is initiating the TCP/IP 
handshakes.

The operating system on the installation server could be Linux, UNIX, z/OS UNIX 
(USS), Windows, whatever.

Now, you can still do the LOAD from the DVD reader in the HMC, as long as you 
copy the data on the DVD to the install server before putting the DVD into the 
reader.  Doing it that way will eliminate the need to be able connect to the 
install server from the HMC itself.

If you decide to keep trying to use the HMC as the FTP server, then of course 
you don't have to copy the contents of the DVD.  Hopefully your network team 
will figure out just what needs to be done to make that work, if that's the 
method you choose.

In one of your previous notes you said
"So for the FTP  file server I can use the hmc enable FTP access to mass 
storage media giving the installer the IP address of the hmc. And giving the 
lpar IP address to the hmc FTP facility (for lack of a
better name/word).  I just want to know for sure If this is valid option for 
me.   If not then I will abandon it and move to other options."

It should be a valid option if the proper inbound network access is enabled.

Later you said
"So for now an IP network is best?"

It is the _only_ thing that will possibly work, so I guess you could call it 
the "best."

In another note you said
"By the way. If I go the route of the network FTP server. Is there any setting 
in the hmc that needs to be addressed to allow access to a network FTP server?"

Other than using the "load from a remote server" dialog and providing the 
proper IP address, no.

In an earlier note today you said
"But since I don't have a valid client ipaddress (in this case the Lpar IP 
address) then it won't work , would it?  The ifconfig command showed inet addr 
of 127.0.0.1 but the hmc did not recognize it as valid."

An IP address of 127.0.0.1 is known as "home" or "localhost."  It won't allow 
you to get traffic into or out of the LPAR.  The fact that you only had the 
loopback interface (lo) configured, concerns me greatly.  It means that you 
didn't get an actual OSA interface "assembled" so you could use it.

The installer asks a bunch of questions about the network hardware so it can do 
what is necessary to perform that assembly.  If something isn't right, you 
won't have a working network device, and you're dead in the water.

Once you've answered all the questions, and if you still get a "no repository 
found" error, then you'll need to get into the shell and poke around to make 
sure you have a working OSA interface.  Things to check are:
ip link show
   This should show you at least two interfaces
   1. lo
   2. eth0
If you don't see eth0, then something went wrong.

Check to see if the qeth and qdio drivers are loaded.
  cat /proc/modules

Check to see if the following directory exists
/sys/bus/ccwgroup/drivers/qeth/
You should see something like this:
  # ls /sys/bus/ccwgroup/drivers/qeth/ 
  0.0.0211   bind  group  module  uevent  unbind

Check to see if there is anything in 
/sys/bus/ccwgroup/devices/
You should see something like this:
  # ls /sys/bus/ccwgroup/devices/
  0.0.0211

If you only see something like this:
  # ls /sys/bus/ccwgroup/drivers/qeth/ 
  bind  group  module  uevent  unbind
then you can try to manually group the interface:
  echo 0.0.0211,0.0.0212,0.0.0213 > /sys/bus/ccwgroup/drivers/qeth/group

If 0.0.0211 then shows up in /sys/bus/ccwgroup/drivers/qeth/, do this:
  echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0211/layer2
  echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0211/online

At that point, an "ip link show" command should be showing an eth0 interface.  
So, try to configure the interface and default route:
  ifconfig eth0 my.ip.add.ress netmask ??.??.??.??
  route add default gw ip.addr.of.gateway
Then try to ping the gateway:
  ping -c 3 ip.addr.of.gateway

If that all works, then you should be able to exit out of the shell and let the 
installer try again.  You should probably ask your network team if the gateway 
system will respond to pings.  Some organizations turn that off to reduce the 
ability of an intruder to figure out what other systems are on the local 
network.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LIN

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Rick Troth]

On 02/03/2015 05:45 PM, Alan Altmark wrote:
> 1. Format the additional cylinders using the same block size as the
> original.   ...

Which is not needed if the underlying media is FBA.

Since this *is* the Linux/390 discussion, it's fair to explain
CMS FORMAT in Linux terms. It is akin to  'mformat'  (from the
"mtools" package) in that it combines both "low level" (blocks,
tracks, cylinders) and "high level" (filesystem). MS-DOS 'format'
is another which does both, for those unafraid to say "voldemort".
Your step #1 there is using it for the "low level" part.
One could use  'dasdfmt -d ldl'  instead.
Just sayin.


On 02/02/2015 07:19 PM, Alan Altmark wrote:
> You can't RECOMP anything larger than the originally formatted size.   You
> can RECOMP lower and back again, but no larger.  And, yes, ADTMCYL holds
> the number of formatted cylinders..

Which you changed in your step #5 (in your latter "ouch" note).


> The protection is in place because of the allocation map.  Unlike other
> files on the disk, it is in a fixed location since it is written during
> FORMAT and its size never changes, as that size is based on the size of
> the disk.  But if you add more cylinders, you add more blocks.  And as you
> do that, the allocation map has to grow.  But it can't grow.  It's
> surrounded by other data.

Am not quite following since you changed ADTMCYL, Mike calls it
malleable, and Ray once had a mod for.

SMOP


> I have to say, it's kind of fun to lean back in my rocking chair and see
> my programmer id in FORMAT (DMSFOR) from back in the mid-80s.

RIP


On 02/03/2015 10:08 AM, Ray Mansell wrote:
> Back in those same mid-80s I added code to the FORMAT command to provide
> an 'EXTEND' option. You could create a new, larger minidisk, the first
> cylinders of which were a replica of the old one. Then you could simply
> FORMAT the new minidisk, specifying the EXTEND option, and it would
> magically grow in size to occupy all of the new space, with all of the
> original files intact.

Various places you could publish that. Various VMers might could make
use of it.



--

Rick Troth
Senior Software Developer

Velocity Software Inc.
Mountain View, CA 94041
Main: (877) 964-8867
Direct: (614) 594-9768
ri...@velocitysoftware.com 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Alan Altmark]

On Tuesday, 02/03/2015 at 01:43 EST, Michael Harding/Oakland/IBM@IBMUS
wrote:
> I have to take exception.

I get that alot, but forgive you.  :-)

> The allocation map like the directory is at heart just another file.
> Changed block(s) in the allocation map get re-written in a different
> location as part of the safe updating of a minidisk's metadata.  It's
size,
> too, is at least partly malleable.  Pulling from another of your posts,
> allocate and format a 200-cylinder minidisk.  That's big enough for the
> allocation map to be larger than one disk block.  It will actually
occupy
> 3: two data and one index block to which the directory points.  Now
recomp
> the disk to 150 cylinders.  The allocation map will now fit in a single
> block and that's all that gets written.  If you later recomp back to 200
> cylinders (as you pointed out, that's do-able) the allocation map will
grow
> back to its original size and its directory entry updated accordingly.

I already said that you can recomp the disk back up to its original size
without problems.  Even so, I got curious (ouch!) and went and looked at
DMSFOR and DMSAUD again, and here's what I got to work:

1. Format the additional cylinders using the same block size as the
original.  Do this with a separate  minidisk, as the FORMAT command
requires that you start on cylinder 0.  This disk must be adjacent to the
old disk.  If you don't do this, then CMS will eventually get I/O errors
on the disk.  Not today, but someday.  N.B. A while back I looked at
updating FORMAT to allow you to format arbitrary extents, with or without
a label.

2. DETACH the current minidisk.

3. Change the MDISK definition for the original disk to include the extra
cylinders and rewrite the directory.

4. LINK the disk.  It now has extra cylinders on the end.  If it doesn't,
go to step 2.

5. Change the ADTMCYL field on disk label to reflect the new cylinder
count, making it look like the disk has been RECOMPed.  ADTMCYL is a
fullword located at offset +24 (decimal) into record 3 of cylinder 0 track
0 (the label).

I used DITTO to change it.  A simple pipe with MDISKBLK READ and WRITE
would easily do it, but be careful since MDISKBLK requires the disk to the
ACCESSed.  (Why?  The blocksize is located on the label, too.)

6. FORMAT vaddr fm  ( RECOMP

I tested this by using temp disks of different sizes and DDR to copy the
small one to a larger one that I had previously formatted.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Steve P]

By the way. If I go the route of the network FTP server. Is there any
setting in the hmc that needs to be addressed to allow access to a network
FTP server?

Thanks

On Tuesday, February 3, 2015, Steve P  wrote:

>
>
> On Tuesday, February 3, 2015, Alan Altmark  > wrote:
>
>> On Tuesday, 02/03/2015 at 01:56 EST, Steve P 
>> wrote:
>> > > But no DVD drive and no USB drives.  They are accessed differently.
>> > > Without the additional support that Mark referred to in one of his
>> first
>> > > responses, the installer cannot access the removable media on the HMC.
>> >
>> > So setup a remote network bases FTP server that can communicate with the
>> > hmc IP ports and load that remote server with the files in those 2
>> > install DVDs.  Or enable  FTP access to mass storage media by giving it
>> the
>> > IP address of the Lpar?
>>
>> Not quite, no.   Having been loaded by the firmware from the DVD, the
>> installer wants to reach out and get the files.  It can't get them from
>> the DVD directly because it doesn't know how (no driver).  So it has no
>> choice but to use an IP network connection to a file server (ftp).
>
>
> So for the FTP  file server I can use the hmc enable FTP access to mass
> storage media giving the installer the IP address of the hmc. And giving
> the lpar IP address to the hmc FTP facility (for lack of a
> better name/word).  I just want to know for sure If this is valid option
> for me.   If not then I will abandon it and move to other options.
>
>
>> To use an IP network, the installer needs two different IP addresses; one
>> for the itself and one for the FTP server.  Those IP addresses must be
>> able to communicate, either directly or over a router.  The network config
>> data you supply to the installer must reflect the proper subnet masks,
>> router IPs, etc. etc.
>
>
> Understood
>
>
>
>>
>> > > When you the "Load from removable media or FTP server" recovery task,
>> that
>> > > media is automatically authorized to be accessed by the LPAR, and it
>> > > remains so until the LPAR is deactivated, you load another LPAR from
>> that
>> > > same media, or you manually release the media.  (I don't remember if
>> > > placing the back-up media into the drive causes it to be disconnected
>> from
>> > > the LPAR or not.)
>> >
>> > So after the LOAD from removable media DVD and the the Installer  starts
>> > the installation prompting for network configuration.  And then asks for
>> > the FTP server IP address, Does the Lpar or Linux installer is
>> > still authorized to access the DVD or not?  I would think yes since it
>> > hasnt been use again since the Load.
>>
>> If it helps, know that there are special instructions that must be used to
>> read the data from the DVD from inside the LPAR.  The LPAR is still
>> authorized to use those instructions (like VM TCP/IP does), but without
>> that removable media device driver, the authorization does it no good.
>>
>>
> The special instructions you're talking about is the proverbial device
> driver that IBM is yet to develop/allow. Correct?  So for now an IP network
> is best?
>
>
>
>> > > But if Linux gets a driver for the HMC removable media, it will be
>> able to
>> > > access the removable media or the remote FTP server to complete the
>> > > installation without having to have a network connection to the LPAR
>> > > itself.
>> >
>> > So there is not a driver for in Linux  for the hmc removable media. Not
>> yet
>> > from IBM.
>>
>> Correct, though an earlier comment from Mark made it sound like someone is
>> looking at it.
>>
>> Alan Altmark
>>
>> Senior Managing z/VM and Linux Consultant
>> Lab Services System z Delivery Practice
>> IBM Systems & Technology Group
>> ibm.com/systems/services/labservices
>> office: 607.429.3323
>> mobile; 607.321.7556
>> alan_altm...@us.ibm.com
>> IBM Endicott
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu 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/
>>
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Steve P]

On Tuesday, February 3, 2015, Alan Altmark  wrote:

> On Tuesday, 02/03/2015 at 01:56 EST, Steve P  >
> wrote:
> > > But no DVD drive and no USB drives.  They are accessed differently.
> > > Without the additional support that Mark referred to in one of his
> first
> > > responses, the installer cannot access the removable media on the HMC.
> >
> > So setup a remote network bases FTP server that can communicate with the
> > hmc IP ports and load that remote server with the files in those 2
> > install DVDs.  Or enable  FTP access to mass storage media by giving it
> the
> > IP address of the Lpar?
>
> Not quite, no.   Having been loaded by the firmware from the DVD, the
> installer wants to reach out and get the files.  It can't get them from
> the DVD directly because it doesn't know how (no driver).  So it has no
> choice but to use an IP network connection to a file server (ftp).


So for the FTP  file server I can use the hmc enable FTP access to mass
storage media giving the installer the IP address of the hmc. And giving
the lpar IP address to the hmc FTP facility (for lack of a
better name/word).  I just want to know for sure If this is valid option
for me.   If not then I will abandon it and move to other options.


> To use an IP network, the installer needs two different IP addresses; one
> for the itself and one for the FTP server.  Those IP addresses must be
> able to communicate, either directly or over a router.  The network config
> data you supply to the installer must reflect the proper subnet masks,
> router IPs, etc. etc.


Understood



>
> > > When you the "Load from removable media or FTP server" recovery task,
> that
> > > media is automatically authorized to be accessed by the LPAR, and it
> > > remains so until the LPAR is deactivated, you load another LPAR from
> that
> > > same media, or you manually release the media.  (I don't remember if
> > > placing the back-up media into the drive causes it to be disconnected
> from
> > > the LPAR or not.)
> >
> > So after the LOAD from removable media DVD and the the Installer  starts
> > the installation prompting for network configuration.  And then asks for
> > the FTP server IP address, Does the Lpar or Linux installer is
> > still authorized to access the DVD or not?  I would think yes since it
> > hasnt been use again since the Load.
>
> If it helps, know that there are special instructions that must be used to
> read the data from the DVD from inside the LPAR.  The LPAR is still
> authorized to use those instructions (like VM TCP/IP does), but without
> that removable media device driver, the authorization does it no good.
>
>
The special instructions you're talking about is the proverbial device
driver that IBM is yet to develop/allow. Correct?  So for now an IP network
is best?



> > > But if Linux gets a driver for the HMC removable media, it will be
> able to
> > > access the removable media or the remote FTP server to complete the
> > > installation without having to have a network connection to the LPAR
> > > itself.
> >
> > So there is not a driver for in Linux  for the hmc removable media. Not
> yet
> > from IBM.
>
> Correct, though an earlier comment from Mark made it sound like someone is
> looking at it.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com 
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu  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/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Alan Altmark]

On Tuesday, February 3, 2015, Alan Altmark 
wrote:
> > When you the "Load from removable media or FTP server" recovery task,
that
> > media is automatically authorized to be accessed by the LPAR, and it
> > remains so until the LPAR is deactivated, you load another LPAR from
that
> > same media, or you manually release the media.  (I don't remember if
> > placing the back-up media into the drive causes it to be disconnected
from
> > the LPAR or not.)

I checked with the HMC folks.  Since the HMC no longer uses the DVD drive
for backups, an LPAR can keep accessing the DVD until one of the various
disconnecting events occurs.  I think SYSTEM RESET and LOAD CLEAR will
also disconnect the implicit connection to the drive.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Alan Altmark]

On Tuesday, 02/03/2015 at 01:56 EST, Steve P 
wrote:
> > But no DVD drive and no USB drives.  They are accessed differently.
> > Without the additional support that Mark referred to in one of his
first
> > responses, the installer cannot access the removable media on the HMC.
>
> So setup a remote network bases FTP server that can communicate with the
> hmc IP ports and load that remote server with the files in those 2
> install DVDs.  Or enable  FTP access to mass storage media by giving it
the
> IP address of the Lpar?

Not quite, no.   Having been loaded by the firmware from the DVD, the
installer wants to reach out and get the files.  It can't get them from
the DVD directly because it doesn't know how (no driver).  So it has no
choice but to use an IP network connection to a file server (ftp).

To use an IP network, the installer needs two different IP addresses; one
for the itself and one for the FTP server.  Those IP addresses must be
able to communicate, either directly or over a router.  The network config
data you supply to the installer must reflect the proper subnet masks,
router IPs, etc. etc.

> > When you the "Load from removable media or FTP server" recovery task,
that
> > media is automatically authorized to be accessed by the LPAR, and it
> > remains so until the LPAR is deactivated, you load another LPAR from
that
> > same media, or you manually release the media.  (I don't remember if
> > placing the back-up media into the drive causes it to be disconnected
from
> > the LPAR or not.)
>
> So after the LOAD from removable media DVD and the the Installer  starts
> the installation prompting for network configuration.  And then asks for
> the FTP server IP address, Does the Lpar or Linux installer is
> still authorized to access the DVD or not?  I would think yes since it
> hasnt been use again since the Load.

If it helps, know that there are special instructions that must be used to
read the data from the DVD from inside the LPAR.  The LPAR is still
authorized to use those instructions (like VM TCP/IP does), but without
that removable media device driver, the authorization does it no good.

> > But if Linux gets a driver for the HMC removable media, it will be
able to
> > access the removable media or the remote FTP server to complete the
> > installation without having to have a network connection to the LPAR
> > itself.
>
> So there is not a driver for in Linux  for the hmc removable media. Not
yet
> from IBM.

Correct, though an earlier comment from Mark made it sound like someone is
looking at it.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Install of SUSE Linux on IBM z LPAR

[Steve P]

Thanks Alan for clearing things up. My replies and responses below...next
to your response.

Thanks.


On Tuesday, February 3, 2015, Alan Altmark  wrote:

> On Tuesday, 02/03/2015 at 12:12 EST, Steve P 
> wrote:
> > As far as issuing the FTP command within the installer shell to view
> > contents of the hmc DVD, I guess that would only work if I enabled the
> FTP
> > access to the hmc DVD. But since I don't have a valid client ipaddress
> (in
> > this case the Lpar IP address) then it won't work , would it?  The
> ifconfig
> > command showed inet addr of 127.0.0.1 but the hmc did not recognize it
> as
> > valid.
>
> I realize now, Steve, that no one has ever stopped to explain to you how
> the mainframe accesses the DVD.
>
> Every LPAR has an associated I/O configuration that includes disk drives,
> tape drives, fibre channel adapters, display terminals, and network
> adapters.


Understood...


>
> But no DVD drive and no USB drives.  They are accessed differently.
> Without the additional support that Mark referred to in one of his first
> responses, the installer cannot access the removable media on the HMC.


So setup a remote network bases FTP server that can communicate with the
hmc IP ports and load that remote server with the files in those 2
install DVDs.  Or enable  FTP access to mass storage media by giving it the
IP address of the Lpar?



>
> When you the "Load from removable media or FTP server" recovery task, that
> media is automatically authorized to be accessed by the LPAR, and it
> remains so until the LPAR is deactivated, you load another LPAR from that
> same media, or you manually release the media.  (I don't remember if
> placing the back-up media into the drive causes it to be disconnected from
> the LPAR or not.)


So after the LOAD from removable media DVD and the the Installer  starts
the installation prompting for network configuration.  And then asks for
the FTP server IP address, Does the Lpar or Linux installer is
still authorized to access the DVD or not?  I would think yes since it
hasnt been use again since the Load.



> You might imagine an LPAR wanting access to the DVD later.  It can, via
> the "Access Removable Media" recovery task on the HMC.  That's how you
> allow the VM FTP server to access to the removable media outside of the
> Load From DVD process.
>
> That way you can install Linux using a network installation to access the
> DVD without going outside the box.  Of course, you don't have z/VM.
>
> But if Linux gets a driver for the HMC removable media, it will be able to
> access the removable media or the remote FTP server to complete the
> installation without having to have a network connection to the LPAR
> itself.


So there is not a driver for in Linux  for the hmc removable media. Not yet
from IBM.


> That's how z/VM and z/OS are able to be installed from the HMC.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Michael Harding]

Linux on 390 Port  wrote on 02/02/2015 04:19:19
PM:

> From: Alan Altmark/Endicott/IBM@IBMUS
> To: LINUX-390@VM.MARIST.EDU
> Date: 02/02/2015 04:20 PM
> Subject: Re: Expanding  CMS  Mini Disk - DDR or Copyfile? - still
> not expanding
> Sent by: Linux on 390 Port 
>
> The protection is in place because of the allocation map.  Unlike other
> files on the disk, it is in a fixed location since it is written during
> FORMAT and its size never changes, as that size is based on the size of
> the disk.  But if you add more cylinders, you add more blocks.  And as
you
> do that, the allocation map has to grow.  But it can't grow.  It's
> surrounded by other data.
>
> I have to say, it's kind of fun to lean back in my rocking chair and see
> my programmer id in FORMAT (DMSFOR) from back in the mid-80s.  :-)
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
I have to take exception.
The allocation map like the directory is at heart just another file.
Changed block(s) in the allocation map get re-written in a different
location as part of the safe updating of a minidisk's metadata.  It's size,
too, is at least partly malleable.  Pulling from another of your posts,
allocate and format a 200-cylinder minidisk.  That's big enough for the
allocation map to be larger than one disk block.  It will actually occupy
3: two data and one index block to which the directory points.  Now recomp
the disk to 150 cylinders.  The allocation map will now fit in a single
block and that's all that gets written.  If you later recomp back to 200
cylinders (as you pointed out, that's do-able) the allocation map will grow
back to its original size and its directory entry updated accordingly.


--
Mike Harding
z/VM System Support

/sp

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Alan Altmark]

On Tuesday, 02/03/2015 at 12:12 EST, Steve P 
wrote:
> As far as issuing the FTP command within the installer shell to view
> contents of the hmc DVD, I guess that would only work if I enabled the
FTP
> access to the hmc DVD. But since I don't have a valid client ipaddress
(in
> this case the Lpar IP address) then it won't work , would it?  The
ifconfig
> command showed inet addr of 127.0.0.1 but the hmc did not recognize it
as
> valid.

I realize now, Steve, that no one has ever stopped to explain to you how
the mainframe accesses the DVD.

Every LPAR has an associated I/O configuration that includes disk drives,
tape drives, fibre channel adapters, display terminals, and network
adapters.

But no DVD drive and no USB drives.  They are accessed differently.
Without the additional support that Mark referred to in one of his first
responses, the installer cannot access the removable media on the HMC.

When you the "Load from removable media or FTP server" recovery task, that
media is automatically authorized to be accessed by the LPAR, and it
remains so until the LPAR is deactivated, you load another LPAR from that
same media, or you manually release the media.  (I don't remember if
placing the back-up media into the drive causes it to be disconnected from
the LPAR or not.)

You might imagine an LPAR wanting access to the DVD later.  It can, via
the "Access Removable Media" recovery task on the HMC.  That's how you
allow the VM FTP server to access to the removable media outside of the
Load From DVD process.

That way you can install Linux using a network installation to access the
DVD without going outside the box.  Of course, you don't have z/VM.

But if Linux gets a driver for the HMC removable media, it will be able to
access the removable media or the remote FTP server to complete the
installation without having to have a network connection to the LPAR
itself.

That's how z/VM and z/OS are able to be installed from the HMC.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Alan Altmark]

On Tuesday, 02/03/2015 at 11:36 EST, Ed Long  wrote:
> So much for easy to use.
> No wonder the INTEL dudes are kicking our butts.
> Consider how much easier it is to create Linux VM's under XEN or VMWARE.

"It's simple to use once you know how."

If you want the HMC to be able to treat your own workstation's drives as
its own when the HMC is accessed via a browser, then that requirement
needs to be made known (RFE).  If you want the HMC to act as an FTP proxy
on behalf of the SEs, RFE.   If you want the HMC to be be able to use
multiple protocols (ftps, scp, sftp), RFE.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Steve P]

When I said ftping into the hmc, I meant FTP to it outside the network.
Right now the network guys are working on fixing the network connection for
the Lpar. It apparently was not done correctly.

In the meantime I issued those commands you provided for the Installer
shell. Since the network info i have for the lpar is not correct then the
ifconfig , route, and ping commands did not give me anything or address
could not be reached.

As far as issuing the FTP command within the installer shell to view
contents of the hmc DVD, I guess that would only work if I enabled the FTP
access to the hmc DVD. But since I don't have a valid client ipaddress (in
this case the Lpar IP address) then it won't work , would it?  The ifconfig
command showed inet addr of 127.0.0.1 but the hmc did not recognize it as
valid.

I am installing SLES11.3

Thanks.

On Friday, January 30, 2015, Mark Post  wrote:

> >>> On 1/30/2015 at 05:52 PM, Steve P  > wrote:
> > Honestly I don't know what file it is looking for.
>
> As I mentioned in my reply to Alan, I know which files are needed.  I'm
> partly responsible for the installer.
>
> > And ftping to the hmc
> > invites all other problems.  Let's just say it would have to involve all
> of
> > the network guys and security access guys to work together and that will
> > take moving a mountain to make happen at this point in time.
>
> Um, if _you_ can't FTP into the HMC, then how would the Linux system be
> able to do it?
>
> > For the moment I am chasing the IP address of the Linux lpar that I am
> > installing this into. I need to verify what was given to me and I suspect
> > it is incorrect.
> >
> > How do I find the command line to enter some hmc commands?  I can't seem
> to
> > find it and I know it exists.  There is a series of commands that will
> tell
> > me the lpar info and their associated IP addresses.
>
> I don't know what you mean by "HMC commands."  I don't think any can get
> shell access on the HMC.  From the Linux perspective, you can get a shell
> running.  After you get the "No repository found" message, you should be
> getting prompted again for the network protocol.  Type in an x and press
> enter.  That should give you a "Linuxrc extras" menu.  Select 3 for "start
> a shell."
>
> At this point you should be able to display your network setup.
> - ifconfig -a
> - route -n
>
> Try to ping your default gateway.  MAKE SURE you specify a count for the
> ping command:
> ping -c 3 ip.addr.default.gw
>
> If you don't, and your keyboard layout isn't set up right, you won't be
> able to terminate the ping command.
>
> If you can ping your default gateway, see if you can ping the IP address
> of the FTP server.  If that works, then try this:
> curl ftp://ip.addr.of.ftpserver/
> You should see a directory listing of the DVD.
>
> curl ftp://ip.addr.of.ftpserver/content
> You should see a bunch of SHA256 hashes.  If you get some sort of error,
> then perhaps the information you were given to use wasn't correct.
>
> One other possibility is if your LPAR is hooked into a switch that expects
> an IEEE vlan to be configured.  If that's the case, they should have told
> you.  Even if they did tell you, depending on what version of SLES you're
> trying to install, the installer might be able to set that up for you, or
> you may need to do it manually from the shell.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu  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/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Mark Post]

>>> On 2/3/2015 at 11:54 AM, "Stewart, Lee"  wrote: 
> Installing Linux in an LPAR without  VM is like  installing Linux on a bare 
> Intel box with no DVD drive and no local disks...

No, an LPAR has "local disks."  Sometimes far too many of them to choose from, 
which can cause its own headaches.  No graphical console, only a serial 
console, however.  I'm sure there are other analogies, but the basic point is 
that without a working connection to a network installation server, you're dead 
in the water, period.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Stewart, Lee]

Installing Linux in an LPAR without  VM is like  installing Linux on a bare 
Intel box with no DVD drive and no local disks...

Lee Stewart ● VM System Support ● Visa ● Phone:  6(750)4601 - +1-303-389-4601 ● 
lstew...@visa.com


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Tuesday, February 03, 2015 9:46 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Install of SUSE Linux on IBM z LPAR

>>> On 2/3/2015 at 11:30 AM, Ed Long  wrote: 
> So much for easy to use.
> No wonder the INTEL dudes are kicking our butts.
> Consider how much easier it is to create Linux VM's under XEN or VMWARE.

If you want to compare apples to apples, then installing Linux on z/VM is far 
easier than in an LPAR, and on par with Xen, KVM, or VMware.  Installing in an 
LPAR is fairly easy, once you have access to a network installation server.

Most of the problems trying to install in an LPAR stem from the fact that most 
companies are very careful about what network connections are allowed to/from 
their mainframes.  Since I have that access on my company's zEC12, I can say 
that installing in an LPAR is a bit of a pain, due to having to work through 
the operating system messages interface, but not particularly horrible.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu 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/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Mark Post]

>>> On 2/3/2015 at 11:30 AM, Ed Long  wrote: 
> So much for easy to use.
> No wonder the INTEL dudes are kicking our butts.
> Consider how much easier it is to create Linux VM's under XEN or VMWARE.

If you want to compare apples to apples, then installing Linux on z/VM is far 
easier than in an LPAR, and on par with Xen, KVM, or VMware.  Installing in an 
LPAR is fairly easy, once you have access to a network installation server.

Most of the problems trying to install in an LPAR stem from the fact that most 
companies are very careful about what network connections are allowed to/from 
their mainframes.  Since I have that access on my company's zEC12, I can say 
that installing in an LPAR is a bit of a pain, due to having to work through 
the operating system messages interface, but not particularly horrible.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Ed Long]

So much for easy to use.
No wonder the INTEL dudes are kicking our butts.
Consider how much easier it is to create Linux VM's under XEN or VMWARE.

Edward Long


On Tue, 2/3/15, Alan Altmark  wrote:

 Subject: Re: Install of SUSE Linux on IBM z LPAR
 To: LINUX-390@VM.MARIST.EDU
 Date: Tuesday, February 3, 2015, 11:21 AM
 
 On Tuesday, 02/03/2015 at 10:00 EST,
 Steve P 
 wrote:
 > Can I open an shell if I am signed onto the hmc
 remotely?  If so where
 and
 > how?  I thought you coul only open a shell if you
 are locally sitting at
 > the hmc console PC.
 
 You cannot open a shell into the HMC, even if you are local
 on the HMC. If
 you're not near the HMC, then installing from the DVD is
 more complicated.
 
 1. The SE (not the HMC!) for the CPC you are using must be
 able to access
 an FTP server that you have set up somewhere.
 2. That FTP server has the DVD mounted on it.
 3. You use the HMC's 'Load from Removable Media or Server'
 and load from
 the FTP server.
 4. Select the installer's 'install from FTP server' function
 and point it
 to the same FTP server.
 
 #1 may be a show-stopper since it requires drilling a small
 hole in your
 HMC/SE LAN.  Adjust the firewalls to allow only a
 limited number of
 communications partners with the SE. (And, no, the HMC
 cannot act as an
 FTP proxy.)
 
 Alan Altmark
 
 Senior Managing z/VM and Linux Consultant
 Lab Services System z Delivery Practice
 IBM Systems & Technology Group
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott
 
 --
 For LINUX-390 subscribe / signoff / archive access
 instructions,
 send email to lists...@vm.marist.edu
 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/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Alan Altmark]

On Tuesday, 02/03/2015 at 10:00 EST, Steve P 
wrote:
> Can I open an shell if I am signed onto the hmc remotely?  If so where
and
> how?  I thought you coul only open a shell if you are locally sitting at
> the hmc console PC.

You cannot open a shell into the HMC, even if you are local on the HMC. If
you're not near the HMC, then installing from the DVD is more complicated.

1. The SE (not the HMC!) for the CPC you are using must be able to access
an FTP server that you have set up somewhere.
2. That FTP server has the DVD mounted on it.
3. You use the HMC's 'Load from Removable Media or Server' and load from
the FTP server.
4. Select the installer's 'install from FTP server' function and point it
to the same FTP server.

#1 may be a show-stopper since it requires drilling a small hole in your
HMC/SE LAN.  Adjust the firewalls to allow only a limited number of
communications partners with the SE. (And, no, the HMC cannot act as an
FTP proxy.)

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Alan Altmark]

On Tuesday, 02/03/2015 at 10:33 EST, "Vitale, Joseph"
 wrote:
> That would be an excellent mod.  IBM should incorporate it, upgrade CMS.

I understand, but given that it is something easily worked around, I don't
see it ever being done.

The challenge is to inform the end user when they've strayed from the
Righteous Path.  Maybe ACCESS should tell you when the formatted size of
the disk doesn't match the physical size.  Then the HELP for the message
could nudge you back into the Light.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Steve P]

I found the "start shell" under Expert in the installer. I will check some
network config from there.

Thanks.

On Tuesday, February 3, 2015, Steve P  wrote:

> Can I open an shell if I am signed onto the hmc remotely?  If so where and
> how?  I thought you coul only open a shell if you are locally sitting at
> the hmc console PC.
>
>
>
> On Monday, February 2, 2015, Steve P  > wrote:
>
>> The message is coming from the Linux installer.
>>
>> On Monday, February 2, 2015, Mark Post  wrote:
>>
>>> >>> On 2/2/2015 at 02:00 PM, Steve P  wrote:
>>> > So I've tried to Ping the Lpar IP from the hmc under Network
>>> Diagnostics to
>>> > see if the lpar is communicating at all through the hmc. But it fails.
>>> So I
>>> > wonder if the failure is because of the the network connection.
>>> >
>>> > Any thoughts?
>>>
>>> If you get into a shell
>>> 1. Do you see the network interface?  (ip link show)
>>> 2. If you have a network interface, does it have an IP address?  (ip
>>> addr show)
>>>   2a. Does it have the right network mask?  (ip addr show)
>>> 3. If you have an IP address, is the default gateway set?  (ip route
>>> show)
>>> 4. Can you ping the default gateway?  (ping -c 3 ip.addr.of.gateway)
>>>
>>> If all those are OK and you can ping your gateway, then the problem is
>>> somewhere beyond the gateway.  Only your network people can help you at
>>> that point.
>>>
>>> Also, note that the LPAR does _not_ "communicate through the HMC."  The
>>> traffic from the OSA adapter you're using goes out through whatever
>>> switches and routes your network team has hooked up, and then to the
>>> (usually well isolated) NIC on the HMC.  As I said, all that part of the
>>> network is outside of your control, so it might be a good idea to see if
>>> you can access another FTP/HTTP/SMB/NFS server somewhere else on the
>>> network.  We have had at least one report of someone using the z/OS FTP
>>> server to install Linux in an LPAR.  Not necessarily a lot of fun, but it's
>>> another possible avenue.
>>>
>>>
>>> Mark Post
>>>
>>> --
>>> For LINUX-390 subscribe / signoff / archive access instructions,
>>> send email to lists...@vm.marist.edu 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/
>>>
>>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Steve P]

Mark,

Sorry i didn't see all your responses from this message from me. I started
to go back and review some of the responses to my messages and saw some of
your responses that I missed.  I will review and get back on this very
informative response from you.

For the record, I have been accessing the hmc remotely through the web
interface. I know there are some limitations on what I can do remotely. The
physical hmc console is elsewhere in another location.

Thanks.

On Friday, January 30, 2015, Mark Post  wrote:

> >>> On 1/30/2015 at 05:52 PM, Steve P  > wrote:
> > Honestly I don't know what file it is looking for.
>
> As I mentioned in my reply to Alan, I know which files are needed.  I'm
> partly responsible for the installer.
>
> > And ftping to the hmc
> > invites all other problems.  Let's just say it would have to involve all
> of
> > the network guys and security access guys to work together and that will
> > take moving a mountain to make happen at this point in time.
>
> Um, if _you_ can't FTP into the HMC, then how would the Linux system be
> able to do it?
>
> > For the moment I am chasing the IP address of the Linux lpar that I am
> > installing this into. I need to verify what was given to me and I suspect
> > it is incorrect.
> >
> > How do I find the command line to enter some hmc commands?  I can't seem
> to
> > find it and I know it exists.  There is a series of commands that will
> tell
> > me the lpar info and their associated IP addresses.
>
> I don't know what you mean by "HMC commands."  I don't think any can get
> shell access on the HMC.  From the Linux perspective, you can get a shell
> running.  After you get the "No repository found" message, you should be
> getting prompted again for the network protocol.  Type in an x and press
> enter.  That should give you a "Linuxrc extras" menu.  Select 3 for "start
> a shell."
>
> At this point you should be able to display your network setup.
> - ifconfig -a
> - route -n
>
> Try to ping your default gateway.  MAKE SURE you specify a count for the
> ping command:
> ping -c 3 ip.addr.default.gw
>
> If you don't, and your keyboard layout isn't set up right, you won't be
> able to terminate the ping command.
>
> If you can ping your default gateway, see if you can ping the IP address
> of the FTP server.  If that works, then try this:
> curl ftp://ip.addr.of.ftpserver/
> You should see a directory listing of the DVD.
>
> curl ftp://ip.addr.of.ftpserver/content
> You should see a bunch of SHA256 hashes.  If you get some sort of error,
> then perhaps the information you were given to use wasn't correct.
>
> One other possibility is if your LPAR is hooked into a switch that expects
> an IEEE vlan to be configured.  If that's the case, they should have told
> you.  Even if they did tell you, depending on what version of SLES you're
> trying to install, the installer might be able to set that up for you, or
> you may need to do it manually from the shell.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu  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/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Vitale, Joseph]

That would be an excellent mod.  IBM should incorporate it, upgrade CMS.


Joseph Vitale
Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ray 
Mansell
Sent: Tuesday, February 03, 2015 10:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

Back in those same mid-80s I added code to the FORMAT command to provide an 
'EXTEND' option. You could create a new, larger minidisk, the first cylinders 
of which were a replica of the old one. Then you could simply FORMAT the new 
minidisk, specifying the EXTEND option, and it would magically grow in size to 
occupy all of the new space, with all of the original files intact.

Now, I wonder where I stashed that code...

Ray

On 2/2/2015 19:19, Alan Altmark wrote:
> On Monday, 02/02/2015 at 05:55 EST, Rick Troth 
>  wrote:
>> Evidently, FORMAT makes a note of the number of cylinders it block 
>> formatted (the "low level" phase) first time around. Guessing that is 
>> the purpose of ADTMCYL. I should have known. Sorry, Joe.
>>
>> So you can (RECOMP smaller and you can (RECOMP larger, but no larger 
>> than some pre-detected size.
> You can't RECOMP anything larger than the originally formatted size.   You
> can RECOMP lower and back again, but no larger.  And, yes, ADTMCYL 
> holds the number of formatted cylinders..
>
> The protection is in place because of the allocation map.  Unlike 
> other files on the disk, it is in a fixed location since it is written 
> during FORMAT and its size never changes, as that size is based on the 
> size of the disk.  But if you add more cylinders, you add more blocks.  
> And as you do that, the allocation map has to grow.  But it can't 
> grow.  It's surrounded by other data.
>
> I have to say, it's kind of fun to lean back in my rocking chair and 
> see my programmer id in FORMAT (DMSFOR) from back in the mid-80s.  :-)
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant Lab Services System z 
> Delivery Practice IBM Systems & Technology Group 
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu 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/
>
>

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu 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, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Expanding CMS Mini Disk - DDR or Copyfile? - still not expanding

[Ray Mansell]

Back in those same mid-80s I added code to the FORMAT command to provide
an 'EXTEND' option. You could create a new, larger minidisk, the first
cylinders of which were a replica of the old one. Then you could simply
FORMAT the new minidisk, specifying the EXTEND option, and it would
magically grow in size to occupy all of the new space, with all of the
original files intact.

Now, I wonder where I stashed that code...

Ray

On 2/2/2015 19:19, Alan Altmark wrote:

On Monday, 02/02/2015 at 05:55 EST, Rick Troth
 wrote:

Evidently, FORMAT makes a note of the number of cylinders it block
formatted (the "low level" phase) first time around. Guessing that is
the purpose of ADTMCYL. I should have known. Sorry, Joe.

So you can (RECOMP smaller and you can (RECOMP larger, but no larger
than some pre-detected size.

You can't RECOMP anything larger than the originally formatted size.   You
can RECOMP lower and back again, but no larger.  And, yes, ADTMCYL holds
the number of formatted cylinders..

The protection is in place because of the allocation map.  Unlike other
files on the disk, it is in a fixed location since it is written during
FORMAT and its size never changes, as that size is based on the size of
the disk.  But if you add more cylinders, you add more blocks.  And as you
do that, the allocation map has to grow.  But it can't grow.  It's
surrounded by other data.

I have to say, it's kind of fun to lean back in my rocking chair and see
my programmer id in FORMAT (DMSFOR) from back in the mid-80s.  :-)

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Re: Install of SUSE Linux on IBM z LPAR

[Steve P]

Can I open an shell if I am signed onto the hmc remotely?  If so where and
how?  I thought you coul only open a shell if you are locally sitting at
the hmc console PC.



On Monday, February 2, 2015, Steve P  wrote:

> The message is coming from the Linux installer.
>
> On Monday, February 2, 2015, Mark Post  > wrote:
>
>> >>> On 2/2/2015 at 02:00 PM, Steve P  wrote:
>> > So I've tried to Ping the Lpar IP from the hmc under Network
>> Diagnostics to
>> > see if the lpar is communicating at all through the hmc. But it fails.
>> So I
>> > wonder if the failure is because of the the network connection.
>> >
>> > Any thoughts?
>>
>> If you get into a shell
>> 1. Do you see the network interface?  (ip link show)
>> 2. If you have a network interface, does it have an IP address?  (ip addr
>> show)
>>   2a. Does it have the right network mask?  (ip addr show)
>> 3. If you have an IP address, is the default gateway set?  (ip route show)
>> 4. Can you ping the default gateway?  (ping -c 3 ip.addr.of.gateway)
>>
>> If all those are OK and you can ping your gateway, then the problem is
>> somewhere beyond the gateway.  Only your network people can help you at
>> that point.
>>
>> Also, note that the LPAR does _not_ "communicate through the HMC."  The
>> traffic from the OSA adapter you're using goes out through whatever
>> switches and routes your network team has hooked up, and then to the
>> (usually well isolated) NIC on the HMC.  As I said, all that part of the
>> network is outside of your control, so it might be a good idea to see if
>> you can access another FTP/HTTP/SMB/NFS server somewhere else on the
>> network.  We have had at least one report of someone using the z/OS FTP
>> server to install Linux in an LPAR.  Not necessarily a lot of fun, but it's
>> another possible avenue.
>>
>>
>> Mark Post
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu 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/
>>
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/