IMS Mobile Feature Pack for z/OS Connect Enterprise Edition is now included as the IMS service provider in
IBM z/OS Connect Enterprise Edition V2.0.5 (APAR PI70432) or later. The information here is provided "AS IS" and will no longer be maintained.
For the latest IMS mobile solution information, see
Using the IMS service provider in z/OS Connect EE documentation.
Operational considerations and restrictions
Examine the operational considerations and restrictions to assist the planning and design of your mobile solution that is based on the IMS™ Mobile Feature Pack for z/OS® Connect EE.
Operational considerations
- The mobile solution that is enabled through the IMS Mobile Feature Pack for z/OS Connect EE provides access to IMS transactions through the IMS Transaction Manager. The transactions can then access IMS DB, DB2®, and other external subsystems. The solution requires IMS Connect.
- IBM® z/OS Connect Enterprise Edition Version 2.0 (PID: 5655-CEE) or later is required.
- IMS Explorer for Development V3.2.1 or later is required for creating, publishing, and testing the services, and for defining the REST APIs for the services. Subsequent releases of IMS Mobile Feature Pack for z/OS Connect EE might require a newer version of IMS Explorer. Check the release notes for minimum required version.
Restrictions
The IMS Mobile Feature Pack for z/OS Connect EE has the following restrictions:
- Only transactions with a single input message and a single output message are supported, although the message can contain multiple segments. For non-response transactions or when IMS encounters an error while processing the transaction, a GMOBA0920E message is generated that includes the DFS message from IMS.
- For COBOL to JSON data conversion restrictions, see COBOL to JSON schema mapping (IMS Explorer).
- For PL/I to JSON data conversion restrictions, see PL/I to JSON schema mapping (IMS Explorer).