Restrictions for IMS Explorer

• Verify that the DBD and PSB source files that you import into IMS Explorer are valid. Valid DBD and PSB source is source that the Database Description Generation (DBDGEN) utility or Program Specification Block (PSB) generation utility can process successfully.
• IMS Explorer follows all references in DBDs to other DBDs when building its model, and it might require access to DBDs that are not referenced directly by PCBs in the PSB. For example, when IMS Explorer processes a PSB that references a logical DBD, IMS Explorer needs access to the primary DBDs that are referenced in the logical DBD. Similarly, all DBDs that are related by logical relationships must be accessible.

Restrictions for SQL access to an IMS database from IMS Explorer

• For SQL access to an IMS database from IMS Explorer, the PCBs in the PSB for the database must be named. They can be named by using statement labels or by using the PCBNAME parameter.
• If your application uses JDBC and the JDBC call includes fields from more than one segment in a hierarchical path, the IMS Universal JDBC driver uses path calls. To ensure that your application can retrieve fields from multiple segments, you must include P as a processing option (PROCOPT) in the PCB statement or SENSEG statement, as appropriate.
• If your application uses the IMS Java™ hierarchical database interfaces (SSA database access) or the IMS Universal DL/I driver, path calls are under your control, and you must choose the appropriate PSB processing options.

Restrictions for creating IMS mobile services

• Use IMS Explorer to create and test services that run on z/OS® Connect EE V2 only. For z/OS Connect EE V3, use the z/OS Connect EE API toolkit instead. For more information, see Create an IMS service (IBM z/OS Connect Enterprise Edition 3.0 documentation).
• The IMS mobile solution can access only the IMS Transaction Manager (IMS TM). The transactions can then access IMS Database Manager (IMS DB), DB2®, and other external subsystems.
• The IMS mobile solution supports only transactions with a single input and a single output. Non-response transactions are not supported.
• The IMS mobile solution supports multiple-segment transaction messages. For more information and restrictions, see Adding segments to transaction messages.
• Only one user can update the IMS mobile server within IMS Explorer at a time. Simultaneous updates from multiple users are not allowed.
• For COBOL to JSON data conversion restrictions, see COBOL to JSON schema mapping.
• For PL/I to JSON data conversion restrictions, see PL/I to JSON schema mapping.

Restrictions for using the IMS Explorer with the IMS Enterprise Suite DLIModel utility plug-in

IMS Enterprise Suite Version 2.1 is the last release of IMS Enterprise Suite that includes the DLIModel utility plug-in. Customers using the IMS Enterprise Suite DLIModel utility plug-in should migrate to using the IMS Explorer instead.

Although IMS Explorer includes enhancements to most IMS Enterprise Suite DLIModel utility plug-in functions, it does not provide support for IMS database web services or IMS XML DB.

• For IMS database web services, you can generate web-enabled IMS database queries by shell sharing IMS Explorer with IBM® Data Studio.
• For IMS XML DB support, customers can continue to use the IMS Enterprise Suite DLIModel utility plug-in.