Woo Hoo good news!
But I'll save it till the end.
First of all, bjverzal, thank-you for posting however the process still gets truncated.
guggach, thank-you as well for your input and you are correct. ps does have a limit but I'm not sure if it is 80 chars since my post above displays a lot more than 80 chars. Having said that, If I run the ps -efl|fold (that bjverzal suggested), it wraps at 80 chars and displays a lot more information but I still run into the truncated process issue. I haven't bothered to count every single character to see what the limit is exactly. It wraps at 80 because the COLUMNS environment parameter is set to 80 by default. (Also, I think you are running on Solaris if you use /usr/ucb/ps (?), on AIX it is in /usr/bin/ps and I've seen different behavior between different flavors of *nix with regard to ps)
Also, I agree that having the short path in the command whould help me out alot and if I were able to manipulate the command, it would proabably show the whole thing but I don't have access to the command or most of it's parameters so it's not possible to change the command and use shorter paths.
So after all that and three days of testing, I finally got it to work soooooooo now on to the good news........
Rob was on a different track. Instead of using the built in "ps" command that comes with AIX, he suggested using a perl function that accesses the internal process table directly. (Thank-you for the sample script, it still works like a charm with perl 5.8 and Proc:

rocessTable-0.39).
So here's my final analysis:
PROBLEM: While running WebSphere 5 on AIX 5.2, I noticed that while doing a ps -ef|grep <pid>, some pids were truncated and I couldn't see the entire command. Unfortunately, some important information is at the end of the process and I need that information.
SOLUTION: Use the Proc:

rocessTable perl module and do not use the built-in ps command with AIX. ps has a limit which causes the display of the command to be truncated.
HOW TO GET THERE:
1. Ensure you have a c compiler (with cc_r and xlc). The compile process for Proc:

rocessTable requires both of them.
2. I was running perl 5.6.0 and wasn't having a lot of luck compiling the Proc:

rocessTable module. I had to download perl 5.8.0-2 and it worked after I changed a few of the links in /usr/bin (like perl, perldoc, perlcc, and perlbug to perl's default install directory: /opt/freeware/bin/). So I suggest downloading perl 5.8 but other people may get other versions working. In the end, you need perl
3. Download and compile the Proc:

rocessTable module. If you read the README, it will tell you everything you need to do to compile it.
4. Take Rod's code above and put it into a file. I called mine test.pl and make sure it is executable.
5. Now to compare, run ps -ef|grep <pid that has a really long command line>. For example, if I run "ps -ef|grep 42550, I get (notice it's truncated)
webadmin 42550 22226 0 06:03:57 - 0:37 /usr/WebSphere/AppServer5/java/bin/java -Xbootclasspath/p:/usr/WebSphere/AppServer5/java/jre/lib/ext/ibmorb.jar:/usr/bsiapps/coonuans/support/jsseExtended.jar -Dcom.ibm.CORBA.ConfigURL=file:/usr/WebSphere/AppServer5/properties/sas.client.props -Dcom.ibm.SOAP.ConfigURL=file:/usr/WebSphere/AppServer5/properties/soap.client.props -Dcom.ibm.CORBA.RasManager=com.ibm.websphere.ras.WsOrbRasManager -Dwas.install.root=/usr/WebSphere/AppServer5 -Dws.ext.dirs=/usr/WebSphere/AppServer5/java/lib:/usr/WebSphere/AppServer5/classes:/usr/WebSphere/AppServer5/lib:/usr/WebSphere/AppServer5/lib/ext:/usr/WebSphere/AppServer5/web/help:/usr/WebSphere/AppServer5/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime:/usr/mqm/java/lib:/usr/opt/wemps/lib -Djava.security.auth.login.config=/usr/WebSphere/AppServer5/properties/wsjaas_client.conf -Dcom.ibm.CORBA.BootstrapHost= -Dcom.ibm.CORBA.BootstrapPort= -Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory -classpath /usr/WebSphere/AppServer5/properties:/usr/WebSphere/AppServer5/lib/bootstrap.jar:/usr/WebSphere/AppServer5/lib/j2ee.jar:/usr/WebSphere/AppServer5/lib/lmproxy.jar:/usr/WebSphere/AppServer5/lib/urlprotocols.jar:/usr/WebSphere/AppServer5/lib/urlprotocols.jar com.ibm.ws.bootstrap.WSLauncher com.ibm.websphere.client.applicationclient.launchClient /usr/bsiapps/coonuans/ear/CooNuans.ear -CCDjavax.net.ssl.trustStore=/usr/bsiapps/coonuans/resources/bsicerts -CCDjavax.net.ssl.keyStorePassword=bsi4admin -CCBootstrapPort=2816 -CCclasspath=/usr/bsiapps/coonuans/resources:/usr/bsiapps/coo/resources:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/jms.jar:usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java:/usr/WebSphere/AppServer5/lib/websphere.jar:/usr/WebSphere/AppServer5/lib/ujc.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/jms.jar:usr/mqm/java/lib/jndi
6. Now run ./test.pl <pid that has a really long cmd line>. For example, I ran ./test.pl 42550 and here's what I got: (notice it isn't truncated)
42550: /usr/WebSphere/AppServer5/java/bin/java -Xbootclasspath/p:/usr/WebSphere/AppServer5/java/jre/lib/ext/ibmorb.jar:/usr/bsiapps/coonuans/support/jsseExtended.jar -Dcom.ibm.CORBA.ConfigURL=file:/usr/WebSphere/AppServer5/properties/sas.client.props -Dcom.ibm.SOAP.ConfigURL=file:/usr/WebSphere/AppServer5/properties/soap.client.props -Dcom.ibm.CORBA.RasManager=com.ibm.websphere.ras.WsOrbRasManager -Dwas.install.root=/usr/WebSphere/AppServer5 -Dws.ext.dirs=/usr/WebSphere/AppServer5/java/lib:/usr/WebSphere/AppServer5/classes:/usr/WebSphere/AppServer5/lib:/usr/WebSphere/AppServer5/lib/ext:/usr/WebSphere/AppServer5/web/help:/usr/WebSphere/AppServer5/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime:/usr/mqm/java/lib:/usr/opt/wemps/lib -Djava.security.auth.login.config=/usr/WebSphere/AppServer5/properties/wsjaas_client.conf -Dcom.ibm.CORBA.BootstrapHost= -Dcom.ibm.CORBA.BootstrapPort= -Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory -classpath /usr/WebSphere/AppServer5/properties:/usr/WebSphere/AppServer5/lib/bootstrap.jar:/usr/WebSphere/AppServer5/lib/j2ee.jar:/usr/WebSphere/AppServer5/lib/lmproxy.jar:/usr/WebSphere/AppServer5/lib/urlprotocols.jar:/usr/WebSphere/AppServer5/lib/urlprotocols.jar com.ibm.ws.bootstrap.WSLauncher com.ibm.websphere.client.applicationclient.launchClient /usr/bsiapps/coonuans/ear/CooNuans.ear -CCDjavax.net.ssl.trustStore=/usr/bsiapps/coonuans/resources/bsicerts -CCDjavax.net.ssl.keyStorePassword=bsi4admin -CCBootstrapPort=2816 -CCclasspath=/usr/bsiapps/coonuans/resources:/usr/bsiapps/coo/resources:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/jms.jar:usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java:/usr/WebSphere/AppServer5/lib/websphere.jar:/usr/WebSphere/AppServer5/lib/ujc.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/jms.jar:usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java:/usr/WebSphere/AppServer5/lib/websphere.jar:/usr/WebSphere/AppServer5/lib/ujc.jar:/home/dbclient/sqllib/java/db2java.zip:/home/dbclient/sqllib/java/db2jcc.jar:/home/dbclient/sqllib/function:/home/dbclient/sqllib/java/db2jcc_license_cu.jar:. -CCjar=CooNuansServiceAppClient.jar
So in conclusion, it is possible, just a lot of work. I still have a few more hurdles to jump in order to get the username in the output, sorting of pids, displaying of more than one pid, etc, but I think I can handle it from here. Thank-you everyone for your input.