Re: z/Linux zFCP issue

2015-07-16 Thread Mainframe Mainframe
Hello,
 Thanks for info. Because of these message, I not able to reach to
login prompt in z/VM 3270 session and get into the system to see the issue.

I will ask storage team to check on fiber port from storage side,
but is there any other way to find the root cause of this issue and isolate
it now.

On Thu, Jul 16, 2015 at 7:05 PM, Raymond Higgs rayhi...@us.ibm.com wrote:

 Unsolicited status notifications are messages from the SAN indicating that
 something has happened.  Eg a target port disappeared because someone
 unplugged a link, or storage array logged out of the fabric.  They might
 be lost if:
 there are lots of them coming very quickly
 the linux system is very busy
 the channel is very busy

 Losing these isn't necessarily a problem, but it indicates that some piece
 of your infrastructure isn't very healthy.

 Regards,

 Ray Higgs
 System z IO Firmware Development
 Bld. 706, B42
 2455 South Road
 Poughkeepsie, NY 12601
 (845) 435-8666,  T/L 295-8666
 rayhi...@us.ibm.com



 From:   Mainframe Mainframe mainframe1...@gmail.com
 To: LINUX-390@VM.MARIST.EDU
 Date:   07/16/2015 08:59 AM
 Subject:z/Linux zFCP issue
 Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU



  In some of my z/Linux guests, I am getting below issues and because of
 this, system is not responding .But I am not able to isolate this issue.

 zfcp: The adapter 0.0.6573 reported the following characteristics:
 WWNN 0x5005076400c5a037, WWPN 0xc05076e206805201, S_ID 0x004f0600,
 adapter version 0x6, LIC version 0x4a6
 zfcp: Switched fabric fibrechannel network detected at adapter 0.0.6573.
 + /sbin/lscss
 + cat online
 + echo 0x5005076306088115
 + cd 0x5005076306088115
 + echo 0x4011400B
 zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
 ELS
 zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
 ELS
 zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
 ELS
 zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
 ELS
 zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
 ELS


 Can anybody provide little hint on this issue and help us to resolve .

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/



 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


z/Linux zFCP issue

2015-07-16 Thread Mainframe Mainframe
 In some of my z/Linux guests, I am getting below issues and because of
this, system is not responding .But I am not able to isolate this issue.

zfcp: The adapter 0.0.6573 reported the following characteristics:
WWNN 0x5005076400c5a037, WWPN 0xc05076e206805201, S_ID 0x004f0600,
adapter version 0x6, LIC version 0x4a6
zfcp: Switched fabric fibrechannel network detected at adapter 0.0.6573.
+ /sbin/lscss
+ cat online
+ echo 0x5005076306088115
+ cd 0x5005076306088115
+ echo 0x4011400B
zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
ELS
zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
ELS
zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
ELS
zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
ELS
zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573, incoming
ELS


Can anybody provide little hint on this issue and help us to resolve .

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: z/Linux zFCP issue

2015-07-16 Thread Mainframe Mainframe
But in my case, I am keep getting these messages and not getting login
prompt.



On Thu, Jul 16, 2015 at 7:49 PM, Raymond Higgs rayhi...@us.ibm.com wrote:

 Those messages won't prevent you from getting to the login prompt.  There
 is some other issue.  I would start at the switch console to figure out
 what is happening in the SAN.  I would use a performance monitor to look
 for issues inside the machine.

 Regards,

 Ray Higgs
 System z IO Firmware Development
 Bld. 706, B42
 2455 South Road
 Poughkeepsie, NY 12601
 (845) 435-8666,  T/L 295-8666
 rayhi...@us.ibm.com



 From:   Mainframe Mainframe mainframe1...@gmail.com
 To: LINUX-390@VM.MARIST.EDU
 Date:   07/16/2015 09:46 AM
 Subject:Re: z/Linux zFCP issue
 Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU



 Hello,
  Thanks for info. Because of these message, I not able to reach to
 login prompt in z/VM 3270 session and get into the system to see the
 issue.

 I will ask storage team to check on fiber port from storage side,
 but is there any other way to find the root cause of this issue and
 isolate
 it now.

 On Thu, Jul 16, 2015 at 7:05 PM, Raymond Higgs rayhi...@us.ibm.com
 wrote:

  Unsolicited status notifications are messages from the SAN indicating
 that
  something has happened.  Eg a target port disappeared because someone
  unplugged a link, or storage array logged out of the fabric.  They might
  be lost if:
  there are lots of them coming very quickly
  the linux system is very busy
  the channel is very busy
 
  Losing these isn't necessarily a problem, but it indicates that some
 piece
  of your infrastructure isn't very healthy.
 
  Regards,
 
  Ray Higgs
  System z IO Firmware Development
  Bld. 706, B42
  2455 South Road
  Poughkeepsie, NY 12601
  (845) 435-8666,  T/L 295-8666
  rayhi...@us.ibm.com
 
 
 
  From:   Mainframe Mainframe mainframe1...@gmail.com
  To: LINUX-390@VM.MARIST.EDU
  Date:   07/16/2015 08:59 AM
  Subject:z/Linux zFCP issue
  Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU
 
 
 
   In some of my z/Linux guests, I am getting below issues and because of
  this, system is not responding .But I am not able to isolate this issue.
 
  zfcp: The adapter 0.0.6573 reported the following characteristics:
  WWNN 0x5005076400c5a037, WWPN 0xc05076e206805201, S_ID 0x004f0600,
  adapter version 0x6, LIC version 0x4a6
  zfcp: Switched fabric fibrechannel network detected at adapter 0.0.6573.
  + /sbin/lscss
  + cat online
  + echo 0x5005076306088115
  + cd 0x5005076306088115
  + echo 0x4011400B
  zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573,
 incoming
  ELS
  zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573,
 incoming
  ELS
  zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573,
 incoming
  ELS
  zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573,
 incoming
  ELS
  zfcp: Unsolicited status notification(s) lost: adapter 0.0.6573,
 incoming
  ELS
 
 
  Can anybody provide little hint on this issue and help us to resolve .
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 
 
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/



 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http

Re: WWPN changes

2015-06-17 Thread Mainframe Mainframe
Using yast. what parameter I should be changing . Can you please guide more
on this.



On Wed, Jun 17, 2015 at 10:06 PM, Mark Post mp...@suse.com wrote:

  On 6/17/2015 at 08:37 AM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Hello ,
  Thanks for reply.Method used in LUN Management with ZFCP:
 SLES
  Post-Installation pdf is YAST. But I am not able to find file name and
  location, where I can manually modify the entry for new WWPN number.

 You _should_ be using YaST.  You should _not_ be trying to edit anything
 manually.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: WWPN changes

2015-06-17 Thread Mainframe Mainframe
Hello ,
  Thanks for reply . I am new in this configuration. I
checked the links provided in earlier email chain. But I am still not clear
the file where I will have to change the WWPN number .



On Wed, Jun 17, 2015 at 3:45 PM, Steffen Maier ma...@linux.vnet.ibm.com
wrote:

 On 06/17/2015 07:45 AM, Mainframe Mainframe wrote:

 We are using SUSE 11.2 z/Linux system with FCP channels. There are  issues
 with one host that WWPN  being dropped .
 So, now we want to use different WWPN number for this host and bring up
 again.


 Do you really mean the WWPN for host as in Fibre Channel host (Linunx
 fc_host), i.e. the initiator WWPN of the FCP device itself?

 Why?

 It's the machine (not the OS) that automatically manages initiator WWPNs;
 both the physical WWPN of the FCP channel as well as all the virtual WWPNs
 of NPIV-enabled FCP devices of FCP channels.
 Both contain an IBM OUI prefix and something derived from the CEC's I/O
 serial.
 NPIV WWPNs also contain an automatically generated suffix.
 Physical Channel WWPNs also contain the PCHID followed by 1 as 4 trailing
 hex digits (as of z196).

 http://www.redbooks.ibm.com/redbooks/SG247266/wwhelp/wwhimpl/api.htm?href=10-1-1.htm

  For doing this, as per my knowledge we have to change entries in two
 places

 1) z/VM text file, which is used while z/Linux comes up and have network
 related information etc.


 If you refer to the parm file used to pass kernel parameters at boot/IPL,
 then this does not deal with initiator WWPNs.
 Only for some distro installers it can be used to configure LUNs but that
 involves storage target WWPNs.

  2) Somewhere in z/Linux kernel. I am not sure the exact location

 Can anybody help me making this WWPN changes in z/Linux kernel  .


 Linux configuration only deals with storage target WWPNs.
 Pointers are in a presentation I referred to earlier:
 http://www.mail-archive.com/linux-390@vm.marist.edu/msg67433.html

 --
 Mit freundlichen Grüßen / Kind regards
 Steffen Maier

 Linux on System z Development

 IBM Deutschland Research  Development GmbH
 Vorsitzende des Aufsichtsrats: Martina Koederitz
 Geschaeftsfuehrung: Dirk Wittkopp
 Sitz der Gesellschaft: Boeblingen
 Registergericht: Amtsgericht Stuttgart, HRB 243294

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: WWPN changes

