SLES12 and WAS8.5 Cookbook?

[Quillen, Channon]

Is there an install cookbook for SLES12 and WAS8.5?

Channon Quillen
SYSTEMS SUPERVISOR

T 254.399.5032
E cquil...@txfb-ins.com

7420 Fish Pond Rd.
Waco, TX  76710

[http://infonet.txfb-ins.com//images//email-signature-image.jpg]


WWW.TXFB-INS.COM

Texas Farm Bureau Insurance received the highest numerical score among auto 
insurance providers in Texas in the proprietary J.D. Power 2012-2014 U.S. Auto 
Insurance Studies SM (Central Region in 2012). 2014 Study based on 44,661 total 
responses measuring 8 providers in Texas and measures opinions of consumers 
with their auto insurance provider. Proprietary study results are based on 
experiences and perceptions of consumers surveyed March-April 2014. Your 
experiences may vary. Visit jdpower.com. (c) 2014 Texas Farm Bureau Insurance 
Companies.

CONFIDENTIALITY STATEMENT: The foregoing message (including attachments) is 
covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 
2510-2521, and is CONFIDENTIAL. If you believe that it has been sent to you in 
error, do not read it. If you are not the intended recipient, you are hereby 
notified that any retention, dissemination, distribution, or copying of this 
communication is strictly prohibited. Please reply to the sender that you have 
received the message in error, then delete it. Thank you.

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

Adding DASD, but unable to automount

[Quillen, Channon]

SLES9 64-bit with all the latest updates.

I'm able to add DASD, format, fdasd, and update the fstab.
However, the mount will not survive a reboot.  After the machine boots,
I'm able to mount it with no problems.

I see this in /var/log/boot.msg
mount: /dev/dasdk1 is not a valid block device

Running the command "vmcp q dasd" I see the DASD:
DASD 020A ON DASD  320C R/W L06V0A SUBCHANNEL = 0010

Running the command "cat /proc/dasd/devices" I see:
0.0.020a(ECKD) at ( 94:40) is dasdk   : active at blocksize:
4096, 601020 blocks, 2347 MB


-Channon

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Expanding SWAP space

[Quillen, Channon]

Ok, so after the swap is created in z/VM and formatted using SWAPGEN, I
see the devices in Linux.  However, I still have to issue the mkswap and
swapon commands to activate them.

I added these commands to boot.swap under start):
modprobe dasd_fba_mod
echo "Creating swap file signature..."
mkswap /dev/dasdg1
mkswap /dev/dasdh1

Looking at /var/log/boot.msg, I see:
Creating swap file signature...
/dev/dasdg1: No such device or address
/dev/dasdh1: No such device or address

After the machine is up, I can run mkswap and swapon.

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Tuesday, October 16, 2007 4:37 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Expanding SWAP space

>>> On Tue, Oct 16, 2007 at  5:31 PM, in message
<[EMAIL PROTECTED]>,
"Quillen,
Channon" <[EMAIL PROTECTED]> wrote: 
> They are VDISK for swap.  All the other drives are ECKD.  Is there any
> benefit to having them one way or the other?

They both seemed to be on the small side for swap, so I thought I'd
better ask.  No, don't change them to ECKD unless you want to seriously
damage your Linux paging performance.  If I were you, I would use Sine
Nomine's SWAPGEN exec to prepare them, though.  They should be showing
up as DIAG, not FBA, which will also provide a performance benefit.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Expanding SWAP space

[Quillen, Channon]

They are VDISK for swap.  All the other drives are ECKD.  Is there any
benefit to having them one way or the other?

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Tuesday, October 16, 2007 2:21 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Expanding SWAP space

>>> On Tue, Oct 16, 2007 at 11:19 AM, in message
<[EMAIL PROTECTED]>,
"Quillen,
Channon" <[EMAIL PROTECTED]> wrote: 
> So, do I need to change them to ECKD rather than FBA?

Not unless you have some other reason to do so.  What are you using them
for?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Expanding SWAP space

[Quillen, Channon]

So, do I need to change them to ECKD rather than FBA?

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Monday, October 15, 2007 5:59 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Expanding SWAP space

