IMS eWay

Hi, these are the settings we're using to connect to IMS:

IRM_LEN: 80

IRM_ID: *SAMPLE*

IRM_TIMER: .25SEC

IRM_SOCT: Persistent

IRM_CLIENTID: CAPS*

IRM_F1: NO_MFS

IRM_F2: COMMIT_MODE_1

IRM_F3: SYNC_LEVEL_NONE

IRM_F4: NO_ACK

IRM_F5: No_auto_flow

IRM_TRNCOD: (empty, we set it in the JCD code)

IRM_TRNCOD_SRC: Cfg

IRM_DESTID: (depends on your IMS Connect settings)

IRM_LTERM: (empty)

IRM_RACF_GRNAME: (one empty space)

IRM_RACF_USERID: (we set it in the JCD code)

IRM_RACF_PW: (again, we set it in the JCD code)

IRM_HEADER_ENCODING: iso-8859-1

SEND_DATA_ENCODING: NO_TRANSLATION

REPLY_DATA_ENCODING: iso-8859-1

Now, about that single whitespace: when you open a managed connection, the eWay will try to match an existing open connection that can be reused by using the RACF_GRNAME and RACF_USERID (besides using the IMS Connect IP address). If you leave any of these empty, the eWay interprets the values as null, but the code doesn't account for null values so you get a NullPointerException. The trick is to put a whitespace in these fields.

Hope it helps,

Celso

Cliffb53a at 2007-7-9 5:08:45 >

Hi,

I can execute a transaction via IMS terminal but if sent via IMS eWay thru IMS Connect I get a DFS1292E SECURITY VIOLATION message from IMS. I use the same userid and password for both methods, yet it gives me an error if I send via IMS Connect.

Anyone encounter this before?

Thanks.

chiewsta at 2007-7-9 5:08:45 >