2015-06-17 Thread Mainframe Mainframe
Hello ,
Thanks for reply.Method used in LUN Management with ZFCP: SLES
Post-Installation pdf is YAST. But I am not able to find file name and
location, where I can manually modify the entry for new WWPN number.

Current output for some of the commands are

sles112 : :/ # lszfcp -D
Error: No fcp devices found.


sles112:/sys/bus/ccw/drivers/zfcp/0.0.651e # cd peer_wwpn
-bash: cd: peer_wwpn: Not a directory

sles112 :/ # lszfcp -Ha | grep -e port_name -e ^0
0.0.651e host0
permanent_port_name = 0x
port_name   = 0x0
strkf32:/ #




On Wed, Jun 17, 2015 at 5:33 PM, Steffen Maier ma...@linux.vnet.ibm.com
wrote:

 On 06/17/2015 01:50 PM, Mainframe Mainframe wrote:

Thanks for reply . I am new in this configuration. I
 checked the links provided in earlier email chain. But I am still not
 clear
 the file where I will have to change the WWPN number .


 Assuming you want to change paths to LUNs to use a different target WWPNs
 on a Linux, that was already installed and is currently running, then the
 slides
 LUN Management with ZFCP: SLES/RHEL Post-Installation
 would apply.

 You use tools with SLES to remove paths with the old WWPN and add paths
 with the new WWPN.

 You edit text files with RHEL.

 More information for such distro specific information is in the distro
 documentation referred to at the bottom half of slide More Information.

 Where appropriate, IBM also refers to distro documentation in the zfcp
 chapter of the book Device Drivers, Features, and Commands.

  On Wed, Jun 17, 2015 at 3:45 PM, Steffen Maier ma...@linux.vnet.ibm.com
 wrote:

 On 06/17/2015 07:45 AM, Mainframe Mainframe wrote:

  We are using SUSE 11.2 z/Linux system with FCP channels. There are
 issues
 with one host that WWPN  being dropped .
 So, now we want to use different WWPN number for this host and bring up
 again.


2) Somewhere in z/Linux kernel. I am not sure the exact location


 Can anybody help me making this WWPN changes in z/Linux kernel  .


 Linux configuration only deals with storage target WWPNs.
 Pointers are in a presentation I referred to earlier:
 http://www.mail-archive.com/linux-390@vm.marist.edu/msg67433.html



 --
 Mit freundlichen Grüßen / Kind regards
 Steffen Maier

 Linux on System z Development

 IBM Deutschland Research  Development GmbH
 Vorsitzende des Aufsichtsrats: Martina Koederitz
 Geschaeftsfuehrung: Dirk Wittkopp
 Sitz der Gesellschaft: Boeblingen
 Registergericht: Amtsgericht Stuttgart, HRB 243294

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


WWPN changes

2015-06-16 Thread Mainframe Mainframe
Hello Group,

We are using SUSE 11.2 z/Linux system with FCP channels. There are  issues
with one host that WWPN  being dropped .
So, now we want to use different WWPN number for this host and bring up
again.

For doing this, as per my knowledge we have to change entries in two places

1) z/VM text file, which is used while z/Linux comes up and have network
related information etc.

2) Somewhere in z/Linux kernel. I am not sure the exact location

Can anybody help me making this WWPN changes in z/Linux kernel  .

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


[no subject]

2015-06-10 Thread Mainframe Mainframe
Hello ,
 Thanks for reply .As I mentioned, fsck is running on rebooting
time and its not getting completed and having issue mentioned earlier email
chain.

So, to isolate this issue, I want to revert back

dev/sda1/scratch   ext3  defaults 1 2

to

/dev/sda1/scratch   ext3  defaults 1 0

under /etc/fstab

From z/VM console and I am not good at using SID  editor commands. Can
anybody provide syntax for changing this line using SID editor commands.


Currently system is accessible in repair filesystem mode.

(Repair filesystem) 1 #




On Tue, Jun 9, 2015 at 2:31 PM, Steffen Maier ma...@linux.vnet.ibm.com
wrote:

 On 06/09/2015 09:22 AM, Mainframe Mainframe wrote:

 Hello Group,
Currently we facing below issue.

 *Issue : *

 /scratch is on dasda1 device. We need mount sda device on /scratch so that
 we can do porting work.

 Steps taken to solve issue :

 # umount -l /scratch


 This seems to be a lazy unmount, so you don't know when this mount point
 will be truely unmounted properly.

  # fsck -y /scratch
 fsck 1.39 (29-May-2006)
 e2fsck 1.39 (29-May-2006)
 fsck.ext3: Attempt to read block from filesystem resulted in short read
 while trying to open /dev/sda1
 Could this be a zero-length partition?


 Maybe due to the lazy unmount, /scratch might be in some intermediate
 state or now even already belong to containing the root-fs(!), so calling
 fsck on that mount point seems dangerous.

 A safe procedure might be to unmount without lazy option and then fsck the
 block device that used to be mounted on /scratch, i.e. /dev/dasda1.

  *cat /etc/fstab*

 LABEL=/ /   ext3
   defaults,usrquota,grpquota1 1
 tmpfs   /dev/shmtmpfs   size=8045M
 0
 0
 devpts  /dev/ptsdevpts  gid=5,mode=620  0
 0
 sysfs   /syssysfs   defaults0
 0
 proc/proc   procdefaults0
 0
 /dev/sda1/scratch   ext3  defaults 1 0


 *We changed *

 /dev/sda1/scratch   ext3  defaults 1 0

 to

 /dev/sda1/scratch   ext3  defaults 1 2


 You should always use multipathing instead of single path SCSI devices,
 otherwise you lack path redundancy.

 How do you ensure that all the paths to this SCSI disk are persistently
 configured?
 (SCSI devices don't appear fully automatically without any user action
 with Linux on z Systems.)
 In other words, it could have been that there is no /dev/sda at all during
 fsck time on boot.


 http://www-05.ibm.com/de/events/linux-on-z/pdf/day2/4_Steffen_Maier_zfcp-best-practices-2015.pdf

  *So, that fsck run on reboot time  and we rebooted system and after reboot
 I was getting below messages.*




 Checking all file systems.
 -/sbin/fsck.ext3 (1) -- /- fsck.ext3 -a /dev/dasda1
 /: clean, 177325/5412928 files, 1517520/5408976 blocks
 -/sbin/fsck.ext3 (1) -- /scratch- fsck.ext3 -a /dev/sda1
 fsck.ext3: No such file or directory while trying to open /dev/sda1
 /dev/sda1:
 The superblock could not be read or does not describe a correct ext2
 filesystem.  If the device is valid and it really contains an ext2
 filesystem (and not swap or ufs or something else), then the superblock
 is corrupt, and you might try running e2fsck with an alternate superblock:
  e2fsck -b 8193 device

 -FAILED-

 *** An error occurred during the file system check.
 *** Dropping you to a shell; the system will reboot
 *** when you leave the shell.
 Give root password for maintenance


 e2fsck -b 8193
 Usage: e2fsck --panyrcdfvstDFSV- --b superblock- --B blocksize-
  --I inode_buffer_blocks- --P process_inode_size-
  --l|-L bad_blocks_file- --C fd- --j external_journal-
  --E extended-options- device

 Emergency help:
   -p   Automatic repair (no questions)
   -n   Make no changes to the filesystem
   -y   Assume yes to all questions
   -c   Check for bad blocks and add them to the badblock
 list
   -f   Force checking even if filesystem is marked clean
   -v   Be verbose
   -b superblockUse alternative superblock
   -B blocksize Force blocksize when looking for superblock
   -j external_journal  Set location of the external journal
   -l bad_blocks_file   Add to badblocks list
   -L bad_blocks_file   Set badblocks list
 (Repair filesystem) 2 #


 Any solution of this issue.


 --
 Mit freundlichen Grüßen / Kind regards
 Steffen Maier

 Linux on System z Development

 IBM Deutschland Research  Development GmbH
 Vorsitzende des Aufsichtsrats: Martina Koederitz
 Geschaeftsfuehrung: Dirk Wittkopp
 Sitz der Gesellschaft: Boeblingen
 Registergericht: Amtsgericht Stuttgart, HRB 243294

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists

