Re: Linux version
R P Herrold wrote: [EMAIL PROTECTED] ~]$ lsb_release -a LSB Version: \ :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: CentOS Description:CentOS release 5.2 (Final) Release:5.2 Codename: Final [EMAIL PROTECTED] ~]$ ihlscoh2:~ # lsb_release -a LSB Version: core-2.0-noarch:core-3.0-noarch:core-2.0-s390x:core-3.0-s390x:desktop-3.1-noarch:desktop-3.1-s390:desktop-3.1-s390x:graphics-2.0-noarch:graphics-2.0-s390:graphics-2.0-s390x:graphics-3.1-noarch:graphics-3.1-s390:graphics-3.1-s390x Distributor ID: SUSE LINUX Description:SUSE Linux Enterprise Server 10 (s390x) Release:10 Codename: n/a ihlscoh2:~ # What a wonderfully kept secret that has been. Many thanks for pointing this out Russ! mark -- 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
Adrienne McGrory/UK/IBM is on vacation until Monday 8th September
I will be out of the office starting 21/08/2008 and will not return until 08/09/2008. I am out of the office on vacation returning on Monday 8th September, I will respond to your mail upon my return. -- 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
Root filesystem error switches to ReadOnly
Hello list, For various tests we have created a group of new SLES10 guests. They all are just one 3390-3 volume so they can be cloned vary fast. But for some reason these machines sometimes switch the rootdisk, and therefore the entire filesystem, to readonly. I have tried a remount but that didn't work so only a reboot will get the / back in write mode. The reboot itself run without errors. But even that sometimes doesn't solve the error and we have to clone the guest again. We also have a different SLES10 installation and there we don't see any errors there but then we aren't running any load there. I can't find any reason for this, other than what I can find in de guest console log. Any ideas? What can be the cause of this and how can it be fixed? The guest is a SLES10 SP2. [EMAIL PROTECTED]:~ uname -a Linux nlzlx921 2.6.16.60-0.21-default #1 SMP Tue May 6 12:41:02 UTC 2008 s390x s390x s390x GNU/Linux [EMAIL PROTECTED]:~ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda12365444 1682640562644 75% / udev14562064145556 1% /dev The message from the console: 08/08/19 12:23:31 NLZLX921 VMLXES21: EXT3-fs error (device dasda1): ext3_readdir: bad entry in directory #270514: rec_len is 08/08/19 12:23:31 NLZLX921 VMLXES21smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0ŸAborting journal on device 08/08/19 12:23:31 NLZLX921 VMLXES21dasda1.Ÿext3_abort called.ŸEXT3-fs error (d 08/08/19 12:23:31 NLZLX921 VMLXES21: Aug 19 12:23:31 nlzlx921 syslog-ngÝ1092¨: io.c: do_write: write() failed (errno 30), Read-only 08/08/19 12:23:31 NLZLX921 VMLXES21file system When I asked one of our linux specialists he did mention there were a few bugs relating ext3 that have been fixed in RHEL 5.1. Now I have noticed that RHEL 5.1 is on a newer kernel level than the SLES 10 SP2. Could a bug in ext3 by any chance be the problem here? Met vriendelijke groet/With kind regards, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven ( +31 (0)6 22564276 Atos Origin http://www.atosorigin.com/ MO OC Mainframe Services image001.gifimage003.jpgÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t
Re: Root filesystem error switches to ReadOnly
van Sleeuwen, Berry wrote: Hello list, For various tests we have created a group of new SLES10 guests. They all are just one 3390-3 volume so they can be cloned vary fast. If you use FLASHCOPY its fast regardless of DASD size. But for some reason these machines sometimes switch the rootdisk, and therefore the entire filesystem, to readonly. I have tried a remount but that didn't work so only a reboot will get the / back in write mode. The reboot itself run without errors. But even that sometimes doesn't solve the error and we have to clone the guest again. We also have a different SLES10 installation and there we don't see any errors there but then we aren't running any load there. I can't find any reason for this, other than what I can find in de guest console log. Any ideas? What can be the cause of this and how can it be fixed? You have a problem in with you root filesystem, so it switches to R/O to give you a chance to fix it, e.g. with fsck. The guest is a SLES10 SP2. I have many SP2 systems, all with ext3 - never any problems at all. [EMAIL PROTECTED]:~ uname -a Linux nlzlx921 2.6.16.60-0.21-default #1 SMP Tue May 6 12:41:02 UTC 2008 s390x s390x s390x GNU/Linux [EMAIL PROTECTED]:~ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda12365444 1682640562644 75% / udev14562064145556 1% /dev The message from the console: 08/08/19 12:23:31 NLZLX921 VMLXES21: EXT3-fs error (device dasda1): ext3_readdir: bad entry in directory #270514: rec_len is 08/08/19 12:23:31 NLZLX921 VMLXES21smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0ŸAborting journal on device 08/08/19 12:23:31 NLZLX921 VMLXES21dasda1.Ÿext3_abort called.ŸEXT3-fs error (d 08/08/19 12:23:31 NLZLX921 VMLXES21: Aug 19 12:23:31 nlzlx921 syslog-ngÃ1092¨: io.c: do_write: write() failed (errno 30), Read-only 08/08/19 12:23:31 NLZLX921 VMLXES21file system When I asked one of our linux specialists he did mention there were a few bugs relating ext3 that have been fixed in RHEL 5.1. Now I have noticed that RHEL 5.1 is on a newer kernel level than the SLES 10 SP2. Could a bug in ext3 by any chance be the problem here? The bug is most likely in your cloning process, perhaps the DASD extents copied and/or used are different. This will only show up when data is used within the bad extent range. mark -- 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: Distribution ages, was: Linux version
Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Cox Sent: Wednesday, August 20, 2008 2:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version 1: http://groups.google.com/group/comp.os.linux.development/msg/a32d4e2ef3b cdcc6 2: http://www.knoppix.net 3: http://www.skolelinux.org 4: http://www.ubuntu.com/ Now if anyone has some dates of when they were started for Slackware, SuSE, or RedHat we can know which is the oldest. As far as I can tell - April 1993 Slackware (update of SLS) (product release as far as I can tell not announcement) - Late 1992 SuSE (based off SLS, then slackware, then developed somewhat). First official release March 1993 (thats product to end users date) Red Hat trundles along in 1994. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Root filesystem error switches to ReadOnly
Hello Mark, I meant fast in a way that the / is copied and then changes the hostname and IP address. No other fancy things, just a default environment for our support staff to play around with. The cloning process is loosly based on the cloning scripts from redp4322. The dasd is copied using DASDFMT and dd. Both source (installation machine) and targets are identical, other than the obvious different location of the minidisk extents. The / is a 3338 cylinder minidisk so there it even uses the same minidisk extents but on different DASD volumes. There is one thing I now see, I first regarded as an error due to new disks, but it is still present even when the disks were in use for the guest before. When the copy is done there are some IO errors. 08/08/19 13:41:20 NLZLX920 VMLXES21: end_request: I/O error, dev dasdd, sector 361776Ÿprintk: 630 messages suppressed.ŸBuffer I/O 08/08/19 13:41:20 NLZLX920 VMLXES21error on device dasdd, logical block 45222Ÿlost page write due to I/O error on dasddŸBuffer 08/08/19 13:41:20 NLZLX920 VMLXES21I/O error on device dasdd, logical bl The disk is linked, then DASDFMT and dd. It looks like the IO errors appear within the dd part of the copy process. But how to fix that? Should the guest have some mdisk option to avoid errors? Thanks, Berry. -- 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 ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y
Re: Root filesystem error switches to ReadOnly
van Sleeuwen, Berry wrote: Hello Mark, I meant fast in a way that the / is copied and then changes the hostname and IP address. No other fancy things, just a default environment for our support staff to play around with. The cloning process is loosly based on the cloning scripts from redp4322. The dasd is copied using DASDFMT and dd. Both source (installation machine) and targets are identical, other than the obvious different location of the minidisk extents. The / is a 3338 cylinder minidisk so there it even uses the same minidisk extents but on different DASD volumes. There is one thing I now see, I first regarded as an error due to new disks, but it is still present even when the disks were in use for the guest before. When the copy is done there are some IO errors. FLASHCOPY is still faster ;-) 08/08/19 13:41:20 NLZLX920 VMLXES21: end_request: I/O error, dev dasdd, sector 361776Ÿprintk: 630 messages suppressed.ŸBuffer I/O 08/08/19 13:41:20 NLZLX920 VMLXES21error on device dasdd, logical block 45222Ÿlost page write due to I/O error on dasddŸBuffer 08/08/19 13:41:20 NLZLX920 VMLXES21I/O error on device dasdd, logical bl The disk is linked, then DASDFMT and dd. It looks like the IO errors appear within the dd part of the copy process. But how to fix that? Should the guest have some mdisk option to avoid errors? Thanks, Berry. If doing a dd from linux and the minidisks are identical in size, then one must assume that you have the rights to write to all cylinders. If you issue a vmcp q v da - are source and target the same number of cylinders? I also assume that the source and target are not mounted to Linux while the dd is running? Have you done an fsck on the source volume to ensure it is good? Are you specifying any dd options? Can you do a foreground dd (with -v) and reproduce the error? Is z/VM logging anything - EREP? mark -- 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: Distribution ages, was: Linux version
Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? K And those of us who have worked on it too ;-) mark -- 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: Root filesystem error switches to ReadOnly
Hello Mark, I'll have to look into the flashcopy process but have not taken the time for it just yet. I guess one thing that would be wrong then is that I copy from the live system. So the source nlzlx920 is being copied from within the nlzlx920. But would that introduce IO errors on the target disks? If anything I'd expect to see errors during boot of the target guest. Either in a filesystemcheck or dmesg afterwards. Much like when you DDR a live VM and get a warmstartdata error when the target is IPLled. Perhaps a rethink of the process is in order. I guess a resque system would be an option. I do like to have a resque machine so I could also use that machine to do the cloning. As for other questions, I also assume I have the rights. No errors on that part. Same amount of cylinders. I have not yet ran the fsck on the source nor did I test it in a failsafe IPL of a new target. I dd with dd bs=4096 if=$sDev of=$tDev no other options. Haven't ran dd during the process by hand, other than a manual test to clone the first machine and to test the steps in the script. No erep or errors within the operator log. There is no error from the VM part. It's only within the linux. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: donderdag 21 augustus 2008 12:22 To: LINUX-390@VM.MARIST.EDU Subject: Re: Root filesystem error switches to ReadOnly van Sleeuwen, Berry wrote: Hello Mark, I meant fast in a way that the / is copied and then changes the hostname and IP address. No other fancy things, just a default environment for our support staff to play around with. The cloning process is loosly based on the cloning scripts from redp4322. The dasd is copied using DASDFMT and dd. Both source (installation machine) and targets are identical, other than the obvious different location of the minidisk extents. The / is a 3338 cylinder minidisk so there it even uses the same minidisk extents but on different DASD volumes. There is one thing I now see, I first regarded as an error due to new disks, but it is still present even when the disks were in use for the guest before. When the copy is done there are some IO errors. FLASHCOPY is still faster ;-) 08/08/19 13:41:20 NLZLX920 VMLXES21: end_request: I/O error, dev dasdd, sector 361776Ÿprintk: 630 messages suppressed.ŸBuffer I/O 08/08/19 13:41:20 NLZLX920 VMLXES21error on device dasdd, logical block 45222Ÿlost page write due to I/O error on dasddŸBuffer 08/08/19 13:41:20 NLZLX920 VMLXES21I/O error on device dasdd, logical bl The disk is linked, then DASDFMT and dd. It looks like the IO errors appear within the dd part of the copy process. But how to fix that? Should the guest have some mdisk option to avoid errors? Thanks, Berry. If doing a dd from linux and the minidisks are identical in size, then one must assume that you have the rights to write to all cylinders. If you issue a vmcp q v da - are source and target the same number of cylinders? I also assume that the source and target are not mounted to Linux while the dd is running? Have you done an fsck on the source volume to ensure it is good? Are you specifying any dd options? Can you do a foreground dd (with -v) and reproduce the error? Is z/VM logging anything - EREP? mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j
Re: Root filesystem error switches to ReadOnly
van Sleeuwen, Berry wrote: Hello Mark, I'll have to look into the flashcopy process but have not taken the time for it just yet. I guess one thing that would be wrong then is that I copy from the live system. So the source nlzlx920 is being copied from within the nlzlx920. But would that introduce IO errors on the target disks? If anything I'd expect to see errors during boot of the target guest. Either in a filesystemcheck or dmesg afterwards. Much like when you DDR a live VM and get a warmstartdata error when the target is IPLled. Perhaps a rethink of the process is in order. I guess a resque system would be an option. I do like to have a resque machine so I could also use that machine to do the cloning. As for other questions, I also assume I have the rights. No errors on that part. Same amount of cylinders. I have not yet ran the fsck on the source nor did I test it in a failsafe IPL of a new target. I dd with dd bs=4096 if=$sDev of=$tDev no other options. Haven't ran dd during the process by hand, other than a manual test to clone the first machine and to test the steps in the script. No erep or errors within the operator log. There is no error from the VM part. It's only within the linux. Regards, Berry. Never clone a live Linux filesystem. Once the filesystem has been mounted the filesystem is cached in storage (as are updates) and the on disk filesystem is marked 'dirty. Stop the master linux system with a clean shutdown, and copy the disk using flashcopy or ddr if you prefer. This new copy is the master disk to be used for future copies. Reboot the Linux system and run an e2fsck on the new copy to ensure it is good. Then clone as you like ;-) mark -- 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: Root filesystem error switches to ReadOnly
I guess one thing that would be wrong then is that I copy from the live system. I think that's your problem. You're copying from a likely unstable source (the live system might be writing to your volume as you attempt to copy it). Try shutting down the master (live) system with shutdown -h now before you copy from it. The errors you're reporting look like file system structural errors. HTH, --Jim-- -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Root filesystem error switches to ReadOnly
Mark, Hm, I even didn't think about cache and what it could do to not only files but also to the filesystem itself. And even if I did I'd have guessed it would only mess up a logfile that isn't in use on the target anyway. We would start in a new machine with an empty /var/log/messages and /var/log/warn for example. I think I'll start on a new machine to be used for resque and cloning so that we must run our cloning from a separate machine. Thanks, Berry. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: donderdag 21 augustus 2008 13:27 To: LINUX-390@VM.MARIST.EDU Subject: Re: Root filesystem error switches to ReadOnly van Sleeuwen, Berry wrote: Hello Mark, I'll have to look into the flashcopy process but have not taken the time for it just yet. I guess one thing that would be wrong then is that I copy from the live system. So the source nlzlx920 is being copied from within the nlzlx920. But would that introduce IO errors on the target disks? If anything I'd expect to see errors during boot of the target guest. Either in a filesystemcheck or dmesg afterwards. Much like when you DDR a live VM and get a warmstartdata error when the target is IPLled. Perhaps a rethink of the process is in order. I guess a resque system would be an option. I do like to have a resque machine so I could also use that machine to do the cloning. As for other questions, I also assume I have the rights. No errors on that part. Same amount of cylinders. I have not yet ran the fsck on the source nor did I test it in a failsafe IPL of a new target. I dd with dd bs=4096 if=$sDev of=$tDev no other options. Haven't ran dd during the process by hand, other than a manual test to clone the first machine and to test the steps in the script. No erep or errors within the operator log. There is no error from the VM part. It's only within the linux. Regards, Berry. Never clone a live Linux filesystem. Once the filesystem has been mounted the filesystem is cached in storage (as are updates) and the on disk filesystem is marked 'dirty. Stop the master linux system with a clean shutdown, and copy the disk using flashcopy or ddr if you prefer. This new copy is the master disk to be used for future copies. Reboot the Linux system and run an e2fsck on the new copy to ensure it is good. Then clone as you like ;-) mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e
Re: Distribution ages, was: Linux version
Very true. I was feeling fine until you made me feel old this morning g. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Thursday, August 21, 2008 6:25 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? K And those of us who have worked on it too ;-) mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Distribution ages, was: Linux version
When I installed VM BSEPP, I did not know if the idea of virtualization would last. Now I have a penguin ranch. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 7:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Very true. I was feeling fine until you made me feel old this morning g. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Thursday, August 21, 2008 6:25 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? K And those of us who have worked on it too ;-) mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Root filesystem error switches to ReadOnly
Just for a test, try switching the disk references in /etc/fstab to by-path syntax. I'm speculating here, but is it possible that there are some issues with correctly identifying which disk to use for /dev/dasda? -- 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: Root filesystem error switches to ReadOnly
Doing a dd on a device goes through the cache, so in this case the cache can't be the problem. Doing a dd on a live system however will not work. With or without a cache the filesystem can change while you are doing the copy, which would result in a bad root on the new system. I suspect that the errors you are getting are due to the target DASD not being formatted. Did you do a dasdfmt on the target volume? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of van Sleeuwen, Berry Sent: Thursday, August 21, 2008 4:53 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Root filesystem error switches to ReadOnly Mark, Hm, I even didn't think about cache and what it could do to not only files but also to the filesystem itself. And even if I did I'd have guessed it would only mess up a logfile that isn't in use on the target anyway. We would start in a new machine with an empty /var/log/messages and /var/log/warn for example. I think I'll start on a new machine to be used for resque and cloning so that we must run our cloning from a separate machine. Thanks, Berry. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: donderdag 21 augustus 2008 13:27 To: LINUX-390@VM.MARIST.EDU Subject: Re: Root filesystem error switches to ReadOnly van Sleeuwen, Berry wrote: Hello Mark, I'll have to look into the flashcopy process but have not taken the time for it just yet. I guess one thing that would be wrong then is that I copy from the live system. So the source nlzlx920 is being copied from within the nlzlx920. But would that introduce IO errors on the target disks? If anything I'd expect to see errors during boot of the target guest. Either in a filesystemcheck or dmesg afterwards. Much like when you DDR a live VM and get a warmstartdata error when the target is IPLled. Perhaps a rethink of the process is in order. I guess a resque system would be an option. I do like to have a resque machine so I could also use that machine to do the cloning. As for other questions, I also assume I have the rights. No errors on that part. Same amount of cylinders. I have not yet ran the fsck on the source nor did I test it in a failsafe IPL of a new target. I dd with dd bs=4096 if=$sDev of=$tDev no other options. Haven't ran dd during the process by hand, other than a manual test to clone the first machine and to test the steps in the script. No erep or errors within the operator log. There is no error from the VM part. It's only within the linux. Regards, Berry. Never clone a live Linux filesystem. Once the filesystem has been mounted the filesystem is cached in storage (as are updates) and the on disk filesystem is marked 'dirty. Stop the master linux system with a clean shutdown, and copy the disk using flashcopy or ddr if you prefer. This new copy is the master disk to be used for future copies. Reboot the Linux system and run an e2fsck on the new copy to ensure it is good. Then clone as you like ;-) mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 __ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. -- 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: Root filesystem error switches to ReadOnly
van Sleeuwen, Berry wrote: Mark, Hm, I even didn't think about cache and what it could do to not only files but also to the filesystem itself. And even if I did I'd have guessed it would only mess up a logfile that isn't in use on the target anyway. We would start in a new machine with an empty /var/log/messages and /var/log/warn for example. I think I'll start on a new machine to be used for resque and cloning so that we must run our cloning from a separate machine. Thanks, Berry. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: donderdag 21 augustus 2008 13:27 To: LINUX-390@VM.MARIST.EDU Subject: Re: Root filesystem error switches to ReadOnly van Sleeuwen, Berry wrote: Hello Mark, I'll have to look into the flashcopy process but have not taken the time for it just yet. I guess one thing that would be wrong then is that I copy from the live system. So the source nlzlx920 is being copied from within the nlzlx920. But would that introduce IO errors on the target disks? If anything I'd expect to see errors during boot of the target guest. Either in a filesystemcheck or dmesg afterwards. Much like when you DDR a live VM and get a warmstartdata error when the target is IPLled. Perhaps a rethink of the process is in order. I guess a resque system would be an option. I do like to have a resque machine so I could also use that machine to do the cloning. As for other questions, I also assume I have the rights. No errors on that part. Same amount of cylinders. I have not yet ran the fsck on the source nor did I test it in a failsafe IPL of a new target. I dd with dd bs=4096 if=$sDev of=$tDev no other options. Haven't ran dd during the process by hand, other than a manual test to clone the first machine and to test the steps in the script. No erep or errors within the operator log. There is no error from the VM part. It's only within the linux. Regards, Berry. I don't recommend it for normal use, but I have cloned a running Linux system, without mounting its filesystems ro. I did it over a network, and used a procedure like this: 1. Partition target drive 2. mke2fs as needed. 3. mkdir and mount to get the volume structure right. 4. ssh [EMAIL PROTECTED] tar clC /boot / var (whatever) | tar xpC /mnt/dest Now this carries the risk of having some corrupted files - log files, and application data such as your databases and email, unless you shut them down. In my case, that was unimportant. You can safely clone the running system as you did, provided that any mounted relevant filesystems, including /, are mounted ro. Generally, this implies booting to single-user mode. Running fsck after the cloning process will show you it's okay. Never clone a live Linux filesystem. Once the filesystem has been mounted the filesystem is cached in storage (as are updates) and the on disk filesystem is marked 'dirty. Stop the master linux system with a clean shutdown, and copy the disk using flashcopy or ddr if you prefer. This new copy is the master disk to be used for future copies. Reboot the Linux system and run an e2fsck on the new copy to ensure it is good. Then clone as you like ;-) -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Distribution ages, was: Linux version
Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Distribution ages, was: Linux version
Yeppers. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 11:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Distribution ages, was: Linux version
OS/VS1? Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Distribution ages, was: Linux version
Nah, MFT and I don't even remember what release CICS was in (it was macro based, ya know DFHKC, DFHFC etc). Suffice it to say, there was no Restart/Recovery. This was when I was at Allied Breweries in England, we wrote our own (with a lot of IBM cooperation - we had several SEs on site back then) and wrapped it around the DFHKC, FC and TC IBM code. I had heard that IBM used much of our original code for the CICS Recovery/Restart product although don't know whether that was really true or not. When we put new releases of CICS in, we just (from what I remember) had 4 places (DFHKC, FC, TC and maybe SC) to insert a CLC and BE to re-institute our own recovery stuff). We even had pre-production 3270 screens g. I know, this dates me a lot g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version OS/VS1? Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Distribution ages, was: Linux version
MFT, MVT, then VS1.I was DOS/VS. Installed CICS 1.0 macro level to replace BTAM stuff like 40407F7F2DOLDER THAN THE HILLS. My new 360/30 had a DISK drive (no more TOS). DFHPCT, DFHPPT, DFHFCT, DFHTCT etc in CICS. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 12:06 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Nah, MFT and I don't even remember what release CICS was in (it was macro based, ya know DFHKC, DFHFC etc). Suffice it to say, there was no Restart/Recovery. This was when I was at Allied Breweries in England, we wrote our own (with a lot of IBM cooperation - we had several SEs on site back then) and wrapped it around the DFHKC, FC and TC IBM code. I had heard that IBM used much of our original code for the CICS Recovery/Restart product although don't know whether that was really true or not. When we put new releases of CICS in, we just (from what I remember) had 4 places (DFHKC, FC, TC and maybe SC) to insert a CLC and BE to re-institute our own recovery stuff). We even had pre-production 3270 screens g. I know, this dates me a lot g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version OS/VS1? Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Distribution ages, was: Linux version
Mine was 360/50 and a 360/30. When the 30 was replaced with a 2nd 50, we ran the 30 for about a month outside of the computer room (with no air conditioning other than opening the windows) with IBMs blessing. 2311 and 2314 disk drives with a paper tape reader that had a flippable table so that the paper tapes we got in from construction sites could be read either started at the outside or the inside of the PT spool. 2540 card reader/puches and 1403 printers. Ah, the good ole days.g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version MFT, MVT, then VS1.I was DOS/VS. Installed CICS 1.0 macro level to replace BTAM stuff like 40407F7F2DOLDER THAN THE HILLS. My new 360/30 had a DISK drive (no more TOS). DFHPCT, DFHPPT, DFHFCT, DFHTCT etc in CICS. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 12:06 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Nah, MFT and I don't even remember what release CICS was in (it was macro based, ya know DFHKC, DFHFC etc). Suffice it to say, there was no Restart/Recovery. This was when I was at Allied Breweries in England, we wrote our own (with a lot of IBM cooperation - we had several SEs on site back then) and wrapped it around the DFHKC, FC and TC IBM code. I had heard that IBM used much of our original code for the CICS Recovery/Restart product although don't know whether that was really true or not. When we put new releases of CICS in, we just (from what I remember) had 4 places (DFHKC, FC, TC and maybe SC) to insert a CLC and BE to re-institute our own recovery stuff). We even had pre-production 3270 screens g. I know, this dates me a lot g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version OS/VS1? Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Distribution ages, was: Linux version
We had a check 13 pocket sorter that was connected to a printer that printed tapes. When the pocket filled, you pulled the tape and banded it to the checks. (1968) Our primary system was a card only 1401G. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 12:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Mine was 360/50 and a 360/30. When the 30 was replaced with a 2nd 50, we ran the 30 for about a month outside of the computer room (with no air conditioning other than opening the windows) with IBMs blessing. 2311 and 2314 disk drives with a paper tape reader that had a flippable table so that the paper tapes we got in from construction sites could be read either started at the outside or the inside of the PT spool. 2540 card reader/puches and 1403 printers. Ah, the good ole days.g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version MFT, MVT, then VS1.I was DOS/VS. Installed CICS 1.0 macro level to replace BTAM stuff like 40407F7F2DOLDER THAN THE HILLS. My new 360/30 had a DISK drive (no more TOS). DFHPCT, DFHPPT, DFHFCT, DFHTCT etc in CICS. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 12:06 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Nah, MFT and I don't even remember what release CICS was in (it was macro based, ya know DFHKC, DFHFC etc). Suffice it to say, there was no Restart/Recovery. This was when I was at Allied Breweries in England, we wrote our own (with a lot of IBM cooperation - we had several SEs on site back then) and wrapped it around the DFHKC, FC and TC IBM code. I had heard that IBM used much of our original code for the CICS Recovery/Restart product although don't know whether that was really true or not. When we put new releases of CICS in, we just (from what I remember) had 4 places (DFHKC, FC, TC and maybe SC) to insert a CLC and BE to re-institute our own recovery stuff). We even had pre-production 3270 screens g. I know, this dates me a lot g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version OS/VS1? Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or
Re: Distribution ages, was: Linux version
-Original Message- From: Linux on 390 Port On Behalf Of Evans, Kevin R Mine was 360/50 and a 360/30. When the 30 was replaced with a 2nd 50, we ran the 30 for about a month outside of the computer room (with no air conditioning other than opening the windows) with IBMs blessing. 2311 and 2314 disk drives with a paper tape reader that had a flippable table so that the paper tapes we got in from construction sites could be read either started at the outside or the inside of the PT spool. 2540 card reader/puches and 1403 printers. Ah, the good ole days.g. In those days I just sat in the tower and told pilots where to go. :-) -jc- -- 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: Distribution ages, was: Linux version
This is getting like Monty Python g. One guy says When we were young, we used to eat the leather from our shoes. The other guy says You had shoes?. LOL Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 1:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version We had a check 13 pocket sorter that was connected to a printer that printed tapes. When the pocket filled, you pulled the tape and banded it to the checks. (1968) Our primary system was a card only 1401G. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 12:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Mine was 360/50 and a 360/30. When the 30 was replaced with a 2nd 50, we ran the 30 for about a month outside of the computer room (with no air conditioning other than opening the windows) with IBMs blessing. 2311 and 2314 disk drives with a paper tape reader that had a flippable table so that the paper tapes we got in from construction sites could be read either started at the outside or the inside of the PT spool. 2540 card reader/puches and 1403 printers. Ah, the good ole days.g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version MFT, MVT, then VS1.I was DOS/VS. Installed CICS 1.0 macro level to replace BTAM stuff like 40407F7F2DOLDER THAN THE HILLS. My new 360/30 had a DISK drive (no more TOS). DFHPCT, DFHPPT, DFHFCT, DFHTCT etc in CICS. Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Thursday, August 21, 2008 12:06 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Nah, MFT and I don't even remember what release CICS was in (it was macro based, ya know DFHKC, DFHFC etc). Suffice it to say, there was no Restart/Recovery. This was when I was at Allied Breweries in England, we wrote our own (with a lot of IBM cooperation - we had several SEs on site back then) and wrapped it around the DFHKC, FC and TC IBM code. I had heard that IBM used much of our original code for the CICS Recovery/Restart product although don't know whether that was really true or not. When we put new releases of CICS in, we just (from what I remember) had 4 places (DFHKC, FC, TC and maybe SC) to insert a CLC and BE to re-institute our own recovery stuff). We even had pre-production 3270 screens g. I know, this dates me a lot g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version OS/VS1? Lea Stahr zVM, Linux and zLinux Administrator Navistar, Inc. 630-753-5445 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, August 21, 2008 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Evans, Kevin R wrote: Kinda makes one realize how long z/OS (or its ancestors) has been around, doesn't it? MFT? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 CONFIDENTIALITY NOTICE: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to
Re: Distribution ages, was: Linux version
I'd like to sit in a tower and tell some people where to go g today. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Chase, John Sent: Thursday, August 21, 2008 1:40 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version -Original Message- From: Linux on 390 Port On Behalf Of Evans, Kevin R Mine was 360/50 and a 360/30. When the 30 was replaced with a 2nd 50, we ran the 30 for about a month outside of the computer room (with no air conditioning other than opening the windows) with IBMs blessing. 2311 and 2314 disk drives with a paper tape reader that had a flippable table so that the paper tapes we got in from construction sites could be read either started at the outside or the inside of the PT spool. 2540 card reader/puches and 1403 printers. Ah, the good ole days.g. In those days I just sat in the tower and told pilots where to go. :-) -jc- -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
z/VM CP commands (LOGON)?
z/VM'ers, After a few searches and actually scanning the CP commands and utilities manual, hopefully I can get some help with this z/VM related question. If I have a z/linux guest called ztrash01, I can logon to z/VM as ztrash01, IPL xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console from my 3270 terminal session, enter logoff. No problem. The why I want to do the following is to potentially stress test some applications by forcing off a z/Linux guest (crash) and then eventually trying to automate and re-IPL, but first I gotta be able to do some basic z/VM CP commands below. I read the LOGON in the CP commands and Utilities reference, but I'm doing something wrong (other than trying to trash and stress test my guest). I'm still playing with test systems, but from a z/VM CP perspective, for now the Linux guest ztrash01 is shutdown and halted, but ztrash01 is still logged onto z/VM. 1. If I'm logged on as operator to z/VM, I can issue CP command q n and see that guest ztrash01 is logged onto z/VM and DSC (disconnected). 2. Still as operator, I can issued CP command force ztrash01 logoff immed and this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR) 3. Still as operator, a q n verifies that the guest is gone (i.e. logged off z/VM) 4. Now, as operator, instead of going to another z/VM terminal session and logging on as ztrash01, still as operator, I would like to cause the guest ztrash01 to logon (and eventually IPL). To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? Thanks in advance, Tom B. -- 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 CP commands (LOGON)?
Check out the AUTOLOG and XAUTOLOG commands. Kris On Thu, Aug 21, 2008 at 03:10:56PM -0400, Tom Burkholder wrote: z/VM'ers, After a few searches and actually scanning the CP commands and utilities manual, hopefully I can get some help with this z/VM related question. If I have a z/linux guest called ztrash01, I can logon to z/VM as ztrash01, IPL xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console from my 3270 terminal session, enter logoff. No problem. The why I want to do the following is to potentially stress test some applications by forcing off a z/Linux guest (crash) and then eventually trying to automate and re-IPL, but first I gotta be able to do some basic z/VM CP commands below. I read the LOGON in the CP commands and Utilities reference, but I'm doing something wrong (other than trying to trash and stress test my guest). I'm still playing with test systems, but from a z/VM CP perspective, for now the Linux guest ztrash01 is shutdown and halted, but ztrash01 is still logged onto z/VM. 1. If I'm logged on as operator to z/VM, I can issue CP command q n and see that guest ztrash01 is logged onto z/VM and DSC (disconnected). 2. Still as operator, I can issued CP command force ztrash01 logoff immed and this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR) 3. Still as operator, a q n verifies that the guest is gone (i.e. logged off z/VM) 4. Now, as operator, instead of going to another z/VM terminal session and logging on as ztrash01, still as operator, I would like to cause the guest ztrash01 to logon (and eventually IPL). To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? Thanks in advance, Tom B. -- 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 -- Never underestimate a Mage with: - the Intelligence to cast Magic Missile, - the Constitution to survive the first hit, and - the Dexterity to run fast enough to avoid being hit a second time. -- 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: Distribution ages, was: Linux version
On 8/20/2008 at 12:26 PM, in message [EMAIL PROTECTED], Alan Cox [EMAIL PROTECTED] wrote: -snip- I'd question that on all sorts of grounds. For one I'm very sure Debian is much much newer than Slackware. Slackware is *old* - really old. You're right, although depending on how you measure age Debian is either only a couple of months or a couple of years younger. I had researched this question some time back when I was going to be giving a presentation on Linux. I could have sworn what I found then revealed Slackware came along after Debian. Looking again now, that just isn't the case. I must be getting old. Argh. -snip- What is 'commercial' ? Trading a product in exchange for money with the intent to make a profit? Works for me. I also assume you mean 'oldest continually maintained' 8) Sure. I thought oldest surviving pretty much covered that. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: z/VM CP commands (LOGON)?
To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? XAUTOLOG guestname Pieter Harder Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- 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 CP commands (LOGON)?
To solve your problem you need to review the CP XAUTOLOG command and place the IPL xxx in the profile exec for your linux guest. Thanks, Detro Senior IT Specialist 1177 S. Beltline Rd, Coppell, TX 75019 Internal Mail Stop: 71-01-3001O Phone: 469-549-8174 (t/l603) Fax: 469-549-8149 (t/l 603) [EMAIL PROTECTED] Global Solution Center (GSC) From: Tom Burkholder [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Date: 08/21/08 02:14 PM Subject: z/VM CP commands (LOGON)? z/VM'ers, After a few searches and actually scanning the CP commands and utilities manual, hopefully I can get some help with this z/VM related question. If I have a z/linux guest called ztrash01, I can logon to z/VM as ztrash01, IPL xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console from my 3270 terminal session, enter logoff. No problem. The why I want to do the following is to potentially stress test some applications by forcing off a z/Linux guest (crash) and then eventually trying to automate and re-IPL, but first I gotta be able to do some basic z/VM CP commands below. I read the LOGON in the CP commands and Utilities reference, but I'm doing something wrong (other than trying to trash and stress test my guest). I'm still playing with test systems, but from a z/VM CP perspective, for now the Linux guest ztrash01 is shutdown and halted, but ztrash01 is still logged onto z/VM. 1. If I'm logged on as operator to z/VM, I can issue CP command q n and see that guest ztrash01 is logged onto z/VM and DSC (disconnected). 2. Still as operator, I can issued CP command force ztrash01 logoff immed and this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR) 3. Still as operator, a q n verifies that the guest is gone (i.e. logged off z/VM) 4. Now, as operator, instead of going to another z/VM terminal session and logging on as ztrash01, still as operator, I would like to cause the guest ztrash01 to logon (and eventually IPL). To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? Thanks in advance, Tom B. -- 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 image/jpegimage/jpeg
Re: z/VM CP commands (LOGON)?
Also, just a little tip.. You might want to either SET OBSERVER .. in the ztrash01 profile exec or in the directory entry for ztrash01. That way you can see the LINUX IPL console messages even though it is comming up disconnected. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Pieter Harder Sent: Thursday, August 21, 2008 2:18 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM CP commands (LOGON)? To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? XAUTOLOG guestname Pieter Harder Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: z/VM CP commands (LOGON)?
Thanks to all! XAUTOLOG it is and an IPL xxx added to the profile. It's already been tested and works. I'll also look at the SET OBSERVER too from the latest email tip. Thanks again, Tom B. From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gary Detro Sent: Thursday, August 21, 2008 3:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM CP commands (LOGON)? To solve your problem you need to review the CP XAUTOLOG command and place the IPL xxx in the profile exec for your linux guest. Thanks, Detro Senior IT Specialist 1177 S. Beltline Rd, Coppell, TX 75019 Internal Mail Stop: 71-01-3001O Phone: 469-549-8174 (t/l603) Fax: 469-549-8149 (t/l 603) [EMAIL PROTECTED] Global Solution Centerhttp://w3.ibm.com/support/stss/gesc.html (GSC) [cid:image001.jpg@01C903A2.D5ADC410]http://www.ibm.com/ondemand [cid:image002.jpg@01C903A2.D5ADC410] From: Tom Burkholder [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Date: 08/21/08 02:14 PM Subject: z/VM CP commands (LOGON)? z/VM'ers, After a few searches and actually scanning the CP commands and utilities manual, hopefully I can get some help with this z/VM related question. If I have a z/linux guest called ztrash01, I can logon to z/VM as ztrash01, IPL xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console from my 3270 terminal session, enter logoff. No problem. The why I want to do the following is to potentially stress test some applications by forcing off a z/Linux guest (crash) and then eventually trying to automate and re-IPL, but first I gotta be able to do some basic z/VM CP commands below. I read the LOGON in the CP commands and Utilities reference, but I'm doing something wrong (other than trying to trash and stress test my guest). I'm still playing with test systems, but from a z/VM CP perspective, for now the Linux guest ztrash01 is shutdown and halted, but ztrash01 is still logged onto z/VM. 1. If I'm logged on as operator to z/VM, I can issue CP command q n and see that guest ztrash01 is logged onto z/VM and DSC (disconnected). 2. Still as operator, I can issued CP command force ztrash01 logoff immed and this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR) 3. Still as operator, a q n verifies that the guest is gone (i.e. logged off z/VM) 4. Now, as operator, instead of going to another z/VM terminal session and logging on as ztrash01, still as operator, I would like to cause the guest ztrash01 to logon (and eventually IPL). To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? Thanks in advance, Tom B. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 inline: image001.jpginline: image002.jpg
Re: 3270 console confusion
On 8/20/2008 at 3:36 PM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: -snip- 2.6.16.46-0.12-default. I am currently trying to workout how to do an upgrade but I am using the SP1 starter system and documentation seems sparse. You're entitled to 180 days of maintenance. Register your system and use YaST Online Update or rug to install it. -snip- Possibly a problem there. I am currently unemployed and this is a home-based self-improvement project, all running on Hercules. (Watch support magically vanish into the distance...) Why would that happen? The non-IBMers on the list don't get the hives when someone mentions Hercules. Even though I have access to various real mainframes, I still have Hercules installed on one of my workstations. Seeing as how my involvement with Linux in general started out as self-improvement, I'm certainly not going to shun someone else doing the same. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 console confusion
On Friday 22 Aug 2008, Mark Post wrote: On 8/20/2008 at 3:36 PM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: -snip- 2.6.16.46-0.12-default. I am currently trying to workout how to do an upgrade but I am using the SP1 starter system and documentation seems sparse. You're entitled to 180 days of maintenance. Register your system and use YaST Online Update or rug to install it. Thanks, I will check this out. But I am having trouble locating good doco as to how to set up the online maintenance. Possibly a problem there. I am currently unemployed and this is a home-based self-improvement project, all running on Hercules. (Watch support magically vanish into the distance...) Why would that happen? The non-IBMers on the list don't get the hives when someone mentions Hercules. Even though I have access to various real mainframes, I still have Hercules installed on one of my workstations. Seeing as how my involvement with Linux in general started out as self-improvement, I'm certainly not going to shun someone else doing the same. Apologies. I had just got home from the pub and was feeling rather bitter. Getting a new contract is not easy in the current economic climate. -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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: 3270 console confusion
On 8/21/2008 at 4:11 PM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: -snip- Thanks, I will check this out. But I am having trouble locating good doco as to how to set up the online maintenance. The first part of my article at http://www.zjournal.com/index.cfm?section=articleaid=992 talks about how you register your system. If you follow those directions, the setup is done for you by the tools. -snip- Apologies. I had just got home from the pub and was feeling rather bitter. Getting a new contract is not easy in the current economic climate. No need to apologize, I just wanted to make sure you understood that you're not alone in your efforts. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Two Different YaST2 Control Center displays
On 8/6/2008 at 3:04 PM, in message [EMAIL PROTECTED], Mrohs, Ray [EMAIL PROTECTED] wrote: We have 2 SLES10 SP1 servers. When I start yast2 on the first linux, the xterm screen shows a long scrolling list of selections, and its slow. On the second linux, the Control Center display is compact and all on one screen, and its faster. Where should I look for the cause of the differences? Did you ever get this figured out? While I can't say I recommend running X or VNC applications on System z, they should still work properly. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Root filesystem error switches to ReadOnly
I expect the problem is using 'dd' for the copying may not get the magic signatures that makes the disk a CDL format, so the driver ends up seeing it as LDL and gets things misaligned. But you should be able to notice that when the new system is booting. Have you considered using DDR or such to copy the disk instead (assuming you may not have the flashcopy feature licenses on the DASD)? -Rob -- 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 CP commands (LOGON)?
Tom, suggestions: 1- To automate the IPL, I start my Linuxes together with VM, coding CP XAUTOLOG guest into AUTOLOG1's profile.exec 2- To automate Shutdown, there are changes on VM (SYSTEM CONFIG) and in Linux (zipl.conf) Resuming: On SYSTEM CONFIG (can be activated by commands, too): (These numbers are times in seconds and must be adjusted for your installation). See manuals. /**/ /*CP SIGNAL */ /**/ SET SIGNAL SHUTDOWN 30 SET SHUTDOWNTIME 60 On zipl.conf, include the parameters vmpoff and vmphalt: [ipl] ... parameters = root=/dev/system/sistema vmphalt=logoff vmpoff=logoff TERM=dumb These customization will instruct the VM to delay the FORCE until the Linux complete his halt process. Also works for the LPAR DEACTIVATE. And instruct the Linux to do the LOGOFF command itself. See details on VM manuals and in the Cookbooks for RHEL and for SLES. Good luck. Clovis Pereira zVM zOS Support - SWS Maintenance and Technical Support Services MTS Brazil phone: 55-11-2132-3399 [EMAIL PROTECTED] Tom Burkholder [EMAIL PROTECTED] vc.comTo Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject z/VM CP commands (LOGON)? 21/08/2008 16:10 Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU z/VM'ers, After a few searches and actually scanning the CP commands and utilities manual, hopefully I can get some help with this z/VM related question. If I have a z/linux guest called ztrash01, I can logon to z/VM as ztrash01, IPL xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console from my 3270 terminal session, enter logoff. No problem. The why I want to do the following is to potentially stress test some applications by forcing off a z/Linux guest (crash) and then eventually trying to automate and re-IPL, but first I gotta be able to do some basic z/VM CP commands below. I read the LOGON in the CP commands and Utilities reference, but I'm doing something wrong (other than trying to trash and stress test my guest). I'm still playing with test systems, but from a z/VM CP perspective, for now the Linux guest ztrash01 is shutdown and halted, but ztrash01 is still logged onto z/VM. 1. If I'm logged on as operator to z/VM, I can issue CP command q n and see that guest ztrash01 is logged onto z/VM and DSC (disconnected). 2. Still as operator, I can issued CP command force ztrash01 logoff immed and this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR) 3. Still as operator, a q n verifies that the guest is gone (i.e. logged off z/VM) 4. Now, as operator, instead of going to another z/VM terminal session and logging on as ztrash01, still as operator, I would like to cause the guest ztrash01 to logon (and eventually IPL). To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? Thanks in advance, Tom B. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 inline: graycol.gifinline: pic06960.gifinline: ecblank.gif
Re: z/VM CP commands (LOGON)?
One other thing you may find useful: If you boot with the kernel parameter vmhalt=LOGOFF (added to /etc/zipl.conf), the guest will logoff after halt. -Brad Tom Burkholder wrote: Thanks to all! XAUTOLOG it is and an IPL xxx added to the profile. It's already been tested and works. I'll also look at the SET OBSERVER too from the latest email tip. Thanks again, Tom B. From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gary Detro Sent: Thursday, August 21, 2008 3:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/VM CP commands (LOGON)? To solve your problem you need to review the CP XAUTOLOG command and place the IPL xxx in the profile exec for your linux guest. Thanks, Detro Senior IT Specialist 1177 S. Beltline Rd, Coppell, TX 75019 Internal Mail Stop: 71-01-3001O Phone: 469-549-8174 (t/l603) Fax: 469-549-8149 (t/l 603) [EMAIL PROTECTED] Global Solution Centerhttp://w3.ibm.com/support/stss/gesc.html (GSC) [cid:image001.jpg@01C903A2.D5ADC410]http://www.ibm.com/ondemand [cid:image002.jpg@01C903A2.D5ADC410] From: Tom Burkholder [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Date: 08/21/08 02:14 PM Subject: z/VM CP commands (LOGON)? z/VM'ers, After a few searches and actually scanning the CP commands and utilities manual, hopefully I can get some help with this z/VM related question. If I have a z/linux guest called ztrash01, I can logon to z/VM as ztrash01, IPL xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console from my 3270 terminal session, enter logoff. No problem. The why I want to do the following is to potentially stress test some applications by forcing off a z/Linux guest (crash) and then eventually trying to automate and re-IPL, but first I gotta be able to do some basic z/VM CP commands below. I read the LOGON in the CP commands and Utilities reference, but I'm doing something wrong (other than trying to trash and stress test my guest). I'm still playing with test systems, but from a z/VM CP perspective, for now the Linux guest ztrash01 is shutdown and halted, but ztrash01 is still logged onto z/VM. 1. If I'm logged on as operator to z/VM, I can issue CP command q n and see that guest ztrash01 is logged onto z/VM and DSC (disconnected). 2. Still as operator, I can issued CP command force ztrash01 logoff immed and this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR) 3. Still as operator, a q n verifies that the guest is gone (i.e. logged off z/VM) 4. Now, as operator, instead of going to another z/VM terminal session and logging on as ztrash01, still as operator, I would like to cause the guest ztrash01 to logon (and eventually IPL). To cause the IPL of guest ztrash01 at LOGON, I believe I can put that in the PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the guest to be logged on (opposite of FORCE) while being logged on to z/VM as operator? Thanks in advance, Tom B. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- 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: Root filesystem error switches to ReadOnly
On 8/21/2008 at 5:22 PM, in message [EMAIL PROTECTED], Rob van der Heij [EMAIL PROTECTED] wrote: I expect the problem is using 'dd' for the copying may not get the magic signatures that makes the disk a CDL format, so the driver ends up seeing it as LDL and gets things misaligned. No, that shouldn't happen if they're using dd against the whole volume device node, such as /dev/dasda. If they're doing it against a partition at a time (/dev/dasda1), that should work also, since they'd need to have created the partitions on the target volume to be able to copy them over. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Distribution ages, was: Linux version
Evans, Kevin R wrote: BE to re-institute our own recovery stuff). We even had pre-production 3270 screens g. We had a few 2260s on one system; 3270s hadn't been invented yet. I know, this dates me a lot g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version OS/VS1? VS1=MFT+VS I should have mentioned PCP. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Distribution ages, was: Linux version
Evans, Kevin R wrote: Mine was 360/50 and a 360/30. When the 30 was replaced with a 2nd 50, we ran the 30 for about a month outside of the computer room (with no air conditioning other than opening the windows) with IBMs blessing. 2311 and 2314 disk drives with a paper tape reader that had a flippable I worked for Amdahl for a while in the late 80s. One of our clients STILL used paper tape. Equipment in the field recorded data to paper tape, and the rolls were read by the computer system running MVS/XA. table so that the paper tapes we got in from construction sites could be read either started at the outside or the inside of the PT spool. 2540 card reader/puches and 1403 printers. Ah, the good ole days.g. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Thursday, August 21, 2008 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version MFT, MVT, then VS1.I was DOS/VS. Installed CICS 1.0 macro level to replace BTAM stuff like 40407F7F2DOLDER THAN THE HILLS. My new 360/30 had a DISK drive (no more TOS). DFHPCT, DFHPPT, DFHFCT, DFHTCT etc in CICS. We had a very buggy BTAM application written to APS[1] (Australian Public Service) standards. I don't think anyone else followed them, and it was wholly incompatible with TCAM (no VTAM yet), though I think I could write a bridge now. I got it working well enough to determine that the network (we had remote terminals) was never going to support enquiry traffic, it was way too slow. Later, we revisited the application and I chose to write using EXCP because: 1. BTAM didn't offer a lot. 2. Our real terminals emulated ASCII 3270s. 3. Our test terminals were real EBCDIC 3270s. 4. Supporting both code sets was easy using EXCP, not so using BTAM. It was very educational. [1] This was my introduction to communications. I was a raw CSO1, the technical expert was a CSO4. I didn't really like to bother him with my trivial problems. There's a lesson there for management everywhere. Oh, the test environment was someone else's 168 running MVS, the production environment our 145 with VS1. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Root filesystem error switches to ReadOnly
Mark Post wrote: On 8/21/2008 at 5:22 PM, in message [EMAIL PROTECTED], Rob van der Heij [EMAIL PROTECTED] wrote: I expect the problem is using 'dd' for the copying may not get the magic signatures that makes the disk a CDL format, so the driver ends up seeing it as LDL and gets things misaligned. No, that shouldn't happen if they're using dd against the whole volume device node, such as /dev/dasda. If they're doing it against a partition at a time (/dev/dasda1), that should work also, since they'd need to have created the partitions on the target volume to be able to copy them over. Done carefully, one can resize partitions copying with dd. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Distribution ages, was: Linux version
Evans, Kevin R wrote: This is getting like Monty Python g. One guy says When we were young, we used to eat the leather from our shoes. The other guy says You had shoes?. OS/360 - some of you guys make me feel young, thanks ;-) You must be around 60, either that or your systems were old at the time ;-) I started on 370s (135,138,145,148,158,168 - 3033, 4341, 3081, 3084 etc.) We wrote our assembler on punched cards and were happy to do so, And you try and tell the young people of today that . they won't believe you. Python: http://www.phespirit.info/montypython/four_yorkshiremen.htm mark -- 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