>>> On Mon, Oct 15, 2007 at 12:30 PM, in message
<[EMAIL PROTECTED]>,
"Quillen,
Channon" <[EMAIL PROTECTED]> wrote: 
> # cat /proc/dasd/devices 
> 0.0.0200(ECKD) at ( 94: 0) is dasda   : active at blocksize:
> 4096, 9 blocks, 351 MB
> 0.0.0201(ECKD) at ( 94: 4) is dasdb   : active at blocksize:
> 4096, 601020 blocks, 2347 MB
> 0.0.0202(ECKD) at ( 94: 8) is dasdc   : active at blocksize:
> 4096, 601020 blocks, 2347 MB
> 0.0.0203(ECKD) at ( 94:12) is dasdd   : active at blocksize:
> 4096, 601020 blocks, 2347 MB
> 0.0.0204(ECKD) at ( 94:16) is dasde   : active at blocksize:
> 4096, 601020 blocks, 2347 MB
> 0.0.0205(ECKD) at ( 94:20) is dasdf   : active at blocksize:
> 4096, 601020 blocks, 2347 MB
> 0.0.0206(ECKD) at ( 94:24) is dasdg   : active at blocksize:
> 4096, 601020 blocks, 2347 MB
> 0.0.0222(FBA ) at ( 94:28) is dasdh   : active at blocksize:
> 512, 20480 blocks, 10 MB
> 0.0.0223(FBA ) at ( 94:32) is dasdi   : active at blocksize:
> 512, 204800 blocks, 100 MB
> 
> dasdh and dasdi are both swap, and they appear to be used as such:
> # swapon -s
> Filename  TypeSize
> Used  Priority
> /dev/dasdh1   partition   10184   0
50
> /dev/dasdi1   partition   102256  14968   100

Yes, but they're FBA devices, not ECKD, so dasdfmt isn't needed for
them, and won't work with them.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Expanding SWAP space

[Quillen, Channon]

# cat /proc/dasd/devices 
0.0.0200(ECKD) at ( 94: 0) is dasda   : active at blocksize:
4096, 9 blocks, 351 MB
0.0.0201(ECKD) at ( 94: 4) is dasdb   : active at blocksize:
4096, 601020 blocks, 2347 MB
0.0.0202(ECKD) at ( 94: 8) is dasdc   : active at blocksize:
4096, 601020 blocks, 2347 MB
0.0.0203(ECKD) at ( 94:12) is dasdd   : active at blocksize:
4096, 601020 blocks, 2347 MB
0.0.0204(ECKD) at ( 94:16) is dasde   : active at blocksize:
4096, 601020 blocks, 2347 MB
0.0.0205(ECKD) at ( 94:20) is dasdf   : active at blocksize:
4096, 601020 blocks, 2347 MB
0.0.0206(ECKD) at ( 94:24) is dasdg   : active at blocksize:
4096, 601020 blocks, 2347 MB
0.0.0222(FBA ) at ( 94:28) is dasdh   : active at blocksize:
512, 20480 blocks, 10 MB
0.0.0223(FBA ) at ( 94:32) is dasdi   : active at blocksize:
512, 204800 blocks, 100 MB

dasdh and dasdi are both swap, and they appear to be used as such:
# swapon -s
FilenameTypeSize
UsedPriority
/dev/dasdh1   partition 10184   0   50
/dev/dasdi1   partition 102256  14968   100

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Sunday, October 14, 2007 6:23 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Expanding SWAP space

>>> On Sun, Oct 14, 2007 at  3:41 PM, in message
<[EMAIL PROTECTED]>,
"Quillen,
Channon" <[EMAIL PROTECTED]> wrote: 
> SLES9 64-bit
> 
> The existing swap disk (/dev/dasda1) wasn't large enough.  We
allocated
> a larger mini disk for device 200 by adding 600 cyl.  However, when I
> bounce the guest, /dev/dasda1 isn't recognized.
> 
> # mkswap /dev/dasda1
> /dev/dasda1: No such device or address
> 
> I have to issue the following commands to make it work:
> # fdasd -ask /dev/dasda
> # mkswap /dev/dasda1
> # swapon /dev/dasda1
> 
> Am I missing something?  Anyone have notes on expanding the swap disk?

In your case, you effectively added a brand new disk, so you have to
follow the same steps you would normally.  Those steps are exactly what
you listing doing.  The alternative would have been to use YaST to
activate, format, partition, and then put a swap signature on the disk.

> Also, I'm getting this error on another machine:
> # fdasd -ask /dev/dasdh
> /dev/dasdh is not an ECKD disk!  This disk type is not supported!

What does /proc/dasd/devices show?  If it's not ECKD, fdasd won't touch
it.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Expanding SWAP space

[Quillen, Channon]

SLES9 64-bit