[no subject]

2015-06-09 Thread Mainframe Mainframe
Hello Group,
  Currently we facing below issue.

*Issue : *

/scratch is on dasda1 device. We need mount sda device on /scratch so that
we can do porting work.

Steps taken to solve issue :

# umount -l /scratch
# fsck -y /scratch
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext3: Attempt to read block from filesystem resulted in short read
while trying to open /dev/sda1
Could this be a zero-length partition?

*cat /etc/fstab*

LABEL=/ /   ext3
 defaults,usrquota,grpquota1 1
tmpfs   /dev/shmtmpfs   size=8045M0
0
devpts  /dev/ptsdevpts  gid=5,mode=620  0 0
sysfs   /syssysfs   defaults0 0
proc/proc   procdefaults0 0
/dev/sda1/scratch   ext3  defaults 1 0


*We changed *

/dev/sda1/scratch   ext3  defaults 1 0

to

/dev/sda1/scratch   ext3  defaults 1 2


*So, that fsck run on reboot time  and we rebooted system and after reboot
I was getting below messages.*



Checking all file systems.
-/sbin/fsck.ext3 (1) -- /- fsck.ext3 -a /dev/dasda1
/: clean, 177325/5412928 files, 1517520/5408976 blocks
-/sbin/fsck.ext3 (1) -- /scratch- fsck.ext3 -a /dev/sda1
fsck.ext3: No such file or directory while trying to open /dev/sda1
/dev/sda1:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 device

-FAILED-

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance


e2fsck -b 8193
Usage: e2fsck --panyrcdfvstDFSV- --b superblock- --B blocksize-
--I inode_buffer_blocks- --P process_inode_size-
--l|-L bad_blocks_file- --C fd- --j external_journal-
--E extended-options- device

Emergency help:
 -p   Automatic repair (no questions)
 -n   Make no changes to the filesystem
 -y   Assume yes to all questions
 -c   Check for bad blocks and add them to the badblock list
 -f   Force checking even if filesystem is marked clean
 -v   Be verbose
 -b superblockUse alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal  Set location of the external journal
 -l bad_blocks_file   Add to badblocks list
 -L bad_blocks_file   Set badblocks list
(Repair filesystem) 2 #


Any solution of this issue.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: z/Linux IPL UNIT ERROR

2015-05-27 Thread Mainframe Mainframe
I am trying from
611E, thats my z/Linux volser for this guest.

On Wed, May 27, 2015 at 11:46 AM, Mark Post mp...@suse.com wrote:

  On 5/27/2015 at 01:29 AM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Below is the output ..
 
  00: CP  Q V DA
  00: DASD 0190 3390 ZVM1RES R/O107 CYL ON DASD  B908 SUBCHANNEL =
  0008
  00: DASD 0191 3390 Q58D2F R/O  5 CYL ON DASD  8D2F SUBCHANNEL =
 0009
  00: DASD 019D 3390 ZVM1RES R/O146 CYL ON DASD  B908 SUBCHANNEL =
  0007
  00: DASD 019E 3390 ZVM1RES R/O250 CYL ON DASD  B908 SUBCHANNEL =
  0006
  00: DASD 0200 3390 LX611E R/W  30050 CYL ON DASD  611E SUBCHANNEL =
 
  00: DASD 0205 3390 LX3617 R/O 50 CYL ON DASD  3617 SUBCHANNEL =
 000A
  00: DASD 0207 9336 (VDSK) R/W4194296 BLK ON DASD  VDSK SUBCHANNEL =
 0001

 And which of these devices are you trying to IPL from?


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


z/Linux IPL UNIT ERROR

2015-05-26 Thread Mainframe Mainframe
Hello Group,
  When I am booting the  z/linux guest , getting below PSW.


HCPVMI232E IPL UNIT ERROR; IRB 00404017 00020988 0E18 0040 SNS
00081
E00
00: HCPGIR450W CP entered; disabled wait PSW 000E 0232


this z/Linux system was working perfectly and now suddenly having this
issue. I am not getting any manual to check this IRB, CCW and sense code to
check for this error.

Please suggest.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: z/Linux IPL UNIT ERROR

2015-05-26 Thread Mainframe Mainframe
Hello Anthony,
   No, this can not be solution. Because the link you sent
point to the IPL error during installation time. But in our case its
different IRB, CCW and sense code.




On Wed, May 27, 2015 at 8:05 AM, Anthony Thompson 
anthony.thomp...@nt.gov.au wrote:

  A trivial Google search gave me this link:

 https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg29431.html



 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Mainframe Mainframe
 Sent: Wednesday, 27 May 2015 11:12 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: z/Linux IPL UNIT ERROR

 Hello Group,
   When I am booting the  z/linux guest , getting below PSW.


 HCPVMI232E IPL UNIT ERROR; IRB 00404017 00020988 0E18 0040 SNS
 00081
 E00
 00: HCPGIR450W CP entered; disabled wait PSW 000E 0232


 this z/Linux system was working perfectly and now suddenly having this
 issue. I am not getting any manual to check this IRB, CCW and sense code to
 check for this error.

 Please suggest.

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: z/Linux IPL UNIT ERROR

2015-05-26 Thread Mainframe Mainframe
Hello Scott,
 Thanks for help.  Is there any possibility to verify this
issue in more detail. We are getting this issue in two systems and not able
to IPL systems now.



On Wed, May 27, 2015 at 8:26 AM, Scott Rohling scott.rohl...@gmail.com
wrote:

 Are you sure you're booting the right device/disk?   The abend code
 basically says the IPL device received an IO interrupt/unit check...   If
 you are booting the right device -- could anything possibly have linked it
 MW so it was corrupted?

 Scott Rohling

 On Tue, May 26, 2015 at 7:46 PM, Mainframe Mainframe 
 mainframe1...@gmail.com wrote:

  Hello Anthony,
 No, this can not be solution. Because the link you
 sent
  point to the IPL error during installation time. But in our case its
  different IRB, CCW and sense code.
 
 
 
 
  On Wed, May 27, 2015 at 8:05 AM, Anthony Thompson 
  anthony.thomp...@nt.gov.au wrote:
 
A trivial Google search gave me this link:
  
   https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg29431.html
  
  
  
   -Original Message-
   From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
   Mainframe Mainframe
   Sent: Wednesday, 27 May 2015 11:12 AM
   To: LINUX-390@VM.MARIST.EDU
   Subject: z/Linux IPL UNIT ERROR
  
   Hello Group,
 When I am booting the  z/linux guest , getting below
  PSW.
  
  
   HCPVMI232E IPL UNIT ERROR; IRB 00404017 00020988 0E18 0040 SNS
   00081
   E00
   00: HCPGIR450W CP entered; disabled wait PSW 000E 0232
  
  
   this z/Linux system was working perfectly and now suddenly having this
   issue. I am not getting any manual to check this IRB, CCW and sense
 code
  to
   check for this error.
  
   Please suggest.
  
   --
   For LINUX-390 subscribe / signoff / archive access instructions, send
   email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
   http://www.marist.edu/htbin/wlvindex?LINUX-390
   --
   For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
  
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: z/Linux IPL UNIT ERROR

