DP Manager 2.0 Release Notes

Released On: 03/21/1994

• A new CICS-based ADHOC report writer provides DPM with extensive, user-configurable batch reporting capabilities. The report writer has a repository of DPM 'files' and record layouts and allows for list-style reports, multiple record joins, and multiple output destination types. You can produce reports or files and automatically route output to the JES/POWER queue, our CICS/Spooler product, or to ADHOC's own report viewer queue. Report composition is performed online and may be submitted from online or batch (all reports are produced in batch). This report writer is a subset of our new ADHOC report writer product.
• Assembler-based AUTOEDIT has been removed and replaced with a LINK-based AUTOEDIT like that used on PC version of DPM. Management of AUTOEDIT messages and table settings is accomplished via free-form syntax input to a batch job. This is the first step on the path to implementing a system-wide, online-based field control and security mechanism. As a by-product of this change, removal of this assembler subroutine makes re-compiling and linking a little less troublesome.
• A new help engine (as used by several of our other products) supports the saving of complete screen contents, supports help text in up to 5 languages (1 per DPM file domain) and allows the user to set color/attribute information in the help text. Help text is still editable as in previous releases, but ONLY in batch. The basis for this engine is also available as a standalone product (Help Screen Toolkit for CICS), for those interested.
• A new print engine (as used by several of our other products) supports SNA, NON-SNA, and SCS printers, supports routing output to our CICS/Spooler product, and provides configuration-based form feed and page length control. Other changes in this area include the centralization of all online print functions in one module.
• A new error logging engine (as used by several of our other products) supports better error messaging and provides a mechanism to save diagnostic information even on errors that occur only once and cannot be reproduced.
• Several security-related exit points were added to DPM's application supervisor. In particular, these control security identification and function/subfunction access control. These exits eliminate the need to modify the source on the large, complex supervisor source module.
• E-mail, exit point DPDOCEML (also see install manual). The problem and change modules that link to our CICS/Message product have been updated to support the current CICS/Message product. The code has been moved into stand-alone CICS modules to allow for easier access and customization for customers who wish to add notification via their E-mail systems.
• User identification selection no longer must be changed via source code. A new configuration option allows selection of OPID, USERID, or TERMID. In addition, the module where these values are determined is provided in source in the event that the customer has special needs in this area. The userid field on the main menu is now protected from entry at all times. As a by-product of this change, member DPDOCUSR (the userid version of DPDOCSUP) is no longer necessary.
• Several cosmetic changes were implemented, including the use of lower case screen text and the standardization of the DATA and S/D? field labels.
• The problem and change system search screens now have an AREA parameter, allowing for a search of problems or changes only in a certain area vs. the entire file. In addition, these screens now release control to CICS periodically to prevent the monopolization of CICS resources.
• The active file domain name now appears on the main menu.
• The automatic page eject in online problem printouts that occurred between problem descriptions and solutions is no longer issued. Likewise, the customization of such inter-document formatting is much simpler on a system-wide basis due to the use of the new print engine.
• An exit point in DPDOCSUP was added to allow customers to customize DPM's actions upon exit from DPM to CICS. The default exit point (DPDOCEXI) performs the same processing DPM performed in previous releases: clear the screen, release the keyboard lock, and return to CICS.
• The capability to create output files from DPM data is partially implemented via the various output file options in the ADHOC report writer portion of DPM 2.0.
• DPM 2.0 requires CICS 1.7 or higher. DPM 2.0 will not run on CICS releases prior to 1.7 without significant source changes. As such, we can not support DPM 2.0 on CICS releases prior to 1.7 UNDER ANY CONDITIONS.