Abstract: Techniques are disclosed to transmit arbitrarily large data units for transaction processing in a networked environment. A request is received to store a data unit of a size exceeding an allocated memory address space of a transaction gateway component of the networked environment. A predefined store function, provided by a repository interface component, is invoked to store the data unit to a data repository component of the networked environment and without segmenting the data unit. A repository handle of the stored data unit is identified. A predefined load function, provided by the repository interface component, is invoked to load a portion of the stored data unit, based on the identified repository handle, where the portion is smaller than the stored data unit.

Abstract: Techniques are disclosed to transmit arbitrarily large data units for transaction processing in a networked environment. A request is received to store a data unit of a size exceeding an allocated memory address space of a transaction gateway component of the networked environment. A predefined store function, provided by a repository interface component, is invoked to store the data unit to a data repository component of the networked environment and without segmenting the data unit. A repository handle of the stored data unit is identified. A predefined load function, provided by the repository interface component, is invoked to load a portion of the stored data unit, based on the identified repository handle, where the portion is smaller than the stored data unit.

Abstract: Techniques are disclosed to transmit arbitrarily large data units for transaction processing in a networked environment. A request is received to store a data unit of a size exceeding an allocated memory address space of a transaction gateway component of the networked environment. A predefined store function, provided by a repository interface component, is invoked to store the data unit to a data repository component of the networked environment and without segmenting the data unit. A repository handle of the stored data unit is identified. A predefined load function, provided by the repository interface component, is invoked to load a portion of the stored data unit, based on the identified repository handle, where the portion is smaller than the stored data unit.

Abstract: IMS source code or a graphical object having corresponding IMS source code can be selected within the graphical user interface (GUI). The IMS source code can include a call out to an external application. An IMS call wizard can be invoked, which graphically prompts a user to specify call-out specific conditions for the external application via an ordered series of presented screens. Each screen can present a user with at least one selectable option. User-made selections from earlier ones of the presented screens can change options presented in later ones of the presented screens. IMS code can be generated to call out an external application in accordance with the user selections of the IMS call wizard. The generated IMS code can be inserted into the selected IMS source code. After the insertion, the IMS source code is operable to call out to the external application.

Abstract: A graphical user interface (GUI) of a software development tool can visually compose process flows for enterprise information system (EIS) process flow applications. The GUI can include a canvas that visually shows a set of process flows of a process flow application as a set of interconnected node objects. Each node object can corresponds to a node, which corresponds to at least one process flow. The GUI can also include a graphical compensation tool through which users define and view compensation actions and compensation scopes of process flows of the process flow application, wherein said graphical compensation tool does not require a user to input code text that defining compensation logic of the process flows.

Abstract: An IMS process flow toolset can be used to create an IMS process flow application. The IMS process flow application can include an IMS process flow control program. The IMS process flow control program can embody process flow elements such as business logic and events as well as communication with external non-IMS applications. Both the IMS process flow application and IMS process flow control program can be run within the IMS.

Abstract: A system for facilitating XML enable IMS transactions includes a generic XML processor inside an IMS connect program to facilitate any TCP/IP clients, including WebSphere and non-WebSphere, to send and receive XML documents to and from existing IMS transaction business logic. Translations between XML documents and IMS transaction message data structures occur within the IMS connect program under an XML task to parse and transform XML requests and responses. Further, the generic XML processor within the IMS connect program can provide data translation for both non-formatted and formatted IMS transactional messages in XML.

Abstract: A graphical user interface (GUI) of a software development tool can visually compose process flows for enterprise information system (EIS) process flow applications. The GUI can include a canvas that visually shows a set of process flows of a process flow application as a set of interconnected node objects. Each node object can corresponds to a node, which corresponds to at least one process flow. The GUI can also include a graphical compensation tool through which users define and view compensation actions and compensation scopes of process flows of the process flow application, wherein said graphical compensation tool does not require a user to input code text that defining compensation logic of the process flows.

Abstract: An IMS process flow toolset can be used to create an IMS process flow application. The IMS process flow application can include an IMS process flow control program. The IMS process flow control program can embody process flow elements such as business logic and events as well as communication with external non-IMS applications. Both the IMS process flow application and IMS process flow control program can be run within the IMS.

Abstract: IMS source code or a graphical object having corresponding IMS source code can be selected within the graphical user interface (GUI). The IMS source code can include a call out to an external application. An IMS call wizard can be invoked, which graphically prompts a user to specify call-out specific conditions for the external application via an ordered series of presented screens. Each screen can present a user with at least one selectable option. User-made selections from earlier ones of the presented screens can change options presented in later ones of the presented screens. IMS code can be generated to call out an external application in accordance with the user selections of the IMS call wizard. The generated IMS code can be inserted into the selected IMS source code. After the insertion, the IMS source code is operable to call out to the external application.

Abstract: A system for facilitating XML enable IMS transactions includes a generic XML processor inside an IMS connect program to facilitate any TCP/IP clients, including WebSphere and non-WebSphere, to send and receive XML documents to and from existing IMS transaction business logic. Translations between XML documents and IMS transaction message data structures occur within the IMS connect program under an XML task to parse and transform XML requests and responses. Further, the generic XML processor within the IMS connect program can provide data translation for both non-formatted and formatted IMS transactional messages in XML.

Abstract: A system for facilitating XML enable IMS transactions includes a generic XML processor inside an IMS connect program to facilitate any TCP/IP clients, including WebSphere and non-WebSphere, to send and receive XML documents to and from existing IMS transaction business logic. Translations between XML documents and IMS transaction message data structures occur within the IMS connect program under an XML task to parse and transform XML requests and responses. Further, the generic XML processor within the IMS connect program can provide data translation for both non-formatted and formatted IMS transactional messages in XML.