2015-05-26 Thread Mainframe Mainframe
Hello,
   I tried your suggestion,


z/VM DASD DUMP/RESTORE PROGRAM
ENTER:
IN 611E 3390 SCRATCH
HCPDDR704E DEVICE 611E NOT OPERATIONAL
ENTER:


and then I tried ,

q 611E
00: DASD 611E CP SYSTEM LX611E   1
Ready;
att 611E *
00: HCPATR122E DASD 611E already attached to SYSTEM
Ready(00122);
det 611E system
00: HCPDTS124E DASD 611E in use by 1 users
Ready(00124);



On Wed, May 27, 2015 at 8:50 AM, Neale Ferguson ne...@sinenomine.net
wrote:

 IPL CMS
 DDR
 IN XXX 3390 SCRATCH
 TY 0 0 1

 XXX = device address of IPL device

 You should see the IPL record. Cut and paste the first 24 bytes to an
 email.

 I assume the IPL statement is in the directory entry for this virtual
 machine. Has it been changed? What other disks does that guest have? What
 happens if you IPL of these others?


  Original message 
 From: Mainframe Mainframe mainframe1...@gmail.com
 Date: 2015/05/26 23:09 (GMT-05:00)
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: [LINUX-390] z/Linux IPL UNIT ERROR

 Hello Scott,
  Thanks for help.  Is there any possibility to verify this
 issue in more detail. We are getting this issue in two systems and not able
 to IPL systems now.



 On Wed, May 27, 2015 at 8:26 AM, Scott Rohling scott.rohl...@gmail.com
 wrote:

  Are you sure you're booting the right device/disk?   The abend code
  basically says the IPL device received an IO interrupt/unit check...   If
  you are booting the right device -- could anything possibly have linked
 it
  MW so it was corrupted?
 
  Scott Rohling
 
  On Tue, May 26, 2015 at 7:46 PM, Mainframe Mainframe 
  mainframe1...@gmail.com wrote:
 
   Hello Anthony,
  No, this can not be solution. Because the link you
  sent
   point to the IPL error during installation time. But in our case its
   different IRB, CCW and sense code.
  
  
  
  
   On Wed, May 27, 2015 at 8:05 AM, Anthony Thompson 
   anthony.thomp...@nt.gov.au wrote:
  
 A trivial Google search gave me this link:
   
https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg29431.html
   
   
   
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf
 Of
Mainframe Mainframe
Sent: Wednesday, 27 May 2015 11:12 AM
To: LINUX-390@VM.MARIST.EDU
Subject: z/Linux IPL UNIT ERROR
   
Hello Group,
  When I am booting the  z/linux guest , getting
 below
   PSW.
   
   
HCPVMI232E IPL UNIT ERROR; IRB 00404017 00020988 0E18 0040
 SNS
00081
E00
00: HCPGIR450W CP entered; disabled wait PSW 000E 0232
   
   
this z/Linux system was working perfectly and now suddenly having
 this
issue. I am not getting any manual to check this IRB, CCW and sense
  code
   to
check for this error.
   
Please suggest.
   
   
 --
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
   visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
   
 --
For more information on Linux on System z, visit
   http://wiki.linuxvm.org/
   
  
   --
   For LINUX-390 subscribe / signoff / archive access instructions,
   send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or
   visit
   http://www.marist.edu/htbin/wlvindex?LINUX-390
   --
   For more information on Linux on System z, visit
   http://wiki.linuxvm.org/
  
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org

Re: z/Linux IPL UNIT ERROR

2015-05-26 Thread Mainframe Mainframe
Below is the output ..

00: CP  Q V DA
00: DASD 0190 3390 ZVM1RES R/O107 CYL ON DASD  B908 SUBCHANNEL =
0008
00: DASD 0191 3390 Q58D2F R/O  5 CYL ON DASD  8D2F SUBCHANNEL = 0009
00: DASD 019D 3390 ZVM1RES R/O146 CYL ON DASD  B908 SUBCHANNEL =
0007
00: DASD 019E 3390 ZVM1RES R/O250 CYL ON DASD  B908 SUBCHANNEL =
0006
00: DASD 0200 3390 LX611E R/W  30050 CYL ON DASD  611E SUBCHANNEL = 
00: DASD 0205 3390 LX3617 R/O 50 CYL ON DASD  3617 SUBCHANNEL = 000A
00: DASD 0207 9336 (VDSK) R/W4194296 BLK ON DASD  VDSK SUBCHANNEL = 0001


On Wed, May 27, 2015 at 9:23 AM, Neale Ferguson ne...@sinenomine.net
wrote:

 661e is the real address. What address is your guest linking to it as?
 What does #CP  Q V DA report?

  Original message 
 From: Mainframe Mainframe mainframe1...@gmail.com
 Date: 2015/05/26 23:50 (GMT-05:00)
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: [LINUX-390] z/Linux IPL UNIT ERROR

 Hello,
I tried your suggestion,


 z/VM DASD DUMP/RESTORE PROGRAM
 ENTER:
 IN 611E 3390 SCRATCH
 HCPDDR704E DEVICE 611E NOT OPERATIONAL
 ENTER:


 and then I tried ,

 q 611E
 00: DASD 611E CP SYSTEM LX611E   1
 Ready;
 att 611E *
 00: HCPATR122E DASD 611E already attached to SYSTEM
 Ready(00122);
 det 611E system
 00: HCPDTS124E DASD 611E in use by 1 users
 Ready(00124);



 On Wed, May 27, 2015 at 8:50 AM, Neale Ferguson ne...@sinenomine.net
 wrote:

  IPL CMS
  DDR
  IN XXX 3390 SCRATCH
  TY 0 0 1
 
  XXX = device address of IPL device
 
  You should see the IPL record. Cut and paste the first 24 bytes to an
  email.
 
  I assume the IPL statement is in the directory entry for this virtual
  machine. Has it been changed? What other disks does that guest have? What
  happens if you IPL of these others?
 
 
   Original message 
  From: Mainframe Mainframe mainframe1...@gmail.com
  Date: 2015/05/26 23:09 (GMT-05:00)
  To: LINUX-390@VM.MARIST.EDU
  Subject: Re: [LINUX-390] z/Linux IPL UNIT ERROR
 
  Hello Scott,
   Thanks for help.  Is there any possibility to verify
 this
  issue in more detail. We are getting this issue in two systems and not
 able
  to IPL systems now.
 
 
 
  On Wed, May 27, 2015 at 8:26 AM, Scott Rohling scott.rohl...@gmail.com
  wrote:
 
   Are you sure you're booting the right device/disk?   The abend code
   basically says the IPL device received an IO interrupt/unit check...
  If
   you are booting the right device -- could anything possibly have linked
  it
   MW so it was corrupted?
  
   Scott Rohling
  
   On Tue, May 26, 2015 at 7:46 PM, Mainframe Mainframe 
   mainframe1...@gmail.com wrote:
  
Hello Anthony,
   No, this can not be solution. Because the link you
   sent
point to the IPL error during installation time. But in our case its
different IRB, CCW and sense code.
   
   
   
   
On Wed, May 27, 2015 at 8:05 AM, Anthony Thompson 
anthony.thomp...@nt.gov.au wrote:
   
  A trivial Google search gave me this link:

 https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg29431.html



 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf
  Of
 Mainframe Mainframe
 Sent: Wednesday, 27 May 2015 11:12 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: z/Linux IPL UNIT ERROR

 Hello Group,
   When I am booting the  z/linux guest , getting
  below
PSW.


 HCPVMI232E IPL UNIT ERROR; IRB 00404017 00020988 0E18 0040
  SNS
 00081
 E00
 00: HCPGIR450W CP entered; disabled wait PSW 000E 0232


 this z/Linux system was working perfectly and now suddenly having
  this
 issue. I am not getting any manual to check this IRB, CCW and sense
   code
to
 check for this error.

 Please suggest.


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

  --
 For more information on Linux on System z, visit
http://wiki.linuxvm.org/

   
   
 --
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO
 LINUX-390
  or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
   
 --
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
   
  
   --
   For LINUX-390 subscribe / signoff / archive access instructions,
   send email to lists...@vm.marist.edu

