Hello,
Did you see the new beta feature of google
http://news.google.com/news?hl=en&q=linux+mainframe&btnG=Google+Search
I found this link :
http://www.informationweek.com/news/IWK20020314S0030
Wisconsin Physicians Service Corp. in Madison, Wis., last year processed
more than $7 billion in cl
Hi, Harry
Your patch to tubfs.c breaks the configuration script in
Documentation/s390/config3270.sh. Either you should remove the tubfs.c
patch or you should make similar changes to tty3270_read_proc() in
tubtty.c.
My preference is that you remove the tubfs.c patch. I'm an extreme
old-timer an
Arg - it is there but not very obvious (like everything else with this
package).
Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598
Phone: (925) 926-5332
Per Rich's suggestion (via private e-mail) I waited 10 minutes and the
link activated.
Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598
Phone: (925) 926
> During the configure process, I did get the following warning:
> THREAD MUTEXES NOT AVAILABLE FOR THIS COMPILER/ARCHITECTURE
>
> I do believe Linux/390 does support multi-threading and hence mutexes
> towards that.
For performance the db libraries try and use architecture specific
locking trick
Is it using ./configure? If so check config.log to see where it was
determining this. Otherwise just search the configure script.
> -Original Message-
> I did a build and install of Berkeley DB 4.0.1 in our SuSE
> Linux 7.0 (s390)
> - Kernel 2.2.16.
>
> During the configure process, I did
I did a build and install of Berkeley DB 4.0.1 in our SuSE Linux 7.0 (s390)
- Kernel 2.2.16.
During the configure process, I did get the following warning:
THREAD MUTEXES NOT AVAILABLE FOR THIS COMPILER/ARCHITECTURE
I do believe Linux/390 does support multi-threading and hence mutexes
towards th
> We installed the 2.4.7 kernel on 5 full pack mini disks as follows:
>
> /dev/dasda1
> /dev/dasdb1
> /dev/dasdc1 lvmsuse
> /dev/dasdd1 lvmsuse
> /dev/dasde1 lvmsuse
>
> Our parmfile is:
> dasd=0200,0100,0101,0102,0103 root=/dev/dasdb1 noinitrd
>
> so dasda1 is the swap file, and
> Hmmm. On taking another look, the "--justdb" function might do this. The
> man page says that it is used to "Update only the database, not the
> filesystem." Does anyone know for sure if this is what Thomas is looking
> for?
to do that you need an rpm. If you have an rpm, best to install it
Frank,
Take a look at basic TCPIP support. It does provide
remote access to MVS access without USS.
--- Original Message ---
From: Frank Prappacher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Communication with OS/390
>Well,
>on some of our OS/390 machines there is no USS
instal
Jim,
Good thing you sent me a picture you liked. This is what I would have had
to use otherwise! LOL. With an appropriately humorous caption, of course.
:)
Mark
<>
Steve,
I went back and checked and yes, it was runsocks. There wasn't a Linux/390
port of it available, so I downloaded the source code. The memory is a
little vague, but I don't recall doing anything heroic to get it to compile
on Linux/390. It was a life saver for doing things like "wget" co
James,
Thanks for the update. That is pretty interesting, and will find its way
onto linuxvm.org (when I get caught up some more).
Speaking of which, I haven't had the time to make any substantive updates to
the site, but I did manage to get a couple more people and pictures added to
the commun
Gordon,
After looking at another one of my systems, I found this in my /dev
directory:
brw---1 root root 254, 0 Sep 23 11:25 btibm0
crw---1 root root 254, 1 Sep 23 11:25 ntibm0
crw---1 root root 254, 0 Sep 23 11:25 rtibm0
brw---1 root
First off, I'd like to thank everyone again who helped me out on the Dev
status 0C Subchannel 40 problem
Mark Post: Totally missed your e-mail about the od command to dump the boot
block. Fortunately someone at IBM did get that to me and I have it
archived.
Duane Mauler, Karin Broecker and Carlo
Steve,
I don't have access to any OSA cards, so I can't test that part of the
installation path.
Mark Post
-Original Message-
From: Steve Gear Schneider Technical Services
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 10:46 AM
To: [EMAIL PROTECTED]
Subject: Re: trying to us
That puts a little different spin on it. Thanks.
On Thursday 14 March 2002 12:59 pm, you wrote:
> Rich: mySAP.com on Linux zSeries is targetted at customers who are
> currently using DB2 on z/OS as the SAP database server. This is the
> highest performing database server out there and using Hipe
zSeries generally available May 31st
> Argghh!! And their pidgeon-holing customers to DB2 for OS/390!
Rich: mySAP.com on Linux zSeries is targetted at customers who are
currently using DB2 on z/OS as the SAP database server. This is the
highest performing database server out there
When you're moving the root file system, the process needs to be adapted
(just a little). If the DASD volume where your root file system lives is
where silo has written the IPL text (most frequently the case), you'll need
to re-run silo after the file system has been copied. Before you do _that_
> Well, on some of our OS/390 machines there is no USS installed. That
> kills my direction towards Java, anayway.
Frank: Since OS/390 1.3, you have not had a choice. USS is always there,
and since OS/390 2.4 the TCP/IP stack on OS/390 requires USS. In other
words, all supported releases of OS/3
Chuck,
What operating system is your FTP server running? If the answer is anything
with MS in it, that's not going to work with the SuSE installer. You can
either do as Patrick Mullen suggested (which requires a lot of available
DASD that you might not have) or temporarily boot a PC with a CDRO
Argghh!! And their pidgeon-holing customers to DB2 for OS/390!
On Thursday 14 March 2002 12:09 pm, you wrote:
> SAP's first major application for Linux/390. It's been under test for a
> while. I'm a little surprised that they're only going to run it on 64-bit
> Linux/390.
>
> Mark Post
>
--
R
Frank,
This can be done through normal FTP, but it won't be interactive in any
usual sense of the word. My first reaction to your question was "what
problem are they trying solve?"
Mark Post
-Original Message-
From: Frank Prappacher [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14,
> Mark: The reason for Linux on zSeries only is that the SAP app server
> requires, in almost every environment, more than 2GB of memory. I have
> seen UNIX SAP environments with a LOT more than 2GB for the
> app server.
I'll second this. SAP does a lot of useful stuff, but it is very, *very*
r
Steve Gear Schneider Technical Services writes:
> i am confused with the usage of 'eth0'. i thought that 'eth0' meant OSA-2
> and 'eth1' meant 'OSA-E giga'.
Post, Mark K writes:
> No, eth0 is simply the first Ethernet device found by the driver. If it
> finds any others, it simply names them e
zSeries generally available May 31st
> SAP's first major application for Linux/390. It's been under test for
> a while. I'm a little surprised that they're only going to run it on
> 64-bit Linux/390.
Mark: The reason for Linux on zSeries only is that the SAP app server
requires, in
Lionel,
Two things. I don't think this should make any difference, since it's a
point to point link, but is the system on the other side of the link really
248.1, or 249.1?
The other is, what does your routing table look like? Any time you can get
an interface up and running, but traffic is no
Much thanks to Neale Ferguson, Ross Patterson, Mark Post, and Joe Jenkins who
responded to my question. My apologies in advance if anyone was omitted (it was
unintentional).
The issue was the "__register_frame_info()" problem that was mentioned in the
responses. I took a look at the SuSE si
SAP's first major application for Linux/390. It's been under test for a
while. I'm a little surprised that they're only going to run it on 64-bit
Linux/390.
Mark Post
-Original Message-
From: Dave Jones [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 9:56 AM
To: Mark K Post
S
Greetings;
Ignore the part about mdisk. That is used for a disk format that is only
available under VM. For your purposes add the 201-203 on the end of your
current dasd= parm and you should be OK.
Good Luck!
Dennis
Sterling James <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/14/2002
11:43:09 AM
Steve,
No, eth0 is simply the first Ethernet device found by the driver. If it
finds any others, it simply names them eth1, eth2, eth3, and so on.
Mark Post
-Original Message-
From: Steve Gear Schneider Technical Services
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 10:43
We getting ready to convert from running LINUX in LPAR mode to running
under zVM. In researching this conversion, I have an unanswered question;
In the "Building Linux Systems under IBM VM" Appendix A. Creating a new
disk on Linux/390 gives an example of a parmfile and changes needed to add
a min
I found that it was much easier to format a dasd with a filesystem, mount
it, and then FTP the CD files to it. Then start Yast and tell it to use the
local directory structure you just created.
> -Original Message-
> From: Chuck Wimpee [mailto:[EMAIL PROTECTED]]
>
>
> I am trying to ins
This is documented on pages 10 and 11 within Chapter 3, Installation
Procedures.
SC24-6034-00 z/VM System Administration Facility:
http://www.vm.ibm.com/pubs/pdf/hcsl5a00.pdf
Kurt Acker
Lionel Dyck
cc:
Sent
Steve,
Just labeleth0, works fine here.
Gerald
-Original Message-
From: Steve Gear Schneider Technical Services
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 10:43 AM
To: [EMAIL PROTECTED]
Subject: Re: trying to us OSA/E Gig with
hello gerald,
i am confused with the
A great big Thank You to you and Willem!
"Post, Mark K" wrote:
> Ann,
>
> For a distribution that is maintained by RPM, such as Red Hat and SuSE, you
> _should_ maintain everything with RPM, unless you're installing a package
> that is not provided by the distributor. Even then you might want t
I *hope* this isn't the problem, but try forcing MTU to 1492 on each end
and see what happens.
--
[EMAIL PROTECTED]
"My eyes say their prayers to her / Sailors ring her bell / Like a moth
mistakes a light bulb / For the moon and goes to hell." -- Tom Waits
I also have an overallocated /usr minidisk that I will be cloning soon. I
was planning on using the procedure (using tar) in the moving part of a
filesystem HOWTO (http://www.linuxvm.org/Info/HOWTOs/movefs.html). I
successfully segregated several directories to their own minidisks so I
figured I c
After doing the YaST setup and ipling from the new boot address my linux
system comes up but does not connect to the network. Here is my ifconfig:
ifconfig
iucv0 Link encap:Serial Line IP
inet addr:172.21.249.21 P-t-P:172.21.248.1 Mask:255.255.255.255
UP POINTOPOINT RUN
hi mark,
do you know if there is a bug in the SUSE 2.4 install script. seems to
me that i should be able to install this stuff using the 'initial system'
install script.
thanks, steve
"Post, Mark K"
cc:
Sent by:
hello gerald,
i am confused with the usage of 'eth0'. i thought that 'eth0' meant OSA-2
and 'eth1' meant 'OSA-E giga'.
thanks,
steve
"Benton,
Gerald" To: [EMAIL PROTECTED]
Fax to:
You could allocate a new minidisk for the root file system, and simply copy
over all the files using tar. Then you can use that new root file system the
ipl device using zipl or silo. Copying the files on the root file system with
tar will preserve links etc...
Kris
On Thu, Mar 14, 200
We installed the 2.4.7 kernel on 5 full pack mini disks as follows:
/dev/dasda1
/dev/dasdb1
/dev/dasdc1 lvmsuse
/dev/dasdd1 lvmsuse
/dev/dasde1 lvmsuse
Our parmfile is:
dasd=0200,0100,0101,0102,0103 root=/dev/dasdb1 noinitrd
so dasda1 is the swap file, and dasdb1 is the root,
I am trying to install SuSE 7.0 under VM on s/390. I get as far as the FTP step :
FTP Settings YaST Version 1.07.1 -- (c) 1994-2000 SuSE GmbH
| |
| FTP Server [Name|IP] :xxx.xxx.xxx.xxx
The documentation for the linux image installation is lacking one step
(that I've noticed so far).
After installing Linux in an image the boot address should be set thus:
vmadmin image set linux2 boot 151
Otherwise I'm noticing that the image boots with the installation image
instead of the new
Steve,
Did you enter in something like this?
0xf030,0xf031,0xf032,portname:OSAPORT1,eth0
My suse appears to get the rest of the cuaddr combinations
of 0xf033,0xf034etc as well. However my eth0 does
communicate with no problem.
I have my OSA shared with a MVS LPAR running the OSA/SF
Support
Mark,
this is what I found in some (internal?) documentation.
According to this, the first LPAR that defines the portname sets the
portname on the card.
Linux is in this regard not different than other operating systems...
On September 12, 2001 the following MCL's were released:
Driver 38 fo
Chris,
Thanks for the offer. I don't have an internet server readily available.
Let's ask the crew. Does anybody know of a server that Chris can
upload this file to? I I am looking for an internet server or any
interenet accessable ftp site that would generously offer to house this
file tem
hello mark,
do you mean the portname defined in vtam for the OSA-E.
i am installing SUSE server 7 (kernel 2.4) and using the 'boot from cd'
option. from the first menu i select '3' for the gigabit OSA. later, i
enter in the device's or auto(i've done both) and then enter in a port
name. i ha
Well,
on some of our OS/390 machines there is no USS installed. That kills my
direction towards Java, anayway.
I thought more of a Linux/TSO package that takes care of this, i.e.
transfers the command, issues the command on TSO, receives the response
and presents it to the caller.
Frank Prappach
You can try that.
Run rexec daemon or somethink like it on UnixSystemServices (OpenEdition),
then from linux run
rexec -l user -p passwd hosttso "command"
But ...
se test
Authorized commands are not supported
IKJ56652I You attempted to run an authorized command or program. This is
not sup
Hi.
Is there a way to easily kick off TSO commands to a (remote) OS/390 host
under VM/Linux? Preferably from Java.
Frank Prappacher
Amadeus Data Processing
> I red RedBook, but, at least, in my case, it doesn't work.
> May be they try to use tapes only with DEVFS?
Maybe try the following patch to assign it to some other major
number:
--- linux/drivers/s390/char/tapechar.h.nodevfs Thu Aug 16 17:20:15 2001
+++ linux/drivers/s390/char/tapechar.h Thu
14.03.2002 06:35:29 "Post, Mark K" ÎÁÐÉÓÁÌ(Á):
I red RedBook, but, at least, in my case, it doesn't work.
May be they try to use tapes only with DEVFS?
>#mknod /dev/rtibm0 c 254 0 (first rewinding character device)
>#mknod /dev/ntibm0 c 254 0 (first non-rewinding character device)
Yes, i have one.
Must be
insmod tape390 tape=290
T390:IBM S/390 Tape Device Driver (v1.01).
kernel: T390:(C) IBM Deutschland Entwicklung GmbH, 2000
kernel: T390:character device frontend : built in
kernel: T390:block device frontend : built in
kernel: T390:support for 3480 compatible :
13.03.2002 23:16:35 Drew Arthur ÎÁÐÉÓÁÌ(Á):
>We are wanting run some benchmark comparisons for performance between
>WAS 3.5 on OS/390 and Linux. We also are having performance issues with
>WebLogic on Linux/390 and would like to see if WAS 3.5 performs any
>better.
When you done it,
56 matches
Mail list logo