The existing swap disk (/dev/dasda1) wasn't large enough.  We allocated
a larger mini disk for device 200 by adding 600 cyl.  However, when I
bounce the guest, /dev/dasda1 isn't recognized.

# mkswap /dev/dasda1
/dev/dasda1: No such device or address

I have to issue the following commands to make it work:
# fdasd -ask /dev/dasda
# mkswap /dev/dasda1
# swapon /dev/dasda1

Am I missing something?  Anyone have notes on expanding the swap disk?

Also, I'm getting this error on another machine:
# fdasd -ask /dev/dasdh
/dev/dasdh is not an ECKD disk!  This disk type is not supported!

-Channon 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: upgrade sles9 to sles10

[Quillen, Channon]

I tried to upgrade from SLES8 64-bit to SLES10 64-bit with no success.
I also tried going from 8 to 9.  With all the frustration, I ended up
creating a new guest.
The upgrade would run, but after the first reboot and before you setup
all the network info, root password, etc., I couldn't get the network
cards to initialize.

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Wednesday, March 14, 2007 10:44 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: upgrade sles9 to sles10

  >>> On Wed, Mar 14, 2007 at 11:20 AM, in message
<[EMAIL PROTECTED]>,
"Levy,
Alan" <[EMAIL PROTECTED]> wrote: 

> 
> Can anyone point me to any documentation on upgrading sles9 to sles10
?

Alan, there is a blurb (to put it politely) at
http://www.novell.com/support/mysupport/viewdocument.do?externalId=36472
44&sliceId=SAL_Public  Essentially, it says you can't use the YaST
System Update function to do the upgrade.  Other than that, I'm not sure
there is anything that would be particularly detailed.  Hopefully,
someone who might know better will correct me.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: pico to xedit mkboot

[Quillen, Channon]

This worked!  Thanks!

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Tison
Sent: Wednesday, February 21, 2007 12:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: pico to xedit mkboot

As an alternative, before you ftp the file, you could run "unix2dos" on
it


--Jim--

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: pico to xedit mkboot

[Quillen, Channon]

What's the difference between the two commands?
I use "locsite fix 80" to transfer all the Linux boot files (boot, parm,
initrd) from my Linux ftp server to the reader.

-Channon 
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Pace
Sent: Wednesday, February 21, 2007 12:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: pico to xedit mkboot

I may have this wrong, but I would think if you are sending the data you
would do a site command and not a locsite.

On 2/21/07, Quillen, Channon <[EMAIL PROTECTED]> wrote:
>
> locsite fix 80 - yes
> I've also tried both ascii and bin transfer.  ascii xfer is readable
but
> w/out CR.  bin is, well, bin. ;-)
>


--
Mark Pace
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: pico to xedit mkboot

[Quillen, Channon]

locsite fix 80 - yes
I've also tried both ascii and bin transfer.  ascii xfer is readable but
w/out CR.  bin is, well, bin. ;-)

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Wednesday, February 21, 2007 11:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: pico to xedit mkboot

When you did the upload to z/VM, did you specify a blocksize of 80
bytes?
Since z/VM doesn't have the concept of CRLF, that's the only way to get
things to look reasonable in xedit.


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Quillen, Channon
Sent: Wednesday, February 21, 2007 11:25 AM
To: LINUX-390@VM.MARIST.EDU
Subject: pico to xedit mkboot


I created a mkboot file using pico in Fedora.  I ftp'ed this file to my
"A" disk in VM.  When I xedit the file to view it there are no carriage
returns.
How do I translate the file so that the CR/LF are recognized?

-Channon

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

pico to xedit mkboot

[Quillen, Channon]

I created a mkboot file using pico in Fedora.  I ftp'ed this file to my
"A" disk in VM.  When I xedit the file to view it there are no carriage
returns.
How do I translate the file so that the CR/LF are recognized?

-Channon 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: WebsphereAS on zSeries performance?

[Quillen, Channon]

Mike-

May I contact you off-list?  I have some questions about your setup.

Channon Quillen
LAN Administrator
Texas Farm Bureau Insurance Companies

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mike Riggs
Sent: Wednesday, April 06, 2005 10:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: WebsphereAS on zSeries performance?

We currently support 6 LINUX guests (soon to be 8) with 3 of them
running
WAS, 3 running UDB.  We do this with a z/890 and only 1 IFL  and 3gig of
memory.
More memory is due in and we're still arguing the need for an additional
IFL.



