Scope: The CA Easytrieve for z/OS will be upgraded to Version11.5. The version 11 release is unlike prior versions because its architecture resulted in a new version of both the language compiler and the runtime system. The changes introduced with CA Easytrieve version 11.5 are extensive, and complete migration to this new release is expected to be potentially prolonged and may require considerable user modifications and or testing to ensure a smooth migration.
However, this release provides the ability to run your programs in "compatibility" mode. In this mode, programs are compiled as in the current 6.4 version and you can put off testing and using any of version 11's new functionality. Version 11.5 will be initially distributed with the options table in compatibility mode by default. Testing of the new function mode will be available by adding a special DD statement to your JCL that invokes CA Easytrieve.
Effective Date: The rollout is scheduled for the weekend of April 14th with Service Center RFCs scheduled with the MVS Maintenance Window IPLs.
Group Name: Tulsa MVS Software Support team
Affected Locations: Sabre, AMR and US Airways systems.
Summary: CA Easytrieve will be upgraded in compatibility mode and after the upgrade users of CA-Easytrieve will be required to start testing of new function mode. Eventually after several months compatibility mode will be turned off and the default will be new function mode. When new function mode is made the default mode a fall back will be made available to still execute in compatibility mode.
Justification & Benefits to Users: To Notify CA Easytrieve users about the new version of Easytrieve along with the required actions after the new version is rolled out.
DETAILS:
Easytrieve Plus is currently scheduled to be upgraded from v6.4 to v11.5 during the April outage. While this new release incorporates major changes to the product, it will initially be running in compatibility mode, so there should be no impact to existing programs. Previously compiled programs should run as-is after the upgrade. An issue we've had with the current release of Easytrieve, are programs that call other non-Easytrieve programs, usually COBOL. Currently, we have two compile options setup, one for 24-bit and another for 31-bit addressing. With this release we are simplifying the process and eliminating the extra 24-bit options table. Those programs that require 24-bit addressing will be handled in another fashion, described below.
Today, Easytrieve Plus programs are compiled from one of two libraries in order to obtain the desired addressing mode:
24-bit - PP.R.EZTPLUS.LOADLIB (OM language type EZT)
31-bit - PP.R.EZTPLUS.ALL31.LOADLIB (OM language type EZZ)
You will no longer need to supply a STEPLIB DD card to either of these two libraries after the upgrade and they will be removed from the system. The STEPLIB DD card will no longer be needed since the Easytrieve library will now be in the system LinkList.
There is a temporary setup that allows for testing prior to the implementation. It is set up for compatibility for now, but the "New Function" mode is available for testing and will also be post-implementation, so that everyone can prepare for when compatibility mode is removed, or at least made the option instead of the default.
Instructions for testing and some release notes follow as well as some pdf documents.
----------------------------- Testing ---------------------------------
For testing prior to implementation add the following statements to any step executing program EZTPA00 to compile or run an Easytrieve program in compatibility mode, or in Object Manager simply use language type E11 for your compile.
//STEPLIB DD DISP=SHR,DSN=SYS3.EZTPLUS.LOAD
//EZOPTBL DD DISP=SHR,DSN=SYS3.EZTPLUS.EZOPTBL
To test the New Function mode use the alternate option table with the STEPLIB, or in Object Manager use language type E1N for your compile.
//EZOPTBL DD DISP=SHR,DSN=SYS3.EZTPLUS.EZOPTBLN
If 24-bit COBOL subroutines are called while executing from source code with no compile/link you must add CALL(AMODE24) to the PARM statement in the Easytrieve source. This only works with the "New Function" mode that requires the EZOPTBL DD above in the execution JCL.
Example:
PARM ABEXIT(NO) ENVIRONMENT(COBOL) CALL(AMODE24)
To create an Easytrieve load module that calls 24-bit COBOL either use the New Function mode and the CALL(AMODE24) parm in the source or simply use RMODE=24 in the linkage editor.
---------------------- Post Implementation ----------------------------
Post-implementation of the new version no STEPLIB or EZOPTBL DD statements are needed for compatibility mode. For New Function mode only the EZOPTBL statement is needed and it becomes SYS2 instead of SYS3.
//EZOPTBL DD DISP=SHR,DSN=SYS2.EZTPLUS.EZOPTBLN
After you start running your programs in compatibility mode and as you move programs and applications through your next development cycle, you can start enabling the new function mode. Enable the new function mode by using the new EZOPTBL DD in your JCL to point to the new function mode options table. The new function mode options table dataset is data set SYS2.EZTPLUS.EZOPTBLN. Thus to test new function mode after version 11.5 is installed add the following DD statement to your Easytrieve JCL:
//EZOPTBL DD DISP=SHR,DSN=SYS2.EZTPLUS.EZOPTBLN
Once a site is comfortable that the majority of applications process correctly using new function mode, the default system-wide options table will be updated to set NEWFUNC(Y). When this is done you will no longer need to code the EZOPTBL DD statement to execute in new function mode. In this way, the majority of users can continue to use new function mode, by default, without having to code an EZOPTBL override. If you need to still execute in compatibility mode after new function mode is made the default there is a fallback option. A fallback options table will be created that is set to compatibility mode. Instructions for fallback to compatibility mode will be provided in further communications as we get closer to turning on new function mode by default.
If you exclusively compile and link your programs, the load modules created under prior release will continue to run in version11.5. In this case, you can migrate directly to new function mode, but you must test the compiled programs.
Note: Compatibility mode is intended to be used as a temporary migration aid, and will likely NOT be supported or available in future releases of the Easytrieve product.
Other notes for users:
1. Dependent Product Documentation Changes:
Users of the following related products should be aware of documentation changes necessary for compatibility with CA Easytrieve version 11.5:
PRODUCT: CA-Easytrieve Plus Tool Kit-MVS RELEASE: 2.0
PRODUCT: CA-PANAUDIT/PLUS-MVS RELEASE: 3.0
PROBLEM DESCRIPTION: EZTC0173E/EZTC0084E ALPHACON missing CALLCOUNTER
---------------------------------------------------------------------
These Easytrieve r11 compile-time errors may occur if the ALPHACON macro is invoked multiple times to convert to numeric fields of different lengths or decimal places. The CALLCOUNTER parm needs to be added to the macro invocation.
This change is necessary for compatibility with CA Easytrieve version 11.
2. Macro Parameter Substitution
If you need to pass a hexadecimal literal as a parameter, you must pass it first as an alphanumeric literal ('X''xx'').
3. Error Messages Displayed in DBCS Characters.
If you are using the CA Easytrieve DBCS feature, you can ensure that any Runtime error message displays in DBCS characters. However, the Compiler does not support messages in DBCS format. DBCS Compile messages are planned for a future release.
4. Compiler Syntax Rules
In many places in the compiler of this release, the syntax checking of statements has been enhanced. This helps ensure that the language remains consistent and unambiguous. A couple of examples of these areas are as follows:
VSAM File Processing
As documented, the FILE statement within r11 continues to honor programs coded with a FILE statement using VS as a file type for compatibility purposes. However, prior releases allowed you to specify either ES or KSDS without checking for the use of a KEY for KSDS files. The r11 release now produces a compile error if Entry Sequential (ES) access is specified and a key is then supplied on a subsequent READ statement.
IMS Statements
Parsing of various statements within r11 may cause compile error messages. This was reported under the following circumstances. A statement from an existing Easytrieve program accessing IMS was coded as follows:
RETRIEVE file-name +
SELECT (Field-name) +
WHERE (Field-name-LEN < Max-Length AND +
Field-name-LEN > Min-Length)
This version of the compiler issues an error on the WHERE statement as not being valid for a RETRIEVE. This error occurred because the WHERE is actually a part of the SELECT. In this case, parentheses were not included according to the statement documentation. Correct syntax for this statement would be:
RETRIEVE file-name +
SELECT ( (Field-name) +
WHERE (Field-name-LEN < Max-Length AND +
Field-name-LEN > Min-Length) )
5. VSAM MACRO Support Removed
MACRO library support for TYPE=VSAM is no longer provided. Existing MACRO=VSAM users should convert to MACRO=PDS.
For additional information about the new version of CA Easytrieve consult the vendor manuals
Refer to the CA Easytrieve Report Generator for z/OS Release Notes document(s) for complete details regarding new features and changes to existing features in this release, too numerous to list here.
Primary Contact: Steve Wagner - wagner@hp.com
Secondary Contact: Rich Reed – richard.reed@hp.com
|
Usercomm - Tulsa Eastytrieve upgrade to v11.5 