Summary of changes

This edition of the document provides information applicable to File Manager Version 15 Release 1 Modification Level 1. Here are the major changes to this document from the previous release.

• File Manager provides internal PL/I compilers that are used regardless of any external PL/I compiler previously installed. If you want to use File Manager view, edit, copy, print, or data create functions with a PL/I include book, you must use the runtime support provided by the Language Environment®. To discover the level of the internal PL/I compiler, you can use the SHOWPLI command from both batch and the File Manager command line. See Customizing for processing PL/I include books for more information about submitting this command.
• FM/IMS has been enhanced to support using the IMS Data Definition Utility (DFS3ID00) to generate dynamic program specification blocks (PSBs) when IMS manages the runtime application control blocks (ACBs). See the new FM/IMS option, USEDDL, that specifies whether or not FM/IMS uses the IMS Data Definition utility (DFS3ID00) to generate dynamic PSBs when IMS management of ACBs is enabled (ACBMGMT=CATALOG).

This edition of the document provides information applicable to File Manager Version 15 Release 1 Modification Level 0. Here are the major changes to this document from the previous release.

• Improved the usability and task orientation of the documentation that explains how File Manager can use FM/CICS to access CICS resources from different environments. The documentation has been reworked and organized, and a checklist clearly defines the steps based on the environment. For more information, see Preparing to access CICS resources from File Manager.
• FM/Db2 supports Db2® version 13.
• With File Manager version 15.1.0, the default value for the FM/CICS FMN3POPI option, START, is now START=TASK. In previous versions, the default value was START=BATCH. See START for the complete syntax.
• Removed the USERLMS parameter from the LMS File Manager option in the FMN0POPI macro statement.
• The security method using the FMNSECUR security exit has been removed from the product.