Before you can create tables with Classic Data Architect, you must import Classic reference files into a data design project. For CA-Datacom, CICS® VSAM, sequential, native VSAM, and IMS™, you import COBOL copybooks and DBDs; For CA-IDMS, you import schema and subschema reports.
About this task
If you want to create tables that map to Adabas databases, you do not need to import files that describe the data structures that you want to map to. When you create an Adabas table, you provide information that tells Classic Data Architect how to locate the data structures in the Adabas database that you want to use.
If you want to create tables that map to CA-IDMS databases, you can either import schema and subschema reports into Classic Data Architect or you can tell Classic Data Architect how to locate the records and sets that you want to use in the CA-IDMS database.
When you import files into a project from a local or remote server, the files are organized into subfolders for that project according to the file types.
You can then use the files that you import into a project to create one or more tables in one or more schemas in any project.
To select the files to import, you can browse the local file system for files or connect to a z/OS® server and browse data sets for members to download using FTP.
When you import a file from your local file system, the file extension is replaced. For example, a COBOL copybook mycopybook.txt is imported into the project as mycopybook.cpy. Imported files are given the following extensions:
File type | Extension |
---|---|
COBOL copybook | cpy |
Schema | sch |
Subschema | sub |
DBD | dbd |
When you import subschemas and schemas, the wizard checks that the subschema belongs to the specified schema and that the file or data set member exists. No other validation is done.
Procedure