Mike Riggs
Supreme Court of Virginia
(804) 786-7823



 Rich Smrcina
 <[EMAIL PROTECTED]
 om>
To
 Sent by: Linux on LINUX-390@VM.MARIST.EDU
 390 Port
cc
 <[EMAIL PROTECTED]
 IST.EDU>
Subject
   Re: WebsphereAS on zSeries
   performance?
 04/05/2005 03:16
 PM


 Please respond to
 Linux on 390 Port
 <[EMAIL PROTECTED]
 IST.EDU>






Going to a z890 IFL (from a MP3K IFL) was a major improvement.  Startup
time went from 15-20 minutes to 2 minutes.  A single IFL of sufficient
power is enough here, but that always depends upon your specific
workload.  The apps are fairly well tuned also (which helps anywhere).

Bennie Hicks wrote:
> Anybody out there running WAS on a single IFL?  Interested in your
> thoughts/comments on performance, impacts of java compiles, etc.  and
> whether or not a single IFL engine is enough..thanks!
>
> --
> E-mail correspondence to and from this address may be subject to the
> North Carolina Public Records Law and may be disclosed to third
parties
> by an authorized state official.
> --
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>

--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service:  (866)569-7378
rich.smrcina at vmassist.com

Catch the WAVV!  http://www.wavv.org
WAVV 2005 - Colorado Springs - May 20-24, 2005

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: WebSphere Portal on z/VM Linux?

[Quillen, Channon]

Jim-

We are in the planning stage as well to run WAS 5.1/WPS 5.1 on two
zLinux guests running SLES 8.0 on a z890.  We plan to use two
stand-alone SLES 9 front end servers with the WPS ISAPI Plug-In
installed.  They will be load balanced.  I have concerns about the
capacity on the z/VM side.  We just completed the TechLine SIZE390 and
will go over it with IBM sometime this week.  If you haven't already
done so, download and read the Redbook "Linux on IBM eserver zSeries and
S/390: z/VM Configuration for WebSphere Deployments"
http://www.redbooks.ibm.com/abstracts/redp3661.html

I would like to keep in discussion with you either on or off the list.

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Jim Enwall
Sent: Friday, March 25, 2005 10:31 AM
To: LINUX-390@VM.MARIST.EDU
Subject: WebSphere Portal on z/VM Linux?

Anyone running WepSphere Portal on z/VM Linux? 

 

We are trying to run WebSphere Portal 5.1 server on a z/800, single IFL
processor, SuSE 8 Linux and at the moment it looks like this is better
suited on the Intel platform. We are in touch with IBM WebSphere support
but interested in talking to anyone that is currently (or tried) running
this product on a z/VM Linux platform. Thank you. 

 

Jim Enwall

Univar USA

Phone: (425) 889-3987

Fax: (425) 828-8502

www.univarusa.com

 


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES9 - install problem - logging in

[Quillen, Channon]

I use a program called SecureToken, on Windows, to connect via ssh.
I have to select, as authentication methods, Public Key, Password, and
Keyboard-Interactive in order to successfully connect. If I don't select
Keyboard-Interactive, I get the following error:
Fatal Error:
Permission denied (publickey,keyboard-interactive).
Session will be terminated...
Connection closed...

Connecting from another Linux box, Fedora Core 3, I don't have any
problems.

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter Rothman
Sent: Tuesday, March 22, 2005 12:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 - install problem - logging in

I am trying to install SLES9 (free download)  - it will be used for a
real
evaluation.

I am able to IPL the rdr and all is OK setting up the network (OSA) etc
- I
chose FTP and SSH.
However when I attempt to use SSH from my workstation I am prompted for
the
root password but am denied access - why?.
At this point I can use telnet (use the temp root password) and am able
to
complete the YAST installation.

Once the install is complete and I IPL the mdisk I am not able to login
using either ssh or telnet. For telnet it appears that there is no
service
and for ssh I am prompted for a password but the original 'temp'
password
does not work. I do see messages to the affect that the temp password
will
'go away' but what am I suppose to use?

Am I missing something?

Any help would be appreciated.
Thanks.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: VNC on SLES9 - Problem Solved!

[Quillen, Channon]

Ranga-

I'm using VNC Viewer for Win32 v.4.0.  I also tested the connection with
the browser.  Both are working fine, but I had to change the following
in /etc/sysconfig: DISPLAYMANAGER to gdm and the DEFAULT_WM to gnome.
Run this command "/opt/gnome/sbin/gdmconfig"
go to tab "XDMCP", and enable XDMCP.
Restart the display manager: "rcxdm restart"