Re: SUSE FTP Server issue

2015-05-07 Thread Mainframe Mainframe
 at that time.
 --
   Donald J.
   dona...@4email.net

 On Wed, May 6, 2015, at 01:03 AM, Mainframe Mainframe wrote:
  Hello Donald,
 Thanks for reply. I checked for my FTP server from
  # netstat -antp |grep listen -i
  tcp0  0 0.0.0.0:32769   0.0.0.0:*
  LISTEN
   -
  tcp0  0 0.0.0.0:20490.0.0.0:*
  LISTEN
   -
  tcp0  0 0.0.0.0:838 0.0.0.0:*
  LISTEN
   4899/rpc.mountd
  tcp0  0 0.0.0.0:15  0.0.0.0:*
  LISTEN
   4994/xinetd
  tcp0  0 0.0.0.0:111 0.0.0.0:*
  LISTEN
   4233/portmap
  tcp0  0 0.0.0.0:21  0.0.0.0:*
  LISTEN
   4994/xinetd
  tcp0  0 0.0.0.0:23  0.0.0.0:*
  LISTEN
   4994/xinetd
  tcp0  0 0.0.0.0:631 0.0.0.0:*
  LISTEN
   4710/cupsd
  tcp0  0 127.0.0.1:250.0.0.0:*
  LISTEN
   4862/master
  tcp0  0 0.0.0.0:667 0.0.0.0:*
  LISTEN
   4726/ypbind
  tcp0  0 :::22   :::*
 LISTEN
   4362/sshd
 
 
  So, in xinetd, we have
 
   # cat /etc/xinetd.d/vsftpd
  # default: off
  # description:
  #   The vsftpd FTP server serves FTP connections. It uses
  #   normal, unencrypted usernames and passwords for authentication.
  # vsftpd is designed to be secure.
  service ftp
  {
  socket_type = stream
  protocol= tcp
  wait= no
  user= root
  server  = /usr/sbin/vsftpd
  #server_args =
  #log_on_success  += DURATION USERID
  #log_on_failure  += USERID
  #nice= 10
  }
 
 
  Now, my query is do I need to add the parameter you mentioned in last
  response in this vsftpd file.
 
  accept_timeout
  The timeout, in seconds, for a remote client to establish connection
 with a
  PASV style data connection.
  Default: 60
 
  connect_timeout
  The timeout, in seconds, for a remote client to respond to our PORT style
  data connection.
  Default: 60
 
  data_connection_timeout
  The timeout, in seconds, which is roughly the maximum time we permit data
  transfers to stall for with no progress. If the timeout triggers, the
  remote client is kicked off.
  Default: 300
 
  idle_session_timeout
  The timeout, in seconds, which is the maximum time a remote client may
  spend between FTP commands. If the timeout triggers, the remote client is
  kicked off.
  Default: 300
 
  We contacted network team as well, But no solution till now. I am really
  not able to find why FTP failing only while coping  MNT190 disk.
 
  IUGIDV8339I  BYPASSING INSTDIR EXEC DUE TO PROGRAM RESTART
  IUGILB8440I NOW LOADING MAINT190 (190) DISK 4 OF 317
  IUGILB8344I FTPGET COMMAND FAILED FOR CKD190
  REISSUING COMMAND.
  CKD190*
  DMSRXS1408W File TCPIP DATA * not found
  PROCESSING CKD19000
  IUGILB8342E THE COMMAND ' PIPE FTPGET CKD190* ' FAILED WITH RC= -111
  IUGIDV8342E THE COMMAND ' EXEC INSTLBMD ' FAILED WITH RC= 100
  IUGIDV8376E INSTDVD EXEC ENDED IN ERROR
  IUGITL8342E THE COMMAND ' EXEC INSTDVD ' FAILED WITH RC=100
  IUGITL8376E INSTALL EXEC ENDED IN ERROR. TO RESTART CORRECT THE PROBLEM
 AND
  REIS
  SUE INSTALL
 
 
  Thanks for help.
 
 
  On Thu, Apr 30, 2015 at 6:37 PM, Donald J. dona...@4email.net wrote:
 
   Are these valid parms on your version of vsftpd?
   But it is unlikely you would exceed 60 or 300 seconds.
  
   accept_timeout
   The timeout, in seconds, for a remote client to establish connection
 with
   a PASV style data connection.
   Default: 60
  
   connect_timeout
   The timeout, in seconds, for a remote client to respond to our PORT
 style
   data connection.
   Default: 60
  
   data_connection_timeout
   The timeout, in seconds, which is roughly the maximum time we permit
 data
   transfers to stall for with no progress. If the timeout triggers, the
   remote client is kicked off.
   Default: 300
  
   idle_session_timeout
   The timeout, in seconds, which is the maximum time a remote client may
   spend between FTP commands. If the timeout triggers, the remote client
 is
   kicked off.
   Default: 300
  
   --
 Donald J.
 dona...@4email.net
  
  
  
   
   
we getting time out error but not sure about the reason.
We using SLES 9.2 with xinetd FTP server running under that.  I
 checked
config file but I couldn't find any such parameter to increase
 session or
connection time out.
   
  
  
   --
   http://www.fastmail.com - Same, same, but different...
  
   --
   For LINUX-390 subscribe / signoff / archive access instructions,
   send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or
   visit
   http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SUSE FTP Server issue

2015-05-06 Thread Mainframe Mainframe
Hello Donald,
   Thanks for reply. I checked for my FTP server from
# netstat -antp |grep listen -i
tcp0  0 0.0.0.0:32769   0.0.0.0:*   LISTEN
 -
tcp0  0 0.0.0.0:20490.0.0.0:*   LISTEN
 -
tcp0  0 0.0.0.0:838 0.0.0.0:*   LISTEN
 4899/rpc.mountd
tcp0  0 0.0.0.0:15  0.0.0.0:*   LISTEN
 4994/xinetd
tcp0  0 0.0.0.0:111 0.0.0.0:*   LISTEN
 4233/portmap
tcp0  0 0.0.0.0:21  0.0.0.0:*   LISTEN
 4994/xinetd
tcp0  0 0.0.0.0:23  0.0.0.0:*   LISTEN
 4994/xinetd
tcp0  0 0.0.0.0:631 0.0.0.0:*   LISTEN
 4710/cupsd
tcp0  0 127.0.0.1:250.0.0.0:*   LISTEN
 4862/master
tcp0  0 0.0.0.0:667 0.0.0.0:*   LISTEN
 4726/ypbind
tcp0  0 :::22   :::*LISTEN
 4362/sshd


So, in xinetd, we have

 # cat /etc/xinetd.d/vsftpd
# default: off
# description:
#   The vsftpd FTP server serves FTP connections. It uses
#   normal, unencrypted usernames and passwords for authentication.
# vsftpd is designed to be secure.
service ftp
{
socket_type = stream
protocol= tcp
wait= no
user= root
server  = /usr/sbin/vsftpd
#server_args =
#log_on_success  += DURATION USERID
#log_on_failure  += USERID
#nice= 10
}


Now, my query is do I need to add the parameter you mentioned in last
response in this vsftpd file.

accept_timeout
The timeout, in seconds, for a remote client to establish connection with a
PASV style data connection.
Default: 60

connect_timeout
The timeout, in seconds, for a remote client to respond to our PORT style
data connection.
Default: 60

data_connection_timeout
The timeout, in seconds, which is roughly the maximum time we permit data
transfers to stall for with no progress. If the timeout triggers, the
remote client is kicked off.
Default: 300

idle_session_timeout
The timeout, in seconds, which is the maximum time a remote client may
spend between FTP commands. If the timeout triggers, the remote client is
kicked off.
Default: 300

We contacted network team as well, But no solution till now. I am really
not able to find why FTP failing only while coping  MNT190 disk.

