Table of Contents

• Current Releases and Service Pack News
• Service Pack 3
• Solutions and Patches


• Development News
• Advantage™ Repository Exchange for ERwin® Release 4.0 in Beta


• Tips from Support



• Online Ordering is Here!

Service Pack 3

Service Pack 3 Genlevel 0203 for Advantage™ Repository for z/OS and OS/390 is now GA. For more information on updates, visit the Advantage Repository for z/OS and OS/390 page on the CA support website.

Service Pack 3, Genlevel 0203 is currently GA.

New enhancements include:

• The DB2 Interface has been upgraded to support Release 7.1 and Stored Procedures.
• The Oracle 8.x Interface was upgraded to support "Candidate Selection".
• A Model was added for XML DTDs.
• Latest confirmed maintenance.

Advantage™ Repository Exchange for ERwin® Release 4.0 in Beta

New features and enhancements in the Advantage™ Repository Exchange for ERwin® Release 4.0 interface are as follows:

• Support for Repository Import of AllFusion™ ERwin® 4.0 data.
• Ability to control the type of data loaded into the Repository by object and/or by attribute.
• Support reuse of objects within the Repository.
• Ability to recognize that an object has been renamed.

For further information and to learn how you can participate in the Beta Program, click here.

A DEBUG/TRACE output file is often the most useful document that you can provide to your technical support representative to help them resolve a problem.

Turning the DEBUG/TRACE facility on is a very simple matter from any of the Advantage™ Repository batch applications. This is simply a question of changing the DEBUG PARM value to ‘Y’ and re-running the problem batch JOB STEP. The correct PARM is indicated by a comment within each individual JOB STEP.

Turning the DEBUG/TRACE facility on within DBEXCEL isn’t quite so straightforward, however. First of all, knowledge of the commands used to turn the facility off and on is required. To turn the DEBUG/TRACE facility on within DBEXCEL, enter the following from the COMMAND LINE:

       TSO %PRMDBUG Y

To turn the DEBUG/TRACE facility off within DBEXCEL, enter the following from the COMMAND LINE:

       TSO %PRMDBUG N

The real trick is capturing just the right amount of information to accurately document the problem. This may require some assistance from support to get it just right. As a general rule of thumb, try to turn it on at a point just before you observe the problem and turn it off immediately after the problem has appeared.

The name of the OUTPUT file, which will contain the DEBUG/TRACE information, is defined within the DBEXCEL CLIST itself. The default value for the file name is:

       ‘&ZUSER..DEBUG’

where ‘&ZUSER’ is the TSO LOGON ID of the DBEXCEL user.

NOTE: The file is not accessible while the user that generated the DEBUG/TRACE has an active DBEXCEL session. This is because the file is allocated to the associated process for the duration of the DBEXCEL session, regardless of the current value of the PRMDBUG parameter.

Having a DEBUG/TRACE readily available for support when you open your issue will help to expedite your problem’s resolution.

We have just begun an exciting new addition to our support offerings - online ordering! You can now order Advantage™ Repository for z/OS and OS/390 service packs through the Advantage Repository Support Web page.

Currently, this service is only available for our customers in North America. If you are outside of North America, you may continue to order Advantage Repository through your local Computer Associates Support Center.