VM VSE linux/390 Employment Web Page
Greetings; (Posted to VMESA-L and VSE-L and LINUX-390) - - Now in its sixth year! - - Includes VSE and linux/390! I have set up a public service web page at http://www.eskimo.com/~wix/vm/ for posting positions available and wanted for VM, VSE and linux/390. Please visit the web page for more information and feel free to send me any info you would like to have posted. Please make VM or VSE or linux/390 the first word in the subject. Questions and comments welcome! (Text or html OK. No java, gifs, .DOC, etc. NO RESUMES or CVs!) Please check the web pages for examples before sending your ad! Good luck, Dennis VM VSE linux/390 Positions Available last updated Dec 14. VM VSE linux/390 Positions Wanted last updated Dec 14. 31340 12/18/03 00:05:01
Interruptible Instruction
Glen, I understand the MVCL now. I also understand some of the set up that was done in CP years ago. Thank you, Paul Hanrahan
Samba and tdb locking on s/390
I've been seeing a lot of tdb problems during our SuSE trial when it comes to Samba. Over time a tdb or two inevitably becomes corrupt, sometimes in just an hour or two. I ran tdbtorture, a tool that comes with the samba source, and got errors left and right. On intel, the tdbtorture suite just runs for a while and prints OK. Well, on s/390 immediately there are a plethora of messages like: tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable I looked in tdb/spinlock.c and saw a bunch of architecture-specific #ifdefs, but nothing S/390ish. Should there be one? ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Problem booting SLES 8 for Install
In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems
Re: Problem booting SLES 8 for Install
Eric, post us your SLES8 exec, you have forgotten a quote or something similar... Regards/Cordialement/Gruss/Saludos John Cassidy Dipl.-Ing (Informatique) S390 zSeries Systems Engineering Schleswigstr. 7 D-51065 Cologne EU Tel: +49 (0) 221 61 60 777 . GSM: +49 (0) 177 799 58 56 E-Mail: [EMAIL PROTECTED] HTTP : www.jdcassidy.net -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Eric Sammons Sent: 18 December 2003 14:41 To: [EMAIL PROTECTED] Subject: Problem booting SLES 8 for Install In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems
Re: Problem booting SLES 8 for Install
I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
Re: Problem booting SLES 8 for Install
Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
Re: Problem booting SLES 8 for Install
My FTP process follows: ftp server binary locsite fix 80 get vmrdr.ikr sles8.image get initrd sles8.initrd asc get parmfile sles8.parm quit I have just downloaded all the files again and still get errors when trying to boot for install. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:00 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
New z900 and SuSE Linux partitions
We are getting a new z900 and would like the three linux partitions running on the X47 partitions to come up and run there. One of the SuSe Linux partitions is running on an OSA Express Card port 1. The card cannot be moved to the new machine. Is there a way to change the SuSe Linux to use port 0 by updating some config file? I believe on the new machine, the address of the OSA card can be set the same as the address on the X47 and if SuSe was set to use port 0 it should work without a regen/rebuild of Linux and all that is running. When I installed SuSe Linux on the Network setup I set the Network device address: to the correct address, and then Relative port was set to 1, because at the time something else was using port 0. So I am hoping this is in a file somewere and can be changed and port 0 will be used without problems. Can anyone give me advice? Ila Z. Miller ___ ___ Health Care Information Systems University of Iowa Hospitals Clinics [EMAIL PROTECTED] Phone: 319.356.0067 FAX: 319.356.3521 Notice: This e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
Re: Problem booting SLES 8 for Install
OK, you should do the suggestion as a previous post and post your exec that punches the files to the reader. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:12 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install My FTP process follows: ftp server binary locsite fix 80 get vmrdr.ikr sles8.image get initrd sles8.initrd asc get parmfile sles8.parm quit I have just downloaded all the files again and still get errors when trying to boot for install. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:00 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
Re: Anyone using OpenLDAP with SLES8? Question with Passwords
You could try using the pam_unix2.so module instead of pam_ldap.so. pam_unux2.so will call pam_ldap.so under the covers if you modify /etc/security/pam_unix2.conf. Hope it helps. sal
Re: Problem booting SLES 8 for Install
OK here is my sles8 exec file: *** top of File *** /**/ 'close rdr' 'spool rdr all' 'spool punch * rdr' 'punch sles8 image a (noh' 'punch sles8 parm a (noh' 'punch sles8 initrd a (noh' 'change rdr all keep nohold' 'ipl 00c clear' *** End of File *** One other thing I should note, this is my first time using this process under VM4.4. Previously and as I documented the process for our office, the VM version was 4.3. Has anything changed? Also, I notice that in filelist the files are listed as follows: SLES8 EXECA1 V 28 9 1 12/18/03 . . . Above you will notice that I punch with an 'a', should I replace the 'a' with an 'a1' as found in filelist? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:25 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install OK, you should do the suggestion as a previous post and post your exec that punches the files to the reader. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:12 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install My FTP process follows: ftp server binary locsite fix 80 get vmrdr.ikr sles8.image get initrd sles8.initrd asc get parmfile sles8.parm quit I have just downloaded all the files again and still get errors when trying to boot for install. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:00 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
Re: Anyone using OpenLDAP with SLES8? Question with Passwords
What mods should I make to the pam_unix2.conf file. This is the first I have heard regarding a modification to this file. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Sal Torres/SBC Inc. [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:30 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Anyone using OpenLDAP with SLES8? Question with Passwords You could try using the pam_unix2.so module instead of pam_ldap.so. pam_unux2.so will call pam_ldap.so under the covers if you modify /etc/security/pam_unix2.conf. Hope it helps. sal
Re: FW: IBM iSource -- U.S. Announcements
All, I spoke to Suse and they will be posting something to the forum later today. However, I will say at this point that the LPAR based pricing post is incorrect. Straight from Suse's mouth, the pricing will remain CPU based for the mainframe. So, if you have 4 LPARS all running off the same CPU, you pay for Suse one time. With pSeries and iSeries, you pay for a box with x number of CPUs. In my past post the example was up to 8. They don't care how many instances you run. The confusion might be coming from their support pricing structure. That is based on the number of instances. 1 - 5, 6- 10,etc. I hope this clears most of the fog. Suse should be posting to the list sometime today also. - Kevin (Embedded image moved to file: pic03929.jpg) PLEASE NOTE NEW CONTACT INFORMATION! Kevin Gates DSG Linux Solutions Specialist __ office 480-471-8276 fax 480-452-1470 cell 480-734-1034 [EMAIL PROTECTED] www.dsgroup.com Adam Thornton [EMAIL PROTECTED]To: [EMAIL PROTECTED] mine.netcc: Sent by: Linux onSubject: Re: FW: IBM iSource -- U.S. Announcements 390 Port [EMAIL PROTECTED] IST.EDU 12/17/2003 10:26 PM Please respond to Linux on 390 Port On Wed, 2003-12-17 at 18:05, Alan Cox wrote: Wouldn't this depend on the price per instance and the number of instances, as well as the availability of both options ? Well, I believe that there are few (note: I'm *not* saying no) good reasons to run Linux/390 in any context other than VM. And, so, no, because if you're using Linux/390 in a cost-effective manner you're almost certainly in a situation where you're using multiple instances per CPU. I suppose in theory the per-instance price could be low enough that this wasn't a problem, but then, how do you ensure license compliance? One of the great things about VM is the ease with which you can set up and then destroy instances. How do you enforce a per-instance license in that scenario, anyway? Adam attachment: pic03929.jpg
Re: Anyone using OpenLDAP with SLES8? Question with Passwords
It looks like my pam_unix2.conf file already has references to ldap. So now my questions are: 1. Do I remove pam_unix.so and pam_ldap.so and use pam_unix2.so instead? 2. What will using pam_unix2.so buy me. The issue with expired passwords I believe goes back to the ldap. I have actually found that I can expire a password by changing shadowLastChanged to 0. However, ssh reacts weird to this. I am informed of the expired password and that I must change it; however, the ssh session is then closed by the remote host. My changing my ACLs I can get to the point where shadowLastChanged is pretty much ignored. I can't seem to find an in between? -- ideas? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Sal Torres/SBC Inc. [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:30 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Anyone using OpenLDAP with SLES8? Question with Passwords You could try using the pam_unix2.so module instead of pam_ldap.so. pam_unux2.so will call pam_ldap.so under the covers if you modify /etc/security/pam_unix2.conf. Hope it helps. sal
Re: Anyone using OpenLDAP with SLES8? Question with...
*** Reply to note of Thu, 18 Dec 2003 09:31:16 -0500 (EST/CDT) *** by [EMAIL PROTECTED] I think that YaST does it for you if you select LDAP. I found out about it by looking at the source code for pam_unux2. (pam-modules rpm). sal Eric Sammons [EMAIL PROTECTED] writes: What mods should I make to the pam_unix2.conf file. This is the first I have heard regarding a modification to this file. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Sal Torres/SBC Inc. [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:30 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Anyone using OpenLDAP with SLES8? Question with Passwords You could try using the pam_unix2.so module instead of pam_ldap.so. pam_unux2.so will call pam_ldap.so under the covers if you modify /etc/security/pam_unix2.conf. Hope it helps. sal
Re: Problem booting SLES 8 for Install
Might I suggest that you PURGE your RDR before you run the EXEC. If you can not do that, then you'll have to ORDER the RDR correctly before attempting to IPL. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:30 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install OK here is my sles8 exec file: *** top of File *** /**/ 'close rdr' 'spool rdr all' 'spool punch * rdr' 'punch sles8 image a (noh' 'punch sles8 parm a (noh' 'punch sles8 initrd a (noh' 'change rdr all keep nohold' 'ipl 00c clear' *** End of File *** One other thing I should note, this is my first time using this process under VM4.4. Previously and as I documented the process for our office, the VM version was 4.3. Has anything changed? Also, I notice that in filelist the files are listed as follows: SLES8 EXECA1 V 28 9 1 12/18/03 . . . Above you will notice that I punch with an 'a', should I replace the 'a' with an 'a1' as found in filelist? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:25 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install OK, you should do the suggestion as a previous post and post your exec that punches the files to the reader. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:12 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install My FTP process follows: ftp server binary locsite fix 80 get vmrdr.ikr sles8.image get initrd sles8.initrd asc get parmfile sles8.parm quit I have just downloaded all the files again and still get errors when trying to boot for install. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:00 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
Anyone using OpenLDAP with SLES8? Question with Passwords
Try to set the shadow last change to zero. pam_ldap is supposed to
expire the account:
...
if (session-info-shadow.lstchg == 0)
{
/*
* Adhere to convention of a shadow last change
* value of 0 implying that the password has
* expired. Apparently this is documented in the
* shadow suite (libmisc/isexpired.c).
*/
session-info-password_expired = 1;
...
sal
Re: Problem booting SLES 8 for Install
That was it, I went back to the orginal SLES8 docs to verify and in fact I had a typo in my generated documentation. Thanks for catching that... Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 10:05 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install It doesn't like SPOOL RDR ALL, I think that should be PURGE RDR ALL Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:30 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install OK here is my sles8 exec file: *** top of File *** /**/ 'close rdr' 'spool rdr all' 'spool punch * rdr' 'punch sles8 image a (noh' 'punch sles8 parm a (noh' 'punch sles8 initrd a (noh' 'change rdr all keep nohold' 'ipl 00c clear' *** End of File *** One other thing I should note, this is my first time using this process under VM4.4. Previously and as I documented the process for our office, the VM version was 4.3. Has anything changed? Also, I notice that in filelist the files are listed as follows: SLES8 EXECA1 V 28 9 1 12/18/03 . . . Above you will notice that I punch with an 'a', should I replace the 'a' with an 'a1' as found in filelist? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:25 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install OK, you should do the suggestion as a previous post and post your exec that punches the files to the reader. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:12 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install My FTP process follows: ftp server binary locsite fix 80 get vmrdr.ikr sles8.image get initrd sles8.initrd asc get parmfile sles8.parm quit I have just downloaded all the files again and still get errors when trying to boot for install. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:00 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
Re: Anyone using OpenLDAP with SLES8? Question with Passwords
I have done that and it sort of worked. It seemed to take on the
characteristics there after of a ACL problem. By changing the acls I get
different behavior; however, I can't seem to find the right acls that
cause the implementation to work.
Do you have this working? Can I ask what your LDAP ACLs look like?
Thanks!
Eric Sammons
(804)697-3925
FRIT - Unix Systems
Sal Torres/SBC Inc. [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
12/18/2003 10:03 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject:Anyone using OpenLDAP with SLES8? Question with
Passwords
Try to set the shadow last change to zero. pam_ldap is supposed to
expire the account:
...
if (session-info-shadow.lstchg == 0)
{
/*
* Adhere to convention of a shadow last change
* value of 0 implying that the password has
* expired. Apparently this is documented in the
* shadow suite (libmisc/isexpired.c).
*/
session-info-password_expired = 1;
...
sal
Re: Problem booting SLES 8 for Install
Try this.. this one works on whatever flavour of z/VM you want: 'VMFCLEAR' Clears the screen for legibility. 'CLOSE 00C'Close all open files in the reader - for purging. 'PUR RDR ALL' Empties (purges) the VM reader. 'CP SP PUN * RDR' Moves the contents of the punch to the reader. 'PU SLES8 IMAGE A (NOH' Moves the LINUX boot file to the reader. 'PU SLES8 PARM A (NOH' Moves the LINUX parameters file to the reader. 'PU SLES8 INITRD A (NOH' Moves the initial RAMdisk file (initial root FS)to the reader. 'CH RDR ALL KEEP NOH' Non-deletion of reader contents after process completion. 'CP IPL 00C CL'Sends the reader an Initial Program Load (IPL) command Regards/Cordialement/Gruss/Saludos John Cassidy Dipl.-Ing (Informatique) S390 zSeries Systems Engineering Schleswigstr. 7 D-51065 Cologne EU Tel: +49 (0) 221 61 60 777 . GSM: +49 (0) 177 799 58 56 E-Mail: [EMAIL PROTECTED] HTTP : www.jdcassidy.net -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Booher Sent: 18 December 2003 16:06 To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install It doesn't like SPOOL RDR ALL, I think that should be PURGE RDR ALL Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:30 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install OK here is my sles8 exec file: *** top of File *** /**/ 'close rdr' 'spool rdr all' 'spool punch * rdr' 'punch sles8 image a (noh' 'punch sles8 parm a (noh' 'punch sles8 initrd a (noh' 'change rdr all keep nohold' 'ipl 00c clear' *** End of File *** One other thing I should note, this is my first time using this process under VM4.4. Previously and as I documented the process for our office, the VM version was 4.3. Has anything changed? Also, I notice that in filelist the files are listed as follows: SLES8 EXECA1 V 28 9 1 12/18/03 . . . Above you will notice that I punch with an 'a', should I replace the 'a' with an 'a1' as found in filelist? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:25 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install OK, you should do the suggestion as a previous post and post your exec that punches the files to the reader. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Eric Sammons Sent: Thursday, December 18, 2003 8:12 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install My FTP process follows: ftp server binary locsite fix 80 get vmrdr.ikr sles8.image get initrd sles8.initrd asc get parmfile sles8.parm quit I have just downloaded all the files again and still get errors when trying to boot for install. Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems David Booher [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12/18/2003 09:00 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Problem booting SLES 8 for Install Also, you must make sure that they are a RECL of 80 for a RDR file. Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee Stewart Sent: Thursday, December 18, 2003 7:56 AM To: [EMAIL PROTECTED] Subject: Re: Problem booting SLES 8 for Install I suspect that either the files didn't get get downloaded as binary, or that you downloaded image for the kernal image instead of vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it from memory it's easy to get the wrong file...) Lee At 06:41 AM 12/18/2003, you wrote: In preparing to install a new guest I have created the sles8 exec file and dowloaded the necessary files. I have done this numerous times already in the same manner. This time however I am getting an error that I have not seen yet. When I execute sles8 the following appears: HCPCSP053E ALL not in CP directory RDR FILE 0028 SENT FROM GUEST RUN WAS 0028 RECS 029K CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM GUEST RUN WAS 0029 RECS 0002 CPY 001 A NOHOLD NOKEEP RDR FILE 0030 SENT FROM GUEST RUN WAS 0030 RECS 101K CPY 001 A NOHOLD NOKEEP 030 FILES CHANGED HCPVMJ23E IPL UNIT ERROR; IRB 01404417 0010 00207264 0080 HCPGIR450W CP entered; disabled wait PSW 000E 0232 Has anyone encountered this before? Thanks! Eric Sammons (804)697-3925 FRIT - Unix Systems Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
SLES 8 and IBM Shark
We are getting ready to move our VM/SUSE installations from an EMC DASD box to an IBM Shark DASD box. I have two questions. 1. Does anyone know of any issues with Linux/VM when the DASD UCB's are genned above the 32MB line. 2. Are there any issues using 3390-9's with VM/LINUX. Thanks for your time. Gene
Re: SLES 8 and IBM Shark
You must be an MVS person :). VM has never had a problem with UCB numbering. 3390-9's work just fine too. Marcy Cortes Wells Fargo Services Company -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gene Walters Sent: Thursday, December 18, 2003 09:14 To: [EMAIL PROTECTED] Subject: [LINUX-390] SLES 8 and IBM Shark We are getting ready to move our VM/SUSE installations from an EMC DASD box to an IBM Shark DASD box. I have two questions. 1. Does anyone know of any issues with Linux/VM when the DASD UCB's are genned above the 32MB line. 2. Are there any issues using 3390-9's with VM/LINUX. Thanks for your time. Gene
Re: SLES 8 and IBM Shark
On Thu, 2003-12-18 at 11:13, Gene Walters wrote: We are getting ready to move our VM/SUSE installations from an EMC DASD box to an IBM Shark DASD box. I have two questions. 1. Does anyone know of any issues with Linux/VM when the DASD UCB's are genned above the 32MB line. Above the 32MB line? 2. Are there any issues using 3390-9's with VM/LINUX. No, works great. Thanks for your time. Gene -- Rich Smrcina Sr. Systems Engineer Sytek Services - A Division of DSG Milwaukee, WI rsmrcina at wi.rr.com rsmrcina at dsgroup.com Catch the WAVV! Stay for requirements and the free-for-all. Update your zSeries skills in 4 days for a very reasonable price. WAVV 2004 in Chattanooga, TN April 30-May 4, 2004 For details see http://www.wavv.org
Re: New z900 and SuSE Linux partitions
Ila wrote that the z900 has an OSA Express Card port 1 On the zSeries, they combined two OSA cards on one physical card and the card is assigned two chpid. Each connection on the OSA card you see is port 0 of a different chpid. Check with your FE or whomever does your iocds. You should have 2 chpid assigned to the card. = Jim Sibley RHCT, Implementor of Linux on zSeries Computer are useless.They can only give answers. Pablo Picasso __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
Re: Samba and tdb locking on s/390
It looks as though those are there for architectures where someone has implemented spinlocks in assembler code. There are also generic routines written in C for everyone else. While it would be a bit of a performance enhancement to have one for Linux/390, it doesn't appear to be a requirement. You might want to re-build Samba specifying -DDEBUG to turn on debugging, at least in the TDB code. It looks like they've got a number of messages that might get generated and tell you something more than you have right now. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Daniel Jarboe Sent: Thursday, December 18, 2003 7:15 AM To: [EMAIL PROTECTED] Subject: Samba and tdb locking on s/390 I've been seeing a lot of tdb problems during our SuSE trial when it comes to Samba. Over time a tdb or two inevitably becomes corrupt, sometimes in just an hour or two. I ran tdbtorture, a tool that comes with the samba source, and got errors left and right. On intel, the tdbtorture suite just runs for a while and prints OK. Well, on s/390 immediately there are a plethora of messages like: tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable I looked in tdb/spinlock.c and saw a bunch of architecture-specific #ifdefs, but nothing S/390ish. Should there be one? ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Linux backup to z/OS or z/VM controlled tapes.
Is there anyone out there with z/OS, the z/OS NFS server, DFSMS/MVS and Linux who would be willing to try an experiment for me? I have an idea wrt to file-level backups w/o requiring TSM/MVS, but limited access to a z/OS system (and not much expertise with SMS policy definition). Failing that, is there a VM site that has SFS, DFSMS/VM configured for migration from SFS pools, TSM/VM and the CMS NFS server that would be willing to try a similar experiment? Please contact me off list if you'd be willing to discuss the idea privately. -- db David Boyes Sine Nomine Associates
Changing Timezone Offset without reinstalling
Hi all... We have a Linux image (SLES 8 under z/VM 4.4) that has a time/date problem. The system hardware clock on the processor runs LOCAL time; the timezone offsets in the SYSTEM CONFIG file are zero; and the VM time is correct -- local time. When installing SLES 8, the user specified the correct timezone (US/Mountain) and that the hardware clock was running local time. But the time displayed after installation is 7 hours off. We've double checked that the hardware clock is local time; the VM offsets are zero; and that SLES 8 was installed specifying that the hardware clock was local time. But the time is still wrong. Poking around it seems that /etc/sysconfig/clock seems like it would control that. Ours said: HWCLOCK=--localtime TIMEZONE=US/Mountain But changing to HWCLOCK=-u (based on the comments in the file) made no difference, even after rebooting... 1) Short of reinstalling from scratch, is there somewhere else to change the clock offset? 2) Any thoughts why specifying that the hardware clock was on local time didn't work as expected? Thanks for any thoughts... Lee Stewart Lee Stewart, Senior SE Sytek Services, a Division of DSG (719) 566-0188 , Fax (719) 566-0655 [EMAIL PROTECTED] www.sytek-services.com www.dsgroup.com
