This article describes what is contained in the SQLSCHEM file after a subschema in the AppMaster Builder Desktop Database View is created, and whether this file can be modified.
Problem:
After creating a subschema in the AppMaster Builder Desktop Database View, can the SQLSCHEM file be modified?
Resolution:
The sequential file TESTSQL1 was created in the SUBSCHEM folder in the AppMaster Builder project. (A sample file is below.) The purpose of this file is to create a list of SQLDDL definitions for each table in the subschema and to list the physical location of those input source files. The SQLDDL files can be located on the mainframe or in a PC folder. In this example, the subschema brings in three DB2 tables. The DDL definitions for the first two tables are read from the mainframe location of MFI01.SOURCE.SQLDDL, and the third SQLDDL file is located on a network mapped drive.
This is an ordinary text file, so it can be manually edited, but you should take care to ensure that the correct format and syntax are used. In particular you will notice that there is an open paren "(" following the CREATE statement. Each table name is comma-delimited. The statement ends with a closing paren ")" with an ending DB2 termination character ";."
CREATE SUBSCHEMA TESTSQL1 (
INFOAPS.TINFINQZ -- OF "MFI01.source.SQLDDL(tinfinqz)"
,INFOAPS.VINFINQZ -- OF "MFI01.source.SQLDDL(tinfinqz)"
,RFF51.VINFINQZ -- OF "Y:\\source\\update3\\mirror\\prod1\\aps\\SQLDDL\\ddlvinqz"
);
Incident Number: 2261672
#MFDS
#EnterpriseDeveloper
