IMS Transaction Manager

Showing 195

Better management of IMS PGM name to Java class name mappings

For IMS Java programms (both Java batch and Java message processing programs) a mapping between IMS program names and Java class names must be provided in IMS PROCLIB member DFSJVMAP. Such a mapping within this member looks like this: IMSJAVPG=com...

about 8 years ago in IMS Transaction Manager / Application Enablement 4 Not under consideration

2 VOTE

Enhance TMRA to get the name of the program performing a callout

APAR PH24630 added the IMS program name of the program performing a callout to the OTMA state header of the callout message. Please add a method to TMRA to get this information from the OTMA state header.

about 4 years ago in IMS Transaction Manager / Open Access TM 1 Future consideration

4 VOTE

IMS JAVA to honor POSIX signaling

POSIX standards allow users to signal to processes. This signaling capability might be honored by the UNIX runtime itself or propagated to the middleware on top of the Unix implementation (or thread). Typically: USS kill -n is the used user-interf...

over 8 years ago in IMS Transaction Manager / Application Enablement 1 Not under consideration

1 VOTE

OTMA Front-End Switch

Our IMS client has following business requirement : DataPower ==> ICON8 ==> IMS A ==> ICON3 ==> IMS B ==> ICON3 ==> IMS A ==> ICON8 ==> DataPower We need the IMS front-end switch function so that the send-receive call from ...

about 2 years ago in IMS Transaction Manager / Open Access TM 1 Not under consideration

5 VOTE

PROCLIM and CPU time

Currently, the cpu time is calculated for each schedule but not for each transaction. For example, if I choose a PROCLIM(5,1), the limit will be 5 x 1 = 5s for the schedule. So IMS stop the schedule if it reaches this limit. But, not necessary if ...

over 10 years ago in IMS Transaction Manager / General TM 1 Not under consideration

3 VOTE

Alter output location for message DFS2014 DFS2015 DFS2016 DFS2017 DFS2018

Alter messages DFS2014 DFS2015 DFS2016 DFS2017 DFS2018 to appear on IMS Control region SYSTEM JOB log as well as the MTO or instead of the MTO

over 6 years ago in IMS Transaction Manager / Message Queue Management 2 Not under consideration

2 VOTE

Improve IMS OTMA resilience in periods of system slowdown.

OTMA storage utilization includes static storage for control blocks and variable storage for various buffers and working storage.The variable storage both varies in size and in duration of allocation, depending on phase of OTMA processing.System s...

over 4 years ago in IMS Transaction Manager / Open Access TM 1 Future consideration

2 VOTE

Stop transactions coming from all sources.

We need a command or procedure to stop transactions comming from all sources, like, prog-to-prog, CICS (APPC), MSC, JAVA, IMS Connect, etc.We can´t use Stop Link(MSC), because another transactions use same link.

over 4 years ago in IMS Transaction Manager / General TM 1 Not under consideration

3 VOTE

IMS OTMA utilization of 64-bit memory for the TPIPES

Each TPIPE control block for an IMS OTMA consumes stores of Extended Private Storage from the IMS CTL region. It has associated other control blocks also allocated at Extended Private Storage.Using 64-bit storage could be a very good enhancement.

almost 7 years ago in IMS Transaction Manager / General TM 2 Not under consideration

3 VOTE