IUGIDV8339I  BYPASSING INSTDIR EXEC DUE TO PROGRAM RESTART
IUGILB8440I NOW LOADING MAINT190 (190) DISK 4 OF 317
IUGILB8344I FTPGET COMMAND FAILED FOR CKD190
REISSUING COMMAND.
CKD190*
DMSRXS1408W File TCPIP DATA * not found
PROCESSING CKD19000
IUGILB8342E THE COMMAND ' PIPE FTPGET CKD190* ' FAILED WITH RC= -111
IUGIDV8342E THE COMMAND ' EXEC INSTLBMD ' FAILED WITH RC= 100
IUGIDV8376E INSTDVD EXEC ENDED IN ERROR
IUGITL8342E THE COMMAND ' EXEC INSTDVD ' FAILED WITH RC=100
IUGITL8376E INSTALL EXEC ENDED IN ERROR. TO RESTART CORRECT THE PROBLEM AND
REIS
SUE INSTALL


Thanks for help.


On Thu, Apr 30, 2015 at 6:37 PM, Donald J. dona...@4email.net wrote:

 Are these valid parms on your version of vsftpd?
 But it is unlikely you would exceed 60 or 300 seconds.

 accept_timeout
 The timeout, in seconds, for a remote client to establish connection with
 a PASV style data connection.
 Default: 60

 connect_timeout
 The timeout, in seconds, for a remote client to respond to our PORT style
 data connection.
 Default: 60

 data_connection_timeout
 The timeout, in seconds, which is roughly the maximum time we permit data
 transfers to stall for with no progress. If the timeout triggers, the
 remote client is kicked off.
 Default: 300

 idle_session_timeout
 The timeout, in seconds, which is the maximum time a remote client may
 spend between FTP commands. If the timeout triggers, the remote client is
 kicked off.
 Default: 300

 --
   Donald J.
   dona...@4email.net



 
 
  we getting time out error but not sure about the reason.
  We using SLES 9.2 with xinetd FTP server running under that.  I checked
  config file but I couldn't find any such parameter to increase session or
  connection time out.
 


 --
 http://www.fastmail.com - Same, same, but different...

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,

Re: SUSE FTP Server issue

2015-04-29 Thread Mainframe Mainframe
Yes, we are handling network as well and we don't find any issues. We tried
manually connecting to FTP server from windows machine and transferred data
and all worked fine .

But not sure, If we have to make any changes in FTP server config file for
session related parameter.



On Thu, Apr 30, 2015 at 10:39 AM, Mark Post mp...@suse.com wrote:

  On 4/30/2015 at 12:44 AM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Hello All,
   We are installing z/VM 6.3 using FTP server. After running
  install script , is getting failed while  NOW LOADING MAINT190 (190)
  DISK 4 OF 317
 
 -snip-
 
  we getting time out error but not sure about the reason.

 -snip-
  Please suggest.

 For a couple of days now, Alan Altmark has been suggesting you work with
 your network team to figure this out.  Have you done that?


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SUSE FTP Server issue

2015-04-29 Thread Mainframe Mainframe
It firewall is the issue then system should not copied first 3 disks. If
you look at the error, we getting error only after 3rd disk copy.

IUGILB8440I NOW LOADING MAINTCF1 (CF1) DISK 1 OF 317
IUGILB8440I NOW LOADING MAINTCFD (CFD) DISK 2 OF 317
IUGILB8440I NOW LOADING MAINTCF3 (CF3) DISK 3 OF 317
IUGILB8440I NOW LOADING MAINT190 (190) DISK 4 OF 317
IUGILB8344I FTPGET COMMAND FAILED FOR CKD190
REISSUING COMMAND.
CKD190*
DMSRXS1408W File TCPIP DATA * not found
PROCESSING CKD19000

FTPGET TIMED OUT READING FROM STREAM, REPLY=0 0 READ WRITE EXCEPTION.
FTPGET FAILED WITH RC=-111



On Thu, Apr 30, 2015 at 11:02 AM, Mark Post mp...@suse.com wrote:

  On 4/30/2015 at 01:27 AM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Yes, we are handling network as well and we don't find any issues. We
 tried

 Does that mean they ran a network trace while reproducing the problem?  If
 not, they should.

  manually connecting to FTP server from windows machine and transferred
 data
  and all worked fine .
 
  But not sure, If we have to make any changes in FTP server config file
 for
  session related parameter.

 There is probably no FTP-related parameter for that.  I suspect the
 problem is not in the FTP server but some firewall or router in between.
 Again, network traces will help figure that 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://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: stinstall.log file issue

2015-03-08 Thread Mainframe Mainframe
Yes. I really mean RHEL 4.



On Thu, Mar 5, 2015 at 5:20 PM, Agblad Tore tore.agb...@volvo.com wrote:

 Do you really mean RHEL 4 ?
 You should use RHEL6 or maybe even RHEL7.

 BR /Tore

 
 Tore Agblad
 zOpen Teamleader
 IT Services

 Volvo Group Headquarters
 Corporate Process  IT
 Assar Gabrielssons väg 9
 SE-405 08, Gothenburg  Sweden
 E-mail: tore.agb...@volvo.com
 http://www.volvo.com/volvoit/global/en-gb/


 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Mainframe Mainframe
 Sent: den 5 mars 2015 6:42
 To: LINUX-390@VM.MARIST.EDU
 Subject: stinstall.log file issue

 Hello Group,
 I am doing some testing on RHEL 4 U5 install and after
 installation, when I tried looking at stinstall.log file /root i didnt find
 any such file. I am not sure, what could be the reason for this.

 Any idea.

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


stinstall.log file issue

2015-03-04 Thread Mainframe Mainframe
Hello Group,
I am doing some testing on RHEL 4 U5 install and after
installation, when I tried looking at stinstall.log file /root i didnt find
any such file. I am not sure, what could be the reason for this.

Any idea.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: mount issue

2014-11-04 Thread Mainframe Mainframe
Output is

[root@linux12 ~]# vmcp q v fcp
FCP  260C ON FCP   260C CHPID AE SUBCHANNEL = 000F
 260C DEVTYPE FCP VIRTUAL CHPID AE FCP REAL CHPID AE
 260C QDIO ACTIVE QIOASSIST DISABLED
 260C
 260C INP + 01 IOCNT = 0010  ADP = 128 PROG = 000 UNAVAIL = 000
 260C  BYTES = 
 260C OUT + 01 IOCNT = 0027  ADP = 000 PROG = 027 UNAVAIL = 101
 260C  BYTES = 00018254
 260C DATA ROUTER ELIGIBLE
FCP  271C ON FCP   271C CHPID AF SUBCHANNEL = 0010
 271C DEVTYPE FCP VIRTUAL CHPID AF FCP REAL CHPID AF
 271C QDIO-ELIGIBLE   QIOASSIST DISABLED
 271C DATA ROUTER ELIGIBLE
[root@linux12 ~]#




On Tue, Nov 4, 2014 at 5:37 PM, Offer Baruch offerbar...@gmail.com wrote:

 Hi

 The /scrarch directory is based on the sda device...
 The fact that lsscsi does not return output means that sda is missing and
 that is why you dont have that directory mounted.

 Can you add the output of the following command please?
 vmcp q v fcp

 Have a good day
 Offer Baruch
 On Nov 4, 2014 2:37 AM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Hello,
  We have  multiple zlinux (RHEL 6) system with below USER DIRECT
  entries
 
   MDISK 0200 3390 1 END   LX131F MR FARM SLES9 SP3
 MDISK 0207 FB-512 V-DISK 4194296 MR
 
  but we facing issue that directory /scratch/prod/ is missing . For
  isolating issue, when I checked lsscsi command I am getting blank output
 in
  nonworking system but in other system I am getting
 
  linux12:/sys/bus/ccw/drivers/zfcp # lsscsi
  [0:0:0:1074675744]diskIBM  2107900  .278  /dev/sda
  [0:0:0:1075527712]diskIBM  2107900  .278  /dev/sdb
 
  I also checked lsdasd command on both wokring and nonworking system but
  output is same.
 
 
  0.0.0200(ECKD) at ( 94:  0) is dasda  : active at blocksize 4096,
  3605940 blocks, 14085 MB
  0.0.0207(FBA ) at ( 94: 28) is dasdh  : active at blocksize 512,
  4194296 blocks, 2047 MB
 
  I also checked fstab entry and both have same
 
  linux12:/sys/bus/ccw/drivers/zfcp # cat /etc/fstab
  /dev/dasda1  /ext3   acl,user_xattr
   1 1
  proc /procproc   defaults
   0 0
  sysfs/sys sysfs  noauto
   0 0
  debugfs  /sys/kernel/debugdebugfsnoauto
   0 0
  devpts   /dev/pts devpts mode=0620,gid=5
  0 0
  /dev/sda1/scratch   ext3  defaults 1 0
 
  can anybody suggest, what else should i be looking into to isolate this
  issue.
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


