I had a trouble last week on three of my linux images that used the diag
option of the dasd driver, that curiously appeared after a VM re-IPL.
my configuration : kernel 2.4.7 + devfs under z/VM 310 on an HDS pilot 48E.
the linux ipl stops systematically for all of these 3 servers ( they were
Are there any IMS database clones available for Linux?
No, the only clone that ever existed was MicroFocus COBOL IMS which is/was
Windows only.
Access to IMS DB is possible using DB2 stored procs and ODBA. See
http://www.redbooks.ibm.com - SG24-5485.
Access to IMS DC (aka TM) is possible using
So, Martin, how long does a jump take before you're on the ground
with both feet again ;-)
About 3-4 minutes.
blue skies,
Martin
Linux/390 Design Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: [EMAIL PROTECTED]
After rhsetu I get the following error
/sbin/zipl
building bootmap: /boot/bootmap
adding Kernel Image : /boot/vmlinuz-2.4.9-17-tape located at 0x0001
Error: Could not retrieve info for target
/boot/vmlinuz-2.4.9-17-tape.Error: Could not add file to bootmap:
/boot/vmlinuz-2.4.9-17-tape.
I am experiencing a problem installing RedHat Linux for S/390 ver. 7.2 in
LPAR mode. We are trying to use an ATM OSA Express card that runs in TR LAN
emulation. The network device is at E100 and relative port 0. When the
following configuration question comes up I ve tried unsuccessfully to
Red Hat has philosophical objections to OCO code, and so refuses to ship
them with their software. You'll need to go to
http://www10.software.ibm.com/developerworks/opensource/linux390/special_oco
_rh_2.4.shtml and read the instructions there, as well as download the OCO
module(s) you need.
We have tried to use CTG 3.5 on a SUSE SLES 7 distro (kernel 2.4.7),
unfortunately we are getting some abnormal connection errors. Utilizing
CTG 3.5 on a kernel 2.2x distro works fine.
Has anyone succeeded installing CTG onto a kernel 2.4.7 like us? If you
did, could you tell us how you
In a message dated 2/26/2002 6:15:08 AM Mountain Standard Time,
[EMAIL PROTECTED] writes:
After rhsetu I get the following error
/sbin/zipl
building bootmap: /boot/bootmap
adding Kernel Image : /boot/vmlinuz-2.4.9-17-tape located at 0x0001
Error: Could not retrieve info for target
To help answer my own questions
I did some searching on the list archives and it appears I need
the defs below in RH7.2.
I also read some conflicting replies on MSU? What should the MSU be for CTC
to OS/390?
Also read about having to fake out SAMBA and tell it the netmask is
255.255.255.0
Dave,
Do you mean MTU instead of MSU? You can have the MTU be anything you want
to make it, up to about 32K (there's some overhead so it can't be quite that
high) so long as both sides agree on what that it.
Yes, tell Samba in /etc/samba/smb.conf that the netmask is not all ones.
Someone on
CTC0 is for the good old parallel channel type channel to channel. Use
ESCON0 if you have a newer escon channel to channel connection. I had all
my systems using virtual ctc under VM. When I tried moving one of these
machines to an LPAR, I found that ctc didn't work because I had physical
For the RH releases, you'll find them in the /etc/rc.x (where x = runlevel)
directories. For example, my runlevel 3 sshd start script is
/etc/rc.3/S55sshd.
--Jim--
James S. Tison
Senior Software Engineer
TPF Laboratory / Architecture
IBM Corporation
+1 203 486-2835 (voice/fax)
[EMAIL PROTECTED]
All depends on what run level you want SSHD running at. Mine
is running at rc2.d and rc3.d. Just symlink from there into the
init directory like this:
cd /etc/rc.d/rc2.d/
ln -s ../init.d/sshd Sxxsshd
cd /etc/rc.d/rc3.d/
ln -s ../init.d/sshd Sxxsshd
where xx is what position you want it to
Quoting Paul C. Williamson [EMAIL PROTECTED]:
cd /etc/rc.d/rc2.d/
ln -s ../init.d/sshd Sxxsshd
cd /etc/rc.d/rc3.d/
ln -s ../init.d/sshd Sxxsshd
Or you can use 'chkconfig' for redhat and 'rctab' for suse.
It will do the work for you. :-)
Yuval.
I am trying to start sshd at boot time. Currently I can only start it
manually by:
./etc/rc.d/init.d/sshd start
Where is it normally initialized at boot?
chkconfig --level 345 sshd on
Or via the gui tools, I guess the command line is the preferred S/390 beast
though ?
I am trying to start sshd at boot time. Currently I can only start it
manually by:
./etc/rc.d/init.d/sshd start
Where is it normally initialized at boot?
Red Hat?
chkconfig --list
chkconfig sshd on
man chkconfig
--
Cheers
John Summerfield
Microsoft's most solid OS:
I am trying to start sshd at boot time. Currently I can only start it
manually by:
./etc/rc.d/init.d/sshd start
Where is it normally initialized at boot?
chkconfig --level 345 sshd on
Or via the gui tools, I guess the command line is the preferred S/390 beast
though ?
If you
Can anybody advise me on defining virtual CPUs for use by
a 2.2.16 level Linux kernel? Does it buy me anything to give
a Linux image more than one (virtual) CPU, or should I just
give each image one and let CP do the multiprocessing? TIA.
Dave Jones
Dave Jones
On SuSE this is placed into /etc/init.d/rc.config as START_SSHD=YES
/etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE
blah blah use /etc/init.d think that is system 5 or LSB some such
standard, not sure why RH adds the other layer.
Regards,
Jon
Jon R. Doyle
Sendmail Inc.
I'm loving chkconfig...so much easier...although it is still nice to
know how chkconfig works...
I learn something new everyday from you folks. Thanks!
and yeah, in most cases I'd agree that you want to check with
what the vendor recommends. I have certain reasons I want
sshd running in
On SuSE this is placed into /etc/init.d/rc.config as START_SSHD=YES
/etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE
blah blah use /etc/init.d think that is system 5 or LSB some such
standard, not sure why RH adds the other layer.
So far as you're concerned, RH uses
Mark Post wrote:
This has gotten to be a FAQ, so I just (right now) put up a new page on
linuxvm.org to address it. Take a look at
http://linuxvm.org/Info/HOWTOs/movefs.html for details, and let me know if
you run into any problems with the instructions. I'm always interested in
making them
Wolfe, Gordon W [EMAIL PROTECTED] writes:
and so on. I'm not really that familiar with the patch and
diff process.
Why do some work and not others? Can anyone point me in the right
direction?
I haven't looked at the kernel source that SuSE ships for 2.4,
but the answer is most likely that
Humm, right, I think the LSB thing might be where this came in, seems I
remember that RH on or around 7.2 started supporting LSB too, I thnk I saw
them talk about this or it was the LSB folks in NY last month at LWE.
Regards,
Jon
On 2/26/02 1:45 PM, John Summerfield [EMAIL PROTECTED]
Can anybody advise me on defining virtual CPUs for use by
a 2.2.16 level Linux kernel? Does it buy me anything to give
a Linux image more than one (virtual) CPU, or should I just
give each image one and let CP do the multiprocessing? TIA.
I don't think it buys you anything
other than to
On Tue, 26 Feb 2002, Jon R. Doyle wrote:
/etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE
blah blah use /etc/init.d think that is system 5 or LSB some such
standard, not sure why RH adds the other layer.
/etc/rc.d/init.d should be (as in if it is not, then make it
Assuming installation and configuration is just a matter of learning
something new, is there any reason to favor one of the Linux/390
distributions over the others?
--
James JohnsonEmail: [EMAIL PROTECTED]
Systems Programmer Voice: 660-543-8065
Depends upon how YOU personally feel about technology vs
peception/marketing. Often the best technology does not win, look around
at Exchange vs GroupWise or Intel and Alpha chips. Windows vs OSX or
Redhat vs SuSE.
Do not remember who told me this, but my favorite line on we American's
buying
Carlos,
You're being a little too vague for me to be sure I know what you're saying.
Do you mean linux-2.4.7-s390-3.tar.gz and s390-4.tar.gz from
http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4.
shtml?
Mark Post
-Original Message-
From: Carlos Ordonez
No sure about that, you should read the LSB docs for builds, certainly has
changed. Right, SuSE did place a symlink there for the RH RPM's But
calling this Standard is a little far, Solaris and system V are
/etc/init.d But, anybody can make a standard I guess, just have to get
people to follow it
Sure, a number of them. Support contract costs. Support contract benefits.
Support contract requirements (who needs to do what for you to be eligible
for support on any given system). Customer Service attitude. Distribution
philosophy. Support for OCO modules from IBM. Responsiveness of
Well,
the basic reason is that the patches on developerworks are meant to be
applied on an
unchanged vanilla kernel as from http://www.kernel.org
Every distributor patches the kernel in a way so that the patches on
developerworks
may or may not apply cleanly. Apart from applying, it is also the
CTG 3.5 for Linux/390 was the original beta release. I'm going to guess that
the only one that will work anymore is 4.0 and, sadly, it is no longer
available for the taking. :(
On Tuesday 26 February 2002 08:28 am, you wrote:
We have tried to use CTG 3.5 on a SUSE SLES 7 distro (kernel
Mark Post wrote:
Actually, all I wanted to indicate was that people with 2.2 kernels will
need to reboot to add DASD. I didn't want to get into the details of how
all that is done in this particular HOWTO. So, I reworded the 2.2 part to
take out those details.
Actually, that was the hardest
Unless the Linux application is multithreaded (like Apache or such), you'll
see a small kick from going from 1 to 2, and diminishing returns for n=3.
Keep in mind that the timeslice for the virtual machine is divided between
all the virtual CPUs defined, so you *can* make it worse (see some of
What are the ISAM options on Linux/390 and Linux/86?
Thanks,
Samy Rengasamy.
-Original Message-
From: Rich Smrcina [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 25, 2002 3:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Cobol and IMS for Linux
I'm not sure about the IMS part, but there
Create a shell script 'sshd' with the following line
/sbin/sshd or /actual-path-of-ssh-installed/sshd
in directory /etc/rc.d
Then create a link S10sshd to /etc/rc.d/sshd at directory /etc/rc.d/rc2.d
Then on reboots, sshd will start running.
This is specific to SuSe. Red Hat may have a
Not necessary, just add the variable YES in rc.config for START_SSHD=.
This file is located in /etc All lot of options are placed here and the
script SuSEconfig builds everything for you. You can also do this through
YAST with System Admin and then change configuration file You need to
have the
38 matches
Mail list logo
