Rocket® Enterprise Developer (formerly a product of Micro Focus or formerly a product of Open Text) documentation, created before Rocket Software acquired certain products from OpenText, may include outdated references to "Micro Focus" or "OpenText", both of which are trademarks of OpenText or its affiliates. Rocket Software is not affiliated with Micro Focus or OpenText and has since rebranded these products as Rocket® products. You may also encounter outdated links in this documentation. If you do, please contact Rocket Support (support@rocketsoftware.com) for assistance.
Restrictions on Function Shipping
Note:
Rocket® Enterprise Suite products provide a proprietary run-time engine to enable compatibility for customers’ IBM® CICS® applications. IBM and CICS are registered trademarks of International Business Machines Corp. Rocket Enterprise Suite products do not include an IBM CICS engine and are not affiliated with IBM. Further information can be found here.
The following restrictions apply to function shipping as implemented in MSS:
- You cannot ship a function directly to a DL/I (IMS) database.
- You should not ship a function that updates a resource across multiple links, because recovery cannot be coordinated.
- You should take syncpoints from your system and not the invoked end of the link, otherwise you might get unpredictable results.
This is advisable because function shipping only incorporates sync level 1 logic. Whether you have single or multiple connected systems, a sync request can be propagated through all the connected systems.