I'm able to choose which any session at the login screen.

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Ranga Nathan
Sent: Tuesday, March 15, 2005 5:56 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VNC on SLES9 - Problem Solved!

Channon:
I would like to get it working too but I get only the xterm in a java
applet under my browser.
I presume you have a windows desktop. If so, do you see the Gnome / KDE
desktop when you vnc into the Linux? Or is it some xterm over java
applet?
__
Ranga Nathan / CSG
Systems Programmer - Specialist; Technical Services;
BAX Global Inc. Irvine-California
Tel: 714-442-7591   Fax: 714-442-2840




"Quillen, Channon" <[EMAIL PROTECTED]>

Sent by: Linux on 390 Port 
03/15/2005 07:30 AM
Please respond to
Linux on 390 Port 


To
LINUX-390@VM.MARIST.EDU
cc

Subject
Re: VNC on SLES9 - Problem Solved!






After uninstalling/reinstalling XFree86-Xvnc, tightvnc, XFree86, and
kdenetwork3-vnc and also following the HOWTO, the problem was with the
display and/or window manager.

In /etc/sysconfig, I changed the DISPLAYMANAGER to gdm and the
DEFAULT_WM to gnome.  I'm now able to use VNC.

It looks like I have a display manager application issue?

Thanks all!
-Channon

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Saulo Augusto Silva
Sent: Wednesday, March 09, 2005 2:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VNC on SLES9

If you are using vnc with utility vncserver , you will never get a logon
screen . For that is necessary to install a tightvnc-server package and
XFree86-Xvnc package .
After that you need to config kdm or gdm and xinetd server to user vnc
like a superdaemon service .

This wiki from gentoo is very usefull and will help you :

http://gentoo-wiki.com/HOWTO_Xvnc_terminal_server

Another way is change the vnc xstartup from twm to kde .

Saulo Augusto Silva
-
Analista de Suporte
Engenheiro Certificado RedHat Linux
Profissional Certificado LPIC-I

[EMAIL PROTECTED]
[EMAIL PROTECTED]

71 3115 7677


Em Qua, 2005-03-09 C s 13:23 -0600, Quillen, Channon escreveu:
> I don't know if this related to SLES9 being installed on zVM, but here
it goes...
>
> I'm able to connect but get a black and white screen with an "X" for a
cursor.  I never get the logon screen.  I've tried googling the problem
and have tried many fixes with no success.
>
> -Channon
>
--





"As informaC'C5es existentes nesta mensagem e nos arquivos anexados sC#o
para
uso restrito, com sigilo protegido por lei. Caso nC#o seja o
destinatC!rio,
favor apagar esta mensagem e notificar o remetente.
O uso imprC3prio das informaC'C5es desta mensagem serC! tratado conforme
a
legislaC'C#o em vigor.

The information contained in this message and in the attached files are
restricted, and its confidentiality is protected by law. In case you are
not the addressee, please, delete this message and notify the sender.
The improper use of this information will be treated according to the
legal
laws."

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: VNC on SLES9 - Problem Solved!

[Quillen, Channon]

After uninstalling/reinstalling XFree86-Xvnc, tightvnc, XFree86, and
kdenetwork3-vnc and also following the HOWTO, the problem was with the
display and/or window manager.

In /etc/sysconfig, I changed the DISPLAYMANAGER to gdm and the
DEFAULT_WM to gnome.  I'm now able to use VNC.

It looks like I have a display manager application issue?

Thanks all!
-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Saulo Augusto Silva
Sent: Wednesday, March 09, 2005 2:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VNC on SLES9

If you are using vnc with utility vncserver , you will never get a logon
screen . For that is necessary to install a tightvnc-server package and
XFree86-Xvnc package .
After that you need to config kdm or gdm and xinetd server to user vnc
like a superdaemon service .

This wiki from gentoo is very usefull and will help you :

http://gentoo-wiki.com/HOWTO_Xvnc_terminal_server

Another way is change the vnc xstartup from twm to kde .

Saulo Augusto Silva
-
Analista de Suporte
Engenheiro Certificado RedHat Linux
Profissional Certificado LPIC-I

[EMAIL PROTECTED]
[EMAIL PROTECTED]

71 3115 7677


Em Qua, 2005-03-09 C s 13:23 -0600, Quillen, Channon escreveu:
> I don't know if this related to SLES9 being installed on zVM, but here
it goes...
>
> I'm able to connect but get a black and white screen with an "X" for a
cursor.  I never get the logon screen.  I've tried googling the problem
and have tried many fixes with no success.
>
> -Channon
>
--