SCSI device issue on RHEL 6.3

2014-11-04 Thread Mainframe Mainframe
Hello,
We have  multiple zlinux (RHEL 6) system with below USER DIRECT
entries

 MDISK 0200 3390 1 END   LX131F MR FARM SLES9 SP3
   MDISK 0207 FB-512 V-DISK 4194296 MR

but we facing issue that directory /scratch/prod/ is missing . For
isolating issue, when I checked lsscsi command I am getting blank output in
nonworking system but in other system I am getting

linux12:/sys/bus/ccw/drivers/zfcp # lsscsi
[0:0:0:1074675744]diskIBM  2107900  .278  /dev/sda
[0:0:0:1075527712]diskIBM  2107900  .278  /dev/sdb

I also checked lsdasd command on both wokring and nonworking system but
output is same.


0.0.0200(ECKD) at ( 94:  0) is dasda  : active at blocksize 4096,
3605940 blocks, 14085 MB
0.0.0207(FBA ) at ( 94: 28) is dasdh  : active at blocksize 512,
4194296 blocks, 2047 MB

I also checked fstab entry and both have same

linux12:/sys/bus/ccw/drivers/zfcp # cat /etc/fstab
/dev/dasda1  /ext3   acl,user_xattr
 1 1
proc /procproc   defaults
 0 0
sysfs/sys sysfs  noauto
 0 0
debugfs  /sys/kernel/debugdebugfsnoauto
 0 0
devpts   /dev/pts devpts mode=0620,gid=5
0 0
/dev/sda1/scratch   ext3  defaults 1 0

[root@linux12 ~]# vmcp q v fcp
FCP  260C ON FCP   260C CHPID AE SUBCHANNEL = 000F
 260C DEVTYPE FCP VIRTUAL CHPID AE FCP REAL CHPID AE
 260C QDIO ACTIVE QIOASSIST DISABLED
 260C
 260C INP + 01 IOCNT = 0010  ADP = 128 PROG = 000 UNAVAIL = 000
 260C  BYTES = 
 260C OUT + 01 IOCNT = 0027  ADP = 000 PROG = 027 UNAVAIL = 101
 260C  BYTES = 00018254
 260C DATA ROUTER ELIGIBLE
FCP  271C ON FCP   271C CHPID AF SUBCHANNEL = 0010
 271C DEVTYPE FCP VIRTUAL CHPID AF FCP REAL CHPID AF
 271C QDIO-ELIGIBLE   QIOASSIST DISABLED
 271C DATA ROUTER ELIGIBLE
[root@linux12 ~]#



can anybody suggest, what else should i be looking into to isolate this
issue.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SCSI device issue on RHEL 6.3

2014-11-04 Thread Mainframe Mainframe
Hello All,
   I tried below step as well to diagnose this issue.

[root@linux12 0.0.260c]# cd /sys/bus/ccw/drivers/zfcp/

[root@linux12 zfcp]# ls
0.0.260c  0.0.271c  bind  module  uevent  unbind

[root@linux12 zfcp]# cd 0.0.260c

[root@linux12 0.0.260c]# ls
availability  cmb_enable  cutype  devtype  driver  modalias  online  power
 subsystem  uevent

[root@linux12 0.0.260c]# cat online
0

[root@linux12 0.0.260c]# cat online
0

[root@linux12 0.0.260c]# echo 1  online

[root@linux12 0.0.260c]# cat online
1

[root@linux12 0.0.260c]# lsscsi

[root@linux12 0.0.260c]# ls -F
0x500507630710c4df/  card_version  cutype   driver@  hardware_version
 in_recovery  modalias  peer_d_id  peer_wwpnport_rescan  status
 uevent
availability cmb_enabledevtype  failed   host0/
 lic_version  onlinepeer_wwnn  port_remove  power/   subsystem@

[root@linux12 0.0.260c]# cd 0x500507630710c4df

[root@linux12 0x500507630710c4df]# ls -F
access_denied  failed  in_recovery  power/  status  uevent  unit_add
 unit_remove

[root@linux12 0x500507630710c4df]# cio_ignore -r 260c

[root@linux12 0x500507630710c4df]# chccwdev -e 260c
WARNING: Device[0.0.260c] is already  online
Done

[root@linux12 0x500507630710c4df]#  lszfcp -P
0.0.260c/0x500507630710c4df rport-0:0-0

[root@linux12 0x500507630710c4df]# lsscsi

[root@linux12 0x500507630710c4df]# lsluns
-bash: /sbin/lsluns: /usr/bin/perl: bad interpreter: No such file or
directory

[root@linux12 0x500507630710c4df]# cat /etc/zfcp.conf
cat: /etc/zfcp.conf: No such file or directory


But After this I couldn't able to progress , as I don't know much about the
way of solving this issue. Can anybody help.

On Wed, Nov 5, 2014 at 5:15 AM, Malcolm Beattie beatt...@uk.ibm.com wrote:

 Grzegorz Powiedziuk writes:
  [0:0:0:1074675744]diskIBM  2107900  .278  /dev/sda
  [0:0:0:1075527712]diskIBM  2107900  .278  /dev/sdb
 
  I've seen that before. I don't like the LUN number - 1074675744
  Make sure that in your ZFCP you have it right.
  I've seen bogus numbers like this when I typed too many zeros in the LUN
  numbe field.

 Those are normal LUN numbers for DS8k and similar scsimask-style LUNs.
 Unlike V7000, XIV, SVC etc which start at LUN ids [0, ], 1, 2, 3 for
 each host, a DS8k assigns a unique 4-hex-digit volume ID 0xWXYZ for
 every volume it creates (whether ECKD or SCSI) and for scsimask-mode
 host connections (such as the Linux one above) to a DS8k volume group
 containing volume ID 0xWXYZ it makes it visible as LUN id
 0x40WX40YZ.

 In the above list, Linux maps it to the old-style host:bus:target:lun
 by using for the LUN those upper 8 hex digits (first 32 bits of the
 64-bit LUN). 1074675744 is 0x400e4020 and 1075527712 is 0x401b4020 so
 those are valid LUN numbers for the what the DS8k would refer to as
 volume ids 0x0e02 and 0x1b20 (in extent pools 0 and 1 respectively by
 looking at the first hex digit of each).

 --Malcolm

 --
 Malcolm Beattie
 Linux and System z Technical Consultant, zChampion
 IBM UK Systems and Technology Group

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


mount issue

2014-11-03 Thread Mainframe Mainframe
Hello,
We have  multiple zlinux (RHEL 6) system with below USER DIRECT
entries

 MDISK 0200 3390 1 END   LX131F MR FARM SLES9 SP3
   MDISK 0207 FB-512 V-DISK 4194296 MR

but we facing issue that directory /scratch/prod/ is missing . For
isolating issue, when I checked lsscsi command I am getting blank output in
nonworking system but in other system I am getting

linux12:/sys/bus/ccw/drivers/zfcp # lsscsi
[0:0:0:1074675744]diskIBM  2107900  .278  /dev/sda
[0:0:0:1075527712]diskIBM  2107900  .278  /dev/sdb

I also checked lsdasd command on both wokring and nonworking system but
output is same.


0.0.0200(ECKD) at ( 94:  0) is dasda  : active at blocksize 4096,
3605940 blocks, 14085 MB
0.0.0207(FBA ) at ( 94: 28) is dasdh  : active at blocksize 512,
4194296 blocks, 2047 MB

I also checked fstab entry and both have same

linux12:/sys/bus/ccw/drivers/zfcp # cat /etc/fstab
/dev/dasda1  /ext3   acl,user_xattr
 1 1
proc /procproc   defaults
 0 0
sysfs/sys sysfs  noauto
 0 0
