Which release of SUSE? Did the DB2 Connect package come as an RPM, or in some
other format?
Mark Post
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU]On
> Behalf Of Tom
> Huegel
> Sent: Tuesday, April 09, 2024 12:34 PM
> To: LINUX
team will have control of the actual
disk volsers, since Linux won't be re-writing them, due to not being
able to modify cylinder 0.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send
.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
I'm very sad to hear this. You're right, he was a great guy. Going through RHCE
training with him (and you) in New York was fun.
Mark Post
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU]On Behalf Of
> Michael MacIsaac
> Sent: Wednesday, June
On 5/11/2023 5:46 PM, Rogério Soares wrote:
I see a lot of oom-killer when dd
runs..
This sounds like you need to increase the amount of memory defined for
this system.
PMR opened with IBM
Glad to hear it.
Mark Post
tried with a more modern version?
Have you collected any performance data both when and when not seeing
the problem?
What sort of crashes are you seeing? Any dumps taken?
I have adjusted multipath.conf as suggested by ibm, but no luck yet...
What sort of adjustments did they recommend?
Mark
See Dan's reply. Red Hat renames that to s390utils-base.
Mark Post
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU]On Behalf Of
> Martha McConaghy
> Sent: Wednesday, May 10, 2023 5:24 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject:
that was made to work with 3270/3215 terminals had been open
sourced before the company went under, but that never happened.
Mark Post
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU]On Behalf Of
> Rich Smrcina
> Sent: Thursday, May 04, 2023 5:55 PM
.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
Hi, Phil,
Thanks, I appreciate the thought.
Mark
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU]On Behalf Of
> Phil Smith III
> Sent: Thursday, February 16, 2023 11:37 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Taking some time
>
>
> Best wishes,
964-8867
> Main: (877) 964-8867
> r...@velocitysoftware.com <mailto:r...@velocitysoftware.com>
>
>
> > On Feb 15, 2023, at 9:55 AM, Mark Post wrote:
> >
> > All,
> >
> > I'm retiring from SUSE. Today is my last day on the job. I intend to
> > stay
literally been
a dream job for me.
I'm thankful to the many people that have helped me over the years.
Without them, I might never have been able to make working with
mainframe Linux my career for 20+ years.
Mark Post
--
For LINUX
On 11/18/22 10:39, Philip Tully wrote:
Hello all,
Is there any interest from the community to have AAP (formerly Ansible Tower)
available to run on s390x?
How is that different from just plain Ansible?
Mark Post
On 10/27/22 14:22, Victor Echavarry wrote:
Our SUSE is 15 SP5 under z/VM 7.2.
Just in case anyone else sees this and thinks they missed something, the
latest version of SLES is SLES15 SP4, so this is most likely a typo.
Mark Post
to
perform a brand new installation, you'll need to either access the SUSE
repositories for all the packages that have not been updated, or a local
mirror of the packages, such as provided by SMT (Subscription Management
Tool), RMT (Repository Mirroring Tool), or SUSE Manager.
This was (hopeful
some time, this is the first that I'm aware of the availability of
no-cost access to IBM Z hardware for z/OS-based Open Source developers.
It will be interesting to see if any more z/OS-based OSS projects come
along to make use of this.
to
perform a brand new installation, you'll need to either access the SUSE
repositories for all the packages that have not been updated, or a local
mirror of the packages, such as provided by SMT (Subscription Management
Tool), RMT (Repository Mirroring Tool), or SUSE Manager.
Mark Post
able to run vgscan and pvscan to see if those report any
missing disks. If they do, then bring the volume online and re-run them.
Then "systemctl default" should bring the system up the rest of the way
and you can check to see if the necessary udev rules are there, or if
they're exclud
you've opened.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
more capable, and hence complex,
than what is needed during cloning. Use chzdev/lszdev for "normal"
system administration tasks where you actually want those udev rules to
be written/deleted.
Mark Post
--
For
that way, use "chzdev -e -p" to write out the new
udev rules. If you leave the "-p" off, the command will look to see if
the device is already online, and say that it's already configured, and
not write out the rules. Then you can manually delete the 51-
On 8/20/21 5:09 PM, Aria Bamdad wrote:
I have
reported these to SUSE but
they tech said she has no access to Z system so is testing on another
architecture. I don't
think that will help!
No, it won't help. Have that person call me directly.
Mark Post
column it lists 'no' for all of them. Clearly not the case!
IBM's lszdev command only looks for /etc/udev/rules.d/41-* files to
report its findings.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions
t;lsdasd | grep
-i diag" will show you all of those.
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://w
rules renamed to .legacy, is there an
equivalent 41-* rule present?
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
On 8/5/21 9:25 AM, Neale Ferguson wrote:
I'll check. All I remember is that it's a bugger to build.
Does that mean you have a binary RPM that Frank can use without building
it himself?
Mark Post
--
For LINUX-390 subscribe
On 7/26/21 12:25 PM, Frank M. Ramaekers wrote:
rsync -avzrni --ignore-existing
/home/framaekersroot@192.168.199.88:/home/framaekers
Try adding a slash to the end of each argument:
rsync -avzrni --ignore-existing /home/framaekers/
root@192.168.199.88:/home/framaekers/
Mark Post
made in this release.
Reading the release notes would be advisable. And not just the IBM Z
specific parts, but all of them. As those who know me can attest, I am
*not* above saying "I told you so" as appropriate. ;)
https://www.suse.com/releasenotes/s390x/SUSE-SLES/15-SP3/
er console management to let
him see early boot errors?
That, I can't answer at all. I remember using the ASCII console to do an
install with the ncurses installer, but I don't recall trying to do any
scroll back on it.
Perhaps using a phone camera to capture video would help?
to the guest.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
is not now, something should
show up in dmesg, or one of the numerous system logs.
-snip-
If I IPL the guest the issue is solve.
Just a simple re-IPL, or actually logging off and back on again?
Mark Post
--
For LINUX-390
and effort
she put into this. It was no small task, and she did a great job.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390
On 5/20/21 5:32 PM, Alan Altmark wrote:
> But I don't know if the Linux device drivers will generate UDEV events
> based on it. It would be nice if they did.
I just ran a test, and it doesn't seem to do so.
Mar
On 5/20/21 4:06 PM, Mark Post wrote:
> If the message you get from CP is an SMSG, then you can have udev rules
> that would get triggered to check to see what was in the SMSG, and act
> on it as appropriate.
>
> I don't know if those *are* SMSGs or not, but if they are, this is t
ggered to check to see what was in the SMSG, and act
on it as appropriate.
I don't know if those *are* SMSGs or not, but if they are, this is the
approach I would take.
Mark Post
--
For LINUX-390 subscribe / signoff /
in case you run the cio_ignore commands
> prior to an LGM?
Better yet, for z/VM and KVM guests, get rid of cio_ignore altogether.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send
to derive value from it. The details on what will be
included are in Mike Friesenegger's blog posting at
https://www.suse.com/c/bringing-rancher-value-to-ibm-z-and-linuxone/
SUSE will be making further announcements about this in the future, so
please say tuned.
On 3/12/21 4:35 PM, Mark Post wrote:
> It sets the scheduler to use mq-deadline (multi-queue deadline). You
> could, if you choose, override that with one of the other choices, but I
> wouldn't do that without getting some indication from one of IBM's
> performance folks that you
(multi-queue deadline). You
could, if you choose, override that with one of the other choices, but I
wouldn't do that without getting some indication from one of IBM's
performance folks that you should. Our direction from that source was
that with the introduction of mq-dead
Hi, Stefan,
I would think sending this to the IBMVM and IBM-Main listservs would
also be a good idea, to increase your chances of reaching the person.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instruction
blems that are
really early in the boot process, this won't suffice. Once you get past
that point, things do indeed look a lot more like "normal" to the
typical Linux system administrator.
Mark Post
--
For LINUX-390
to
perform a brand new installation, you'll need to either access the SUSE
repositories for all the packages that have not been updated, or a local
mirror of the packages, such as provided by SMT (Subscription Management
Tool), RMT (Repository Mirroring Tool), or SUSE Manager.
Mark Post
ting
cio_ignore into the kernel parms by default. That caused problems like
this one, and we changed the installer so that installs performed in a
virtualized environment did not insert cio_ignore. I.e., z/VM and KVM.
That eliminated a large number of customer proble
rip you up at some point.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
ved to KVM as a model.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
of the packages, such as provided by SMT (Subscription
Management Tool), RMT (Repository Mirroring Tool), or SUSE Manager.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.mar
t's time to open up a support request.
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://www2.marist.edu/htbin/wlvin
gt; path 01 leads to device EMC.09000ATVHC.3000.0f.000101f
What version is this from? According to the man page for SLES15 SP2, the
message should say "path xx leads to instead of "
Mark Post
--
, is it a correct assumption ?
>
> Scenario 1:
> 2x zLinux on VSWITCH (option Layer-2), same VLAN, connected to same VSWITCH
> (same CHPID) on the same zVM LPAR.
Yes, unless OSAs are put into "hairpin" mode, which forces the traffic
to go out of the LPAR to the switch,
m/components/ibm-linuxone/gettingstarted/ for
more information.
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
t. I will try
to avoid doing that again in the future.
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://www2.mar
inframe when it first came out.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
e packages were
*just* made available. Why they aren't maintained on github like some of
their other packages is unknown.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists..
On 9/8/20 1:16 PM, Alan Altmark wrote:
> Your paint brush is a bit too large with "any and all", Mark.
A bit, yes.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send e
ools out there that run from a privileged account that
will go into the control blocks for the target guest and change things.
As you might expect, that sort of thing can be dangerous. Still, if
getting this done is important enough, you could ask on the IBMVM
mailing list to see
On 8/19/20 4:45 PM, Christian Svensson wrote:
> I might end up writing a patch for AF_IUCV unless somebody can
> convince me it is a bad idea.
I would say that trying to get this upstream would be preferable for
everyone.
Mar
ARE entitled "If
I Send a Special Message to Linux on System z Will it Answer? Automating
Linux on z/VM"
It should be in the proceedings from SHARE 119, 120, 121, and 122. If
not, I can send you a copy.
Mark Post
--
F
nd difficult.
That should happen automatically within systemd. I would say try without
doing that yourselves, and see if the appropriate pid file shows up
somewhere under /run. If it doesn't show up, then you'll need to write
something yourselves.
On 8/18/20 1:30 AM, r.stricklin wrote:
> Once the install completes I shall have to see about experimentally finding
> the actual limit.
The tracepath command should be able to show you that without a lot of
trial and error.
Mar
>tx_errors: 10
>Do you want to ignore this error and continue anyway?
>
> So... where am I going wrong?
Well, to me, where you're going wrong is not defining the Linux system
as a guest of your z/VM system. :) Why do you want it as an LPAR, and
not a guest?
Beyond that, I think that y
o specify 16 virtual CPUs for one Linux guest,
while not changing the number of actual CPUs available to the LPAR?
That's usually a bad idea.
If you're talking about something different, please say so.
Mark Post
--
For LINUX-390
problems, since the communications between the "jump
server" and the target system are over IUCV.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the
ia a web browser to the HMC? Or some other method?
I don't have much faith this will help, but "shift+insert" may help. At
times on my Linux desktop, I have to use "shift+control+insert."
Mark Post
--
For LIN
e hvc0 console device
are active. You can miss some of the very early messages because of that.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message
it sounds like we're (almost) on the same page.
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://www2.marist.edu/htbin
sorts of REXX execs and bash scripts to figure out
this small set of information. There may be others out there that are
interested in much more than this, but so far they haven't said so (on
this mailing list anyway).
Mark Post
--
For
terested in finding out they're running 6
layers of virtualization deep and what each of those is. If someone does
want that, they should speak up.
I believe something like this would allow for easy scripting by system
administrators. Of course, others may have differing op
you never know, I suppose.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
On 7/22/20 4:37 PM, Alan Ackerman wrote:
> Humpf! I think my opinion still counts. I may never use it, but I think Bank
> of America probably will.
Are they running SUSE Linux Enterprise Server?
Mark Post
--
For LIN
ed environments.
> So: Would the output below help, or should we rather have a separate tool
> with a
> more comprehensible format?
The latter. Please let me know if you're going to proceed with this. If
so, I won't start working on the limited command I already talk
the SLES 11 runs on the z/15 to finish the migration.
SUSE does not have a z15, so we are not able to test that combination.
Personally, I wouldn't risk trying it.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access
On 7/20/20 1:09 PM, Stewart, Lee wrote:
> +1
OK, that's one (sorry, but retirees who won't use the tool don't help
the business case). Anyone else?
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructi
guest would be wrong, but I don't think you use that.
Would people find it helpful if a command is introduced to the
s390-tools package that will return one or more of the following data
points:
1. z/VM or KVM Guest name
2. z/VM Host name
3. KVM Host name
4. LPAR name
support for multipathing in the
initrd or not. That may be something to run a Google search on.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
On 6/30/20 1:44 PM, marcy cortes wrote:
> The correct way would be to use /etc/mod probe.d/ for SUSE
True, but I didn't have time to play around and make sure I had the
correct syntax needed.
Mark Post
--
For LINUX-
d work.
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://www2.marist.edu/htbin/wlvindex?LINUX-390
robe command for it, and use chkconfig to set
it on.
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://www2.marist.edu/htbin/wl
/ then
you shouldn't have to do anything with this.
Is the reason you're doing this because everything is lumped into one
large file system, and things like /usr, /tmp, etc., are all in it? If
so, then there's a "how to" on linuxvm.org that talks about how you can
split off things into separate file sy
getty
running:
Welcome to SUSE Linux Enterprise Server 12 SP2 (s390x) - Kernel
4.4.121-92.120-default (ttyS0).
The "terminal" is shown as ttyS0. Would a LINEMODE session wind up on a
different terminal, somehow?
Mark Post
--
s hoping my line mode telnet session would be working
again. But, it wasn't.
Any ideas on just what problem(s) I'm running into here? Pointers to
documentation on how to get things working?
Thanks,
Mark Post
--
For LINUX-390 sub
site. Just to remind everyone, there's also gzip compressed copies of
all the archives at http://linuxvm.org/archives/
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist
On 6/1/20 2:36 PM, Dave Jones wrote:
> It was an M3K, Mark. Interesting times, then.
That is one of the bigger understatements I've heard lately. :)
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructi
ux guest on z/VM:
http://www.fsf.net/~adam/NT-on-390-desktop.png
When the snapshot was taken, they were using Dave Jones' Multiprise. I
can't recall if it was a Multiprise 2000 or 3000.
Mark Post
--
For LINUX-390 subscribe / s
On 5/29/20 5:13 AM, Berthold Gunreben wrote:
> osc chroot --vm-type qemu --vm-memory=8192 standard s390x
Interesting. There's a group of people on Twitter that would be happy to
know about this, if you have an account there.
Mark P
MS FTP client, or from an
FTP client running elsewhere.
If you're signed onto CMS and executing FTP GET commands, then the
"locsite" is correct. If you're doing FTP PUT commands from somewhere
else, then the "QUOTE SITE" form is correct. The example shown in the
Red Hat document
On 4/29/20 10:49 AM, Alan Altmark wrote:
> (I never realized QEMU was a general purpose emulator,
> capable of doing cross-platform emulation.)
It always has been, but SUSE, for example, has never built it with that
option for our products because the performance is rather horrible.
Mar
ug=1
3. Close the spool file (#CP SP CONS STOP CLOSE)
4. Transfer the console log to either another Linux guest, or to a CMS
user so that it can be examined.
You're going to see a *lot* of output from this. Hopefully somewhere in
there
tually there? Are any missing?
At this point, is the root file system available? Is it mounted?
Are any devices being ignored, in /proc/cio_ignore?
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
ot;grub2 kernel" and "grub2
initrd" that are located in /boot/zipl.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-3
ng a logical volume again and see if the problem
reoccurs or not. This is very much stabbing in the dark, but it might
provide some relief.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
log from
the boot process. Is every device being found and handled properly? And
so on. Check /etc/lvm/lvm.conf to make sure the filter statement(s) in
there aren't excluding anything you need. Essentially, you need to dig
into the whole configuration and devices to make sure everything lines
up prope
a z/VM guest, it doesn't need that. At
all. If you were a brand-new z/VM systems programmer that had tons of
unnecessary devices defined, that would be different. But, you're not. :)
Mark Post
--
For LINUX-390 subscribe / s
okbook for IBM z Systems Volume 2: Red Hat
Enterprise Linux 7.1 Servers
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visi
hing* the system would have done
for you before it failed. But, if what you need is the biggest hammer
you can find, that's it.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists.
ans packages can be replaced, dropped,
etc. It also means that any shift in general philosophy will be seen
there first. So you may see differences in Tumbleweed, before they are
seen in SLES, but most (or all) of those will eventually show up in SLES
as w
same.
I don't understand what you're asking here.
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://www2.marist.
be to try and specify "hvc_iucv=8 console=hvc0
init=/bin/bash" on the command line, and use the terminal server tools
from another guest to get access.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instr
On 3/9/20 12:29 PM, Will, Chris wrote:
> Have a broken sles 12 server. I believe at one point there was an option on
> the "ipl 100" to go into single user mode. Any help?
IPL 100 PARM 1
Mark Post
--
For LIN
other things listed there. The Installation Quick Start
document from https://documentation.suse.com/sles/15-SP1/ can tell you
more. The whole document is only 31 pages long including the table of
contents, and legal stuff, so it's not very long.
Mark Post
-
3033MB 5896620
Using the dmesg command may provide some more info. If not, you can put
udev into debug mode to see if you can get more information that way.
It may also be worthwhile to execute
echo 0 > /sys/bus/ccw/devices/0.0.012c/readon
1 - 100 of 3645 matches
Mail list logo