"As informaC'C5es existentes nesta mensagem e nos arquivos anexados sC#o
para
uso restrito, com sigilo protegido por lei. Caso nC#o seja o
destinatC!rio,
favor apagar esta mensagem e notificar o remetente.
O uso imprC3prio das informaC'C5es desta mensagem serC! tratado conforme
a
legislaC'C#o em vigor.

The information contained in this message and in the attached files are
restricted, and its confidentiality is protected by law. In case you are
not the addressee, please, delete this message and notify the sender.
The improper use of this information will be treated according to the
legal
laws."

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: VNC on SLES9

[Quillen, Channon]

Yes, I get the same type of background using the browser as I do using a VNC 
client. - no logon screen.
I do get the prompt for the password though, connecting via browser.
 
-Channon

-Original Message- 
From: Linux on 390 Port on behalf of Mark D Pace 
Sent: Wed 3/9/2005 1:46 PM 
To: LINUX-390@VM.MARIST.EDU 
Cc: 
Subject: Re: VNC on SLES9



Have you by chance tried just using a web browser instead of a VNC 
client?

http://ipaddr:5800  I think it's 5800



Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
Office: 850.219.5184
Fax: 888.221.9862
http://www.mainline.com


This e-mail and files transmitted with it are confidential, and are
intended solely for the use of the individual or entity to whom this 
e-mail
is addressed.  If you are not the intended recipient, or the employee or
agent responsible to deliver it to the intended recipient, you are 
hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited.  If you are not one of the named
recipient(s) or otherwise have reason to believe that you received this
message in error, please immediately notify sender by e-mail, and 
destroy
the original message.  Thank You.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or 
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: VNC on SLES9

[Quillen, Channon]

Made the changes, notably the "protocol version 3.3", but still no logon screen.
What files should be in the /root/.vnc folder?
-Channon

-Original Message- 
From: Linux on 390 Port on behalf of Peter E. Abresch Jr. - at Pepco 
Sent: Wed 3/9/2005 1:30 PM 
To: LINUX-390@VM.MARIST.EDU 
Cc: 
Subject: Re: VNC on SLES9



I had to have the following VNC client options selected for it to work 
for me: 




  






    
"Quillen, Channon" <[EMAIL PROTECTED]> 
Sent by: Linux on 390 Port  

03/09/2005 02:23 PM 
Please respond to
Linux on 390 Port 


To
LINUX-390@VM.MARIST.EDU 
cc
Subject
VNC on SLES9






I don't know if this related to SLES9 being installed on zVM, but here 
it goes...

I'm able to connect but get a black and white screen with an "X" for a 
cursor.  I never get the logon screen.  I've tried googling the problem and 
have tried many fixes with no success.

-Channon




This Email message and any attachment may contain information that is 
proprietary, legally privileged, confidential and/or subject to copyright 
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is 
intended solely for the use of the person(s) to which it is addressed. If you 
are not an intended recipient, or the employee or agent responsible for 
delivery of this Email to the intended recipient(s), you are hereby notified 
that any dissemination, distribution or copying of this Email is strictly 
prohibited. If you have received this message in error, please immediately 
notify the sender and permanently delete this Email and any copies. PHI 
policies expressly prohibit employees from making defamatory or offensive 
statements and infringing any copyright or any other legal right by Email 
communication. PHI will not accept any liability in respect of such 
communications. 

Re: VNC on SLES9

[Quillen, Channon]

Contents of xstartup:
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &
 
How do I check Xauthority?
This is a default install of SLES9 64-bit.  I have also checked the option for 
remote admin in yast.
 
-Channon

-Original Message- 
From: Linux on 390 Port on behalf of David Kreuter 
Sent: Wed 3/9/2005 1:25 PM 
To: LINUX-390@VM.MARIST.EDU 
Cc: 
Subject: Re: VNC on SLES9



what are the contents /root/.vnc/xstartup ?
also could be related to Xauthority
David



From: Linux on 390 Port on behalf of Quillen, Channon
Sent: Wed 3/9/2005 2:23 PM
To: LINUX-390@VM.MARIST.EDU
Subject: VNC on SLES9



I don't know if this related to SLES9 being installed on zVM, but here 
it goes...

I'm able to connect but get a black and white screen with an "X" for a 
cursor.  I never get the logon screen.  I've tried googling the problem and 
have tried many fixes with no success.

