home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
datatl25.zip
/
_SETUP.LIB
/
README.DCT
< prev
next >
Wrap
Text File
|
1997-03-02
|
35KB
|
695 lines
README.DCT
IBM TeamConnection DataAtlas for OS/2 Version 1.0.1
===================================================
DataAtlas on the Web
====================
TeamConnection DataAtlas product support is provided via its web site:
http://www.software.ibm.com/ad/datatlas
README.DCT Contents
===================
This file explains the following:
* How to install DataAtlas Version 1.0.1
(See 1. Installation below)
* How to access and use online and printable book files
(See 2. Online and Printable Books below)
* Version 1.0.1 functions and restrictions that are not cited in the books
DataAtlas on the Web
====================
TeamConnection DataAtlas product support is provided via its web site:
http://www.software.ibm.com/ad/datatlas
1. Installation
===============
The information in this section guides you through the TeamConnection
DataAtlas V1.0.1 (Fixpak 1) installation process. DataAtlas must be installed
on each client system where it will be used.
1.1 Installation Prerequisites
a) If you are upgrading your installed TeamConnection DataAtlas V1.0
to DataAtlas V1.0.1 (Fixpak 1), then you must have already installed
the following products and their components in the order presented
as described in "IBM TeamConnection DataAtlas for OS/2 Installation,
Version 1.0" (SC26-8083).
TeamConnection Server
---------------------
* IBM TeamConnection for OS/2 V1.0 Server
TeamConnection V1.0 was shipped on a separate CD-ROM that was
included in the DataAtlas V1.0 package.
* IBM TeamConnection for OS/2 V1.0 Fixpak 3
June 24 version downloaded from the TeamConnection home page.
TeamConnection DataAtlas Modeler Server
---------------------------------------
* IBM TeamConnection DataAtlas for OS/2 V1.0 Modeler Server
This was included on the DataAtlas V1.0 CD-ROM.
TeamConnection DataAtlas Client
-------------------------------
* TeamConnection for OS/2 V1.0 Client
TeamConnection V1.0 was shipped on a separate CD-ROM that was
included in the DataAtlas V1.0 package.
* IBM TeamConnection for OS/2 V1.0 Fixpak 3
June 24 version downloaded from the TeamConnection home page.
* TeamConnection DataAtlas for OS/2 V1.0 Modeler Client
* TeamConnection DataAtlas for OS/2 V1.0 Dictionary and Designer
b) A version of TeamConnection Fixpak 3 was shipped on the
TeamConnection DataAtlas V1.0 CD-ROM. Shortly after the
availability of DataAtlas V1.0, it was discovered that the
TeamConnection Fixpak 3 shipped on the DataAtlas V1.0 CD-ROM
had a problem. TeamConnection Fixpak 3 was re-released and
made available via the TeamConnection home page on June 24.
If you:
1. Installed TeamConnection V1.0
2. Installed TeamConnection Fixpak 3 from the DataAtlas V1.0 CD-ROM
3. Installed DataAtlas V1.0
4. Defined data in your TeamConnection database using DataAtlas
then the data in your TeamConnection database will be unusable
if you install any other TeamConnection fixpak, including the
re-release of TeamConnection Fixpak 3. At this time there is no
way to recover the data in your TeamConnection database. You must
re-create your TeamConnection Family Server database.
If you:
1. Installed TeamConnection V1.0
2. Installed the June 24 TeamConnection Fixpak 3 downloaded from
the TeamConnection home page.
3. Installed DataAtlas V1.0
4. Defined data in your TeamConnection database using DataAtlas
Now you can:
5. Download and install TeamConnection Fixpak 5 on your
TeamConnection V1.0 Server and on every TeamConnection V1.0
Client.
6. Download and install DataAtlas V1.0.1 (Fixpak 1) on your
DataAtlas V1.0 Modeler Control Server and on every DataAtlas
V1.0 Client.
and you can continue to use the data in your TeamConnection
database.
If you are installing TeamConnection and DataAtlas for the first time:
1. Install TeamConnection V1.0 from the CD-ROM included in the
DataAtlas V1.0 package.
2. Download and install TeamConnection Fixpak 5 on your
TeamConnection V1.0 Server and on every TeamConnection V1.0
Client.
3. Install DataAtlas V1.0 from the CD-ROM included in the
DataAtlas V1.0 package.
4. Download and install DataAtlas V1.0.1 (Fixpak 1) on your
DataAtlas V1.0 Modeler Control Server and on every DataAtlas
V1.0 Client.
Now you can start defining data in your TeamConnection database
using DataAtlas.
Note: TeamConnection Fixpak 5 is available from the TeamConnection
home page, which can be accessed from the IBM Application Development
home page at http://www.software.ibm.com/ad or directly at
http://www.software.ibm.com/software/ad/teamcon.
1.2 Getting Ready to Install TeamConnection DataAtlas V1.0.1
Before you begin installing DataAtlas V1.0.1, be sure to shut down
your DataAtlas Modeler V1.0 Server and each DataAtlas V1.0 Modeler
and/or Dictionary and Designer Client.
1. Stop or shut down DataAtlas Modeler Clients:
a. Close all open windows except the tree view of the model.
b. Close the tree view.
c. If you are using DataAtlas Modeler in a single-user
environment, or if you are the only person using the model
in a multiuser environment, the Unload Data Model window opens.
d. Do one of the following:
* Unload and save changes to end the data modeling session
and check the changes to the data model into TeamConnection.
This also unlocks any objects that were still locked when
you closed the model.
* Unload and discard changes to end the data modeling session
and discard all changes made to the data model since the
model was checked out of the TeamConnection database. This
discards ALL changes made by ALL users.
2. Stop or shut down the DataAtlas Modeler Control Server:
a. Ensure that there are no data models loaded.
b. Double-click on the DataAtlas Modeler Control Server icon or close the
DataAtlas Modeler Control Server from the OS/2 Window List. You can
stop or shut down the DataAtlas Modeler Control Server from the OS/2
Window List, from the OS/2 command prompt, or using the program icon.
3. Stop or shut down DataAtlas Dictionary and Designer Clients:
a. Close all object Settings notebooks.
b. Close all workfolders.
c. Close the Workfolders folder.
d. Close the DataAtlas Main Folder.
1.3 Using Software Installer/2 to Install TeamConnection DataAtlas V1.0.1
Once you have downloaded and unpacked DataAtlas V1.0.1, you are
ready to install this fixpak. You must install it on your
TeamConnection DataAtlas Modeler V1.0 Server and on every
TeamConnection DataAtlas V1.0 Modeler and Dictionary and Designer
Client.
Furthermore, if you want to use TeamConnection Build to invoke
DataAtlas to build DB2/MVS or DB2/2 DDL, IMS source, or COBOL COPY
files, you must install DataAtlas Dictionary and Designer V1.0 on your
TeamConnection build server first and then install DataAtlas
Dictionary and Designer V1.0.1 (Fixpak 1).
For instructions on installing DataAtlas V1.0, refer to
"IBM TeamConnection DataAtlas for OS/2 Installation, Version 1.0"
(SC26-8083), which was included in your original TeamConnection
DataAtlas V1.0 product package.
Finally, in the directory into which you unpacked DataAtlas V1.0.1,
you will find two subdirectories:
* DataAtlas Modeler: modeler
* DataAtlas Dictionary and Designer: dictnary
The following step-by-step process applies to each component:
Step 1: Starting the installation
1. At an OS/2 command prompt:
a. Change directory to that of the product you want to install.
b. Type Install and press Enter.
The product installation window appears, followed by the
installation instructions window.
2. Select Continue. The Install window opens.
Step 2: Updating CONFIG.SYS
1. From the Install window, indicate that you want to have your
CONFIG.SYS file updated. This is the default. If you want
existing installation files overwritten during the installation
process, select Overwrite files.
If you select not to have your CONFIG.SYS file updated
automatically, you must update the file manually after the
installation program completes. The installation process
creates a file called CONFIG.ADD that contains your entire
CONFIG.SYS with the installation modifications included.
2. Select OK or press Enter. The Install - directories window opens.
Step 3: Selecting components for installation
1. From the Install - directories window, select the components to
be installed.
2. To verify that the default drive has sufficient space, or to see
what other drives are available, select Disk space.
If you want to use a different drive, do the following from the
Disk space window:
a. Select the drive you want to use.
b. Select Change directories to selected drive.
c. Select OK or press Enter. The Install - directories window opens.
3. Select Install from the Install - directories window to start the
installation. The Install - progress window shows you the
progress of the installation.
Step 4: Completing the installation
1. After the installation completes, the Installation and Maintenance
window appears indicating the product successfully installed.
Select OK or press Enter to return to the product Installation window.
2. Select Exit or press F3.
3. After you've installed the desired products, shutdown your
workstation and then restart it to accept any changes made
to CONFIG.SYS.
Step 5: Verifying your TeamConnection setup
Before using DataAtlas, ensure that the TeamConnection clients can
still access the TeamConnection Server. Refer to IBM TeamConnection
for OS/2 Getting Started, SC34-4498, for TeamConnection Client
installation and setup documentation.
Step 6: Starting TeamConnection DataAtlas
1. Before you can start a DataAtlas Modeler Client, you must start the
DataAtlas Modeler Control Server. You can start a control server
in one of the following two ways:
* From the command line
- From the OS/2 command prompt, type:
start cdmcsrv /F family /D dbpath
where:
* family is the name of the TeamConnection family that you
are using. This parameter is optional; if not specified,
the TC_FAMILY setting in CONFIG.SYS is used.
* dbpath is the fully qualified path of the directory where
the TeamConnection family database is located. This
parameter is optional; if not specified, the TC_DBPATH
setting in CONFIG.SYS is used.
* From the program icon
- Double-click on the DataAtlas Modeler Control Server icon
in the DataAtlas folder
2. Start DataAtlas Modeler Client by double-clicking on the DataAtlas
Modeler icon in the DataAtlas folder.
3. Start DataAtlas Dictionary and Designer by double-clicking on the
DataAtlas Dictionary/Designer icon in the DataAtlas folder.
As before, all of the preceding actions assume that a TeamConnection
Family Server is up and running, and that both the DataAtlas Modeler
Control Server and DataAtlas clients have been set up properly to
access the TeamConnection Family.
Binding ewsddb2x.bnd to your DB2/x databases
--------------------------------------------
In order for DataAtlas to populate data definitions from a DB2 family
database, you must bind 'ewsddb2x.bnd' to every database that will
be accessed by DataAtlas. If you have already used DataAtlas V1.0
to populate data definitions from your existing databases, you must
bind the latest version of 'ewsddb2x.bnd' shipped with DataAtlas V1.0.1
to each database from which to expect to populate data definitions
in the future. See the "DataAtlas Dictionary User's Guide" for more
information on how to do this. Also note the following correction in
the bind command in the User's Guide:
db2 bind ewsddb2x.bnd
Special Notes
-------------
* Install OS/2 Warp Fixpak 17 or higher to fix the following problems:
- Notebook tab text always aligns on the left of the tab.
- The 'Tab' key doesn't move the cursor between controls on a
notebook page.
2. Online and Printable Books
=============================
Four publications accompanied the release of DataAtlas Version 1.0:
* DataAtlas Modeler User's Guide
* DataAtlas Dictionary User's Guide
* DataAtlas Designer User's Guide
* DataAtlas Installation
Of these, the first two have been updated for DataAtlas Version 1.0.1.
The Installation booklet, although unchanged, is superseded by the
instructions in section 1. Installation in this file.
After you have installed DataAtlas Version 1.0.1, you can double-click
on the folder labeled "DataAtlas Information," and then double-click on
the book icons inside to read any of the online books. You should refer
to the "Summary of Changes" pages in both the Dictionary User's Guide
and the Modeler User's Guide to see a synopsis of the updates.
For your convenience, the two updated guides are also available in Adobe
Acrobat and PostScript formats. You can find the DataAtlas Dictionary
Version 1.0.1 Acrobat file in the \HELP subdirectory of the directory
where you installed DataAtlas Dictionary and Designer Version 1.0.1.
For DataAtlas Modeler Version 1.0.1, the Adobe Acrobat file is in the
\LANG\EN_US subdirectory of the directory where you installed DataAtlas
Modeler Version 1.0.1.
In both cases, the PostScript files are in the \PRINTABL subdirectory in
the
directory into which you downloaded and unpacked each respective product.
The Acrobat and PostScript files are named as follows:
EWSDC000.PDF - Dictionary User's Guide (Acrobat)
EWSDC000.PS - Dictionary User's Guide (PostScript)
CDMU7A00.PDF - Modeler User's Guide (Acrobat)
CDMU7A00.PS - Modeler User's Guide (PostScript)
To view the Acrobat files, you must have the Adobe Acrobat reader. You can
download this free of charge from the Adobe website: http://www.adobe.com/.
3. General
==========
* After reading this document, we recommend that you:
1. Read the DataAtlas Dictionary and Designer
Installation booklet for installation,
setup, and startup instructions.
2. Use the online tutorial to learn how to
use DataAtlas Dictionary and Designer quickly.
3. Refer to the DataAtlas Dictionary User's Guide
and the DataAtlas Designer User's Guide as needed.
4. Refer to the readme file for the TeamConnection
DataAtlas Modeler for further information on that
part of DataAtlas.
* Install OS/2 Warp fixpack 17, to fix the following:
- Notebook tab text is always aligning on the left of the tab.
- The Tab key not moving the cursor between controls on a notebook page.
* Sample data for running DataAtlas Dictionary and Designer scenarios
is supplied with the Version 1 product.
DB2 for OS/2 database:
The DA_CELD DB2 for OS/2 database is used with the
DataAtlas Dictionary and Designer tutorial. Directions
for installing DA_CELD are in the Installation
booklet. Before attempting to install the database,
at the OS/2 command line change to the
<DARoot>\samples\celdial directory, where <DARoot>
is the root directory in which DataAtlas is installed.
You must have DB2 for OS/2 Version 1.2 or higher in
order to install the sample DA_CELD sample database.
IMS data:
Sample IMS DBD and PSB source files are in
<DARoot>\samples\ims.
Sample Queries:
Sample SQL queries are in <DARoot>\samples\query.
4. TeamConnection 1.x Considerations
=====================================
* In TeamConnection there is a limitation on the maximum amount
of data which can be integrated in a single workarea. We have
successfully integrated a workarea in which 200 DB2/MVS tables
and their associated objects had been populated. To help avoid
exceeding this limitation, we strongly recommend that you make
large changes incrementally, creating and integrating a workarea
for each increment. If you do not limit your workareas, there
is a possibility that the workarea cannot be integrated, and
therefore your data cannot be used in the database.
* You may experience a problem in which a TeamConnection workarea
integrate appears to be successful on the client, but which the
audit.log on the TeamConnection server shows to have actually
failed. If you encounter this defect, this workarea cannot be
successfully integrated. We recommend that you make changes to
your data incrementally, creating and integrating a workarea for
each increment. This will help minimize the potential impact of
this defect. Also, we strongly recommend that you periodically
back up your TeamConnection database, perhaps before every workarea
integrate, and verify the success of every integrate by checking the
server audit.log. Another possible workaround is to have all users
do their work in a single common workarea which is never integrated,
avoiding TeamConnection versioning function at this time. IBM does
not recommend this solution, as it does not give you the advantages
of using the versioning function.
* A TeamConnection server which will support clients using DataAtlas
must be run with only one server daemon. We strongly recommend that
you do not start more than one daemon, as you may see unpredictable
failures.
* TeamConnection is actively working on removing these limitations
and restrictions. If you encounter additional problems, please
contact your service representative.
5. DataAtlas Performance Considerations
=======================================
* Significant performance and scalability improvements have been
made in this DataAtlas CSD and its associated TeamConnection
fixpack, especially for DB2/MVS related objects. Further
improvements in performance will be a focus for the next release
of DataAtlas.
* TeamConnection currently supports DataAtlas only on an OS/2-based
server, which supports a limited number of concurrent users of
"fine-grained" data, such as that used by DataAtlas. Operations
that are described below as "CPU-intensive" may degrade the
performance of other DataAtlas operations which would otherwise
perform well. We recommend that if many users will be active in
DataAtlas concurrently, you should schedule such "CPU-intensive"
operations for a time when the expected user load will be light.
* The DataAtlas populate function can be quite CPU-intensive,
depending upon the number of objects involved in the populate.
To obtain adequate performance during populate, close any
workfolders that contain objects used during the populate. This
will allow populate to clean up the local cache memory as it
progresses.
* Queries that involve many DataAtlas objects, or that span across
many objects, can be very CPU-intensive. To get the best performance
from your SQL queries, write queries that reference only those
columns in which you are interested. A few viewtypes have hundreds
of columns, so returning all columns can potentially be slow.
For example:
1) SELECT d.* FROM OUTER DataAtlasDBD d; --> potentially long-running
2) SELECT d.rootDBDname FROM OUTER DataAtlasDBD d; --> faster query
* Some DataAtlas Designer activities are CPU-intensive, requiring some
time for execution:
- Concurrent tasks, like propose, validate, or inform, on many
objects simultaneously
- The Propose Foreign Key task for a given table when the
physical design object contains many tables
- Opening a physical design group (DB2/MVS table, DB2/MVS
tablespace, etc.) with more than 50 objects in that group
* The DataAtlas Modeler forward and reverse transform operations can be
very CPU-intensive. We recommend that for models with more than 100
entities, these operations be done on a client machine with more than
32MB RAM.
* In each execution of DataAtlas, there is an initial overhead for the
first access of each object type in the TeamConnection database.
Later accesses of any other objects of each type will not incur this
overhead.
* Opening the maintenance notebook for certain DB2/MVS objects will
also retrieve information for certain related objects into the local
cache. For example, opening an Index will retrieve information about
the related Table. Opening a Table will retrieve any other Tables for
which it has a foreign key. Retrieving this additional information
will slow the performance of opening the maintenance notebook for the
object. However, that information is now in the local cache, so the
performance of opening the related objects would be improved.
* Objects which have been viewed via their maintenance notebook
or which have been generated may take up space in the local cache
memory so long as the workfolder is open, degrading performance
over time. Periodically closing the workfolder will clean up the
local cache, improving the performance as well as saving the state
of the workfolder. We also recommend closing and restarting
DataAtlas each day for complete local cache cleanup.
* We strongly recommend that you run the DataAtlas client on a separate
machine from your TeamConnection server. This will improve the
performance for most DataAtlas tasks.
* With the TeamConnection server on its own machine, we recommend that
you set the OS_CACHE_SIZE environment variable for the TeamConnection
server daemon to at least half the total memory of the machine, but
leaving at least 16MB available. For example, on a server machine
with 64MB RAM, set OS_CACHE_SIZE to at least 32MB but no greater than
48MB. This will improve the performance of the largest DataAtlas
tasks, such as populates and Modeler transforms.
6. Population of IMS PSBs and DBDs in Object Form
=================================================
IMS PSBs and DBDs in object form, typically members in a PSBLIB or
DBDLIB, can be populated by DataAtlas. Since the populate function
works only from source code, the object modules must be converted
to source form before they can be populated. A set of utilities
to do this conversion are available in the IMS System Utilities/Data
Base Tools (DBT) Version 2 product. DBT's DBD/PSB/ACB Library
Management Utilities contain several useful functions: DBD/PSB/ACB
Compare, Mapper and Reversal. The function used to convert object
code to source is Reversal.
Even in the best-run shops, the definitions of objects stored in
a repository database sometimes differ from those in production.
You should periodically regen and compare all of the objects for
a given application to the objects being used in production to
verify the integrity of the data in the database. This process
is analogous to taking an annual inventory to verify that the
perpetual inventory records are correct.
7. Loading Generated DB2 DDL
============================
* The generated DDL that you wish to load into your target DB2/2
system from a file requires the -f option to specify a file and
the -t option to accept the semicolon (;) as the statement
termination character in the DB2 batch command.
* Generated DDL for DB2/MVS needs post processing:
Due to a known problem that will be fixed in a future release, the
generated DDL places the ALTER statements for foreign key
creation ahead of the INDEX statements, resulting in DDL that may
be out of order. The REXX command file EWSMVALT.CMD
can be used to move the ALTER statements to the end of the DDL file.
This command file can be found in the \CLIENT subdirectory of the
directory where you installed DataAtlas Dictionary and Designer
Version 1.0.1.
8. DataAtlas Dictionary Maintenance Limitations
================================================
* DB2/MVS partitioned indexes that use GRAPHIC columns in the
index are currently not supported.
* Very little syntax checking is performed on the COBOL PICTURE clause.
* Negative scale values are not yet supported on the RDB, VisualGen,
or COBOL representations.
* In some notebooks, validation will be performed on the name,
variation and revision fields to ensure that invalid or reserved
characters are not used. This validation may not be performed
in all cases, however. Among the set of characters that you may
not use in an object name, variation, or revision are <, >, :, and |.
If you use any of these characters and the mistake is not caught
by a validator in a notebook, unexpected results may occur.
* DataAtlas reports are saved on your hard disk in the directory
specified by your DataAtlas profile. You can delete any of the
files with the name val*.rpt, dbd*.rpt, psb*.rpt, cob*.rpt or rdb*.rpt
when you no longer need these reports.
* New tables created as a result of a forward transfrom from the
Modeler are not automatically added to your workfolder. You must
add them to a workfolder before you can generate the DDL.
* If you are using a profile created by the DataAtlas 1.0 product,
ensure that the mandatory fields on the General Page of the Profile
(working, Populate, Generate, and Query directory paths) are filled
in with a value. If you do not do this, you may encounter the
following error:
EWS0088S: A processing error occurred while attempting to access
an attribute or object. The object type being accessed was
<DSMultiPlatformFile>. The attribute that could not be
gotten was <OS2/MVS info>.
* When attempting to use the ims, db22, db2 or cobol builder, the
DataAtlas Profile must exist on the build processor machine. If
the Profile does not exist, start DataAtlas on the machine. After
the create Profile panel appears, press OK to create the Profile.
Close DataAtlas. This is also true for any user-created builder
using DataAtlas build scripts.
* Included Source Definition and Shareable Data Structure maintenance
functions have these limitations:
- Information may be hidden if the notebook is not resized
- Little syntax checking is done during create or update; the
validation done during the Generate step will catch problems
that would otherwise be caught by the compiler
- The Included Source Definition support does not allow Level 88s
on items nested directly within the Included Source Definition
- The Shareable Data Structure support does not allow arrays of
shareable components or the creation of OCCURS DEPENDING ON
relationships between arrayed objects and components outside
of the root Shareable Data Structure
- There is no support for POINTER and PROCEDURE-POINTER types
of data items
9. DataAtlas Designer Maintenance Limitations
=============================================
* You cannot create a physical design directly from a DataAtlas
workfolder. To create a new physical design, you must first create
a relational design, and then create the physical design from that
notebook.
* When working with the propose function of the Designer, you must
provide as input the necessary data load and work load information.
* You can specify a usage intent of a DB2/MVS storage group. However,
this usage intent will not be enforced by the system.
* Proposed new objects are not automatically included in the current
workfolder. If you want to include them in a workfolder, you must
search the TeamConnection database after running the propose function
which created the new objects.
* If you start a propose rule action from an opened notebook and then
execute the proposals, you will see the changes only after you have
closed the proposal actions panel.
* When object names are changed, new names are not directly reflected
in the notebooks of affected objects. You will see the new names only
after you have closed and reopened these notebooks.
10. TeamConnection DataAtlas Build Scripts
==========================================
When using TeamConnection to build DB2/x DDL, IMS source, or COBOL COPY
files, you may see the following messages in the Build Progress window on your
TeamConnection client workstation:
6021-700 Number of distinct build events for this build: 1.
Build of 'ims01.dbd' failed at '17:33:15 1996-08-20'.
Completed Jobs: 726908
Remaining Jobs: 726804
Processing Completed for 'ims01.dbd'.
6021-637 The build of part: 'ims01.dbd' in work area: '' and release:
'(null)' has already been canceled.
Disregard these messages in the Build Progress window and view the Build
Message for the output part, namely the DB2/x DDL, IMS source, or COBOL
COPY file, to determine the disposition of build events.
11. COBOL Populate/Generate Limitations
=======================================
* There is a known problem with the SYSADATA produced by the VisualAge
for COBOL for OS/2 compiler version 1.2 that results in incorrect
data being populated into the DataAtlas Dictionary. For example,
if you populate a Included Source Definition containing a data item
with a value of four (4) apostrophes
05 APOST-04 PIC X(4) VALUE ''''.
the populate will appear to work correctly. However, an attempt to
generate the Included Source Definition that contains this data item
will fail because the VALUE is incorrect.
This problem should be fixed by the VisualAge for COBOL for OS/2
"1.2 Refresh" that is planned to be available in September 1996.
* There is another known SYSADATA problem in which a level 88 data item
that has a large number of values (for example, more than 50) appears
to be populated correctly. However, the SYSADATA actually contains
one or more incorrect values. Therefore, an attempt to generate
the includedSourceDefinition that contains the level 88 data item
will fail with a compilation error.
The fix for this problem should be available in the release of
the VisualAge for COBOL for OS/2 compiler that follows the
"1.2 Refresh."
* There is a known problem in DataAtlas in which a data item with a
picture of the form X(nnnnn) where n is a numeric can be populated,
but not generated. An example is "05 DataItemA PIC X(32000)". Also,
an attempt to open an includedSourceDef or shareable Data Structure
that contains a data item with such a picture may trap.
A fix for this problem can be obtained from DataAtlas service.
* You may experience problems when executing a Trial Run Populate
followed by a real Populate of the same object within the same
DataAtlas session; you may receive Duplicate Name errors. A common
cause for this error is that the cache is not cleaned up properly
between populates. If you receive this error, ensure that all
workfolders that contain objects used during the Populate are closed
prior to executing subsequent populates.
12. National Language Support
=============================
DataAtlas supports the following code pages:
437 (English), 850 (Multilingual), 852 (Latin 2), 857 (Turkish),
932 (Japanese), 942 (Japanese SAA), 933 (Korean), 950 (Taiwanese).
The current version of DataAtlas is presented in English. A Japanese
language version wll be available next year.