Re: Examples of tape access

2019-01-22 Thread Duerbusch, Tom
Are you talking something like this?

/bin/sh /sbin/chccwdev -e 0.0.05b0
regina /home/sleep30.rexx
/bin/sh /sbin/lstape
mtst -f /dev/ntibm0 rewind
regina /home/sleep30.rexx
/bin/sh /sbin/lstape
mtst -f /dev/ntibm0 fsf 1
regina /home/sleep30.rexx
/bin/sh /sbin/lstape
mtst -f /dev/ntibm0 compression 1
regina /home/sleep30.rexx
/bin/sh /sbin/lstape

Tom Duerbusch
THD Consulting

On Mon, Jan 21, 2019 at 9:46 AM Frank M. Ramaekers 
wrote:

> Does anyone have examples (bash script) of accessing tape units?  In my
> case it would be emulated 3490 (actual is TS7700).  I want to retrieve BVIR
> (Batch Volume Information Retrieval).  This involves writing a request to a
> new tape, closing, opening as input and reading the same tape back.
>
> Frank Ramaekers Jr. | System Analyst I | Public Cloud Operations Cloud &
> Infrastructure  Services
> Unisys | Skype-(512) 387-3949 | francis.ramaek...@unisys.com francis.ramaek...@unisys.com>
>
> [unisys_logo]
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all devices.
> [Grey_LI]  [Grey_TW] <
> http://twitter.com/unisyscorp>  [Grey_GP] <
> https://plus.google.com/+UnisysCorp/posts> [Grey_YT] <
> http://www.youtube.com/theunisyschannel> [Grey_FB] <
> http://www.facebook.com/unisyscorp> [Grey_Vimeo] 
> [Grey_UB]   [Grey_Weibo] <
> https://weibo.com/unisyschina>
>
>
> --
> 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 privacy...@torchmarkcorp.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 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


Re: SLES 12 upgrade fails

2018-03-16 Thread Duerbusch, Tom
Marcy's posts have been going to my spam folder.

That just started happening recently.

Tom Duerbusch
THD Consulting


On Wed, Mar 14, 2018 at 9:56 PM, Alan Ackerman 
wrote:

> I have the same problem — I am not seeing Marcy’s posts. I also don’t see
> anything about SLES 12 upgrade fails on the web page.
>
> Sent from my iPhone
>
> On Mar 14, 2018, at 5:15 PM, Gregg Levine  wrote:
>
> Hello!
>
> Mark as interesting as our discussions are, there is a more
> interesting problem, I'm not seeing anything by Marcy except as a
> response. That is when someone responds to something that Marcy
> posted.
> -
> Gregg C Levine gregg.drw...@gmail.com
> "This signature fought the Time Wars, time and again."
> --
> 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: Recommendation on FSTAB Options

2018-01-02 Thread Duerbusch, Tom
rt1", provided the disk is labeled
> (with the
> >> dasdfmt default) 0X0200 label.
> >>
> >> So for fixed names I think you can only use by-id or by-path. Both do
> not
> >> depend on the physical location of the (mini)disk. The by-id depends on
> the
> >> disk label, regardless of the disk address. The by-path depends on the
> disk
> >> address, regardless of the disk label. I would prefer by-path as that
> cannot
> >> have duplicates.
> >>
> >>
> >> Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
> >> Berry van Sleeuwen
> >>
> >>
> >> -Original Message-
> >> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Rick
> >> Troth
> >> Sent: Tuesday, January 02, 2018 3:22 PM
> >> To: LINUX-390@VM.MARIST.EDU
> >> Subject: Re: Recommendation on FSTAB Options
> >>
> >> I was going to say, as Berry says, that UUID is the current trend. It's
> like
> >> a superlabel if you're okay with mount-by-label. (A certain other distro
> >> threw mount-by-label at me, which aside from the astonishment factor is
> not
> >> a bad idea.) Linux FS labels are (duh) the moral equivalent of IBM
> VOLSER.
> >> You have to set them. (But the installer will set a label, as I recall.)
> >>
> >> Never was fond of mount-by-label. Not sure why. That's the norm for
> z/VM,
> >> but it oddly bothered me in the Linux world. UUID seems to bother me
> less in
> >> certain cases. I like to be able to say "make the 1B1 be root and the
> 1B2 be
> >> /home" and so on. Maybe I'm spoiled by that lovely mainframe I/O space,
> plug
> >> things in where I want them plugged in, know what's where.
> >>
> >> One handy thing about UUID is it's always there.
> >> IMX* it follows a 'dd' copied filesystem and as far as I know remains
> intact
> >> through grow/shrink operations. That would mean a clone would have the
> same
> >> UUID as the original. But if "copy" means to create a fresh filesystem
> and
> >> then move or copy its content, then yeah, you
> >> *will* get a new UUID.
> >>
> >> The annoying thing about mount-by-path is that the "path" changes
> depending
> >> on where the driver slotted the disk of interest.
> >> Mount-by-name is a little better because UDEV tries to compensate for
> the
> >> musical DASD paths by maintaining a name (which is really just a
> different
> >> path) that aligns with the device address (as we know it on z, but is
> >> perhaps more like a "name" on the other platforms). I have always tried
> to
> >> force a range of pre-defined slots by giving "dasd=" as a boot
> parameter or
> >> when loading the driver.
> >>
> >> So ... what are you after? Always put a particular FS at the same mount
> >> point? Try mounting by UUID.
> >>
> >> -- R; <><
> >>
> >> *in my experience
> >>
> >>
> >> On 01/02/2018 04:51 AM, van Sleeuwen, Berry wrote:
> >>> Hi Tom,
> >>>
> >>> I think the safest should be by-path.
> >>>
> >>> I don't quite understand your remark that you have problems with
> >>> device path when moving a dasd subsystem. The "by-path" shouldn't
> >>> change as that depends on the guest or LPAR configuration. As long as
> >>> your minidisk stays on the same device address then the fstab will
> point
> >> to the correct device.
> >>> Regardless of where the minidisk is actually located (ie moving to
> >>> another DASD subsystem or copying to a new guest).
> >>>
> >>> The UUID does change whenever a minidisk is copied and/or moved. Be
> >>> aware that using the UUID is pretty much default in current Linux
> >>> systems so you must make sure grub isn't using UUID. In SLES 12 SP3 a
> >>> rule for dracut is included in the s390 system to make sure the
> by-path is
> >> used.
> >>> Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
> >>> Berry van Sleeuwen
> >>>
> >>> -Original Message-
> >>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> >>> Duerbusch, Tom
> >>> Sent: Friday, December 29, 2017 9:49 PM
> >>> To: LINUX-390@VM.MARIST.EDU
> >>>

Recommendation on FSTAB Options

2017-12-29 Thread Duerbusch, Tom
As we just upgraded from a z/890 to z/13, I'm also skipping version of SLES.

This is SLES 12 SP 3 under z/VM 6.4 with CKD dasd.

Back in the old days, say 10 years ago, when you used the default "Device
Path" in the FSTAB Options, everything worked.  That is, until you move the
disk.  I know there was a problem when you moved the disk to another dasd
subsystem (as in upgrading), and I think there was a problem if you moved
the disk, within the same dasd subsystem, to another rank, or some other
unit (in cases where you have a much larger shop).  At that time, the
suggestion was to use "Device Name".

Is this still the case?

The default in SLES 12 SP 3 is still "Device Path".

I don't want to get in the situation, down the road, of selecting the wrong
type of device naming scheme.

i.e.  Changing to "Device Name", works for a while, then gives me problems.

Thanks

Tom Duerbusch
THD Consulting
Happy New Year

--

--
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: SYSTEMD and autostarting VSE VTAPE (SUSE 12)

2017-12-20 Thread Duerbusch, Tom
I think I'm missing how to specify a working directory.

When I CD to /opt/IBM/VSEVTAPE, I can issue a
./run.sh
and VTAPE starts up.

If I'm in any other directory and issue
./opt/IBM/VSEVTAPE/run.sh
I receive
Could not find or load main class com.ibm.vse.vtape.VirtualTapeServer

When I issue:
systemctl start vtape.service, I get the same error:

systemctl status vtape.service
linux91 systemd[1]: Started VSE VTAPE daemon.
Dec 20 14:06:35 linux91 run.sh[6128]: Error: Could not find or load main
class com.ibm.vse.vtape.VirtualTapeServer

Currently, my vtape.service is:
[Unit]
Description=VSE VTAPE daemon
After=network.target

[Service]
ExecStart=/opt/IBM/VSEVTAPE/run.sh

[Install]
WantedBy=multi-user.target


I have yet to find documentation that tells all the statements available in
a "service" file.  So I'm hoping
for something that specifies a working directory.

I'm sure this is easy, once you know how.
Personally, I think the VSE documentation on Linux hosted VTAPE, should
have examples, but

Thanks

Tom Duerbusch
THD Consulting

On Wed, Dec 20, 2017 at 7:17 AM, Mark Pace  wrote:

> This worked for me.  I'm certain someone will point out the flaws.
>
> [Unit]
> Description=VSE vtape daemon
> After=network.target
>
> [Service]
> ExecStart=/usr/bin/su - vtape -c "nohup ./run.sh  >>/var/log/vtape.log" &
> ExecStop=/usr/bin/pkill -f VirtualTapeServer$
>
> [Install]
> WantedBy=multi-user.target
>
>
> I also had to create the /var/log/vtape.log
> touch /var/log/vtape
> chown vtape /var/log/vtape.log
>
>
>
> On Tue, Dec 19, 2017 at 4:18 PM, Mark Pace  wrote:
>
> > Thanks for the update.  I'm going on vacation until the end of the year.
> > I'll pick it back up then.  Hopefully one of use will figure out soon.
> >
> > Have a great day.
> >
> > On Tue, Dec 19, 2017 at 4:16 PM, Duerbusch, Tom <
> duerbus...@stlouis-mo.gov
> > > wrote:
> >
> >> I'm just getting back to it (I was out last week).
> >>
> >> Currently, my notes from two weeks ago, don't make a lot of sense.
> >> But, once everything gets paged back into my brain, they will make
> sense.
> >>
> >> Tom Duerbusch
> >> THD Consulting
> >>
> >> On Tue, Dec 19, 2017 at 3:07 PM, Mark Pace 
> >> wrote:
> >>
> >> > Tom -
> >> > What did you finally end up doing to get vtape started on you SLES12?
> >> I'm
> >> > about to go down the same path and don't to have to reinvent the
> wheel.
> >> >
> >> > Thanks
> >> >
> >> > On Wed, Dec 6, 2017 at 3:09 PM, Duerbusch, Tom <
> >> duerbus...@stlouis-mo.gov>
> >> > wrote:
> >> >
> >> > > With SUSE 12 SP3, I found that I needed to start converting my
> startup
> >> > > scripts from using INIT.D to SYSTEMD.
> >> > >
> >> > > While SYSTEMD looks a lot cleaner, INIT.D was working.  But it's
> time
> >> to
> >> > > convert.
> >> > >
> >> > >
> >> > > The script to startup VTAPE, as delivered by IBM is:
> >> > >
> >> > > linux91:/opt/IBM/VSEVTAPE # cat run.sh
> >> > > #!/bin/sh
> >> > > # ---
> >> > > # Startup file for VSE VTAPE Server
> >> > > # ---
> >> > > if [ -e "$JAVA_HOME/bin/java" ]; then
> >> > >   JAVA_EXEC="$JAVA_HOME/bin/java"
> >> > > else
> >> > >   JAVA_EXEC=java
> >> > > fi
> >> > > export CLASSPATH=".:VirtualTape.jar:$CLASSPATH"
> >> > > "$JAVA_EXEC" com.ibm.vse.vtape.VirtualTapeServer "$@"
> >> > >
> >> > > And can be run from the command line without any problem.
> >> > >
> >> > > The service file is:
> >> > >
> >> > > linux91:/etc/systemd/system # cat vtape.service
> >> > > [Unit]
> >> > > Description=VSE VTAPE daemon
> >> > > After=graphical.target
> >> > >
> >> > > [Service]
> >> > > ExecStart=/opt/IBM/VSEVTAPE/run.sh
> >> > >
> >> > > [Install]
> >> > > WantedBy=graphical-user.target
> >> > >
> >> > >
> >> > > When I try to start it, I get the following logged in the journal
> >> file:
> >> > >

Re: SYSTEMD and autostarting VSE VTAPE (SUSE 12)

2017-12-19 Thread Duerbusch, Tom
I'm just getting back to it (I was out last week).

Currently, my notes from two weeks ago, don't make a lot of sense.
But, once everything gets paged back into my brain, they will make sense.

Tom Duerbusch
THD Consulting

On Tue, Dec 19, 2017 at 3:07 PM, Mark Pace  wrote:

> Tom -
> What did you finally end up doing to get vtape started on you SLES12?  I'm
> about to go down the same path and don't to have to reinvent the wheel.
>
> Thanks
>
> On Wed, Dec 6, 2017 at 3:09 PM, Duerbusch, Tom 
> wrote:
>
> > With SUSE 12 SP3, I found that I needed to start converting my startup
> > scripts from using INIT.D to SYSTEMD.
> >
> > While SYSTEMD looks a lot cleaner, INIT.D was working.  But it's time to
> > convert.
> >
> >
> > The script to startup VTAPE, as delivered by IBM is:
> >
> > linux91:/opt/IBM/VSEVTAPE # cat run.sh
> > #!/bin/sh
> > # ---
> > # Startup file for VSE VTAPE Server
> > # ---
> > if [ -e "$JAVA_HOME/bin/java" ]; then
> >   JAVA_EXEC="$JAVA_HOME/bin/java"
> > else
> >   JAVA_EXEC=java
> > fi
> > export CLASSPATH=".:VirtualTape.jar:$CLASSPATH"
> > "$JAVA_EXEC" com.ibm.vse.vtape.VirtualTapeServer "$@"
> >
> > And can be run from the command line without any problem.
> >
> > The service file is:
> >
> > linux91:/etc/systemd/system # cat vtape.service
> > [Unit]
> > Description=VSE VTAPE daemon
> > After=graphical.target
> >
> > [Service]
> > ExecStart=/opt/IBM/VSEVTAPE/run.sh
> >
> > [Install]
> > WantedBy=graphical-user.target
> >
> >
> > When I try to start it, I get the following logged in the journal file:
> >
> > Dec 06 14:03:36 linux91 systemd[1]: Started VSE VTAPE daemon.
> > Dec 06 14:03:36 linux91 run.sh[17403]: Error: Could not find or load main
> > class com.ibm.vse.vtape.VirtualTapeServer
> > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Main process exited,
> > code=exited, status=1/FAILURE
> > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Unit entered failed
> > state.
> > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Failed with result
> > 'exit-code'.
> >
> > When I run it manually, it starts up fine:
> >
> > linux91:/opt/IBM/VSEVTAPE # ./run.sh
> > Licensed Materials - Property of IBM
> > (C) Copyright IBM Corp. 1998, 2010. All Rights Reserved.
> >
> > US Government Users Restricted Rights -
> > Use, duplication or disclosure restricted by
> > GSA ADP Schedule Contract with IBM Corp.
> >
> > VirtualTapeServer starting...
> > VirtualTapeServer listening on port 2386
> > Enter 'quit' to stop the server
> >
> > I take it that SYSTEMCTL is running in a different environment than I am.
> > Is there something in the service file where I can set the correct
> > environment?
> >
> > Thanks
> >
> > Tom Duerbusch
> > THD Consulting
> >
> > --
> >
> > --
> > 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 postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> 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/


SYSTEMD and autostarting VSE VTAPE (SUSE 12)

2017-12-06 Thread Duerbusch, Tom
With SUSE 12 SP3, I found that I needed to start converting my startup
scripts from using INIT.D to SYSTEMD.

While SYSTEMD looks a lot cleaner, INIT.D was working.  But it's time to
convert.


The script to startup VTAPE, as delivered by IBM is:

linux91:/opt/IBM/VSEVTAPE # cat run.sh
#!/bin/sh
# ---
# Startup file for VSE VTAPE Server
# ---
if [ -e "$JAVA_HOME/bin/java" ]; then
  JAVA_EXEC="$JAVA_HOME/bin/java"
else
  JAVA_EXEC=java
fi
export CLASSPATH=".:VirtualTape.jar:$CLASSPATH"
"$JAVA_EXEC" com.ibm.vse.vtape.VirtualTapeServer "$@"

And can be run from the command line without any problem.

The service file is:

linux91:/etc/systemd/system # cat vtape.service
[Unit]
Description=VSE VTAPE daemon
After=graphical.target

[Service]
ExecStart=/opt/IBM/VSEVTAPE/run.sh

[Install]
WantedBy=graphical-user.target


When I try to start it, I get the following logged in the journal file:

Dec 06 14:03:36 linux91 systemd[1]: Started VSE VTAPE daemon.
Dec 06 14:03:36 linux91 run.sh[17403]: Error: Could not find or load main
class com.ibm.vse.vtape.VirtualTapeServer
Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Main process exited,
code=exited, status=1/FAILURE
Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Unit entered failed
state.
Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Failed with result
'exit-code'.

When I run it manually, it starts up fine:

linux91:/opt/IBM/VSEVTAPE # ./run.sh
Licensed Materials - Property of IBM
(C) Copyright IBM Corp. 1998, 2010. All Rights Reserved.

US Government Users Restricted Rights -
Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.

VirtualTapeServer starting...
VirtualTapeServer listening on port 2386
Enter 'quit' to stop the server

I take it that SYSTEMCTL is running in a different environment than I am.
Is there something in the service file where I can set the correct
environment?

Thanks

Tom Duerbusch
THD Consulting

--

--
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: Having trouble getting started.

2017-03-03 Thread Duerbusch, Tom
You might need more than 256MB of memory.
Installation does work with 512MB.
The reason for the large memory requirement during installation is the
install process creates a ram disk for the starter system.  The ram disk is
ipl'ed and then you use yast to do the installation/configuration to dasd.

Once you ipl from disk, your memory requirement can be changed to whatever
you need.

Tom Duerbusch
THD Consulting

On Fri, Mar 3, 2017 at 2:25 PM, Hamilton, Robert  wrote:

> For those of you following this thread, or not...
>
> It took some effort, but I was able to get IBM to replace the DVD drive in
> my HMC, so I could get it to "Load from removable media" for my LPAR-only
> install.
>
> So, here's my situation:
>
> I have an LPAR ready to run SLES 12 SP2. We only have 256MB of memory to
> give it, so when I can, I shut down our z/OS sandbox LPAR (1.5GB) to use
> for the installation.
>
> It will now boot from the DVD (no, the DVD media weren't the problem...),
> and after some trials and errors, I can get into YaST2 over a VNC
> connection.
>
>   - There is a glitch in the network setup once you get into YaST. If
> you're not careful, there's a nice error message you will get that says:
>
> Internal error. Please report a bug report with logs.
> Details: undefined method `[]' for nil:NilClass
> Caller: 
> /mounts/mp_0002/usr/share/YaST2/modules/NetworkInterfaces.rp:879:in
> 'block in Write'
>
>  I think there is a fix for that; I downloaded some RPMs that,
> somehow, I need to merge into the ISO burned on my DVD. More on that later.
>
>   - If I was careful, I was able to get past that and get to the DASD
> activation screen. A little painful, since it looks over every disk device
> you have every time you press enter, but I was able to activate a dozen
> drives. The IBM class on VM and Suse setup that I took last year told me
> that I could multithread the dasd-formatting task, but that appears not to
> be true here. Not sure why.
>
>   - THEN, after YaST is finished formatting your disk space and you choose
> to go forward, it goes into the "System Probing", , and gets all the
> way to the "Initialize Software Manager" part, when I get
>
>Unable to create repository
>From URL 'dir:/mounts/mp_0006'
>
>Details"  [SLES12-SP2-12.2-0|dir:///mounts/mp_0006] Valid metadata
> not found at specified URL
>History:
>   - Can't hardlink/copy /mounts/mp_0006/license.tar.gz to
> /var/cache/zypp/SLES12-SP2-12.2-0Wtd3Si
>   - Can't provide license.tar.gz
>
>Try again?
>
> I've asked about these on the Suse fora, but haven't gotten any responses.
> Since this is an evaluation, I'm not permitted to open a service ticket.
> I'm trying to build/create a new ISO from my SLES12SP2 distro, and have
> two new RPMs to replace existing ones...but I can't seem to find out how to
> make a bootable ISO.
>
>
> Got a nice node from Suse saying my evaluation period is about to
> end...wonder if they really want my evaluation...
>
> Any info that could help would be greatly appreciated.
>
> R;
>
> Rob Hamilton
> Sr. System Engineer
> Chemical Abstracts Service
>
> Confidentiality Notice: This electronic message transmission, including
> any attachment(s), may contain confidential, proprietary, or privileged
> information from Chemical Abstracts Service ("CAS"), a division of the
> American Chemical Society ("ACS"). If you have received this transmission
> in error, be advised that any disclosure, copying, distribution, or use of
> the contents of this information is strictly prohibited. Please destroy all
> copies of the message and contact the sender immediately by either replying
> to this message or calling 614-447-3600.
>
> --
> 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: Oracle under z/VM without Linux?

2017-02-15 Thread Duerbusch, Tom
Dreaming...

When Oracle was supported under VM, it was VM/SP.  It was 24 bit code.
I also want to say it was in 370 mode which, I think, has long since bit
the dust in the CMS world.

Tom Duerbusch
THD Consulting

On Wed, Feb 15, 2017 at 10:27 AM, David Boyes  wrote:

> > Am I dreaming to assume that Oracle would actually=20 support 7 on a
> current z/VM?
>
> Probably not. I'm sure if you a) managed to find a copy, and b) threw
> large bales of cash at them, they'd find a way, but Oracle 7 was long, long
> ago. I doubt any modern application would be able to connect to it, and all
> their VM talent has long ago gotten other jobs and moved on. I doubt they
> even have a way to generate a license key for it anymore, but you'd have to
> ask them.
>
> --
> 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: LinuxOne and Oracle License

2017-02-14 Thread Duerbusch, Tom
Not any more.

I use to run Oracle/VM 6 under VM/SP back in the old days.
It didn't run well, as we were limited to 16 MB real and virtual and we had
a couple VSE guests in the mix also.

But it was an upgrade from when we ran Oracle under VSE/SP.

Tom Duerbusch
THD Consulting

On Mon, Feb 13, 2017 at 8:25 AM, Paul Flint  wrote:

> Greetings Mohd (et al),
>
> I realize that this may be a genuinely stupid question, but is it possible
> to run Oracle directly under IBM zVM like you can with DB2?  I looked at
> the Oracle matrix: (http://www.oracle.com/technet
> work/database/virtualizationmatrix-172995.html), there it cites the only
> way to operate the Oracle database is under Red Hat the way you are doing
> it below.
>
> Sorry to ask such a stupid question, but with...
>
> Kindest Regards,
>
> Paul Flint
>
> On Mon, 13 Feb 2017, Bfishing wrote:
>
> Date: Mon, 13 Feb 2017 07:38:04 -0500
>> From: Bfishing 
>> Reply-To: Linux on 390 Port 
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: LinuxOne and Oracle License
>>
>> Hopefully you did a study to see how many Oracle DB's will run on your 5
>> IFL's.
>> - Studies can also be used to help you properly size your DR environment,
>> in addition to the effects of breaking them up into different LPAR's.  .
>>
>> Chances are (but not 100% given) that 4 LPAR's each with 5 IFL's defined
>> to
>> them with only 5 real ones available to run on maybe over committing a bit
>> to much.
>> If your sharing engines (like you most likely should) consider placing
>> dev/test into a lower weighted LPAR and break them out like this:
>> LPAR1 = 3
>> LPAR2 = 3
>>
>> That would allow you to set at least 1 Linux guest to use up to 3 CPU's
>> while helping to control your over commit.
>> Note:  You should of course really map this out with IBM or your BP to
>> review goals.
>> - Having a means to measure your system and track its behavior as you grow
>> is also important.
>> - If you have a great performance product, chances are they come with a
>> team of folks that will help you on things like this as well.
>> - And if you ask me, it's better to have them engaged early over trying to
>> scramble to get them engaged as they can really help you set realistic
>> expectations.
>>
>> BTW, here is a link for the Oracle z Systems special interest group (SIG)
>> web site.
>> http://zseriesoraclesig.org/
>>
>> Lots of great material from past sessions is available from it.
>> I did talk to some of the team working on it recently and they do plan to
>> have this years info updated soon.
>> - They did confirm DC as reported from last years event.
>>
>> Enjoy and good luck,
>> Kurt
>>
>>
>>
>> On Mon, Feb 13, 2017 at 6:12 AM, Johan Schelling <
>> johan.schell...@icu-it.nl>
>> wrote:
>>
>> I believe that’s correct.
>>> But keep in mind that also IFL’s on a DR system (active or CBU) can be
>>> seen (by Oracle) as real cores Oracle can run on.
>>> So if you have 5 active IFL’s and 5 CBU IFL’s on a DR machine this could
>>> mean that you need licenses for 10 IFL’s…..
>>> But as Kurt said, this depends entirely on the negotiations with Oracle.
>>>
>>> Johan Schelling
>>> Infrastructure Solution Architect
>>>
>>>
>>>
>>>
>>>
>>> ICU IT Services BV
>>> Transistorstraat 55b  I  1322 CK  ALMERE
>>>
>>> M 06 – 21 245 992  I  E johan.schell...@icu-it.nl >> johan.schell...@icu-it.nl>
>>> T 088 – 5 234 123  I  www.icu-it.nl   I  KvK
>>> 32135776
>>>
>>> Op 13 feb. 2017, om 11:34 heeft Bfishing  het

>>> volgende geschreven:
>>>

 My understanding, noting that everyone has to do there own negotiating

>>> with
>>>
 Oracle, is they charge for all real cores Oracle can run on.  5 IFL'S =
 5
 cores. Cores in reserve should not matter.

 How you set up your lpar's really depends on goals.

 The Oracle z Linux SIG is still being worked on for April in DC this
 year
 (so I heard).  That is of course a really great place to talk to Oracle

>>> and
>>>
 peers about stuff like this.

 Good luck,
 Kurt

 On Feb 13, 2017 5:02 AM, "Guest, Darren" 
 wrote:

 Hi,
>
> My understanding is that having 5 IFLs on each LPAR would mean you'd
>
 have
>>>
 to license all 10 IFLs on the box; the total of 20 logical IFLs would be
> dispatched on all 10 physical IFLs.
>
> I believe that if your total logical IFLs is 5 or less then you would
> be
> OK; only 5 physical IFLs worth could be running at any one time. Your
> second example should also be OK for the same reason.
>
> This is purely my own personal understanding and shouldn't be relied
>
 upon
>>>
 in any arguments with Oracle!
>
>
> Cheers,
>
> Darren
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> mohd rizal
> Sent: 13 February 2017 3:22 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: LinuxOne a

Re: zvm64 ipwizard

2016-11-23 Thread Duerbusch, Tom
Yea...I've had some troubles viewing documentation on my phone before.
But in this case, with a Galaxy S7, the doc was very viewable.  It looks
like it was brought up under the Chrome browser.  I wonder what plug-in I
was using?

Tom Duerbusch
THD Consulting

On Wed, Nov 23, 2016 at 11:31 AM, Rick Troth  wrote:

> On 11/23/2016 12:22 PM, Duerbusch, Tom wrote:
>
>> Interestingit was readable here.
>> Do you think it was a codepage thing?
>>
>
> I initially tried reading it via hand-held.
> The interaction has been annoying for years. "I just wanna read the
> doc!" Occasionally actually obstructive, like it was for me via mobile.
>
> -- R; <><
>
> --
> 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: zvm64 ipwizard

2016-11-23 Thread Duerbusch, Tom
Interestingit was readable here.
Do you think it was a codepage thing?

Tom Duerbusch
THD Consulting

On Wed, Nov 23, 2016 at 11:15 AM, Rick Troth  wrote:

> Another unreadable page thanks to IBM's Eclipse-based web interface into
> their online doc. Just too much clutter, interference from interactive
> crap.
>
> Dead trees would have not been sacrificed in vain by comparison.
>
> -- R; <><
>
>
>
> On Nov 23, 2016 11:56 AM, "Cabiya, Manuel" 
> wrote:
>
> >
> > if you are having issues with the ipwizard, read this note and avoid the
> > troubleshooting.
> >
> > http://www-01.ibm.com/support/docview.wss?uid=isg1_TCPIP640_VM640
> >
> >
> >
> >
> > Manuel Cabiya
> >
> >
> >
> >
> > Email transmitted across the Internet is normally not protected and may
> be
> > intercepted and viewed by others. Therefore, you should refrain from
> > sending any confidential or private information via unsecured email to
> > PenFed. We will not ask you to send confidential information to us via
> > email, such as your logon ID, password, account numbers, or Social
> Security
> > number. We prohibit our employees from sending confidential information
> to
> > you via email that is not encrypted. The recommended document submission
> > method is FAX; a partial list of generic fax numbers can be found <
> > https://www.penfed.org/aboutUs/contactUs.asp#fax> here<
> > https://www.penfed.org/aboutUs/contactUs.asp#fax>. > tps://www.penfed.org/aboutUs/contactUs.asp#fax>
> >
>
> --
> 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: Fixing Device ID on LVMs

2016-10-25 Thread Duerbusch, Tom
I'm beginning to think everyone is right concerning LVM.
I went down that path because it was the first image that failed and when I
look at the fstab.conf, the root drive was "by path".  So I assumed it was
drives with LVM.

However, now I see that the zipl.conf still has the "by id" in it:
[ipl]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x400
parameters = "root=/dev/disk/by-id/ccw-IBM.1300075850.6801.84-part1
  TERM=dumb"

I would have expected yast to have taken care of this when I changed the
root volume to "by path".

I'm getting too old
I was doing some research on this, and I found I asked the exact same
question on this listserv back in 2008.  That was back when I was doing
flashcopies of Oracle databases and I hit the "by id" problem.

Anyway, we are now discussing connecting both dasd subsystems on the
mainframe.
With some process, deal with thousands of duplicate volsers, or not (we
current have metro/mirror running, but we may just destroy all the volumes
on the DS8884 and start from scratch).
Then for each system, copy and test.
When we are happy, copy image again, and move to production.
Deal with the old image on the DS6800 (relabel or format, whatever it
takes).

Thanks

Tom Duerbusch
THD Consulting

On Mon, Oct 24, 2016 at 5:05 PM, Marcy Cortes  wrote:

> It should just be /etc/fstsab and /etc/zipl.conf that need the work
> LVM should find its stuff regardless if the devices are online to Linux
> during the vgscan/pvscan process.
>
>
> -Original Message-----
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Duerbusch, Tom
> Sent: Monday, October 24, 2016 1:16 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: [LINUX-390] Fixing Device ID on LVMs
>
> I got caught this weekend.
> We were converting from a DS6800 to a DS8884 using metro mirror.
>
> This is on Suse 11, pretty much maintained by yast.
>
> When I brought up the Linux images, some failed due to "device path" not
> being specified in the "fstab options".  Anyway, we backed out.
>
> Now looking at the setups, I did specify "device path" on all the non-LVM
> volumes.  But it looks like I took the default on all volumes that were to
> be part of a LVM.
> (so they specify "device id").
> So, the LVM volumes look like:
> ccw-IBM.1300075850.6802.85-part1 ccw-0X0150-part1
>
> So, when I go into yast, into Partitioner, and select a volume that is
> currently in a LVM, I get:
>
> The selected device belongs to a volume group (LVM1).
> Remove it from the volume group before editing it.
>
> OK, so is there a way of doing this update, without destroying and
> rebuilding the LVM?
>
> It may be that the LVM isn't a part of the problem.
> We used up our standalone time on some other problems and when I started
> getting hit with Linux not coming up and things like
> "IBM.1300075850.6802.85" flashing by, we were already past our go/no-go
> time.  So we took everything down and recabled the boxes.  We also didn't
> save any documentation other then what I stored in my head.
>
> On some images, out fstab looks good, but the zipl is bad:
> [ipl]
> image = /boot/image
> target = /boot/zipl
> ramdisk = /boot/initrd,0x400
> parameters = "root=/dev/disk/by-id/ccw-IBM.
> 1300075850.6801.84-part1
>   TERM=dumb"
>
> I was under the impression that yast also updated the zipl.conf nowadays,
> but apparently it doesn't do it automatically.
>
> So, what is the process to get the zipl.conf updated via yast
> (preferrably), by manual command, or (last resort) manually editing.
>
> Thanks
>
> Tom Duerbusch
> THD Consulting
>
>
> --
>
> --
> 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/


Fixing Device ID on LVMs

2016-10-24 Thread Duerbusch, Tom
I got caught this weekend.
We were converting from a DS6800 to a DS8884 using metro mirror.

This is on Suse 11, pretty much maintained by yast.

When I brought up the Linux images, some failed due to "device path" not
being specified in the "fstab options".  Anyway, we backed out.

Now looking at the setups, I did specify "device path" on all the non-LVM
volumes.  But it looks like I took the default on all volumes that were to
be part of a LVM.
(so they specify "device id").
So, the LVM volumes look like:
ccw-IBM.1300075850.6802.85-part1 ccw-0X0150-part1

So, when I go into yast, into Partitioner, and select a volume that is
currently in a LVM, I get:

The selected device belongs to a volume group (LVM1).
Remove it from the volume group before editing it.

OK, so is there a way of doing this update, without destroying and
rebuilding the LVM?

It may be that the LVM isn't a part of the problem.
We used up our standalone time on some other problems and when I started
getting hit with Linux not coming up and things like
"IBM.1300075850.6802.85" flashing by, we were already past our go/no-go
time.  So we took everything down and recabled the boxes.  We also didn't
save any documentation other then what I stored in my head.

On some images, out fstab looks good, but the zipl is bad:
[ipl]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x400
parameters = "root=/dev/disk/by-id/ccw-IBM.1300075850.6801.84-part1
  TERM=dumb"

I was under the impression that yast also updated the zipl.conf nowadays,
but apparently it doesn't do it automatically.

So, what is the process to get the zipl.conf updated via yast
(preferrably), by manual command, or (last resort) manually editing.

Thanks

Tom Duerbusch
THD Consulting


--

--
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/


Other migration problems (was Unable to login with ssh)

2016-06-29 Thread Duerbusch, Tom
I didn't want to hijack the original thread so

The conclusion on the original thread was that you need to be on a
supported release of Suse when you go to a new z13.  This involved SSH and
I assume crypto hardware.

We have been planing to go to a z13 this year.
I've said that many times before as we are on a z890, and have planed to go
to a z9, z10, z114, z12 and now z13.

We have SLES 9, SLES 10 and SLES 11 running.
(After WAVV in 2011, I did manage to sunset our SLES 7 and SLES 8 guests)

I'm ok with not being able to use new features/functions that are on a
z13/zVM 6, on the unsupported software, but I'm now concerned about what I
might loose, or crash with the new hardware.

SSH isn't much of a problem, as there are so few people that actually log
on to Linux or use SSH with Linux applications.

So, the question is:
Is there any other problems that others have come across, when migrating
unsupported SLES systems to a z13?

Thanks

Tom Duerbusch
THD Consulting

--

--
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: Simple DASD question

2016-04-19 Thread Duerbusch, Tom
df would show something like this (for a dual disk system):
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/dasda17098008   352   3292988  52% /
devtmpfs510668   100510568   1% /dev
tmpfs   51066816510652   1% /dev/shm
/dev/dasdb17098008925552   5811888  14% /home

In this case, dasda1 has the root directory "/".
dasdb1 has the home subdirectory "/home".

Tom Duerbusch
THD Consulting


On Tue, Apr 19, 2016 at 1:51 PM, Tom Huegel  wrote:

> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
>
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> I tried to add a package and I get 'no space on DASD' condition.
> I am guessing the installation only used the first disk, but how can I be
> sure?
> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?
>
> Thanks
> Tom
>
> --
> 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/


zLinux and Cobol

2016-02-09 Thread Duerbusch, Tom
We are looking at moving an application to DB2/UDB on zLinux (Suse).
That application has 6 Stored Procedures that have been written in Cobol.

What are some of my options?
Hiring or training a programmer to convert 6 programs to C, just doesn't
seem feasible.
But then, buying a Cobol compiler just for 6 programs also doesn't seem
cost effective.
What other options have shops employed?
Are there multiple Cobol compiler vendors available?
Micro Focus Cobol?
Does IBM's Visual Age/Cobol work in zLinux (or still available)?

Thanks

Tom Duerbusch
THD Consulting

--

--
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: New Subscriber's first question.

2015-12-18 Thread Duerbusch, Tom
Hi Bruce

A conversion piece that is frequently forgotten during VM upgrades is what
is your MDC (minidisk cache) setting?

Q MDC

The default (perhaps use to be) all storage was available.
Most of us set it to a smaller amount.
Once it has been set, it is set forever (unless a performance monitor tells
you to use a different about).  And hence, easily forgotten.

Those of us that run second level VM systems usually hit a "rude awaking"
when MDC settings are allowed to run "free and wild" .

Tom Duerbusch
THD Consulting


On Fri, Dec 18, 2015 at 1:31 PM, Davis, Jim [PRI-1PP] <
jim.da...@primerica.com> wrote:

> Hi Bruce
>
> I had to backout the 630 upgrade while they finished upgrading their apps
> to sles 11.4 which is running with very little paging if any at all under
> 540 with 4gb xstore and cmma=on in kernel parms.
>
> This Sunday I will try VM 630 again but without xstore and with 16GB of
> central storage.
>
> Someone else replied that cmma has been removed from sles 11 but I think I
> am using really using what is called cmm2.
>
> When we first started with sles 9 and vm530 the recommendations  from IBM
> were to let the linux swap to vdisk and only increase the vm size when
> swapping became excessive.  My linux clients have 2GB or less of storage
> and at least 3GB of swap to vdisk defined.
> The early write may be my problem as 630 would be writing all of the vdisk
> pages to aux storage before cmma would tell VM to throw away the page.
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Bruce Hayden
> Sent: Friday, December 18, 2015 1:56 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: New Subscriber's first question.
>
> Hi Jim, welcome to the mailing list.
>
> z/VM 6.3 had many changes to memory management, and it will use more
> paging space.  For one, it will write pages out "early", meaning before it
> has to actually free up a page.  As part of that, XSTORE is no longer
> recommended and I'd suggest the next time you IPL, change the LPAR
> configuration to 16 GB of storage with no expanded storage.
>
> Without knowing more details on your VM and Linux configuration, it is
> hard to say why it is using so much more page space.  Did the size of the
> guests increase when you upgraded them to SLES 11?  The CMMA support in
> z/VM did not change between 5.4 and 6.3 but it may have changed in Linux
> from SLES
> 10 to SLES 11.
>
> On Fri, Dec 18, 2015 at 1:12 PM, Davis, Jim [PRI-1PP] <
> jim.da...@primerica.com> wrote:
>
> > I am a systems programmer at Primerica Life Insurance.
> > We have been running SLES linux under VM for nine years.
> > We only have four production VMs on one lpar using a single IFL.
> >
> > We will be installing a Z13 in Jan 2016 which has required me to
> > upgrade all SLES 10.3 VMs to SLES 11.4 and VM from 540 to 630.
> >
> > The VM lpar has 12GB of storage plus 4GB of xstore.
> > Under 540 I did not experience any paging to external VM page datasets.
> > CMMA=ON
> >
> > When I bring up VM 630, I see massive movement of pages to xstore and
> > then page outs to aux storage, filling up aux storage.
> > I have  increase aux storage to 3x but it keeps growing.
> >
> > It acts like CMMA is not functioning under VM 630.
> >
> > Any assistance would be greatly appreciated.
> >
> > Jim Davis
> >
> >
> >
> >
> > --
> > 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/
> >
>
>
>
> --
> Bruce Hayden
> z/VM and Linux on z Systems ATS
> IBM, Endicott, NY
>
> --
> 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: SLES12 Question

2015-12-04 Thread Duerbusch, Tom
In the VM directory you don't have a disk 201 defined, so the link fails.
Perhaps you do have the disk in the directory, but didn't DIRECTXA the file.
Or, the real disk that the minidisk is on, isn't attached to system.

In other words, the problem isn't in the VMCP command, it is that the
minidisk isn't available.
Look at the problem from that perspective.

Tom Duerbusch
THD Consulting

On Fri, Dec 4, 2015 at 2:49 PM, Michael Weiner 
wrote:

> Hi all,
>
> I am trying to link a disk which I added to the profile of my guest and it
> doesn't seem to be liking something and I can bring my device online.
>
> sles12:~ # vmcp link '* 201 201 rr'
> RPIMGR031E RESOURCE SLES12SP.201 SPECIFIED BY LINK COMMAND NOT FOUND
> sles12: ~ # chccwdev -e 201
> Device 0.0.0201 not found
>
> Any suggestions? I am scratching my head on this as I can't see why that
> would happen.
>
> Have a good weekend!
>
> --
> Michael Weiner
> Systems Admin
> Infinity Systems Software, Inc.
> One Penn Plaza Suite 2010
> New York, NY 10119
> o: (646) 405-9300
> c: (845) 641-0517
>
> --
> 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: Change common service filepool name from POOL1 to VMPSFS - New z/VM cookbook questions

2015-11-06 Thread Duerbusch, Tom
Right you are.

I need a drink.

Tom Duerbusch
THD Consulting
(it must be 5 o'clock somewhere)

On Fri, Nov 6, 2015 at 2:18 PM, Rich Smrcina 
wrote:

> Sub-directory names are separated by periods, not back-slashes:
>
> vmlink .dir vmsysvps:zvps.consoles
>
> On 11/06/2015 02:05 PM, Duerbusch, Tom wrote:
>
>> Right.
>>
>> The syntax is:
>>
>> Poolname colon rootname period
>> and, if necessary backslash subdirectory backslash subdirectory etc
>>
>> Poolname: is only needed if it is not the same pool that is specified as
>> your default poolname.
>> 'SET FILEPOOL VMSYSU:'   (in my user direct)
>>
>> Rootname defaults to your CMS userid but you still need the period.
>> Assuming you are logged on as MAINT:
>>
>> ACCESS . W
>> is the same as:
>> ACCESS MAINT. W
>> is the same as:
>> ACCESS VMSYSU:. W
>> is the same as:
>> ACCESS VMSYSU:MAINT. W
>>
>> Tom Duerbusch
>> THD Consulting
>>
>> On Fri, Nov 6, 2015 at 1:31 PM, Will, Chris  wrote:
>>
>> Well it appears to be a typo in the cookbook.  I added a "." after vwmm2
>>> and it works.
>>>
>>> access vmpsfs:vmww2. z (forcerw
>>>
>>> I was getting the following error without the dot.
>>>
>>> access vmpsfs:vmww2 z (forcerw
>>> DMSPCL389E Invalid operand: VMPSFS:VMWW2
>>>
>>> Chris Will
>>>
>>> -Original Message-
>>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>>> Duerbusch, Tom
>>> Sent: Friday, November 06, 2015 11:30 AM
>>> To: LINUX-390@VM.MARIST.EDU
>>> Subject: Re: Change common service filepool name from POOL1 to VMPSFS -
>>> New z/VM cookbook questions
>>>
>>> To split hairs.
>>>
>>> You don't have to create a CMS user (i.e. in the USER DIRECT or DIRMAINT)
>>> in order to ENROLL USER (create a SFS user).
>>>
>>> Process is:
>>>
>>> 1.  Optionally create a CMS user.
>>> 2.  Enroll the SFS user which creates the default root directory.
>>> 3.  Optionally create subdirectories on that root directory.
>>> 4.  If directories/subdirectories/files are to be access by any
>>> NON-SFS-ADMIN user, or the base user that was created in step 1, then you
>>> need to GRANT authorizations those userids.
>>>
>>> Q LIMITS ALL  will show all the users that are enrolled.
>>>
>>> Filepool VMSERVS is the IBM filepool.  It will get replaced by IBM.  Not
>>> a
>>> good place to store your stuff.
>>>
>>> Filepool VMSERVU is setup as the default for users.  As shipped, it
>>> doesn't have much disk space.
>>>
>>> If you use VMSERVU, the first thing you need to do is add disk space.
>>>  If
>>> you create your own, you need to generate it with lots of disk space.
>>>
>>> Once SFS became available (VM/SP 5), I would never want to operate
>>> without
>>> it .
>>>
>>> Tom Duerbusch
>>> THD Consulting
>>>
>>> On Fri, Nov 6, 2015 at 7:29 AM, Will, Chris  wrote:
>>>
>>> SFS is new for us.  I have been happy using regular minidisks in the
>>>> past but if there is a good reason to start looking at SFS (better for
>>>> SSI, LGR, DR, etc.), we will try to get up to speed on it.  Another
>>>> question about the redbook is creation of the files under VMWW2.
>>>> Would you not have to define a userid VMWW2 and create a directory
>>>> prior to accessing the directory?  Here is the portion of the redbook in
>>>>
>>> question.
>>>
>>>> ===> enroll user vmww2 vmpsfs ( blocks 5000  << there is no step in
>>>> the book to create a user.
>>>> ===> access vmpsfs:vmww2 z (forcerw << shouldn't there be a step to
>>>> create the directory?
>>>> ===> copy VMWW2 VMARC M = = Z
>>>> ===> erase VMWW2 VMARC M
>>>>
>>>> Chris Will
>>>>
>>>> -Original Message-
>>>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>>>> Alan Altmark
>>>> Sent: Friday, November 06, 2015 4:28 AM
>>>> To: LINUX-390@VM.MARIST.EDU
>>>> Subject: Re: Change common service filepool name from POOL1 to VMPSFS
>>>> - New z/VM cookbook questions
>>>>
>>>> On Thursday, 11/05/2015 at 12:06 EST, "Will, Chris" 
>>>> wr

Re: Change common service filepool name from POOL1 to VMPSFS - New z/VM cookbook questions

2015-11-06 Thread Duerbusch, Tom
Right.

The syntax is:

Poolname colon rootname period
and, if necessary backslash subdirectory backslash subdirectory etc

Poolname: is only needed if it is not the same pool that is specified as
your default poolname.
'SET FILEPOOL VMSYSU:'   (in my user direct)

Rootname defaults to your CMS userid but you still need the period.
Assuming you are logged on as MAINT:

ACCESS . W
is the same as:
ACCESS MAINT. W
is the same as:
ACCESS VMSYSU:. W
is the same as:
ACCESS VMSYSU:MAINT. W

Tom Duerbusch
THD Consulting

On Fri, Nov 6, 2015 at 1:31 PM, Will, Chris  wrote:

> Well it appears to be a typo in the cookbook.  I added a "." after vwmm2
> and it works.
>
> access vmpsfs:vmww2. z (forcerw
>
> I was getting the following error without the dot.
>
> access vmpsfs:vmww2 z (forcerw
> DMSPCL389E Invalid operand: VMPSFS:VMWW2
>
> Chris Will
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Duerbusch, Tom
> Sent: Friday, November 06, 2015 11:30 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Change common service filepool name from POOL1 to VMPSFS -
> New z/VM cookbook questions
>
> To split hairs.
>
> You don't have to create a CMS user (i.e. in the USER DIRECT or DIRMAINT)
> in order to ENROLL USER (create a SFS user).
>
> Process is:
>
> 1.  Optionally create a CMS user.
> 2.  Enroll the SFS user which creates the default root directory.
> 3.  Optionally create subdirectories on that root directory.
> 4.  If directories/subdirectories/files are to be access by any
> NON-SFS-ADMIN user, or the base user that was created in step 1, then you
> need to GRANT authorizations those userids.
>
> Q LIMITS ALL  will show all the users that are enrolled.
>
> Filepool VMSERVS is the IBM filepool.  It will get replaced by IBM.  Not a
> good place to store your stuff.
>
> Filepool VMSERVU is setup as the default for users.  As shipped, it
> doesn't have much disk space.
>
> If you use VMSERVU, the first thing you need to do is add disk space.   If
> you create your own, you need to generate it with lots of disk space.
>
> Once SFS became available (VM/SP 5), I would never want to operate without
> it .
>
> Tom Duerbusch
> THD Consulting
>
> On Fri, Nov 6, 2015 at 7:29 AM, Will, Chris  wrote:
>
> > SFS is new for us.  I have been happy using regular minidisks in the
> > past but if there is a good reason to start looking at SFS (better for
> > SSI, LGR, DR, etc.), we will try to get up to speed on it.  Another
> > question about the redbook is creation of the files under VMWW2.
> > Would you not have to define a userid VMWW2 and create a directory
> > prior to accessing the directory?  Here is the portion of the redbook in
> question.
> >
> > ===> enroll user vmww2 vmpsfs ( blocks 5000  << there is no step in
> > the book to create a user.
> > ===> access vmpsfs:vmww2 z (forcerw << shouldn't there be a step to
> > create the directory?
> > ===> copy VMWW2 VMARC M = = Z
> > ===> erase VMWW2 VMARC M
> >
> > Chris Will
> >
> > -Original Message-
> > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> > Alan Altmark
> > Sent: Friday, November 06, 2015 4:28 AM
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: Re: Change common service filepool name from POOL1 to VMPSFS
> > - New z/VM cookbook questions
> >
> > On Thursday, 11/05/2015 at 12:06 EST, "Will, Chris" 
> > wrote:
> > > I have been going through the new z/vm 6.3 cookbook that uses sfs
> > > for
> > many
> > > functions.  I set up a 2 member SSI cluster using the previous z/vm
> > > 6.3
> > redbook
> > > but used name "POOL1" for the common service filepool name during
> > > the
> > install
> > > and would like to change it to VMPSFS.  Any way to change this?
> > > Also,
> > in the
> > > redbook they format a disk for use by vmses/e (address 1564/label
> > > vv1564
> > in the
> > > book) but then it is never referenced again.
> >
> > If an answer doesn't appear soon, I suggest opening a PMR.
> >
> > 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 / 

Re: Change common service filepool name from POOL1 to VMPSFS - New z/VM cookbook questions

2015-11-06 Thread Duerbusch, Tom
To split hairs.

You don't have to create a CMS user (i.e. in the USER DIRECT or DIRMAINT)
in order to ENROLL USER (create a SFS user).

Process is:

1.  Optionally create a CMS user.
2.  Enroll the SFS user which creates the default root directory.
3.  Optionally create subdirectories on that root directory.
4.  If directories/subdirectories/files are to be access by any
NON-SFS-ADMIN user, or the base user that was created in step 1, then you
need to GRANT authorizations those userids.

Q LIMITS ALL  will show all the users that are enrolled.

Filepool VMSERVS is the IBM filepool.  It will get replaced by IBM.  Not a
good place to store your stuff.

Filepool VMSERVU is setup as the default for users.  As shipped, it doesn't
have much disk space.

If you use VMSERVU, the first thing you need to do is add disk space.   If
you create your own, you need to generate it with lots of disk space.

Once SFS became available (VM/SP 5), I would never want to operate without
it .

Tom Duerbusch
THD Consulting

On Fri, Nov 6, 2015 at 7:29 AM, Will, Chris  wrote:

> SFS is new for us.  I have been happy using regular minidisks in the past
> but if there is a good reason to start looking at SFS (better for SSI, LGR,
> DR, etc.), we will try to get up to speed on it.  Another question about
> the redbook is creation of the files under VMWW2.  Would you not have to
> define a userid VMWW2 and create a directory prior to accessing the
> directory?  Here is the portion of the redbook in question.
>
> ===> enroll user vmww2 vmpsfs ( blocks 5000  << there is no step in the
> book to create a user.
> ===> access vmpsfs:vmww2 z (forcerw << shouldn't there be a step to create
> the directory?
> ===> copy VMWW2 VMARC M = = Z
> ===> erase VMWW2 VMARC M
>
> Chris Will
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Alan Altmark
> Sent: Friday, November 06, 2015 4:28 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Change common service filepool name from POOL1 to VMPSFS -
> New z/VM cookbook questions
>
> On Thursday, 11/05/2015 at 12:06 EST, "Will, Chris" 
> wrote:
> > I have been going through the new z/vm 6.3 cookbook that uses sfs for
> many
> > functions.  I set up a 2 member SSI cluster using the previous z/vm
> > 6.3
> redbook
> > but used name "POOL1" for the common service filepool name during the
> install
> > and would like to change it to VMPSFS.  Any way to change this?  Also,
> in the
> > redbook they format a disk for use by vmses/e (address 1564/label
> > vv1564
> in the
> > book) but then it is never referenced again.
>
> If an answer doesn't appear soon, I suggest opening a PMR.
>
> 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/
>
>
> The information contained in this communication is highly confidential and
> is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you are
> hereby notified that any viewing, copying, disclosure or distribution of
> this information is prohibited. Please notify the sender, by electronic
> mail or telephone, of any unintended receipt and delete the original
> message without making any copies.
>
>  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and Blue
> Shield Association.
>
> --
> 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: SUSE12 Gold image on VM

2015-06-16 Thread Duerbusch, Tom
Thanks Alan

I'll drop portname from my install documentation and, eventually, when we
get a new processor, we can go to SLES 12 and beyond, and portnames will
eventually die out (no zOS here...for bettor or worse).

Tom Duerbusch
THD Consulting

On Tue, Jun 16, 2015 at 11:00 AM, Alan Altmark 
wrote:

> On Tuesday, 06/16/2015 at 11:41 EDT, "Duerbusch, Tom"
>  wrote:
> > Back in the old days, SLES 7, the statement about portname was, "it is
> not
> > required, but if you do use it, you must use it every where"  (or
> something
> > to that effect).
> >
> > So, as I never when back to the older running images to delete the
> > portname, I still continue to specify the portname on all new images.
> >
> > So, the question is, can I have a mixture of images that specify a
> portname
> > with images that do not specify a portname?
> >
> > Also, I have running images that goes back to SLES9 running.  Does your
> > answer go all the way back to SLES9?
> >
> > (I'm on a z/890almost everything I run is currently unsupported )
>
> I can't speak to SLES requirements, but as far as the OSAs go, the
> portname is optional.  IF it is specified, then it must match anyone else
> who also specified the portname, be they z/OS, Linux, VM, or VSE.  So,
> yes, you can mix specify/unspecified on the port.  All the 'specified'
> hosts must use the same value.
>
> 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: Are weekly z/VM IPLs necessary?

2015-05-27 Thread Duerbusch, Tom
It really wouldn't.

Our VM machines are really "guests" only.
Other than me, no one else is actively logged on.
(ok there are some others that use CMS )

Now a days, shutting down VM and restarting it, takes 2-3 minutes.
Just not worth having a second set of procedures for something that happens
every 590 to 1,537 days ).

There are times I miss the old days...
then I go home, grab a beer, and I get over it .

It it was really a problem, I would have a startup script that would test
to make sure any guest is up that is required before the next guest is
started.  But then I could argue that the amount of down time required to
test the script, and continued downtime to retest after images are
enabled/disabled in the future, doesn't warrant the savings every couple of
years.

But, then, that is this shop.

Tom Duerbusch
THD Consulting


On Wed, May 27, 2015 at 10:05 AM, Scott Rohling 
wrote:

> This could help next time?
>
> pipe cp q signals | locate /Enabled/ | specs /FORCE/ 1 w1 nw | cons
>
> You can issue this safely to see what I'm talking about
>
> Change the 'cons' to 'CP'    and each guest who has signal enabled
> (usually Linux and SFS) will get forced  (signalled).   Wait for them to
> come down and then autolog AUTOLOG1/2 or whatever to restart things.
>
> 'CP SHUTDOWN' essentially does the above and then brings z/VM down..  so
> this way you can bring down the guests and not z/VM itself..
>
> Scott Rohling
>
> On Wed, May 27, 2015 at 7:55 AM, Duerbusch, Tom  >
> wrote:
>
> > The last time we have IPL'ed either of our VM systems was due to a air
> > conditioner failure (thermal shutdown of the z/890 box) 590 days ago.
> >
> > The only problem we had was with the zLinux side starting up.
> > We got the messages:
> > /dev/system/home has gone 1537 days without being checked, check forced.
> > /dev/dasda1 has gone 931 days without being checked, check forced.
> > /dev/dasda1 has gone 1075 days without being checked, check forced.
> >
> > Since check disk was being run, and the time they run varies by disk size
> > (or disk used, or number of files or) the guests came up out of
> order.
> >
> > To fix it, we did the dumbest (ok easiest...requires no thinking) thing
> to
> > do
> >
> > Wait for all 27 images to come up and go idle.
> > Issue the shutdown script.
> > IPL z/VM again and let AUTOLOG bring up all guests in the proper order.
> >
> > So, for some of us, the only time we need to IPL VM, is for a box swap,
> > LPAR reconfiguration (add memory), maintenance to CP or installation of a
> > new CP.
> >
> > It will be interesting to here what others had issues with.
> >
> > Tom Duerbusch
> > THD Consulting
> >
> > On Wed, May 27, 2015 at 9:33 AM, Will, Chris  wrote:
> >
> > > We have gotten in the habit of IPLing our z/VM and zLinux guests every
> > > Sunday during our standalone window.  With the window shrinking and the
> > > need for 24/7 availability is it really necessary to IPL every week?
> If
> > > not what potential problems could we run into by not doing the IPL
> > (memory
> > > leaks, logs filling etc.).  This is in comparison to the Intel side of
> > the
> > > shop (Red Hat, Windows) where they go months between IPLs.  The only
> > > benefit I see is the opportunity to recycle WMB execution groups.
> > >
> > > Chris Will
> > >
> > >
> > >
> > > The information contained in this communication is highly confidential
> > and
> > > is intended solely for the use of the individual(s) to whom this
> > > communication is directed. If you are not the intended recipient, you
> are
> > > hereby notified that any viewing, copying, disclosure or distribution
> of
> > > this information is prohibited. Please notify the sender, by electronic
> > > mail or telephone, of any unintended receipt and delete the original
> > > message without making any copies.
> > >
> > >  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan
> are
> > > nonprofit corporations and independent licensees of the Blue Cross and
> > Blue
> > > Shield Association.
> > >
> > > --
> > > 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
> > > ---

Re: Are weekly z/VM IPLs necessary?

2015-05-27 Thread Duerbusch, Tom
The last time we have IPL'ed either of our VM systems was due to a air
conditioner failure (thermal shutdown of the z/890 box) 590 days ago.

The only problem we had was with the zLinux side starting up.
We got the messages:
/dev/system/home has gone 1537 days without being checked, check forced.
/dev/dasda1 has gone 931 days without being checked, check forced.
/dev/dasda1 has gone 1075 days without being checked, check forced.

Since check disk was being run, and the time they run varies by disk size
(or disk used, or number of files or) the guests came up out of order.

To fix it, we did the dumbest (ok easiest...requires no thinking) thing to
do

Wait for all 27 images to come up and go idle.
Issue the shutdown script.
IPL z/VM again and let AUTOLOG bring up all guests in the proper order.

So, for some of us, the only time we need to IPL VM, is for a box swap,
LPAR reconfiguration (add memory), maintenance to CP or installation of a
new CP.

It will be interesting to here what others had issues with.

Tom Duerbusch
THD Consulting

On Wed, May 27, 2015 at 9:33 AM, Will, Chris  wrote:

> We have gotten in the habit of IPLing our z/VM and zLinux guests every
> Sunday during our standalone window.  With the window shrinking and the
> need for 24/7 availability is it really necessary to IPL every week?  If
> not what potential problems could we run into by not doing the IPL (memory
> leaks, logs filling etc.).  This is in comparison to the Intel side of the
> shop (Red Hat, Windows) where they go months between IPLs.  The only
> benefit I see is the opportunity to recycle WMB execution groups.
>
> Chris Will
>
>
>
> The information contained in this communication is highly confidential and
> is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you are
> hereby notified that any viewing, copying, disclosure or distribution of
> this information is prohibited. Please notify the sender, by electronic
> mail or telephone, of any unintended receipt and delete the original
> message without making any copies.
>
>  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and Blue
> Shield Association.
>
> --
> 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: SUSE dump file location

2015-03-11 Thread Duerbusch, Tom
Finally found it.

Using:

find / -size +100k –mtime -30 –printf ‘\n\r%h’/’’%f %c %bK’

(lists any file greater than 100K that was modified within the last 30 days)

I found a log file in the db2dump subdirectory which was a little over 2GB
in size.


Thanks for the suggestions.


Tom Duerbusch

THD Consulting

On Tue, Mar 10, 2015 at 1:10 PM, Rob van der Heij  wrote:

> You need to escape the wildcards to avoid bash glob it.
>
> find -name \*.log
>  On Mar 10, 2015 7:06 PM, "Duerbusch, Tom" 
> wrote:
>
> > I was looking to reclaim some disk space.
> >
> > find / -name *.log
> >showed some likely candidates.
> >
> > Now looking for obsolete dumps.
> >
> > find / -name *.dmp
> > find / -name *.dump
> >   both shows nothing.
> >
> > Really?  I don't have any dumps?
> > I must have died and gone to heaven (or at least the nearest bar )
> >
> > This is a DB2 Connect application server.
> > So I really didn't expect it to use the 2 GB free space it had after
> > installation.
> >
> > So, logs, dumps, what else could be using this space?
> >
> > Thanks
> >
> > Tom Duerbusch
> > THD Consulting
> >
> > --
> >
> > --
> > 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/
>



--

--
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: SUSE dump file location

2015-03-10 Thread Duerbusch, Tom
I use du a lot.
Problem is that a lot of Linux directories are large.
Finding out what is fairly new would be the key.

Back, well over 10 year ago, I wrote a REXX exec to do a directory listing
of all files and only return the directory info for any file modified in
the last month.  This was a brute force method back on SLES 7 before I
started learning the weird command syntax that Linux has (vs mainframe
syntax...as god intended).

I packed up my SLES 7 and SLES 8 images on to tape back in 2012.
I knew there was a reason not to get rid of them .

Thanks

Tom Duerbusch
THD Consulting


On Tue, Mar 10, 2015 at 1:10 PM, Neale Ferguson 
wrote:

> Did you mean core*?
>
> du -h -x --max-depth=1 
>
> (-x will keep you on the same device or logical volume)
>
> Will help you identify directories using lots of space.
>
> On 3/10/15, 2:06 PM, "Duerbusch, Tom"  wrote:
>
> >I was looking to reclaim some disk space.
> >
> >find / -name *.log
> >   showed some likely candidates.
> >
> >Now looking for obsolete dumps.
> >
> >find / -name *.dmp
> >find / -name *.dump
> >  both shows nothing.
> >
> >Really?  I don't have any dumps?
> >I must have died and gone to heaven (or at least the nearest bar )
> >
> >This is a DB2 Connect application server.
> >So I really didn't expect it to use the 2 GB free space it had after
> >installation.
> >
> >So, logs, dumps, what else could be using this space?
>
>


--

--
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/


SUSE dump file location

2015-03-10 Thread Duerbusch, Tom
I was looking to reclaim some disk space.

find / -name *.log
   showed some likely candidates.

Now looking for obsolete dumps.

find / -name *.dmp
find / -name *.dump
  both shows nothing.

Really?  I don't have any dumps?
I must have died and gone to heaven (or at least the nearest bar )

This is a DB2 Connect application server.
So I really didn't expect it to use the 2 GB free space it had after
installation.

So, logs, dumps, what else could be using this space?

Thanks

Tom Duerbusch
THD Consulting

--

--
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/


SUSE 11 SP1 Missing configuration panel (yast)

2014-09-17 Thread Duerbusch, Tom
Network is changing our DNS servers, so I need to point our Linux images to
the new servers.

Under prior release of SUSE, it can be done via yast:

yast
   Network Devices
  DNS and Hostname
  and it drops you in DNS and Hostname Configuration panel

Under SUSE 11 (SP1) the DNS and Hostname option under Network Devices isn't
there.

I can manually edit the configuration files to get around this, but when
available, I use the panels  (sometimes the panels do something else that
I'm not aware of ).

So, is there a "yast" way of doing this?

Thanks

Tom Duerbusch
THD Consulting
--

--
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: SUSE 11 (SP 1) Missing configuration panel (yast)

2014-09-17 Thread Duerbusch, Tom
Exactly where it was moved to...

Thanks

Tom Duerbusch
THD Consulting

On Wed, Sep 17, 2014 at 2:05 PM, Pedro Principeza 
wrote:

> Tom,
>
> I could find, over Network Devices > Network Settings, a menu named
> "Hostname / DNS".
> Anyway, you could reach it through "yast dns".
>
> HTH,
> --
> Pedro.
>
>
>
> From:   "Duerbusch, Tom" 
> To: LINUX-390@VM.MARIST.EDU
> Date:   17/09/2014 16:01
> Subject:SUSE 11 (SP 1) Missing configuration panel (yast)
> Sent by:Linux on 390 Port 
>
>
>
> Network is changing our DNS servers, so I need to point our Linux images
> to
> the new servers.
>
> Under prior release of SUSE, it can be done via yast:
>
> yast
>Network Devices
>   DNS and Hostname
>   and it drops you in DNS and Hostname Configuration panel
>
> Under SUSE 11 (SP1) the DNS and Hostname option under Network Devices
> isn't
> there.
>
> I can manually edit the configuration files to get around this, but when
> available, I use the panels  (sometimes the panels do something else that
> I'm not aware of ).
>
> So, is there a "yast" way of doing this?
>
> Thanks
>
> Tom Duerbusch
> THD Consulting
>
> --
>
> --
> 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/
>



--

--
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/


SUSE 11 (SP 1) Missing configuration panel (yast)

2014-09-17 Thread Duerbusch, Tom
Network is changing our DNS servers, so I need to point our Linux images to
the new servers.

Under prior release of SUSE, it can be done via yast:

yast
   Network Devices
  DNS and Hostname
  and it drops you in DNS and Hostname Configuration panel

Under SUSE 11 (SP1) the DNS and Hostname option under Network Devices isn't
there.

I can manually edit the configuration files to get around this, but when
available, I use the panels  (sometimes the panels do something else that
I'm not aware of ).

So, is there a "yast" way of doing this?

Thanks

Tom Duerbusch
THD Consulting

--

--
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: Problem Unpacking SWAPGEN

2014-04-01 Thread Duerbusch, Tom
I've never got it to work:
VMARC UNPK

The way that works for me:

VMARC UNPK  FN FT FM = = differentFM

Tom Duerbusch
THD Consulting


On Tue, Apr 1, 2014 at 3:56 PM, Scott Rohling wrote:

> Did you ftp as binary?
>
> Scott Rohling
>
>
> On Tue, Apr 1, 2014 at 1:44 PM, Andrew Lemay  wrote:
>
> > I'm not sure if I'm missing something, But does anyone have any idea's
> why
> > this is failing to unpack.
> > I would wget the file from
> > http://download.sinenomine.net/swapgen/old/swap1308.vmarc and then tftp
> > the
> > file over.
> >
> >
> > Ready; T=0.01/0.01 15:34:21
> > VMARC UNPK
> > Incomplete input file specification
> > Ready(8); T=0.01/0.01 15:34:48
> > VMARC UNPK SWAP1308 VMARC A = = A
> > No archive members found in SWAP1308 VMARC A1.
> > Ready; T=0.01/0.01 15:35:08
> > PIPE < SWAP1308 VMARC a | fblock 80 00 | > SWAP1308 VMARC a F 80
> > Ready; T=0.01/0.01 15:38:00
> > VMARC UNPK SWAP1308 VMARC A = = A
> > No archive members found in SWAP1308 VMARC A1.
> > Ready; T=0.01/0.01 15:38:04
> >
> > --
> > 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/
>



--

--
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 disk space.

2013-08-16 Thread Duerbusch, Tom
I have also occasionally had that kind of problem.

I'm under VM, so I IPL the guest and specify another 512 MB of virtual
storage.
Run my maintenance.
Then reipl with the normal amount of memory for that guest.

Tom Duerbusch
THD Consulting


On Fri, Aug 16, 2013 at 10:32 AM, van Sleeuwen, Berry <
berry.vansleeu...@atos.net> wrote:

> Tom,
>
> What part in the install complains? Is it too low on /tmp or /var space or
> too low on / or /usr? And is it in lvm or not? LVM can be extended quite
> easy, a single minidisk might be a bit harder to extend.
>
> As a general rule:
>
> In the directory add the disk to the guest.
>
> On the guest (as root). The instructions might vary a bit depending on
> distribution and/or version.
>
> vmcp linkw
> chccwdev -e 
>
> Cat /proc/dasd/devices -> shows the 200 disk, note the /dev/dasd name.
>
> dasdfmt -b 4096 /dev/dasd
> fdasd -a /dev/dasd
>
> Now you can use the disk in the filesysystem or assign to lvm.
>
> Standalone:
> mke2fs /dev/dasd1
> mount /dev/dasd1 /mnt
>
> In lvm you need to pvcreate, vgextend, lvextend and resizefs the new space.
>
> If you want the disk to remain after a reboot, add it into udev or zipl.
> And add it to /etc/fstab to mount it at boot.
>
> Regards, Berry.
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Tom
> Huegel
> Sent: Friday, August 16, 2013 5:11 PM
> To: LINUX-390@vm.marist.edu
> Subject: Expanding disk space.
>
>
> This is a very basic question, but I am a basic LINUX novice.
> When attempting to install updates I get a message that I don't have
> enough disk space. How do I increase the space? I have another 3390-9 I can
> give to the guest LINUX vm, but how do I tell LINUX to use it?
>
> Thanks..
> Tom
>
> --
> 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/
>



--

--
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: IPLing from tape

2013-08-09 Thread Duerbusch, Tom
" As of next week, passwords will be entered in Morse code."

da dit da dit da da dit da

Tom Duerbusch
THD Consulting
(brother of K0BX)


On Fri, Aug 9, 2013 at 12:18 PM, John McKown
wrote:

> On Fri, Aug 9, 2013 at 11:26 AM, Alan Altmark  >wrote:
>
> >
> > I would like the HMC to allow upload of ISO images to a large-capacity
> USB
> > drive and for the Load from Removable Media function to allow selection
> of
> > said ISO image.  This would be similar in thought to the Mount Virtual
> > Media function available for zBX blades.
> >
> > Folks need to help your organizations move past the quaint notion that
> the
> > HMC is only for Other People.  It has a role for systems programmers, not
> > just machine jockeys.  And I expect that role will grow over time.
> There's
> > a reason it has remote access capability.  (Of course, I find lots of
> > shops fail to create individual user IDs on the HMC for the sysprogs with
> > appropriate assigned resource roles, causing the very thing they want to
> > avoid!)
> >
> > Alan Altmark
> >
> > Senior Managing z/VM and Linux Consultant
> > IBM System Lab Services and Training
> > ibm.com/systems/services/labservices
> > office: 607.429.3323
> > mobile; 607.321.7556
> > alan_altm...@us.ibm.com
> > IBM Endicott
> >
> >
> I'm still "lusting" after that SSD in the zEC12. What a neat place to be
> able to put some IPLable image. Of course, that would only be
> machine-specific. Being able to use the HMC could allow all CECs connected
> to it to IPL from it. Instead of a USB, have a portion of the HMC's hard
> disk "reserved for user files" for IPL et al.
>
> --
> As of next week, passwords will be entered in Morse code.
>
> Maranatha! <><
> John McKown
>
> --
> 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: Putty security

2013-03-06 Thread Duerbusch, Tom
IBM's PCOM has a TELNET option.

But really, Putty is just a name of a product that does TELNET (vs TN3270
for traditional mainframes).
Do a Google on TELNET and you can spend days looking at different TELNET
products.

Just to be different, I use KITTY instead of Putty .

Tom Duerbusch
THD Consulting

On Wed, Mar 6, 2013 at 2:47 PM, Rob van der Heij  wrote:

> On 6 March 2013 21:31, Peter Webb, Toronto Transit Commission <
> peter.w...@ttc.ca> wrote:
>
> > As a replacement, check out BlueZone VT from Rocket Software
> > http://www.rocketsoftware.com/.
> >
> >
> You sure? At least they only mention TN3270 over SSL etc.
>
> For SSH the easiest is probably a Linux desktop, and you can have a
> supported distribution for that. For Windows there's a list here:
> http://en.wikipedia.org/wiki/Comparison_of_SSH_clients  And if you're
> shopping for a Windows desktop, you might want to look into an X-Server as
> well.
>
> --
> 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: Hurricane webserver

2012-10-30 Thread Duerbusch, Tom
Don't discount the DASD system on a z box.

My IBM DS6800 manual states that a properly configured DS6800 can support
330,000 I/Os per second.  Obviously, no one actually has a properly
configured DS6800 (and I assume that the DS8*** boxes are even better).

My point is that the PC I/O system really pales compared to a modern
mainframe.  If your application needs to support 10,000 I/Os per second or
so, you won't need the "tricks".

And, of course, a good performance monitor can, more easily, point you to
where any performance bottlenecks are.

Tom Duerbusch
THD Consulting

On Tue, Oct 30, 2012 at 9:00 AM, David Boyes  wrote:

> >But our Z enthusiast
> > says we can put Redis and memcache on Z-Linux (under VM) without any
> > loss of functionality or performance (because we have extra capacity and
> > "paging on Z doesn't cost anything").
>
> I'd agree on functionality, but performance is a harder question.  Both
> redis and memcache build and run fine on Z, no problems there. The trick is
> that memory usage in a shared environment is much trickier to calculate the
> impact of mass allocations of RAM -- depends a lot on where and how fast
> you page, whether you have XSTOR or not, etc, etc, etc,.
>
> I'd try it with a smaller database and see how it goes. XSTORE will have a
> measurable impact, as will use of VDISK for paging.
>
> --
> 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: HyperPAV and LVM striping

2012-10-10 Thread Duerbusch, Tom
So that might have been my problem (but not necessarily limited to that
one).

I was on Suse 10 system.  I initially stripped the LVM.  When it got nearly
full, I tried to add a pack.  Couldn't do it.  So I went back and recreated
the LVM without striping and I could add a pack.  I want to say that the
documentation at that time, also said you couldn't add packs to a striped
LVM, but that was a while ago.

Anyway, it hasn't been a performance issue.  But that is due to us not
needing the I/O performance.

Thanks for the update.  I'm updating my notes.

Tom Duerbusch
THD Consulting

On Wed, Oct 10, 2012 at 12:53 PM, Mark Post  wrote:

> >>> On 10/10/2012 at 11:35 AM, "Duerbusch, Tom" 
> wrote:
>
> > Just speaking to LVM...
> >
> > Striping the data across multiple volumes (which in modern dasd is
> already
> > stripped in the Raid array), would give you the best performance.
> >  Especially if you can strip across multiple DS8000 (or other dasd
> > subsystems).
> >
> > But you can also use LVM as a pool of DASD, with no striping involved.
> >
> > In case 1, if you need to expand the LVM pool, it is a hassle.  It might
> > mean backing up, reformatting and reloading the data.  In any case, it
> > involves a knowledgeable person and most likely, downtime.
>
> This is simply not true.  Expanding a striped LV can be done dynamically
> with no downtime.  The only aspect that is different from a non-striped LV
> is that you have to have enough free space on as many different PVs as the
> number of stripes you have.  That is, if you did an "lvcreate -i 2" then
> when you do an lvextend/lvresize, you have to have free space available on
> 2 different PVs in the pool.  An "lvcreate -i 3" means you need free space
> on 3 PVs, etc.
>
> A lot of people tend to add space to a volume group one PV at a time.  If
> you're using striped LVs, that won't work unless you make sure that the
> existing PVs have enough free space on them to accommodate additional
> stripes being allocated.
>
>
> 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: HyperPAV and LVM striping

2012-10-10 Thread Duerbusch, Tom
Just speaking to LVM...

Striping the data across multiple volumes (which in modern dasd is already
stripped in the Raid array), would give you the best performance.
 Especially if you can strip across multiple DS8000 (or other dasd
subsystems).

But you can also use LVM as a pool of DASD, with no striping involved.

In case 1, if you need to expand the LVM pool, it is a hassle.  It might
mean backing up, reformatting and reloading the data.  In any case, it
involves a knowledgeable person and most likely, downtime.

In case 2, if you need to expand the LVM pool, you can just add disks to it
on the fly (and even easier with VM).  No downtime.  I add dasd to my LVM
pool in minutes.

The trade off is normally (well isn't it always), performance vs man power.
 If you find you really don't need the "BEST" performance, then make the
job easier.

But then, I you know the requirements of your application.

Tom Duerbusch
THD Consulting

On Tue, Oct 9, 2012 at 5:50 PM, Brad Hinson  wrote:

> Hi folks,
>
> What are the best practices for HyperPAV and LVM striping?  I assumed that
> if you have HyperPAV enabled, you don't need to stripe the data.  Is this
> true, or if not, what is the best practice for optimum performance?
>
> I have lots of mod-9 ECKD with HyperPAV enabled, so I want to use LVM.  So
> my two choices are standard LVM, or LVM striping.  If I stripe across the
> disks I spread the I/O across the physical volumes, but my gut tells me I
> shouldn't have to do this, since HyperPAV is moving around aliases
> dynamically.  For example, say I have 2 PVs and 4 HyperPAV aliases.  If I
> send some heavy I/O through the Linux (device-mapper) block device, then I
> would assume:
>
> - #1, for the case with LVM striping enabled, LVM will spread the I/O to
> both PVs, and HyperPAV will assign 2 aliases to each PV since I'm banging
> on them both.
> - #2, for the case without LVM striping, HyperPAV will assign 4 aliases to
> the first PV since that's the only one in use.
>
> In either case, it seems I'm using all 4 aliases, so seems like I would
> get the same performance.  Please correct me if I'm wrong.  And if so,
> which of these configs is better?
>
> Lastly, is there a presentation or doc that talks about how to enable
> HyperPAV in Linux, or is bringing the HyperPAV aliases online enough to
> trigger the dasd driver to do the right thing?
>
> Thanks as always,
> -Brad
>
> --
> Brad Hinson
> Solution Architect, Red Hat
> +1 (919) 360-0443
>
>
>
>
> --
> 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/