-Channon




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or 
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES 8 vs 9 Install and vswitch config

[Quillen, Channon]

I cleared some files out of the reader, and it worked.  BTW... how do I figure 
the size of the guest virtual machine?
 
-Channon

-Original Message- 
From: Linux on 390 Port on behalf of Post, Mark K 
Sent: Tue 3/8/2005 12:41 PM 
To: LINUX-390@VM.MARIST.EDU 
Cc: 
Subject: Re: SLES 8 vs 9 Install and vswitch config



Mike already mentioned the guest virtual machine size.  To me, this 
looks
like the ramdisk is too small.  64MB may be cutting it a little close, 
when
the uncompressed ramdisk is about 55MB.  You might try bumping that up 
to
the "92358" value that gets mentioned in the error message.

Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
    Quillen, Channon
Sent: Monday, March 07, 2005 10:42 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES 8 vs 9 Install and vswitch config


I modified the PARMFILE, but now get the following error:

Freeing unused kernel memory: 108k freed
attempt to access beyond end of device
ram0: rw=0 want=92358, limit=65536
Buffer I/O error on device ram0, logical block 46178
Kernel panic: Attempted to kill init!

-Channon

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or 
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

VNC on SLES9

[Quillen, Channon]

I don't know if this related to SLES9 being installed on zVM, but here it 
goes...

I'm able to connect but get a black and white screen with an "X" for a cursor.  
I never get the logon screen.  I've tried googling the problem and have tried 
many fixes with no success.

-Channon

Re: SLES 8 vs 9 Install and vswitch config

[Quillen, Channon]

I never did see the error message, but I have succeeded with the install.  I 
have since uninstalled/reinstalled a couple times trying different network 
settings.  Sometimes it works, sometimes it doesn't, so it looks like I am 
experiencing the mentioned "bug" in the OSA card.
 
Thank you!
-Channon

-Original Message- 
From: Linux on 390 Port on behalf of Michael MacIsaac 
Sent: Sat 3/5/2005 5:15 PM 
To: LINUX-390@VM.MARIST.EDU 
Cc: 
Subject: Re: SLES 8 vs 9 Install and vswitch config



> I am able to install SLES 8 31-bit on a configured guest.
> When I try to install SLES 9 31 or 64 bit over the same guest, the
> install fails when trying to ping the gateway.
This may the same issue I've seen. It is always during a SLES install 
and
it is preceeded (about one 3270 screen earlier) by the message:

HCPIPN2833E IP address is already registered.

The guys who dug into this believe there may be a bug in the OSA card 
and
we still don't have a fix.  It may have to do with a race condition and
thus is intermittent.

The way we work around it is to keep trying.  Set up a PARMFILE with all
the appropriate networking variables set, if you don't have one already
(it will save you a lot of typing). When you hit the error, just do a 
"#CP
IPL 00C" to IPL the reader and start over. I usually get past it on the
second or third try, but have gone up to eight.

Here's an example PARMFILE:

ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb
INST_PASSWORD=xx IP_ADDR=nnn.nnn.nnn.nnn AUTOINSTALL=yes
IP_HOST=xx.xxx.xxx IP_GATEWAY=nnn.nnn.nnn.nnn
IP_INTERFACE=qeth IP_MTU=1500 IP_NETMASK=255.255.255.0
IP_BROADCAST=nnn.nnn.nnn.nnn READ_DEVNO=600 WRITE_DEVNO=601
DATA_DEVNO=602 PORTNAME=dontcare IP_DNS=nnn.nnn.nnn.nnn
INST_INFO=nfs INST_IP_ADDR=nnn.nnn.nnn.nnn
INST_IP_DIR=/nfs/sles9root INST_SCREEN=VNC VNC_PASSWORD=xx

Hope this helps.


"Mike MacIsaac" <[EMAIL PROTECTED]>   (845) 433-7061

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or 
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES 8 vs 9 Install and vswitch config

[Quillen, Channon]

I modified the PARMFILE, but now get the following error:

Freeing unused kernel memory: 108k freed
attempt to access beyond end of device
ram0: rw=0 want=92358, limit=65536
Buffer I/O error on device ram0, logical block 46178
Kernel panic: Attempted to kill init!

-Channon 
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Michael MacIsaac
Sent: Saturday, March 05, 2005 5:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES 8 vs 9 Install and vswitch config

