Sponsored Content
Full Discussion: AIX 5.3 migration gone bad
Operating Systems AIX AIX 5.3 migration gone bad Post 302363619 by zxmaus on Tuesday 20th of October 2009 07:37:46 PM
Old 10-20-2009
Hi,
I had similar issues and it turned out to be a defective CD. Do you have the possibility to try another CD set?

Kind regards
zxmaus
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Migration UP-UX scripts to AIX.2

Hello, We would to migrate some shell (korn shell) scripts from HP-UX to AIX 5.2 I would know: - If the HP-UX scripts work as well in AIX? - In no, is there a migration tool to detect incompatible lines in scripts? - How do proceed? Our scripts do: - Loads data in Oracle... (1 Reply)
Discussion started by: P026687
1 Replies

2. UNIX for Dummies Questions & Answers

AIX Migration

Hi , Migrating AIX 4.3.3 ML10 to 5.3 ML1 (retaining 32 bit) after successfully going through 5 of the 5.3 Install CD's. After "All fileset's processed successfully " message I was told that system would reboot and then I would get prompted for setting TERm type ( i have an ascii ibm3151) and... (1 Reply)
Discussion started by: Student37
1 Replies

3. UNIX for Advanced & Expert Users

script migration from HP-UX to AIX

Dear All, What points should i keep in mind while migrating scripts from HP-UX to AIX. Are there any notes available for this? cheers, vishal (1 Reply)
Discussion started by: vishal_ranjan
1 Replies

4. AIX

AIX 5.2 to 5.3 migration

Hello All, We want to upgrade our 44p Model 270 from AIX 5.2 to 5.3. This is a standalone devlopment server but downtime is something we don't want because we have a short development deadline looming. I have no tape drive to make backups to. I myself am a developer and don't have any... (4 Replies)
Discussion started by: Fred Vogel
4 Replies

5. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

Hi, redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages. - My system is ML11 : oslevel –r 4330-11 - But xlC.rte is on wrong version : lslpp -L xlC.rte xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies

6. AIX

what is the procedure of aix migration?

can u tell me about AIX migration and NIM configuration (2 Replies)
Discussion started by: nagchundu
2 Replies

7. Solaris

Migration from AIX to Solaris

Hi All, We are planing to do a migration of our server from AIX 5.3 to Solaris (Linux). But we are not aware about the gap between the both and also impact of that gap. We want to migrate following things, - Common directories setup (like control-M, emer,sysout, and others) - Inbound &... (1 Reply)
Discussion started by: vinod369
1 Replies

8. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

9. Linux

AIX 6.1 to Linux 7.2 migration

Hi, recently we have migrated our current AIX server to Linux, we have lot of shell script, few of them are FTP scripts. we have copied the complete AIX file system to linux 7.2 as it is. could you please highlight what are the things we need to look into it . in AIX we are using .netrc to... (3 Replies)
Discussion started by: Riverstone
3 Replies

10. Solaris

Migration from AIX to Solaris

We are going to work on a project which aims at migrating set of applications from AIX to Solaris. The major portion of the source code involves C, C++, Shell/PERL scripts and Oracle database. We are grateful hear about any commercial tools available for porting AIX to Solaris. Another... (2 Replies)
Discussion started by: Namitap
2 Replies
epm(1)							      Easy Software Products							    epm(1)

NAME
epm - create software packages. SYNOPSIS
epm [ -a architecture ] [ -f format ] [ -g ] [ -k ] [ -m name ] [ -n[mrs] ] [ -s setup.xpm ] [ --depend ] [ --help ] [ --keep-files ] [ --output-dir directory ] [ --setup-image setup.xpm ] [ --setup-program /foo/bar/setup ] [ --setup-types setup.types ] [ -v ] [ name=value ... name=value ] product [ listfile ] DESCRIPTION
epm generates software packages complete with installation, removal, and (if necessary) patch scripts. Unless otherwise specified, the files required for product are read from a file named "product.list". The -a option ("architecture") specifies the actual architecture for the software. Without this option the generic processor architecture is used ("intel", "sparc", "mips", etc.) The -f option ("format") specifies the distribution format: aix Generate an AIX distribution suitable for installation on an AIX system. bsd Generate a BSD distribution suitable for installation on a FreeBSD, NetBSD, or OpenBSD system. deb Generate a Debian distribution suitable for installation on a Debian Linux system. inst, tardist Generate an IRIX distribution suitable for installation on an system running IRIX. lsb, lsb-signed Generate RPM packages for LSB-conforming systems. The lsb-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. native Generate an native distribution. This uses rpm for Linux, inst for IRIX, pkg for Solaris, swinstall for HP-UX, bsd for FreeBSD, Net- BSD, and OpenBSD, and osx for MacOS X. All other operating systems default to the portable format. osx Generate a MacOS X software package. pkg Generate an AT&T software package. These are used primarily under Solaris. portable Generate a portable distribution based on shell scripts and tar files. The resulting distribution is installed and removed the same way on all operating systems. [default] rpm, rpm-signed Generate a Red Hat Package Manager ("RPM") distribution suitable for installation on a Red Hat Linux system. The rpm-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. setld Generate a Tru64 (setld) software distribution. slackware Generate a Slackware Linux software distribution. swinstall, depot Generate a HP-UX software distribution. Executable files in the distribution are normally stripped of debugging information when packaged. To disable this functionality use the -g option. Intermediate (spec, etc.) files used to create the distribution are normally removed after the distribution is created. The -k option keeps these files in the distribution directory. The -s and --setup-image options ("setup") include the ESP Software Wizard with the specified GIF or XPM image file with the distribution. This option is currently only supported by portable and RPM distributions. The --setup-program option specifies the setup executable to use with the distribution. This option is currently only supported by portable distributions. The --setup-types option specifies the setup.types file to include with the distribution. This option is currently only supported by porta- ble distributions. The --output-dir option specifies the directory to place output file into. The default directory is based on the operating system, version, and architecture. The -v option ("verbose") increases the amount of information that is reported. Use multiple v's for more verbose output. The --depend option lists the dependent (source) files for all files in the package. Distributions normally are named "product-version-system-release-machine.ext" and "product-version-system-release-machine-patch.ext" (for patch distributions.) The "system-release-machine" information can be customized or eliminated using the -n option with the appropriate trailing letters. Using -n by itself will remove the "system-release-machine" string from the filename entirely. The "system-release- machine" information can also be customized by using the -m option with an arbitrary string. Debian, IRIX, portable, and Red Hat distributions use the extensions ".deb", ".tardist", "tar.gz", and ".rpm" respectively. LIST FILES
The EPM list file format is now described in the epm.list(5) man page. KNOWN BUGS
EPM does not currently support generation of IRIX software patches. SEE ALSO
epminstall(1) - add a directory, file, or symlink to a list file mkepmlist(1) - make an epm list file from a directory epm.list(5) - epm list file format setup(1) - graphical setup program for the esp package manager COPYRIGHT
Copyright 1999-2008 by Easy Software Products, All Rights Reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. 26 August 2008 ESP Package Manager epm(1)
All times are GMT -4. The time now is 11:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy