|This is a summary of the technical changes to the DB2 Server for VSE |& VM database management system for this edition of the book. All |manuals are affected by some or all of the changes discussed here. For |your convenience, the changes made in this edition are identified in the text |by a vertical bar (|) in the left margin. This edition may also |include minor corrections and editorial changes that are not |identified.
This summary does not list incompatibilities between releases of the DB2 Server for VSE & VM product; see either the DB2 Server for VSE & VM SQL Reference, DB2 Server for VM System Administration, or the DB2 Server for VSE System Administration manuals for a discussion of incompatibilities.
|Version 7 Release 1 of the DB2 Server for VSE & VM database |management system is intended to run on the Virtual Machine/Enterprise Systems |Architecture (VM/ESA(R)) Version 2 Release 3 or later environment and on |the Virtual Storage Extended/Enterprise Systems Architecture (VSE/ESA(TM)) |Version 2 Release 3 Modification 1 or later environment.
|TCP/IP support allows: |
|For more information, see the following DB2 Server for VSE & VM |documentation: |
|DRDA Remote Unit of Work Application Requester provides read and update |capability in one location in a single unit of work.
|This support provides VSE batch application programs with the ability to |execute SQL statements to access and manipulate data managed by any remote |application server that supports IBM's implementation of the DRDA |architecture.
|VSE batch application programs can access only one remote application |server per unit of work, and must use TCP/IP communications.
|For more information, see the following DB2 Server for VSE & VM |documentation: |
|A stored procedure is a user-written application program compiled and |stored at the server. Stored procedures allow logic to be encapsulated |in a procedure that is local to the database manager. The ability to |use stored procedures provides distributed solutions that let more people |access data faster. SQL statements and replies flowing across the |network are reduced and performance is improved.
|This support provides VM and VSE (online and batch) application programs |with the ability to invoke stored procedures from any remote application |servers that support IBM's implementation of the DRDA |architecture. It also allows processing of result sets if supported by |the remote DRDA application server.
|For more information, see the following DB2 Server for VSE & VM |documentation: |
|A REXX procedure Job Manager is supplied to assist in the DB2 Server |for VSE Installation/Migration process. It controls the overall job |flow based on the contents of the job list control tables and the parameter |table (supplied as Z-type members). The job manager selects the job |control member from the job list file (a Z-type member), extracts the member |from the Installation Library, modifies the JCL, submits the job, evaluates |the execution, posts the results, and then repeats the process as |required. The users are required to modify the parameter table, |according to their environment.
|This support simplifies the process of installation and migration by |reducing user intervention - the Job Manager submits the prepared jobs.
|See the DB2 Server for VSE Program Directory for further details.
|The following CCSIDs are now supported: |
|Additional support has been added for conversions from Unicode (UTF-8) to |host CCSIDs.
|For a complete list of CCSIDs supported, refer to the DB2 Server for VM System Administration and DB2 Server for VSE System |Administration manuals.
|The following is a list of enhancements that have been made to the |Control Center for VM: |
|The following enhancements have been provided for Control Center for |VSE: |
|The following enhancements have been provided for QMF for VSE & |VM: |
|The following enhancements have been provided for QMF for Windows |: |
|ARISDIRD has been restructured to improve readability and |flexibility. Each DBNAME entry is now defined explicitly by its type |(Local, Remote or Host VM (Guest Sharing)). CICS AXE Transaction TPNs |(Transaction Program Names) are still included in the directory as a type of |'LOCALAXE'. The DBNAME Directory Builder program, ARICBDID |has been rewritten as a REXX/VSE procedure with extensive error and dependency |checking. Support for TCP/IP information is added and 'alias' |DBNAMEs are supported. ALL DBNAMEs must be |specified in the new DBNAME Directory, including the Product Default DBNAME |"SQLDS". A migration REXX/VSE procedure, ARICCDID, is provided to |assist in migrating to the new format. See the DB2 |Server for VSE System Administration and DB2 Server for VSE Program Directory for additional information.
|Migration is supported from SQL/DS(TM) Version 3 and DB2 Server for VSE |& VM Versions 5 and 6. Migration from SQL/DS Version 2 |Release 2 or earlier releases is not supported. Refer to the DB2 Server for VM System Administration or DB2 Server for VSE System Administration manual for migration considerations.
|Some general library enhancements include: |
|Note: Information from this book can now be found in the DB2 Server for VSE & VM Performance Tuning Handbook
|Refer to the new DB2 Server for VSE & VM |Overview for a better understanding of the benefits DB2 Server for VSE & |VM can provide.