debugfs  /sys/kernel/debugdebugfsnoauto
 0 0
devpts   /dev/pts devpts mode=0620,gid=5
0 0
/dev/sda1/scratch   ext3  defaults 1 0

can anybody suggest, what else should i be looking into to isolate this
issue.

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


Upgrade RHEL 6.3

2014-08-01 Thread Mainframe Mainframe
We have requirement of upgrading RHEL 6.3 to RHEL 6.5 and i checked release
note of RHEL 6.5. But I couldn't find any detail on supported version for
this upgrade.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/pdf/6.5_Release_Notes/Red_Hat_Enterprise_Linux-6-6.5_Release_Notes-en-US.pdf

I have two option for this upgrade,
1) Moving from RHEL 6.3 to RHEL 6.4 and then RHEL 6.4 to RHEL 6.5
2) Directly upgrading RHEL 6.4 to RHEL 6.5.

But I am not finding any document confirming upgrade from RHEL 6.3 to RHEL
6.5 directly without any issue.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SUSE RPM issue

2014-06-12 Thread Mainframe Mainframe
Thanks Van.  do we have any such command in z/Linux to find  about the z/VM
name under which it is running.




On Wed, Jun 11, 2014 at 1:09 PM, van Sleeuwen, Berry 
berry.vansleeu...@atos.net wrote:

 Take a look at xorg-x11-devel. This rpm contains makedepend:

 rpm -qlp xorg-x11-devel-6.9.0-50.58.s390x.rpm | grep makedepend
 /usr/X11R6/bin/makedepend

 Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
 Berry van Sleeuwen.

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of
 Mainframe Mainframe
 Sent: Wednesday, June 11, 2014 5:16 AM
 To: LINUX-390@vm.marist.edu
 Subject: SUSE RPM issue

 Hello,
   We have requirement to install makedepend on /usr/X11R6/bin on
 SL10SP2. But I am not able to find required RPM . but somewhere I found
 XFree86-devel-4.3.99.902-43.48 is required but not sure on this. I also
 checked SL10SP2 repository but I couldn't find this
 XFree86-devel-4.3.99.902-43.48  in repository . Any anyone suggest, what
 exact rpm do we need to install this makedepend

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SUSE RPM issue

2014-06-12 Thread Mainframe Mainframe
this sysinfo gives LPAR name.. not z/VM under which z/Linux running. Is it
possible to z/VM name..


On Thu, Jun 12, 2014 at 12:42 PM, Neale Ferguson ne...@sinenomine.net
wrote:

 grep ^VM /proc/sysinfo | grep Name

 On Jun 12, 2014, at 5:04 PM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Thanks Van.  do we have any such command in z/Linux to find  about the
 z/VM
  name under which it is running.

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SUSE RPM issue

2014-06-12 Thread Mainframe Mainframe
and grep ^VM /proc/sysinfo | grep Name  command gives z/Linux name
itself.. notthng more..


On Thu, Jun 12, 2014 at 3:18 PM, Mainframe Mainframe 
mainframe1...@gmail.com wrote:

 this sysinfo gives LPAR name.. not z/VM under which z/Linux running. Is it
 possible to z/VM name..


 On Thu, Jun 12, 2014 at 12:42 PM, Neale Ferguson ne...@sinenomine.net
 wrote:

 grep ^VM /proc/sysinfo | grep Name

 On Jun 12, 2014, at 5:04 PM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  Thanks Van.  do we have any such command in z/Linux to find  about the
 z/VM
  name under which it is running.

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SUSE RPM issue

2014-06-12 Thread Mainframe Mainframe
In my case, in place of VM00, I am getting linux guest name. But I am
looking for z/VM name under which this z/Linux is running.

VM00 Name:LNEALE1





On Thu, Jun 12, 2014 at 3:40 PM, Neale Ferguson ne...@sinenomine.net
wrote:

 Here's what I get on a VM User called LNEALE1 running as a guest of z/VM:

 Manufacturer: IBM
 Type: 2098
 Model:Y03  E10
 Sequence Code:00067EE2
 Plant:02
 Model Capacity:   Y03  0202
 Model Perm. Capacity: Y03  0202
 Model Temp. Capacity: Y03  0202

 CPUs Total:   10
 CPUs Configured:  3
 CPUs Standby: 0
 CPUs Reserved:7
 Capability:   1352 2032
 Adjustment 02-way:60850 60850
 Adjustment 03-way:57900 57900
 Adjustment 04-way:55500 55500
 Adjustment 05-way:53780 53780
 Adjustment 06-way:53780 53780
 Adjustment 07-way:53780 53780
 Adjustment 08-way:53780 53780
 Adjustment 09-way:53780 53780
 Adjustment 10-way:53780 53780
 Secondary Capability: 1236

 LPAR Number:  0
 LPAR Characteristics: Dedicated
 LPAR Name:LP1
 LPAR Adjustment:  750
 LPAR CPUs Total:  6
 LPAR CPUs Configured: 3
 LPAR CPUs Standby:0
 LPAR CPUs Reserved:   3
 LPAR CPUs Dedicated:  3
 LPAR CPUs Shared: 0

 VM00 Name:LNEALE1
 VM00 Control Program: z/VM6.2.0
 VM00 Adjustment:  666
 VM00 CPUs Total:  2
 VM00 CPUs Configured: 2
 VM00 CPUs Standby:0
 VM00 CPUs Reserved:   0

 As you can see VM00 Name: is LNEALE1

 Neale

 On Jun 12, 2014, at 7:49 PM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  and grep ^VM /proc/sysinfo | grep Name  command gives z/Linux name
  itself.. notthng more..

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: SUSE RPM issue

2014-06-12 Thread Mainframe Mainframe
Thanks . It worked for me . Is it possible to know any information about
the production USER DIRECT file from z/Linux rather then using z/VM .




On Thu, Jun 12, 2014 at 7:03 PM, Marco Bosisio marco_bosi...@it.ibm.com
wrote:

 Hi,
 maybe that you already know this zVM cmd :   CP Q USERID
 It  providesvirtual_machine_name  where you are logged on   AT
 zVM_sysname .

 From a zLinux you can launch this cmd and receive this info:

 lxmodcd:~ # vmcp q userid
 LXMODCD AT ITAVMLX1

 Where in this case LXMODCD is the zVM virtual machine where is running
 this zLinux O.S.  and   ITAVMLX1 is the zVM system id.

 The only problem could be that you have to execute the  cmd  vmcp  from
 root  or  via  sudo

 Cordiali saluti  / Best regards

 Marco Bosisio





 From:   Neale Ferguson ne...@sinenomine.net
 To: LINUX-390@vm.marist.edu
 Date:   06/12/2014 12:58 PM
 Subject:Re: SUSE RPM issue
 Sent by:Linux on 390 Port LINUX-390@vm.marist.edu



 I understand now. The z/VM name is in DIAG 0 output but I'm not sure
 that's available anywhere.

 On Jun 12, 2014, at 8:21 PM, Mainframe Mainframe mainframe1...@gmail.com
 wrote:

  In my case, in place of VM00, I am getting linux guest name. But I am
  looking for z/VM name under which this z/Linux is running.
 
  VM00 Name:LNEALE1

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



 IBM Italia S.p.A.
 Sede Legale: Circonvallazione Idroscalo - 20090 Segrate (MI)
 Cap. Soc. euro 347.256.998,80
 C. F. e Reg. Imprese MI 01442240030 - Partita IVA 10914660153
 Società con unico azionista
 Società soggetta all?attività di direzione e coordinamento di
 International Business Machines Corporation

 (Salvo che sia diversamente indicato sopra / Unless stated otherwise
 above)

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


SUSE RPM issue

2014-06-10 Thread Mainframe Mainframe
Hello,
  We have requirement to install makedepend on /usr/X11R6/bin on
SL10SP2. But I am not able to find required RPM . but somewhere I
found XFree86-devel-4.3.99.902-43.48 is required but not sure on this. I
also checked SL10SP2 repository but I couldn't find
this XFree86-devel-4.3.99.902-43.48  in repository . Any anyone suggest,
what exact rpm do we need to install this makedepend

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