Sponsored Content
Top Forums Shell Programming and Scripting Inputs required in decoding file on AIX- executable (RISC System/6000) or object module not stripped Post 302988675 by bakunin on Friday 30th of December 2016 06:16:06 PM
Old 12-30-2016
Quote:
Originally Posted by venkatesh17
There is a script of type "executable (RISC System/6000) or object module not stripped" on AIX and we are unable to read the contents of it.
This is because there is nothing to read in it. This is a binary file (in the so-called XCOFF-format) and it is most probably the result of a compiler compiling some code written in a normal computer language (C, C++, FORTRAN, or whatever) into an executable file.

If this program (not script) is the result of some in-house development at your site you should be able to find the source code of it somewhere. Use the respective compiler on Linux (mostly gcc, but maybe something else) and compile it there, then you will have a Linux version of the program. (Well, in principle. There are many things that could go wrong, but in theory this will work).

Quote:
Originally Posted by venkatesh17
Is there a way to read the contents of the file on AIX, so that we can rewrite the code in Linux.
No. You can use the strings-program as suggested to find out more details about the program, but that's it. Even if you succeed in reading the program it won't help you because on Linux you will not need this but a different program (that is: the different output the compiler on Linux will produce from the same source code) todo the same thing on Linux which this program did on AIX.

If you have no access to the source code at all you could try to decompile it (notice that there might be copyright issues involved, clear that first), but this is something you need an expert for and even then it might not succeed at all. Even if it does it will be a complicated process.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

Ibm Risc/6000 Os

:o Unix Sirs, :eek:RE: IBM RISC/6000 1990 Used on Application: Image buffer: 3D "Catia" (3D "Autocad" sim.) engineering C.A.D. Written by Deso. Cash prior to main frame dump:cool: * :oCan I purchase the oem operating system from you unix people? :cool: ... (1 Reply)
Discussion started by: penguins
1 Replies

2. AIX

PCI Ethernet Cards for IBM RISC 6000 - B50's

I am trying to find PCI Ethernet cards that are compatible with the IBM RISC 6000 - B50 Power PC. None of the regular NIC's seem to have AIX drivers. Does anyone know of AIX drivers for standard PCI Ethernet NIC's or a non IBM NIC that works with the Model B50 at 10/100 MB ? (0 Replies)
Discussion started by: rahe
0 Replies

3. Programming

dbx error ("Executable contains object file compiled on ...")

Hi, We are trying to run dbx on a core file for which we have the original executable and libs, but not the source / object tree. We have recompiled the objects from the original source, but dbx complains that they were compiled at a different time, and refuses to read them: Object file:... (0 Replies)
Discussion started by: Sabari Nath S
0 Replies

4. UNIX for Dummies Questions & Answers

0403-015 - Cannot access a required executable file. It is in use.

How is this error resolved please? I'm just trying to run a shell script and am getting this error. All file permissions are fine. Thanks (0 Replies)
Discussion started by: miwinter
0 Replies

5. AIX

Fibre channel drivers on RS/6000 aix 5L

Want to configure IBM raid strorage but the aix 5L cds do not have the drivers for the fibre channels. The machine is RS/6000. I have gone to IBM downlaodable sites but i can't find the drivers? help pliz:mad: (4 Replies)
Discussion started by: Zim-Aix-Guru
4 Replies

6. UNIX for Advanced & Expert Users

How can i read a non text file in unix - ELF-64 executable object file - IA64

The binary file is ELF-64 executable object file - IA64. How i know that the source is Is there any comamnd in unix i can read these kind of files or use a thirty party software? Thanks for your help (8 Replies)
Discussion started by: alexcol
8 Replies

7. Shell Programming and Scripting

Can't locate loadable object for module GD in @INC

I am trying to use the GD module on a on Unix Solaris environment machine by including gd.pm from a temporary location but I am receiving the following error: perl -w polyline.pl > imageoutput.png Can't locate loadable object for module GD in @INC (@INC contains:... (1 Reply)
Discussion started by: wadhwa.pooja
1 Replies

8. Linux

"not stripped" executable file

Hi, What exactly is meant by a "not stripped" executable file? (4 Replies)
Discussion started by: bruceblacklaws
4 Replies

9. UNIX for Advanced & Expert Users

Can AIX 5.3 - 6 Boot From HP EVA 6000 SAN

