This chapter describes differences between Mainframe Express 2.0 and Mainframe Express 2.5 that might require you to make alterations in existing applications that you are migrating, or to change familiar methods of working.
The overall product shape of Mainframe Express 2.5 is very similar to that of 2.0.
In Mainframe Express 2.5 Assembler Option has been extended to provide:
For more details see the online help: click Help Topics on the Mainframe Express Help menu, then on the Contents tab click Reference, Assembler Option and Linker directives
In Mainframe Express 2.5 CICS Option has been extended to provide:
The impact is as follows:
The default resource definition file supplied with Mainframe Express 2.5 contains new resource definitions to support the running of applications that have been Web-enabled using EnterpriseLink. When a resource definition file is upgraded, the new resource definitions are added to it.
In addition, CICS Option to CICS Option communications have changed in Mainframe Express 2.5, such that when security is specified on an ISC connection, the user ID and password are now converted to EBCDIC. As a result, if security is required you cannot connect a region from CICS Option in Mainframe Express 2.5 (or later) with a region from CICS Option in Mainframe Express 2.0 (or earlier).
In Mainframe Express 2.5, Host Compatibility Option provides the ability to check EXEC SQL statements included in copybooks for syntax errors. The default behavior is that EXEC SQL statements are checked for syntax errors. If you do not want EXEC SQL statements in copybooks to be checked, you should specify the compiler directive DB2(COPY).
In Mainframe Express 2.5, XDB Server runs as a service, that is, it starts automatically whenever you boot your machine, whereas in previous versions, you started it manually using a menu option. One result of this is that if you upgraded from Mainframe Express 1.1 to Mainframe Express 2.5 without changing the details of your client and server configuration, and you use the Win32Local protocol, there could be a mismatch between the name of the server in the server configuration and the name of the server in the client configuration. If you find that after upgrading, your client applications cannot connect to the XDB Server (that is, they receive a N511 error message), you should do the following:
After doing this, you should find that your applications can connect to the XDB Server.
Copyright © 2001 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.