IBM AIX5L, AIX 4.3 manual Shell scripts, CDE or TCL/Tk

Page 22

3.1 Shell scripts

With AIX 5L, there are a few functional enhancements of ksh, the Korn shell. The default shell is still /usr/bin/ksh. It is hard linked to /usr/bin/psh, /usr/bin/sh, and /usr/bin/tsh. It is an implementation of the 1988 version of the Korn Shell, enhanced to be POSIX compliant. In addition to this shell, an unmodified version of the 1993 version of ksh is supplied as /usr/bin/ksh93. This version is also POSIX compliant. For a detailed description of the enhancements, refer to the KornShell Web site at:

http://www.kornshell.com

One important issue is that the shell attribute is changed to the root user. In AIX Version 4.3 it is /bin/ksh, which means it relies on the link between /bin and /usr/bin. This could lead to boot problems because of the unavailability of a shell. The new shell attribute is /usr/bin/ksh. This means that as part of your migration task, you need to verify the compatibility of your shell scripts.

3.2 CDE or TCL/Tk

To prepare the new AIX 5L environment for the workstation, all user-created Shell scripts, CDE (Common Desktop Environment) enhancements, or TCL/Tk (Tool Command Language/ Toolkit) programs should be transferred to a new installed AIX 5L machine for verification. Depending on the complexity and history of the programs, additional filesets are needed to install, for example, compatibility libraries for X11R5 or older versions.

For user-written C, C++, or FORTRAN programs a functionality check is required to ensure that all required libraries are installed on the machine. It is also a good time to recompile the source programs in the new AIX 5L environment.

During the verification process, it is a good time to define a specific environment to store all necessary software in a common installation filetree. In our example the path /usr/mylpp represents a single file system with several subdirectories for different purposes. The advantage in using this environment is that all programs are located in a common path and for future changes the entire file system could be replaced. See Table 3-1.

At the end of all installation and verification tasks, the migrated machine represents the "master client" or the "reference client". All future changes will be checked on the "master or reference client" before distribution of updates to other servers.

/

var/

 

DassaultSystem es/

 

opt/

 

lpp/

 

spaceball/

 

 

 

usr/

 

 

m ylpp/

 

 

TCL/Tk/

 

 

 

 

 

 

 

 

tm p/

 

opt/

 

scripts/

 

 

 

 

 

 

 

 

Figure 3-1 Common filetree example

12CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Image 22
Contents IBM Page International Technical Support Organization First Edition December Contents Abbreviations and acronyms Copyright License Trademarks Set ++Preface Team that wrote this RedpaperBecome a published author Comments welcomeSupported hardware Supported hardware for AIX 5L Supported hardware for Catia and Enovia Supported software levels for Catia and Enovia3lists the minimum required software levels for Enovia Migration methods Reasons to migrate Definition of migrationMigration methods Migration installation New and complete overwrite installationPreservation installation Migration sourcesAlternate disk migration Network Installation ManagementAIX and compiler CDs Catia and Enova migration AIX 4.3 to AIX 5L Version Planning the migration Shell scripts CDE or TCL/TkWorkstation Last updated Version MicrocodeInstallation preparation IBM Sserver pSeries Customer-Managed MicrocodeAIX fix delivery center AIX and compiler runtime download Web sites3 C++ runtime Catia and Enova migration AIX 4.3 to AIX 5L Version Starting the migration Migration using NIM Hardware layoutWebSM NIM launch panel Accept new license agreement checkmark Migration experiences Migration experiences for AIX Post-migration tasksUmlaute on a German language keyboard Netscape cannot be launched Activating spaceball or spacemouseDocumentation cannot be launched AIX CDE login hang Migration experiences for Catia and EnoviaAppendix A. Fileset and bundle information AIX Version 4.3.3 ML10 filesets Example A-1 lslpp -L from AIX VersionAppendix A. Fileset and bundle information Catia and Enova migration AIX 4.3 to AIX 5L Version Appendix A. Fileset and bundle information ISA Appendix A. Fileset and bundle information AIX 5L Version 5.1 ML05 filesets Example A-2 lslpp -L from AIX 5L VersionAppendix A. Fileset and bundle information Catia and Enova migration AIX 4.3 to AIX 5L Version Appendix A. Fileset and bundle information Catia and Enova migration AIX 4.3 to AIX 5L Version Appendix A. Fileset and bundle information Catia and Enova migration AIX 4.3 to AIX 5L Version AIX 5L Version 5.1 Bundle Example A-3 AIX 5L Version 5.1 Bundle fileCatia and Enova migration AIX 4.3 to AIX 5L Version PEXPHIGS.dev.pci.14107001 Catia and Enova migration AIX 4.3 to AIX 5L Version Appendix B. Checklists Client checklist EnvironmentServer checklist Catia and Enova migration AIX 4.3 to AIX 5L Version Abbreviations and acronyms Catia and Enova migration AIX 4.3 to AIX 5L Version Other publications IBM RedbooksOnline resources How to get IBM Redbooks Help from IBMPage Redpaper