Re: VM system name
STore HYpervisor Information returns system name and ssi name of the top 3 levels of hypervisors. Op wo 8 jul. 2020 om 18:42 schreef Alan Altmark > On Wednesday, 07/08/2020 at 04:12 GMT, "Tully, Phil (CORP)" > wrote: > > When I look at /proc/sysinfo, I can see the LPAR name but I don’t see > the VM > > system name. Is there a place that the VM system name would be shown > from > > linux? > > > > LPAR Number: 2 > > LPAR Characteristics: Shared > > LPAR Name:PLB2 > > LPAR Adjustment: 390 > > LPAR CPUs Total: 32 > > LPAR CPUs Configured: 32 > > LPAR CPUs Standby:0 > > LPAR CPUs Reserved: 0 > > LPAR CPUs Dedicated: 0 > > LPAR CPUs Shared: 32 > > LPAR CPUs G-MTID: 0 > > LPAR CPUs S-MTID: 1 > > LPAR CPUs PS-MTID:1 > > > > VM00 Name:DMZLA004 > > VM00 Control Program: z/VM6.4.0 > > VM00 Adjustment: 15 > > VM00 CPUs Total: 1 > > VM00 CPUs Configured: 1 > > VM00 CPUs Standby:0 > > VM00 CPUs Reserved: 0 > > /proc/sysinfo provides you with the response from STORE SYSTEM INFORMATION > (STSI) instruction. It does not include the z/VM system ID. The CP QUERY > USERID command is the only API in the system that I'm aware of that > returns (by design) the system ID. > > Alan Altmark > > Senior Managing z/VM and Linux Consultant > IBM Systems Lab Services > IBM Z Delivery Practice > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > alan_altm...@us.ibm.com > IBM Endicott > > > -------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- Ronald van der Laan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Replacement the root disk with a larger disk (without LVM)
Csaba, Did you also run zipl? Op do 12 sep. 2019 om 17:14 schreef Csaba Polgar > Hello, > > We have many system with SLES 11 SP4, and would like to upgrade these to > SLES 12 SP4. > The the root filesystem (/, on dasd 201, with ext3, and without LVM, simple > dasd) has the OS (itself the Linux, without the applications). > But this root filesystem is too small for the upgrade. So, I did the > following steps; > - I requested a new and larger disk (on 209 address) > - after the shutdown, I formatted the new disk (209) as ext3 (from another > Linux system) > - copied the full content from the small disk (201) to the larger disk > (209, with "rsync -avxHAX --progress /sourcepath/ /targetpath/" command, > with the other Linux) > - I changed the addresses of the disks in the Guest definition: > from 201 -> to 1201 > from 209 -> to 201 > - And I started the new guests, but the boot failed. > > After it I compared the successful and unsuccessful boot logs, and I think > the below lines show the root cause of the fail; > in the successful log: > dasdb:VOL1/ LBX201: dasdb1 > in the unsuccessful log: > dasdb:VOL1/ LBX209: dasdb1 > In the unsuccessful log show, the 209 dsk address, but I use the new 201 > dasd, and the 209 should not be important for the boot. > > Somebody knows, what should be changed/updated for the usage of larger and > replaced root disk ? > > FYI, the last error messages: > devtmpfs: error mounting -2 > Freeing unused kernel memory: 396k freed > Kernel panic - not syncing: No init found. Try passing init= option to > kernel. > See Linux Documentation/init.txt for guidance. > CPU: 0 Not tainted 3.0.101-108.87.1.tux4vm-default #1 > Process swapper (pid: 1, task: 07d82038, ksp: 07d87700) > 07d87d68 0002 >07d87e08 07d87d80 07d87d80 0062a032 >0011 >000d 07d87dd0 000e >0063a978 00100ac4 07d87d68 07d87db0 > Call Trace: > ([<001009ca>] show_trace+0xe6/0x138) > [<00629d80>] panic+0xcc/0x288 > [<00100300>] init_post+0x104/0x16c > [<0096b34c>] kernel_init+0x1fc/0x248 > [<0062dfde>] kernel_thread_starter+0x6/0xc > [<0062dfd8>] kernel_thread_starter+0x0/0xc > HCPGIR450W CP entered; disabled wait PSW 00020001 8000 > 001130E4 > > > > Regards / Mit freundlichen Grüßen / Üdvözlettel, > > Csaba Polgar > > -------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- Ronald van der Laan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Red Hat 7.2 - Root not staying Auto Logged on Console ttyS0
Joseph, Looks like you got OPERATOR and CAOPER (both z/VM userids, nothing to with Linux), competing over being the SECUSER of your Linux server. Do you have CA Operator running in both userids and both being configured to monitor the Linux console? Ronald van der Laan Op dinsdag 27 september 2016 heeft Vitale, Joseph < joseph.vit...@bnymellon.com> het volgende geschreven: > Hello, > > Just installed Red Hat 7.2, running as a zVM 6.3 guest. Followed Red Hat > instructions to autolog Root on Console(ttyS0) initially works. > > Our CA Operator is used for automation which sets Observer and SECUSER > to issue commands. Seems to perform those functions too quickly > resulting in Console service to fail. > > Messages from /var/log/messages fllow: > systemd: getty@ttyS0.service has no holdoff time, scheduling restart. > systemd: start request repeated too quickly for getty@ttyS0.service > systemd: Failed to start Getty on ttyS0. > systemd: Unit getty@ttyS0.service entered failed state. > systemd: getty@ttyS0.service failed. > > > Console snippet which repeats: > Ýroot@r028n0z ~¨# HCPCFX6769I Your observation terminated by OPERATOR > HCPCFX6768I Your SECUSER set to OPERATOR by OPERATOR. > wapPassword: HCPCFX6769I Your SECUSER terminated by OPERATOR. > HCPCFX6768I Your observation by CAOPER set by OPERATOR > > > Steps to create ttyS0 Root auto login: > cp -p /lib/systemd/system/getty@.service /etc/systemd/system/getty@ > ttyS0.service > > vi /etc/systemd/system/getty@ttyS0.service > > Change from: > ConditionPathExists=/dev/tty1 > Change To: > ConditionPathExists=/dev/ttyS0 > > Change from: > [Service] > ExecStart=-/sbin/agetty --noclear %I $TERM > Change To: > [Service] > ExecStart=-/sbin/agetty --autologin root --noclear %I $TERM > : > [Install] > Change From: > DefaultInstance=tty1 > To: > DefaultInstance=ttyS0 > > Add at end: > Alias=getty@ttyS0.service<<-- ADD at end > > ln -s /etc/systemd/system/getty@ttyS0.service /etc/systemd/system/getty. > target.wants/getty@ttyS0.service<mailto:/etc/systemd/ > system/getty.target.wants/getty@ttyS0.service> > > > Thanks > Joe > > Technology Services Group > Mainframe Operating Systems > > Pershing Plaza > 95 Christopher Columbus Drive > Floor 14 > Jersey City, N.J. 07302 > Work 201-395-1509 > Cell917-903-0102 > > > The information contained in this e-mail, and any attachment, is > confidential and is intended solely for the use of the intended recipient. > Access, copying or re-use of the e-mail or any attachment, or any > information contained therein, by any other person is not authorized. If > you are not the intended recipient please return the e-mail to the sender > and delete it from your computer. Although we attempt to sweep e-mail and > attachments for viruses, we do not guarantee that either are virus-free and > accept no liability for any damage sustained as a result of viruses. > > Please refer to http://disclaimer.bnymellon.com/eu.htm for certain > disclosures relating to European legal entities. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu <javascript:;> 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/ > -- Ronald van der Laan -- 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: Back to the future?
Martin and Rob, Op woensdag 27 juli 2016 heeft Rob van der Heij <rvdh...@gmail.com> het volgende geschreven: > On 27 July 2016 at 14:09, Martin Schwidefsky <schwidef...@de.ibm.com > <javascript:;>> wrote: > > > > Are you referring to the RTC clock interface of the kernel? If so then > yes, > > that never worked for s390. If you look into drivers/rtc/Kconfig you'll > > find this: > > > > No, I meant the HWCLOCK setting in the startup which tried to read the > RTC > check and then primed the ntp offset with a bogus value. > I believe ntpd uses two files with previous offset and drift. It might be > interesting if you could manufacture those with the proper offset and prime > the ntp offset and do away with the steering. > > > > If I do a "#cp query time" on my z/VM guests I get something like this: > > > > 00: CP QUERY TIME > > 00: TIME IS 14:01:14 CST WEDNESDAY 07/27/16 > > 00: CONNECT= 99:59:59 VIRTCPU= 007:13.79 TOTCPU= 007:35.53 > > > > The interesting part is "CST", which stands for coordinated server time. > > And this does not include leap seconds. That implies that your local time > > for CP and CMS is not in UTC, no? > > > > > No, I believe "CST" is the time zone name. This might be abusing the > abbreviation for "Central Standard Time" as something like "Central Europe > Summer Time". If you do a Q TIMEZONE you may find that it's been set to so > many hours off GMT (or you see it's linked to STP). > > Almost certainly CeST for Böblingen. For some reason I do not really understand, the timezone fields in CP are 4 chars long, only at a few places, the maximum timezone name is limited to 3. Strange if you consider that most official timezone names are 3 or 4 long. A similar odd restriction is in the maximum timezone offset, local time in Kiribati is hard to configure in VM, East 14:00 and officially called LINT. Though there are probably not that many z's installed there. > The logic in z/VM does not have the leap seconds table built-in, so if you > want the right local time then someone must have compensated for the leap > seconds (either by hardware clock UTC or LPAR offset to UTC-TA1). > > Rob > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu <javascript:;> 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/ > -- Ronald van der Laan -- 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: FTP to Linux
http://wiki.linuxvm.org/ > > > > > > - > > > > The information contained in this e-mail, including any attachment(s), is > > intended solely for use by the named addressee(s). If you are not the > > intended recipient, or a person designated as responsible for delivering > > such messages to the intended recipient, you are not authorized to > > disclose, copy, distribute or retain this message, in whole or in part, > > without written authorization from PSEG. This e-mail may contain > > proprietary, confidential or privileged information. If you have received > > this message in error, please notify the sender immediately. This notice > is > > included in all e-mail messages leaving PSEG. Thank you for your > > cooperation. > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu <javascript:;> 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 <javascript:;> 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/ > -- Ronald van der Laan -- 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: SLES12 Question
Michael, The message says it all. There is no matching RACF profile for your minidisk, so RACF returns "defer" to CP and CP is configured to fail the request when RACF doesn't know. >From a RACF special Id, issue: RAC RDEFINE VMMDISK SLES12SP.201 OWNER(SLES12SP) RAC PERMIT SLES12SP.201 CLASS(VMMDISK) RESET ID(SLES12SP) ACCESS(ALTER) Or of course a different owner or access level when dictated in your environment. Note that you would normally configure DirMaint to automatically create/delete the RACF profiles. Ronald. Op vrijdag 4 december 2015 heeft Michael Weiner <mwei...@infinite-blue.com> het volgende geschreven: > Hi all, > > I am trying to link a disk which I added to the profile of my guest and it > doesn't seem to be liking something and I can bring my device online. > > sles12:~ # vmcp link '* 201 201 rr' > RPIMGR031E RESOURCE SLES12SP.201 SPECIFIED BY LINK COMMAND NOT FOUND > sles12: ~ # chccwdev -e 201 > Device 0.0.0201 not found > > Any suggestions? I am scratching my head on this as I can't see why that > would happen. > > Have a good weekend! > > -- > Michael Weiner > Systems Admin > Infinity Systems Software, Inc. > One Penn Plaza Suite 2010 > New York, NY 10119 > o: (646) 405-9300 > c: (845) 641-0517 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu <javascript:;> 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/ > -- Ronald van der Laan -- 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:
Cameron, Did you try: cp file.name "//'MVS_data_set(member)'" So double quotes around the whole filename and single quotes around the dsn? -- Ronald van der Laan -- 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: Using OSA port 1 in LPAR
Martha,
Just configure a second eth device on another triplet on the same chpid.
Then in the udev rule, you find the portno parameter.
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.", ATTR{portno}="1"
--
Ronald van der Laan
--
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: openssh ssh-ldap-wrapper missing for SLES 11 SP4
Mark, openssh-helpers is what I am looking for. But as I wrote, I can't find it. I do see: openssh openssh-fips And from another package: openssh-askpass openssh-askpass-gnome openssh-fips But I can not find the following two subpackages: openssh-cavs openssh-helpers I do not care about openssh-cavs, but I need openssh-helpers. So can you tell me which binary repository I need to use? Op maandag 27 juli 2015 heeft Mark Post mp...@suse.com het volgende geschreven: On 7/27/2015 at 01:55 PM, Ronald van der Laan nl50...@gmail.com javascript:; wrote: With SLES11 SP3, we used the /usr/lib64/ssh/ssh-ldap-wrapper that was part of the openssh package, but with SP4, the LDAP integration part seems to have been split off into openssh-helpers. I only cannot find the package among the base packages, nor among the sdk ones. Has it somehow dropped of the packaging list or I am looking in the wrong repositories? Look for the openssh-helpers package. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu javascript:; 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/ -- Ronald van der Laan -- 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: openssh ssh-ldap-wrapper missing for SLES 11 SP4
Mark, Thanks, I'll open a ticket... Op dinsdag 28 juli 2015 heeft Mark Post mp...@suse.com het volgende geschreven: On 7/28/2015 at 10:48 AM, Ronald van der Laan nl50...@gmail.com javascript:; wrote: But I can not find the following two subpackages: openssh-cavs openssh-helpers I do not care about openssh-cavs, but I need openssh-helpers. So can you tell me which binary repository I need to use? It's possible that they were not added to the list of packages that wind up on the media. I recommend you open up a bug with your service provider to get that fixed. The packages do exist in the build service, so they should be able to get you a copy of the current package while they work on the underlying problem. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu javascript:; 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/ -- Ronald van der Laan -- 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/
openssh ssh-ldap-wrapper missing for SLES 11 SP4
With SLES11 SP3, we used the /usr/lib64/ssh/ssh-ldap-wrapper that was part of the openssh package, but with SP4, the LDAP integration part seems to have been split off into openssh-helpers. I only cannot find the package among the base packages, nor among the sdk ones. Has it somehow dropped of the packaging list or I am looking in the wrong repositories? -- Ronald van der Laan -- 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: Creating an accessible disk
Cameron, I'ld never thought I would once say this, but if your students need simultanious write access to a CMS formatted disk (MW link), then ISPF is the way to synchronise the various users and allows updating multiple files on the same disk. (Given that you work on only a single lpar, so that ISPVM can talk to all users of the disk). If you have the option, I would advise to use SFS, much easier, file level control and works across lpars, both in an SSI cluster and/or via APPC/VM connections. For multiple write access, you grant ALTER access in RACF. For a single writer/multiple reader solution, you grant CONTROL access. All that only need to read will need READ access. -- Ronald van der Laan -- 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: Expanding CMS Mini Disk - DDR or Copyfile?
Joe, If you got DFSMS installed, the DFSMS COPY command followed by a CMS format recomp, is a very nice and fast option to copy one minidisk to a new fresh (unformatted) minidisk. More convinient is of course to use a directory manager... Ronald van der Laan. -- Ronald van der Laan -- 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: sles 12
Alan, Are both the z10 and z196 part of a single SSI cluster? If so, and you have no domains specified, even the z196 may report to be a z10 so that you can do a vmrelocate from z196 to z10. -- Ronald van der Laan -- 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: Need an Easy way to Identify whether on 1st or 2nd Level System
Robert, You could use the STATUS command in the SYSTEM CONFIG to change the usual CP RUNNING, CP READ, etc into something else. We once had messages like CP CRAWLING and so on a very slow test lpar Ronald van der Laan Op donderdag 10 april 2014 heeft Hobbs, Robert robert.ho...@fmr.com het volgende geschreven: I need to be able to easily identify whether I am running on my 1st level or 2nd level z/VM system. My preference is for an eye-catcher rather than a command or exec. My 1st level system is z/VM 5.4 and the 2nd level system is z/VM 6.3 I have been running my 2nd level system with a different name, but am getting near acceptance test time and according to a document IBM provided there are approx. 19 steps that need to be followed to rename the z/VM 6.3 to the proper production system name, not something I want to do doing the window I have to available to test my system. Robert Hobbs -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu javascript:; 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/ -- Ronald van der Laan -- 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: RHEL 6.3 DASD configuration
Larry, You should use the linkmode M in the Linux guests CP directory to prevent yourself from that problem. Using M instead of MR, you will not get the minidisk linked when someone else linked the disk in write mode. On Friday, 22 February 2013, Davis, Larry (National VM Capability) wrote: Thanks I found my gun I had the disks linked RW by another ID and the whole in my foot is much better now Larry Davis, VM Capability -Original Message- From: Peter Oberparleiter [mailto:ober...@linux.vnet.ibm.comhttps://mail.google.com/mail/mu/mp/168/ ] Sent: Friday, February 22, 2013 4:00 AM To: Linux on 390 Port Cc: Davis, Larry (National VM Capability) Subject: Re: RHEL 6.3 DASD configuration On 21.02.2013 15:57, Davis, Larry (National VM Capability) wrote: I finally got the Graphical installer working using X but now when I try to Install Linux on my DASD I end up with DASD accessed R/O when it was initially all R/W. No Matter what option I use I always end up with this error. Just prior to connecting to the new Linux to perform the install all DASD looks like this Activated DASDs: 0.0.0150(ECKD) dasdb : active, blocksize: 4096, 54000 blocks, 210 MB 0.0.0151(ECKD) dasdc : active, blocksize: 4096, 1746000 blocks, 6820 MB 0.0.0160(FBA ) dasdd : active, blocksize: 512, 524288 blocks, 256 MB 0.0.0161(FBA ) dasde : active, blocksize: 512, 1048576 blocks, 512 MB Initial configuration completed. After I do the basic installation steps and create a custom layout /boot on 150 / on 151 Swapon 160 Swapon 161 In the end I always get an error that a device is R/O and the process can't continue /dev/dasdx is marked as R/O From the available output it is not clear if 0150 and 0151 where formatted with the CDL format (dasdfmt with default options or -d ldl). Please note that the use of partitions is mandatory for CDL formatted DASDs (/dev/dasdx1 instead of /dev/dasdx). By not using a partition, the filesystem on the DASD will get corrupted, which can also result in it being re-mounted read-only. Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on System z Development - IBM Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.eduhttps://mail.google.com/mail/mu/mp/168/ 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/ -- Ronald van der Laan -- 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: VM6.2 Network issue
Ruddy, I see no devices listed on the port group VSIGRP and LACP active. Please check your port group with: QUERY PORT GROUP VSIGRP And add the missing devices with: SET PORT GROUP VSIGRP JOIN n.Pn Note that with LACP active, you cannot share OSA ports across lpars. In other words, each OSA port (not device address!) that is used for link aggregation is dedicated to a single vswitch. Ronald van der Laan -- 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: Linux ZVM command help ....
Or without root access: $ grep 'VM00 Name:' /proc/sysinfo Ronald van der Laan -- 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: Adding an additional network to z/VM and zLinux
Daniel, Did you define two virtual NICs (eth0 and eth1) to the same VSWITCH? I noticed that eth0 and eth1 are in the same subnet. So perhaps you have a routing table problem. Can you also issue a vmcp q nic details to show the connections from NIC to the VSWITCH(es)? Ronald van der Laan -- 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: DASD assignment different between SLES10 and SLES11
Peter, Have you tried: parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 dasd=0.0.0150-0.0.015f TERM=dumb Ronald van der Laan -- 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: Archive libraries in SlES11
Roger, Have you tried installing: libopenssl-devel pcre-devel zlib-devel Ronald van der Laan -- 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: DIAG
Gene, Shouldn't that be: MODULE=dasd_diag_mod Ronald van der Laan -- 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: vdisk
David, Please be aware that if you do not have an external security manager in your z/VM system, CP will provide access to other minidisks based on the minidisk passwords in the CP directory. When you define all for instance all your Linux swap disks as: MDISK 203 FB-512 V-DISK 409600 MR READ WRITE MULTIPLE That means that anyone who knows the passwords (and that is now the whole community), can, when they have access to your system, do a CP LINK other_userid 0203 MW PASS=MULTIPLE and get the ability to read/write the swap disk of other_userid. So I would advise to only add minidisk passwords where and when you need them. For instance the ALL as read password allows any user-id to link the disk in read mode. A second word of caution, Linux does not like to get a disk in read/only mode when it does not expect so. The linkmode MR gives you the disk in read/write mode, unless someone has the disk already linked in write mode, you get the disk then linked in read/only mode. The linkmode you want for Linux guests is M. That links you the disk in read/write mode, unless someone already has the disk linked read/write, in that case the link fails, something that even Linux user-land tools notice. Ronald van der Laan -- 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: APAR VM64814 STP_TZ
Steve, Why don't you define: FEATures ENABle STP_Timestamping DISable STP_TIMEZone Ronald van der Laan -- 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: Server rebooting after doing a CP Q DA from the console
James, As Alan said, someone is intercepting in Linux your CP command. The vmcp q term does not generate so much output that it does not fit in the standard vmcp buffer, so you should be fairly safe issueing that command. An other option is to issue from an other authorized VM user (for instance MAINT) the command FOR linux_guest_id CMD QUERY TERMINAL For what it is worth, in my days as an operator (a long long time ago), we intercepted the D T command, sometimes issued by MVS operators to Display Time. Only on VM it was a Dump Terminal, so we were less amused when that got issued under OPERATOR .. Ronald van der Laan -- 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: Anyone have 2 NICs on SLES11 SP1 working ?
Tore, It won't help solving your solution path, but you can also assign each DMGR a different portnumber. When you install them in the same profile, the installer should pick different ports automatically, otherwise you would need to assign them manually. Look for the serverindex.xml files, they contain the port mapping and also the hostname that is used to bind to. Perhaps you can tweak a bit there by defining different hostnames for each of your two ip addresses there too. Ronald van der Laan -- 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: zLinux operating as a zVM guest host
Walter, You'ld want to add SHARE settings for the two guests (test sandbox). If the main machine has two processors and you want the test machine to use up to 25% of a processor, then you need to cap it on 12.5% of the hypervisor's resources.. Please note that a recent apar (november if I remember correctly) was created to fix a problem in respecting the limiting on IFLs.. The following should work in the directory entries... TEST: SHARE ABSOLUTE 12.5% LIMITHARD SANDBOX: SHARE ABSOLUTE 5.0% LIMITHARD Ronald van der Laan -- 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: SPOOL area increase in continuesly.(z/VM 5.4)
Yoon-suk Cho, You should also check the System Definition Files, QUERY SDF Perhaps you have a lot of old segments or large system trace files laying around. Ronald van der Laan -- 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: SLES10 su only id
Ann, I use sudo and locked shared userids. Ronald van der Laan -- 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: How to share files/disk between 2 LPARS
Lee, Maybe a stupid question, but have you compared the minidisk definitions on both Linuxes and checked if all the different layers say R/W ? From each Linux: # vmcp q v address # vmcp q md address location # cat cat /sys/devices/css*/*/0.0.address/readonly Also, I hope your planning to use a shared directory and at least xlink protection between your z/VM systems for the shared volumes. Ronald van der Laan -- 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: How to share files/disk between 2 LPARS
Tore, It may be easier to use a similar, but slightly different approach. Just define a placeholder like: USER CODEDISK NOLOG LINK CODEDISK 0401 0400 R MDISK 0401 . MDISK 0402 . MDISK 0403 . You then start with the code installed on the 401 disk and let users link the 400 disk. If you need an update, copy the 400 to the 402 and update the 402. When satisfied with your updates, modify the link to LINK CODEDISK 0402 0400 R and recycle the other servers. This gives you a stable disk for the Linux servers to work with, and allows you to test or go back very easily. Ronald van der Laan -- 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: How to share files/disk between 2 LPARS
Bernie, First, use CSE (XLINK part) on the VM level, so that VM handles linking (and locking) across the lpars. When the disk is used read-only on all Linux guests, you can just let all the guests link it read only (use link mode R) and do the same as you're doning on a single z/VM system. If you want to write to it to, then you should, just like with the single z/VM system make sure that only one Linux guests writes, and that NO other Linux guests can access the disk at the same time (link mode W). Or, you can use on SLES 10 SP2 the OCFS2 filesystem to make the disk shared write across the Linux systems (link mode MW). Note however, that you do not have Posix locking on OCFS2 with SLES 10 yet, but if you migrate to SLES 11, you can choose between GFS and OCFS2 and get Posix locking, so that for instance the HA functionality of MQSeries 7.0.1 can be used with Linux. Ronald van der Laan -- 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: Windows emulation
Bernie, Your X display (your PC) doesn't normally accept incoming X11 sessions from others than the local host. There are two ways to get a remote system to create a X11 window on your screen: 1) run xhost +*remote_hostname*. Note the + infront of the remote hostname. 2) use ssh to create a tunnel over your session to the remote host, that forwards port 6010+ back to your local X11 port. When you use option 1), anyone on the remote server can open an X11 window on your PC. When you use option 2), ssh uses xauth on your userid at the remote system to register the credentials to use the tunnel. It will also set the DISPLAY variable to the correct port. This makes it easier to use, as the DISPLAY will always point to your PC, no matter what IP address you got today. And, very important, some other user who uses the remote system will not be able to create windows on your screen. My advise would be to use option 2. If you use ssh, then use the option -X (upper case X). If you use PuTTY, then look at Connection - SSH - X11 and select Enable X11 forwarding. Ronald van der Laan -- 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: SWI-PROLOG and OPENJDK
Bruce, Did do you check the packages on the SLES 10 SDK cds? I found most of the documentation code, like latex, docbook and so on there. Ronald van der Laan -- 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: Z/Linux CKD DASD migration from one DASD Subsystem to another
David On Wed, Jan 21, 2009 at 7:42 PM, David Boyes dbo...@sinenomine.net wrote: 3) From an appropriately privileged ID (MAINT, etc): LINK guest 150 150 RR (you don't need/want write access to this volume) LINK guest F150 F150 MR(you're going to overwrite this one, so write) My advise to make absolutely sure there is no problem to copy the data: 3) From an appropriately privileged ID (MAINT, etc): LINK guest 150 150 *R* (you don't need/want write access to this volume) LINK guest F150 F150 *W*(you're going to overwrite this one, so write) The R link prevents linking when someone else has a write link and the W link prevents linking when someone else uses the minidisk. A similar thing goes for a lot of Linux directory entries, linking the Linux minidisks with M makes sure that the guest will only get the disk if there are no write links, without getting the disk in readonly mode as normally used for CMS disks using the MR linkmode. Ronald van der Laan -- 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: Security question and using scp
James,
I normally use a combination of ssh, sudo and tar to copy files with root
authorization from one system to the other:
cd ${sourcedir}
sudo tar -cp ${files} | ssh ${targetsys} sudo tar -C ${targetdir}
-xpv
Ronald van der Laan
--
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: bash shell question
John, Apache comes with rotatelogs that appends a timestamp to the logfile and starts a new logfile after a certain interval. This works without the need to stop and rotate the logfile. daemon args daemon.log daemon args 21 | rotatelogs daemon.log 86400 This will put all output (normal + error) into a file called daemon.log.xxx and start with a new file each day. Change 86400 into 3600 and you'll get your logs per hour. With SuSE the code is in /usr/sbin/rotatelogs and for Apache2 it is called /usr/sbin/rotatelogs2 There is also a man page for more information. Ronald van der Laan -- 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: Layer 3 to Layer 2 on the VSWITCH
Ryan, Yes, add the following line to the /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-* files QETH_LAYER2_SUPPORT=1 and blank out an optional QETH_OPTIONS= parameter if you done things like fake_ll or so. In the z/VM system config, add the keyword ETHERNET to, or replace IP with ETHERNET for your DEFINE VSWITCH statement. Ronald van der Laan -- 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: z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 2
Peter, These kind of things is where a SFS filepool for the user A-disks comes in handy (and then not one of the standard system ones). Just create a new (global) filepool, lets say USERSFS and migrate the user data from minidisk into this filepool. Then define a real CTC from and to your first level system by for instance looping a fiber between two spare FICON or ESCON ports, Then attach one of the CTC sides to your second level system and do an ACTIVATE ISLINK on both first and second level. That will share the resources between first and second level and allow first and second level users to access their files. An alternative to the ISFC (ISLINK) cluster approach would be to install IPGATE first an second level and use IPGATE to export/import the filepool from first to second level. Ronald van der Laan -- 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: Question re communicating with VM guest machine
Andy, That is sure something from the past At the second level z/VM, define and start your virtual reader. Let say 000C is its virtual reader, then SET RDEV 000C TYPE RDR START 000C Now from your userid at first level, create the file you want to submit (I think it must be Fixed 80) and prefix it with the line: USERID 2nd_level_userid Then issue: SPOOL PUN TO 2nd_level_zvm_guest RDR PUN fn ft fm (NOH You should now see the file in the reader of your vm userid at second level. Ronald van der Laan -- 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
IP takeover across lpars fails through a vswitch
I've got 2 z/VM lpars and run a Linux server in each lpar that should be able to service common ip address. Both lpars are connected via double OSA cards to a real switch. VM1 VM2 /==\ /==\ | | | | | /--\ | | /--\ | | | Linux1 | | | | Linux2 | | | \+-/ | | \+-/ | || | || | || | || | | /+-\ | | /+-\ | | | vswitch1 | | | | vswitch2 | | | \--++--/ | | \--++--/ | | || | | || | \=OSA==OSA=/ \=OSA==OSA=/ || || || || || || /--++--\ /--++--\ | switch1 |-| switch2 | \--/ \--/ All IP addresses are in the same subnet and the vswitches are connected to access ports on the switches. Normally Linux1 has the common IP address, but when it becomes unavailable, Linux2 should take over. This process works, when Linux1 can normally terminate, or when it gets logged off and CP cleans up its OSA IP registrations. When it breaks, for instance with a kernel panic, then the Linux1 server retains its registered IP addresses, so Linux2 should forcefully obtain the common IP address. To be sure that that happens, the common IP address is registered in Linux with the qethconf ipa add ip_address command. In the situation, were the take over is forcefully (eg, Linux1 has the IP address still registered), something strange happens. On VM1's vswitch and OSAs, the common IP address remains registered. But on VM2, the vswitch shows the IP address registered, but with a local flag and the console of the vswitch controller shows the familiar Return code E00A from SETIP for IPv4 error, indicating it could not register the IP address to the switch. We are running z/VM 5,2 and the VMLAN level is VM63989. The OSAs are OSA-Direct Express Gigabit Ethernet types and the vswitches are defined with only the RDEV parameters. Does anyone know how to make the IP take over being forwarded to the real switches and then to the other vswitch? Ronald van der Laan -- 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: Single user mode and root password
Rob, Yes, by replacing the /sbin/sulogin by a script that just calls /bin/bash, you prevent the password check for both the fsck and single user modes. Ronald van der Laan -- 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: route table manipulation
Anna, What Linux distribution and version are you using? Ronald van der Laan -- 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: AW: route table manipulation
Anna, Sorry, I have no RHEL 4 to check against. Ronald van der Laan -- 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 1 terabyte disk assignments
Eric, Please see http://www.novell.com/documentation/suse91/suselinux-adminguide/html/apas04.html Ronald van der Laan -- 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: speed of an interface
Eric, You're displaying virtual devices connected to a virtualized network. I've tried it again after attaching some real OSA devices. When displaying a GbE card (1Gbs): cat /proc/qeth devnos (hex) CHPID device cardtype port chksum prio-q'ing rtr fsz C cnt -- --- -- -- -- -- -- --- --- - --- D000/D001/D002 xB2 eth0 OSD_1000 0 no always_q_2 no 64k 128 When displaying a 1000BaseT card (in 1Gbs mode): cat /proc/qeth devnos (hex) CHPID device cardtype port chksum prio-q'ing rtr fsz C cnt -- --- -- -- -- -- -- --- --- - --- C000/C001/C002 xF1 eth0 OSD_1000 0 no always_q_2 no 64k 128 Ronald van der Laan -- 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: zLinux VIPA setup.
Jim, Your vipa should be registered to your NIC to be able to receive packets (unless you set up a layer 2 vswitch), you can check that using: $ hcp q nic details( being the address of your eth0 or eth1 virtual NIC) If it does not show your vipa, you can set it manually using: $ qethconf vipa add xxx.xxx.xxx.xxx eth0 $ qethconf vipa add xxx.xxx.xxx.xxx eth1 Ronald van der Laan -- 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
A question about using a NIC in promiscuous mode
Hi, I'm running z/VM 5.2 and RACF/VM with APAR VM63750 installed. My Linux guest has CONTROL access to the vswitch resource. When I try to set the NIC into promiscous mode, I get a positive reply, but checking the NIC says something differently. lnxnew03:/ # hcp set nic d002 promisc hcp set nic d002 promisc Promiscuous Mode has been enabled for device D002 lnxnew03:/ # hcp q nic d000 details hcp q nic d000 details Adapter D000 Type: QDIO Name: LNXNEW03Devices: 3 Port 0 MAC: 02-E0-12-06-82-03 VSWITCH: SYSTEM L2HA RX Packets: 20 Discarded: 0 Errors: 0 TX Packets: 38 Discarded: 0 Errors: 0 RX Bytes: 2830 TX Bytes: 2859 Connection Name: HALLOLE State: Session Established Device: D000 Unit: 000 Role: CTL-READ Device: D001 Unit: 001 Role: CTL-WRITE Device: D002 Unit: 002 Role: DATA Options: Broadcast Multicast IPv6 IPv4 VLAN Promiscuous_Denied Unicast IP Addresses: 9.149.68.203 MAC: 02-E0-12-06-82-03 FE80::2E0:1200:106:8203 MAC: 02-E0-12-06-82-03 Local Multicast IP Addresses: 224.0.0.1MAC: 01-00-5E-00-00-01 FF02::1 MAC: 33-33-00-00-00-01 FF02::1:FF06:8203MAC: 33-33-FF-06-82-03 Local And from the RAC RL VMLAN SYSTEM.L2HA: CLASS NAME - VMLAN SYSTEM.L2HA USER ACCESS ACCESS COUNT -- -- - LNXNEW03 CONTROL 00 Q VMLAN VMLAN maintenance level: Latest Service: VM63784 VMLAN MAC address assignment: MACADDR Prefix: 02E012 MACIDRANGE SYSTEM: 01-FF USER: 00-00 VMLAN default accounting status: SYSTEM Accounting: OFF USER Accounting: OFF VMLAN general activity: PERSISTENT Limit: INFINITE Current: 1 TRANSIENT Limit: INFINITE Current: 0 Q VSWITCH VSWITCH SYSTEM L2HA Type: VSWITCH Connected: 35 Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware State: Ready IPTimeout: 5 QueueStorage: 8 Portname: UNASSIGNED RDEV: 0030 Controller: VSWCTL2 VDEV: 0030 Portname: UNASSIGNED RDEV: 0040 Controller: NONE I'm running on a z990 processor and want to check the traffic on the vswitch. Does someone know what I'm doing wrong? Ronald van der Laan -- 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: Mounting ext3 disk read-only as ext2
Michael, Please check how the dasd driver sees the dasdd disk ( /proc/dasd/devices ), read/only or read/writable. If it says rw, then the journalling code seems to want to write to the disk, even if you say ro or ext2. If it says rw, then you can issue blockdev --setro /dev/dasdd before you mount the disk and your dasd error messages will disappear. Ronald van der Laan -- 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: Trying to use ldapsearch command from linux to query RACFLDAP
James, On 3/22/06, James Melin [EMAIL PROTECTED] wrote: When I try that same command on my linux box: abinodji:~ # ldapsearch -h hawk -p 389 -s base -b objectclass =* subschemasubentry SASL/EXTERNAL authentication started ldap_sasl_interactive_bind_s: Unknown authentication method (-6) additional info: SASL(-4): no mechanism available: abinodji:~ # You might try adding the -x option to your ldap query to go for simple authentication (or none) instead of SASL. # ldapsearch -x -h hawk -p 389 -s base -b objectclass =* subschemasubentry Ronald van der Laan -- 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: IBM HTTP Question/Problem
Jim, Please check /opt/IBM/IHS/bin/adminctl and /opt/IBM/IHS/conf/admin.conf Ronald van der Laan -- 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: forgotten command
Mike, cat /etc/SuSE-release Ronald van der Laan -- 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: How to make Linux re-read the directory of a read-only file system?
On 10/26/05, James Melin [EMAIL PROTECTED] wrote: We are using a procedure developed by Steve Wehr of IBM where you have a master /opt/IBM/WebSphere directory that is then shared read-only with other Linux guests. Apparently there has been little latency in the directory structure being refreshed on the read-only systems after a change has been made on the owning r/w system. This has stopped happening, and I'm wondering how you make Linux refresh the directory of the r/o disk? James, You should use multiple disks and keep 1 stable version on each inuse disk.. So do not update a minidisk that is readonly used by one or more other servers, but copy the data to a new disk, update that disk and let all others swap over to that disk. 1) copy the data from your active disk to a new disk. (If you use disks of the same size, you can use the z/VM FLASHCOPY or DDR commands to mirror the current to the new disk) 2) link the new disk into your build server at the /opt/IBM/WebSphere spot. 3) run the updateinstaller to load a new fix or refresh pack, or update the files that need updating. 4) stop and logoff the build server. 5a) stop the runtime WebSphere servers. 5b) umount and detach the old shared WebSphere minidisk. 5c) link and mount the new shared WebSphere minidisk at /opt/IBM/WebSphere. 5d) when applicable, manually run the upgrade jacl scripts. 5e) restart the WebSphere servers. When all servers released the original disk and you no longer want to be able to return to the older disk, you can safely reuse it for the next update. Ronald van der Laan -- 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: z/VM Monitor Stream patch - any one using this?
On 6/3/05, James Melin [EMAIL PROTECTED] wrote: except when I run those commands some of the structures in /procsys/appldata are not there to manipulate: /proc/sys/appldata/mem: No such file or directory /proc/sys/appldata/os: No such file or directory /proc/sys/appldata/net_sum: No such file or directory Did you issue modprobes to load the kernel modules? $ modprobe appldata_os $ modprobe appldata_mem $ modprobe appldata_net_sum Ronald van der Laan -- 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: Restrict user to only one active login
You could do something in /etc/ssh/sshrc, as that exit is called by sshd during login and before the user gets control. logons=`who | grep ^$USER | wc -l` if [ $logons -gt 1 ]; then fi Ronald van der Laan -- 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: LDAP + SSL Authentication
Cameron wrote on 11-01-2005 17:53:41: Greetings, I am testing some LDAP + SSL Authentication. We have an LDAP server running on z/OS and it is setup with a single certificate. I want to setup a Linux Guest to authenticate with this certificate, how do you import that certificate in Linux? Does anyone have experience with or know how to do this? -Cameron Put the certifate or the certificate of the CA (world readable) on the Linux system and add the following line to your system ldap.conf file: TLS_CACERT certicate filename Ronald van der Laan. -- 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: Problem solving z/VM and Linux
Michael Coffin wrote on 29-12-2004 17:43:44: OPERATOR should be spooling it's console, if not put the following in it's PROFILE EXEC: 'CP SPOOL CONSOLE START TO * CLASS T' Please make that: 'CP SPOOL CONSOLE START TO * CLASS T EOF' The EOF option will close the current log and start a new console log every 5 records, so you will actually be able to read the log when you need it... Ronald van der Laan -- 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 installation problem - again
Linux on 390 Port [EMAIL PROTECTED] wrote on 22-10-2004 13:12:33: Linux on 390 Port [EMAIL PROTECTED] rta 2004.10.22 09:47:25 idpontban: It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. 1000 Base-T is not Gigabit Ethernet??? 10 Base-T = Ethernet (eth) 100 Base-T = Fast Ethernet (FEth) 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... 1000Base-T uses electrons through copper to connect to 10Base-T, 100Base-T or 1000Base-T GbE uses photons through fiber to connect to a 1Gbs LAN. Ronald van der Laan -- 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: VDSK, Swapgen et al
Jim, Please check if your initrd contains the dasd_diag_mod kernel module. You also seem to lack the dasd_fba_mod module, otherwise it would have loaded instead. Please try: insmod dasd_diag_mod Ronald van der Laan -- 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: New version of SWAPGEN available
Dave Jones wrote on 25-06-2004 15:48:32: K. I've just gotten to the point where our VM guy is going to finally let me USE vdisk for swap (took much convincing) and he assigned that device at dev 300. swapgen not withstanding, I've been unable to get linux to recognize the device. I've tried adding it using an add command echoed to /proc/dasd/devices and I get 0203(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 216000 blocks, 843 MB 0300(none) at ( 94: 16) is dasde : unknown I wanted to resolve THIS part before I tried to do something slick with swapgen. Perhaps I am being premature? Dave, Please check if you've got the dasd_diag_mod and/or dasd_fba_mod kernel module loaded. The dasd_diag_mod module allows you fast access to CMS reserved disks via the diagnose driver, or the dasd_fba_mod module lets you use fba type devices like the dasd_eckd_mod module lets you talk to 3390s. Ronald van der Laan -- 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: GLIBC problem : Newbie
Srinivas, My version of compat does not require GLIBC_2.3. # rpm -qf /usr/lib/libstdc++-libc6.2-2.so.3 compat-2002.8.15-20 # rpm -q --requires compat ld.so.1 libc.so.6 libm.so.6 libstdc++-libc6.2-2.so.3 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libm.so.6(GLIBC_2.0) libm.so.6(GLIBC_2.1) rpmlib(PayloadIsBzip2) = 3.0.5-1 And a quick scan on the SuSE SLES-8 SP3 (s390 arch) packages does not give me a package that provides (or requires) GLIBC_2.3. Ronald -- 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: VSWITCH router
Hi, Probably a stupid remark, but should you not define both VSWITCHes with the PRIROUTER function? VSWITCH1 to be able to route to your destination, and VSWITCH2 to route the answer back to the originator? Ronald van der Laan -- 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: VSWITCH Connections
Steve, My understanding is that the address triplet must be defined as qethN,even address,odd address,remaining address. cat /etc/chandev.conf noauto qeth0,0x3909,0x390A,0x390B,0,0 add_parms,0x10,0x3909,0x390B,portname:VSI3000 qeth1,0x3009,0x300A,0x300B,0,0 add_parms,0x10,0x3009,0x300B,portname:HSI3000 becomes: » cat /etc/chandev.conf » noauto » qeth0,0x390A,0x390B,0x3909,0,0 » add_parms,0x10,0x3909,0x390B,portname:VSI3000 » qeth1,0x300A,0x300B,0x3009,0,0 » add_parms,0x10,0x3009,0x300B,portname:HSI3000 Ronald van der Laan -- 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: dasd mount
Sopia, Please try: mount /dev/dasdn1 /mnt -t reiserfs -o rw This mounts the first partition on the disk that contains your filesystem. Ronald van der Laan
Re: dasd mount
Sophia, The easiest way is: $ umount /mnt $ echo -n set 800 off /proc/dasd/devices and when available: $ hcp detach 800 or from the VM console: #CP DETACH 800 Ronald
Re: Question: setting up SuSE SLES7 to automatically be logged on as root during boot up .....
Terry, Rob wrote: On Wed, 2003-10-29 at 19:48, Terry Spaulding wrote: Linux List: Can someone point me to the doc on how to setup SuSE SLES7 to come up and already be logged on as root user ? Change the sulogin in /etc/inittab into /bin/bash Rob Do the folllowing in /etc/inittab: ~~:S:respawn:/bin/sh 1:1235:respawn:/bin/sh --login ca::ctrlaltdel:/sbin/shutdown -h now The last line shuts down the system (SLES 7 and SLES 8) on a SIGNAL SHUTDOWN. Please note that /proc/sys/kernel/ctrl-alt-del must be 0, otherwise a SIGNAL SHUTDOWN will do reboot. To check if your kernel level reacts on a SIGNAL SHUTDOWN, issue a QUERY SIGNALS command from a class B user. Ronald van der Laan.
Re: hw addr
Marian Gasparovic [EMAIL PROTECTED] wrote: And another question, it is pure VM - they say in redbook, I need APAR VM63172 installed for DHCP broadcast. How do I find out if it is installed ? I never worked with VMSES. Marian, Please logon to user MAINT. Then type when using minidisks: - VMFINFO ZVM CP ( SETUP or when using SFS - VMFINFO ZVM CPSFS ( SETUP Then select PTFs/APARs and follow the panels. Ronald van der Laan
Attempting to use a VM Guest LAN
Thomas wrote: cat /etc/chandev.conf noauto add_parms,0x10,0xf00,0xf02,portname=VMLAN01 hsi0,0xf00,0xf01,0xf02,0,0 Try: (replace the '=' with ':') cat /etc/chandev.conf noauto add_parms,0x10,0xf00,0xf02,portname:VMLAN01 hsi0,0xf00,0xf01,0xf02,0,0 Good luck, Ronald van der Laan
VM PTFs
Andy Robertson wrote: We run LINUX under z/VM 1.4 I guess you're running z/VM 4.1 I have a request to determine if a PTF is on the VM system, and if it is not on to put it on I am sorry if this is obvious, but is there a quick easy way to do this? Logon to MAINT and run VMFINFO on your VM system Then select the product you want to investigate (for instance ZVM) Select the part you want to investigate (for instance CP or CPSFS) Change Setup... NO into YES and hit enter. Select PTFs/APARs Put the cursor on the PTF number input field and hit the PF1 key You can now select the ptf you want to look into If not what Manual do I RTF? See http://www.vm.ibm.com/pubs/ and look for the VM/SES manual and the Program Directories in the z/VM 4.1 section. I am running the VM system with about a tenth of my time, the rest of it is spent on a lot of z/OS work, and I would really appreciate any pointers. Ronald van der Laan * Notice: This email is confidential and may contain copyright material of the John Lewis Partnership. If you are not the intended recipient, please notify us immediately and delete all copies of this message. (Please note that it is your responsibility to scan this message for viruses). * John Lewis plc Registered in England 233462 Registered office 171 Victoria Street London SW1E 5NN Websites: http://www.johnlewis.com and http://www.waitrose.com
Re: Kernel patch to add VM IPL PARM support
Leland Lucius wrote: A bigger question might be why must vmpoff be in upper case?? Well, I reckon cause the book says so, but you're right about what you say below. The VMPOFF and VMPHALT processing could convert the command to uppercase since it is a requirement. How about a nice 1 liner to rememdy that? Please don't! That way you can no longer pass lowercase to Diagnose8. I say Leland's translate-to-lower should stay! VMPOFF processing could be a lot smarter. And this is getting very messy. Ya know, I have to agree with you there. I didn't realize (hadn't tried it yet) that you had to use DIAG to get the thing to retain mixed case. So, it really boils down to: The Majority Rules Since most Linux kernel parmaeters are expected to be in lowercase, I'll keep the conversion to lower in the patch and not try to get all fancy and everything. What I did (for the patch we're trying to get incorporated by our Boeblingen friends) is, translating EBCDIC to ASCII with reversed case. That way you get the benefit of having your (by default) uppercased parm string passed lowercase to Linux, and you keep the option open for passing uppercased characters to the kernel. So you would do something like: /* */ Call Diag 8, 'CP IPL LINUX PARM VMPOFF=ipl cms MEM=64M' Ronald van der Laan
Re: Similar Command....
Lemarr T. Ketchens wrote: What's the equivalent to the chkconfig (under RedHat) on SuSe? Lemarr, try the insserv command. Ronald van der Laan
Re: VG to Mdisk mapping ?
Phil, Try a 'cat /proc/dasd/devices' to see the device_name to mdisk_address mapping. For further mapping info of how are those logical volumes mapped onto your physical volumes, try 'pvdata -av /dev/dasdb1'. Ronald van der Laan
Re: HOW define another OSA Interface ?
Harald, Please look into the /etc/modules.conf file and check if you have got the following aliases defined: alias eth0qeth alias eth1qeth alias eth2qeth alias eth3qeth Ronald van der Laan
Re: IUCV between Linux systems
Thomas, Yes. In /etc/modules.conf you define: alias iucv0 netiucv alias iucv1 netiucv alias iucv2 netiucv ... alias iucvN netiucv options netiucv iucv=userid0:userid1:userid2:...:useridN And in the CP directory you can define 'IUCV ALLOW' in all your linux servers to allow every other vm userid on your system to connect to this linux server, or you define a list of authorized servers that may connect to your server (if you want to be more restrictive): IUCV userid0 IUCV userid1 IUCV userid2 ... IUCV useridN And of course you'll have to add an 'IUCV your_linux_userid' to the directories of userid0 .. useridN to authorize it the other way around too. You normally would not give 'IUCV ANY'. That authorisation will give your linux server the ability to make an iucv connection to every other userid on your system. Though if you have a central router that connects all other linux servers to the outside world, it might be convenient to give that route both 'IUCV ALLOW' and 'IUCV ANY' and leave the other directories without an IUCV statement. Ronald van der Laan
Re: IUCV and RH7.2
Huerlimann Heinz wrote: I would like to use this situation to get into linux diagnosing and debugging and hopefully fix the problem. Unfortunately I don't know how to start. Can anyone tell me more about methods for achieving this task. In the /usr/src/linux/drivers/s390/net directory, you'll find two files: iucv.c and netiucv.c - iucv.c is the kernel part that provides the iucv api's. - netiucv.c is the tcp/ip iucv driver. Both files have a line '#undef DEBUG' that you can replace by '#define DEBUG'. Then rebuild the kernel and you'll get lots of debug messages. Ronald van der Laan
Re: netiucv question
Erwann wrote: I can't figure out why i can't use more than one iucv interface with the precompiled 2.4.9 debian kernel image (unstable) and also after recompilation of a 2.4.16 kernel insmod: /lib/modules/2.4.16/kernel/drivers/s390/net/netiucv.o: too many values for iucv (max 1) This is something in the Linux 2.4 parameter parsing for kernel modules that causes the parser to see the comma as a delimiter between module parameters. And as the netiucv module only wants 1 parameter, you get the error message. (Note that the 'iucv' refers to the variable name within netiucv.c that receives the parameter string and not the iucv.c part of the kernel). If you use a colon instead of a comma between the userids, it works fine. So from the command line: insmod netiucv iucv=userid0:userid1 or in /etc/modules.conf alias iucv0 netiucv alias iucv1 netiucv optionnetiucv iucv=userid0:userid1 You should be able to define up to 10 userids that way. Ronald van der Laan
Re: Installing DB2 Fixpak
Thomas wrote:
# db2_install
Specify one or more of the following keywords, \nseparated by spaces, to
install
DB2 products.\n
No license packages available on CD
DB2.RCAE - Run-Time Client
Enter help to redisplay product names, enter quit to exit.
***
DB2.RCAE
Installing ./db2cliv71-7.1.0-55.s390.rpm ...
file /usr/IBMdb2/V7.1/Readme/en_US/Release.Notes from install of
db2cliv71-7.1.0-55 conflicts with file from package db2cliv71-7.1.0-40
and so on.
Do I have to deinstall the GA level first? Where is the trick?
I noticed that the db2_install code does a 'rpm -ivh' and thus causes
problems with upgrades.
You can either run db2_deinstall from the old version, and then do a
db2_install, or
**UNTESTED**
update db2_install in line :248 and change 'rpm -ivh ${fullrpmname?}' into
'rpm -Uvh ${fullrpmname?}'
**END UNTESTED**
Ronald van der Laan
