Author |
Message |
Topic: [*REQSTS*40, *REQSTS*233] |
chiewst
Replies: 2
Views: 3349
|
Forum: IMS Posted: Mon May 25, 2009 9:55 pm Subject: [*REQSTS*40, *REQSTS*233] |
Thanks. Your reply lead me to the IMS Connect manuals. The '40' meant the IRM_TIMER value has expired, and the '233' was the IRM_TIMER value.
Sorry forgot to mention that I was using IMSConnect. |
Topic: [*REQSTS*40, *REQSTS*233] |
chiewst
Replies: 2
Views: 3349
|
Forum: IMS Posted: Mon May 25, 2009 7:10 pm Subject: [*REQSTS*40, *REQSTS*233] |
I intermittently get this response from an IMS transaction. I've looked several IMS manuals but can;t find an exact definition of these codes. Anyone knows what it means or can point me to a manual?
... |
Topic: Is IMS Connect integrated into IMS Version 9? |
chiewst
Replies: 1
Views: 1468
|
Forum: IMS Posted: Mon Feb 26, 2007 9:47 pm Subject: Is IMS Connect integrated into IMS Version 9? |
I read in manuals that : (quote)
"IMS Version 9 provides an integrated IMS Connect function, which offers a functional replacement for the IMS Connect tool (program number 5655-K52). In this i ... |
Topic: DFS1292E SECURITY VIOLATION issue |
chiewst
Replies: 2
Views: 6441
|
Forum: IMS Posted: Fri Feb 16, 2007 1:01 am Subject: DFS1292E SECURITY VIOLATION issue |
Hi,
I'm using Sun's JCAPS integration suite to connect to IMS via IMS eWay and IMS Connect software.
I have an issue where I can execute a transaction via IMS terminal but I get a DFS1292E SECURIT ... |
|