> I am able to install SLES 8 31-bit on a configured guest.
> When I try to install SLES 9 31 or 64 bit over the same guest, the
> install fails when trying to ping the gateway.
This may the same issue I've seen. It is always during a SLES install
and
it is preceeded (about one 3270 screen earlier) by the message:

HCPIPN2833E IP address is already registered.

The guys who dug into this believe there may be a bug in the OSA card
and
we still don't have a fix.  It may have to do with a race condition and
thus is intermittent.

The way we work around it is to keep trying.  Set up a PARMFILE with all
the appropriate networking variables set, if you don't have one already
(it will save you a lot of typing). When you hit the error, just do a
"#CP
IPL 00C" to IPL the reader and start over. I usually get past it on the
second or third try, but have gone up to eight.

Here's an example PARMFILE:

ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb
INST_PASSWORD=xx IP_ADDR=nnn.nnn.nnn.nnn AUTOINSTALL=yes
IP_HOST=xx.xxx.xxx IP_GATEWAY=nnn.nnn.nnn.nnn
IP_INTERFACE=qeth IP_MTU=1500 IP_NETMASK=255.255.255.0
IP_BROADCAST=nnn.nnn.nnn.nnn READ_DEVNO=600 WRITE_DEVNO=601
DATA_DEVNO=602 PORTNAME=dontcare IP_DNS=nnn.nnn.nnn.nnn
INST_INFO=nfs INST_IP_ADDR=nnn.nnn.nnn.nnn
INST_IP_DIR=/nfs/sles9root INST_SCREEN=VNC VNC_PASSWORD=xx

Hope this helps.


"Mike MacIsaac" <[EMAIL PROTECTED]>   (845) 433-7061

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

SLES 8 vs 9 Install and vswitch config

[Quillen, Channon]

I am able to install SLES 8 31-bit on a configured guest.
When I try to install SLES 9 31 or 64 bit over the same guest, the
install fails when trying to ping the gateway.

I have other guests installed that can ping their gateway.
Is there a module config that needs to be in the parmfile?

Channon R. Quillen
LAN Administrator
Texas Farm Bureau Insurance Companies

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Need help with Websphere 5.0 Silent Install on zLinux

[Quillen, Channon]

We had the same problem, and fixed it by increasing the storbuf settings
from the default of 135 125 115 to 300 250 200
'set srm storbuf 300 250 200'

-Channon 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Dave_Myers/sesg/[EMAIL PROTECTED]
Sent: Friday, March 04, 2005 4:25 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Need help with Websphere 5.0 Silent Install on zLinux

We are attempting the WAS 5.0 silent install
on a z890 using 2 GP CPU's (about 50 mips per engine).

We have SLES9 with SP1 installed (31bit)

I have the entire WAS CD1 uploaded to the server
and it is located at:  /usr/local/WAS5.1

We enter:
/usr/local/WAS5.1/linuxs390/install -options
/usr/local/WAS5.1/linuxs390/responsefile.txt

We get msg:

Initializing Installation Wizard...
Searching for Java Virtual Machine
.

Then we see java take over the CPU at about 99%.

We have the responsefile.txt settings so that it should
get installed into /opt
but we never see anything get created in that directory.

So far we've let the java process run for about 20minutes
and it keeps getting high cpu usage...but we don't see
anything happening.

Is this a bug...or will it take a looonnng time for the install
or to see some files getting created in /opt  ???

Also, there is suppose to be a log.txt file created,
and we don't see that.

Any ideas...

Thanks,
 Dave

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

SLES 9 Install and NFS Server

[Quillen, Channon]

I followed the "SLES 9 ISO mount structure, not sure?" thread, and setup
a NFS server to hold the structure.  I've used this same NFS server for
a SLES 8.0 31-bit install.  I'm now trying to install SLES 9 64-bit, and
it is racking my brain.

I'm able to login to the guest via the 3270 and begin the install.  I
have tried the install many times with no success.  I did get to one
point where I was able to VNC into the install, but there were no drives
to be found.  I tried "cat /proc/dasd/devices" only to find there is no
devices file.

My last attempt failed as the install was not able to ping the gateway
and therefore not the NFS server.  What did I do?

Curious... on the SLES 8 install, the NFS directory was
/usr/sles8_31/cd1.  Installing SLES 9 64-bit, (/usr/sles9_64 is my
installroot) should it be /usr/sles9_64 or /usr/sles9_64/sles9/CD1?

Channon R. Quillen
LAN Administrator
Texas Farm Bureau Insurance Companies 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390