At our shop we primarily use z/OS for production. We have complete DR
routine software and we regularly have DR drills at least 4 times a year.
With that in mind I found it easier to backup our VM using what is already
in place for z/OS, namely varying the VM DASD online to our z/OS
production
raid-disk 3
I looked in the /var/log/messages but it had nothing that would indicate
would had failed.
Any help with this would be greatly appreciated.
Thanks,
Greg Evans
I am running TurboLinux 6.5 fot Z/OS. I have recently added and formatted
a new DASD to the Linux guest and I have been attempting to copy my /usr
directory to the new disk to give it more space. In the course of doing
this I have to copy all of the files and dir's on the current /usr to the
new
: unable to
read ino
de block - inode=71562, block=131264
Has anyone had a similar experience and if so how did you correct it.
Thanks, Greg Evans
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email
Is it the case that IBM will be coming out with a version of CICS that
will run on SUSe Linux ?
I have searched the web, however I have only gotten hits for CICS
Transaction Gateway.
If you know otherwise please share that information. Thanks, Greg Evans
I have been running TurboLinux 6.5 on our z800 processor for the last 5
months. However I cannot seem to find a good XMCP based server.The
X-windows server that came with the distribution seemed to work for a
while but was very limited. I need to know if there is anything compatible
that has
I have found out that our 9672 processor is actually a G4 class. Does
anyone have any info on microcode levels for a G4? The only thing in the
pre-install manual is pertinent to G4/G5 and the Multiprise 3000 series.
- Forwarded by Greg Evans/MOIS/Phila on 10/15/02 01:10 PM -
Greg
I have been trying to install TurboLinux 6.5 on our 9762-R35 (G4) box with
no success.
I made the IPL tape using the free distribution following the
documentation to the letter.
I wrote the 3 datasets LINUX390.IMAGE.TXT, LINUX390.PARM.LINE and
LINUX390.INITRD.TXT to a 3480 cartridge using
to the OS
messages ICON either. I know this is not a case of the drive not being
configured to the LPAR, I have been there already (thanks).If anyone
else had this experience with TurboLinux please let me know how you
managed to get around it.
Thank You
Greg Evans
