impossible to log region with portal/J

Hello,

My Asset Suite 6.0 region is working fine with FA but not with Portal/J. I got the following error message after waiting a long time:

P/J Fatal Exception Report
==========================

Error occured during handshake PASS,NOLENGTH ?????UOB???O`UOB
com.iint.pjbasic.util.ICGenException: Error occured during handshake PASS,NOLENGTH ?????UOB???O`UOB
at com.iint.pj.ui.core.TCPPPConnection.hostHandShake2(TCPPPConnection.java:453)
at com.iint.pj.ui.core.TCPPPConnection.hostHandShake(TCPPPConnection.java:225)
at com.iint.pj.ui.core.PassPort.send(PassPort.java:417)
at com.iint.pj.ui.core.PassPort.doTransaction(PassPort.java:231)
at com.iint.pj.ui.core.PJLoginPanel.validateLogin(PJLoginPanel.java:812)
at com.iint.pj.ui.core.PJLoginPanel.doLogin(PJLoginPanel.java:644)
at com.iint.pj.ui.core.DelayedAction.run(DelayedAction.java:233)

Maybe somebody had this trouble and know the way to fix it.
Thanks for your help.
Claude.

Portal/J not being able to execute TransID PASS

It appears that Portal/J is not successfully executing TransID PASS. TransID PASS is defined in the Asset Suite region's TRANSACT.INI. Most likely you are unable to get past the Portal/J login panel.

The TransID's simulate IBM mainframe CICS TransID's. TransID PASS is giving access to TIGMAIN.

"NOLENGTH" makes it look like Portal/J is not passing arguements.

Does error message change with a different user ID and password?

If the error message changes after "NOLENGTH" when different values for user ID and password are entered, it might be a code page problem.

Reference: National Language Support Guide.

Java Socket problem perhaps

Make certain the user ID and password are limited to 8 characters. If they are shorter than 8, Portal/J right pads with spaces.

",NOLENGTH " is meaningless.

Not positive about this:
"?????UOB" is the user in ASCII after encryption
"???O`UOB" is the pass in ASCII after encryption

Pretty certain about this:
If Asset Suite is running on a EBCDIC machine, IBM mainframe, the user and pass were converted from ASCII to EBCDIC.

The user and pass were encrypted either from their ASCII or EBCDIC values.

I'm on thin ice here, but given the above, it would appear to be a Java Socket problem. Portal/J is attempting to write to a Socket most likely created via "Socket new_socket = new Socket(host,port)". The writing to the socket is done by sending a byte array to the Socket's OutputStream.

The error message looks pretty reasonable, so it's a guess that the Socket isn't working. Check the host and port.

Hope this helps.

Seen again at client site in January 2010

This error occurred at a client site in January 2010. Turned out to be a combination of not enough COBOL licenses and in what order Asset Suite regions were brought up on 1 server. The failing region was fixed by stopping another region on the same server (freeing licenses) and stopping and starting the failed region.

We didn't see any nice trail of evidence. The Solaris tiglstn processes looked OK for the successful regions and the failing region.