Hi There, Has anyone had any luck with or know how to get AIX 5+ to boot from a HP EVA 6000 SAN? The servers used here will be P Class Blades My initial searches on this so far did not bring results so I am guessing this may not be possible on HP SAN's but please let me know if I am... (0 Replies)
Discussion started by: fazzasx
0 Replies

10. Shell Programming and Scripting

Can't locate loadable object for module IO::Tty

I am getting this error: Can't locate loadable object for module IO::Tty in @INC (@INC contains: /production/79p/perl5/lib/site_perl/5.28.0/x86_64-linux /production/79p/perl5/lib/site_perl/5.28.0 /production/79p/perl5/lib/5.28.0/x86_64-linux /production/79p/perl5/lib/5.28.0... (2 Replies)
Discussion started by: mrn6430
2 Replies
FCASPLIT(1)						      General Commands Manual						       FCASPLIT(1)

NAME
fcasplit - tool to split source code into separate per-routine files SYNOPSIS
fcasplit [ -f nmft ] [ -c nmcc ] [ -a nmas ] [-noh] [-log] [ +fo incf ] [ +co incc ] [ +ao incs ] [ -fo optf ] [ -co optc ] [ -ao opts ] file.ext fcasplit file.ext [ fca_n ] [ optf [ optc [ opts [ nmft [ nmcc [ nmas ]]]]]] DESCRIPTION
fcasplit, used with a command line of either form shown above, splits file file.ext having a mixture of FORTRAN / C / assembler routines into separate files n.f or n.c or n.s, "n" being the name of each routine, creating at the same time a shell script file.shfca and a Make file file.mkfca either of which can be used to compile all routines individually. All new files are generated in the current directory, even if the original file.ext is in a different location. NOTE that the program does not work on source code written without having it in mind, since fcasplit looks for special identifying lines in comments of the source code in the original file, as noted below. It is able to operate, for instance, on source code output by nypatchy. Defaults are defined in fcasplit for the names by which the compilers are called in the generated shell script and Makefile; with the -f, -c, -a options they could be changed. In Debian GNU/Linux, these defaults are gcc for the C compiler, gfortran for the FORTRAN compiler, and as for the assembler. Defaults are also defined for the options with which they are called; with the -fo, -co, -ao options they can be re-defined; with the +fo, +co, +ao options they can be incremented. In Debian GNU/Linux, these defaults are "-c -g -O2" for the C compiler, "-c -g -O2 -fno-auto- matic" for the FORTRAN compiler, and "" (i.e., no flags) for the assembler. To be backward compatible these options can also be specified by the positional parameters after the file-name (as in the second form of the command shown above). If the -noh option is given (or if the first parameter after the file-name is "fca_n") the identifying header line of each routine is not written out. If the -log option is given the name of each routine is printed on standard output. FILE FORMAT
Each routine in the original file file.ext must start with an identifying line: "CDECK ID>, " in cols. 1-12 for FORTRAN "/*DECK ID>, " in cols. 1-12 for C ";DECK ID>, " in cols. 1-12 for assembler "DECK ID>, " in cols. 2-12 or "DECK ID>, " in cols. 3-12 for anything else "name" in cols. 13-40 gives the name In the last two cases, or if "name" contains an extension, the file created will be "name" without extension .f, .c or .s added to it and without an entry into the script. A trailing blank terminates the name, symbol . followed by blank also terminates, symbols ; < # ! all terminate, symbol */ also terminates. SEE ALSO
nycheck(1), nydiff(1), nyindex(1), nylist(1), nymerge(1), nypatchy(1), nyshell(1), nysynopt(1), nytidy(1), yexpand(1) The reference manual for the Nypatchy suite of programs is available in compressed PostScript format at the following URL: http://wwwasdoc.web.cern.ch/wwwasdoc/psdir/p5refman.ps.gz AUTHOR
This manual page was written by Kevin McCarty <kmccarty@debian.org> for the Debian GNU/Linux system (but may be used by others), based on the help information printed by the fcasplit program when called with no arguments. Both fcasplit and this man page are licensed under the GNU General Public License, version 2 or later (at your choice). COPYRIGHT
Copyright (C) CERN, 1996, 1999 and Kevin B. McCarty, 2008. Mar 12, 2008 FCASPLIT(1)
All times are GMT -4. The time now is 10:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy