OK, now i got it: you were trying to clone a server. This is far easier done (and much more reliably so) by using the following information:
Investigate the mksysb command. It creates a backup image of a rootvg, but enriched by boot code and other information necessary to isntall a system from this image. You need a tape drive or disk space outisde of your rootvg to do it.
Result of the mksysb is a system image, basically a file. If it is written to some special devices (DVD, tape) it is bootable and you can use it on another system (doesn't even have to be identical, just sufficiently similar) to boot this and install it to a copy of the system from which you took it.
If you use any other device as a target (including a disk file) this will not be bootable by itself so you will need a boot media to boot the system and then you are able to still use the file as a source of installation arriving at the sasme result as above.
Hi all,
I have encountered the issue with the hard disk, the disk is failed and need to replace by the new one.
As my understanding, this is just to take out the failed disk and insert the new ones, and that's all.
But the third party hardware vendor said, there should be another procedure... (9 Replies)
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
in red hat 4, 5 any one know any commands or any scritps to monitor HP DL 380 G5/6 server and trigger alarm when hard disk failed.
thanks for all support
---------- Post updated at 02:45 PM ---------- Previous update was at 12:00 PM ----------
does HP ProLiant Support Pack support is... (4 Replies)
Continuing saga of working on making a retail store more robust by creating a backup clone of the main server, a 1995 era :eek: PC running SCO OpenServer 5.0.0b and a discontinued Point of Sales (POS) software system.
I have a PC of the same make and model. The CPU runs faster and it has a... (5 Replies)
Hi.
We tried cloning a SCO Unix hard disk using Norton Ghost.
However, the new cloned hard disk encounter booting problem.
What possibly go wrong? (1 Reply)
A sparc server has a new SCSI hard disk added and labeled by the engineer, but they need to be formatted identically to an existing disk (c4t0d0). You decide to script the process and run from the command line without interaction.
I know that the following command line must be achieve this.
#... (3 Replies)
Hi Engg. ! :mad:
I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Hi,
Other than df -k, is there any command that will tell me all physical hard drives installed on the system as well as the size of each one?
I'm using AIX 5.1
Thanks, (3 Replies)
PERLOS400(1) Perl Programmers Reference Guide PERLOS400(1)NAME
perlos400 - Perl version 5 on OS/400
DESCRIPTION
This document describes various features of IBM's OS/400 operating system that will affect how Perl version 5 (hereafter just Perl) is
compiled and/or runs.
By far the easiest way to build Perl for OS/400 is to use the PASE (Portable Application Solutions Environment), for more information see
<http://www.iseries.ibm.com/developer/factory/pase/index.html> This environment allows one to use AIX APIs while programming, and it
provides a runtime that allows AIX binaries to execute directly on the PowerPC iSeries.
Compiling Perl for OS/400 PASE
The recommended way to build Perl for the OS/400 PASE is to build the Perl 5 source code (release 5.8.1 or later) under AIX.
The trick is to give a special parameter to the Configure shell script when running it on AIX:
sh Configure -DPASE ...
The default installation directory of Perl under PASE is /QOpenSys/perl. This can be modified if needed with Configure parameter
-Dprefix=/some/dir.
Starting from OS/400 V5R2 the IBM Visual Age compiler is supported on OS/400 PASE, so it is possible to build Perl natively on OS/400. The
easier way, however, is to compile in AIX, as just described.
If you don't want to install the compiled Perl in AIX into /QOpenSys (for packaging it before copying it to PASE), you can use a Configure
parameter: -Dinstallprefix=/tmp/QOpenSys/perl. This will cause the "make install" to install everything into that directory, while the
installed files still think they are (will be) in /QOpenSys/perl.
If building natively on PASE, please do the build under the /QOpenSys directory, since Perl is happier when built on a case sensitive
filesystem.
Installing Perl in OS/400 PASE
If you are compiling on AIX, simply do a "make install" on the AIX box. Once the install finishes, tar up the /QOpenSys/perl directory.
Transfer the tarball to the OS/400 using FTP with the following commands:
> binary
> site namefmt 1
> put perl.tar /QOpenSys
Once you have it on, simply bring up a PASE shell and extract the tarball.
If you are compiling in PASE, then "make install" is the only thing you will need to do.
The default path for perl binary is /QOpenSys/perl/bin/perl. You'll want to symlink /QOpenSys/usr/bin/perl to this file so you don't have
to modify your path.
Using Perl in OS/400 PASE
Perl in PASE may be used in the same manner as you would use Perl on AIX.
Scripts starting with #!/usr/bin/perl should work if you have /QOpenSys/usr/bin/perl symlinked to your perl binary. This will not work if
you've done a setuid/setgid or have environment variable PASE_EXEC_QOPENSYS="N". If you have V5R1, you'll need to get the latest PTFs to
have this feature. Scripts starting with #!/QOpenSys/perl/bin/perl should always work.
Known Problems
When compiling in PASE, there is no "oslevel" command. Therefore, you may want to create a script called "oslevel" that echoes the level
of AIX that your version of PASE runtime supports. If you're unsure, consult your documentation or use "4.3.3.0".
If you have test cases that fail, check for the existence of spool files. The test case may be trying to use a syscall that is not
implemented in PASE. To avoid the SIGILL, try setting the PASE_SYSCALL_NOSIGILL environment variable or have a handler for the SIGILL. If
you can compile programs for PASE, run the config script and edit config.sh when it gives you the option. If you want to remove fchdir(),
which isn't implement in V5R1, simply change the line that says:
d_fchdir='define'
to
d_fchdir='undef'
and then compile Perl. The places where fchdir() is used have alternatives for systems that do not have fchdir() available.
Perl on ILE
There exists a port of Perl to the ILE environment. This port, however, is based quite an old release of Perl, Perl 5.00502 (August 1998).
(As of July 2002 the latest release of Perl is 5.8.0, and even 5.6.1 has been out since April 2001.) If you need to run Perl on ILE,
though, you may need this older port: <http://www.cpan.org/ports/#os400> Note that any Perl release later than 5.00502 has not been ported
to ILE.
If you need to use Perl in the ILE environment, you may want to consider using Qp2RunPase() to call the PASE version of Perl.
AUTHORS
Jarkko Hietaniemi <jhi@iki.fi> Bryan Logan <bryanlog@us.ibm.com> David Larson <larson1@us.ibm.com>
perl v5.16.2 2012-10-11 PERLOS400(1)