AUTODB2 and AUTOSQL

The AUTODB2 and AUTOSQL facilities are FOCEXECs that gather column information from RDBMS catalog tables and use the information to create Master and Access Files.

In this section: AUTODB2 Support for DDF Use AUTODB2 and AUTOSQL AUTODB2 in Batch Mode How to: Install AUTODB2 DDF Support Example: Creating a Location List

When you invoke the AUTODB2 and AUTOSQL facilities, they present you with a series of menus that prompt you to identify the tables you want to describe and the relationships between them. If you are unfamiliar with any of the terms used in this section, review Multi- Table Structures. Subsequent sections explain each menu in detail, and AUTODB2 Sample Session contains a sample session.

The following is a brief overview of the AUTODB2 and AUTOSQL screens:

• The initial screen, or Main Menu, allows you to name your Master and Access Files and to identify the tables that may contain columns needed for defining them. You can use wildcard characters to generate a list of tables from which to choose. You can also change certain default values that are displayed on this screen.
• The Table Selection Screen displays the list of tables generated as a result of your entries on the Main Menu. You can select tables from the list displayed. If you choose more than one table, you must designate one to be the root and the rest to be children.

Note:

Descendant is a synonym for child. Both terms, used interchangeably in the following discussion, refer to tables related by embedded equijoins, as described in Multi-Table Structures.

If you select just a root table, and no children, on the Table Selection Screen, AUTODB2 or AUTOSQL creates your single-table Master and Access File at this point. If you choose at least one child table, you proceed to the Child Selection Screen.

• The Child Selection Screen prompts you to identify pairs of related tables.
• The Common Column Selection Screen asks you to identify the primary and foreign key columns for each pair of related tables (see Multi-Table Structures, for an explanation of multi-table structures).

After you describe all the relationships, AUTODB2 or AUTOSQL creates the Master and Access Files. How to Use AUTODB2 and AUTOSQL contains sample screens and explains AUTODB2 and AUTOSQL defaults.

You can use the resulting pair of file descriptions immediately or edit them to include such options as DEFINE commands. As with any Master File, you can add additional security by including FOCUS DBA security attributes.

Note: If a table has a Master File created in a prior FOCUS release, and if you re-run AUTODB2 or AUTOSQL on the table, some field names and/or USAGE formats generated in the new Master File may differ from those in the old Master File. As a result, requests that ran against the old Master File, and DEFINE fields based on field length, may require changes.

The RDBMS system catalog table, SYSCOLUMNS, provides column information such as column names, data types, column lengths, and whether null values are allowed. System catalog tables SYSKEYS (DB2) and SYSINDEXES provide unique index information. The RDBMS searches for the first unique index created and uses the columns on which this index is defined as the primary key.

In addition to the ability to create multi-table Master and Access Files in interactive mode (batch mode remains limited to one table description per execution), the AUTODB2 and AUTOSQL facilities include the following three key features:

• They provide an option on the Main Menu for assigning a USAGE attribute of either x or x.0 to table columns of data type DECIMAL(x,0).
• They provide an option on the Main Menu for changing default Main Menu entries and logging the new default values to a text file for repeated use.
• They provide an extensive on-line help facility.

AUTODB2 uses only FOCUS DYNAM dynamic allocation, freeing it from any dependence on TSO. The MSO run-time requirements and user interface are identical to those of AUTODB2 running in the TSO environment; the user or installer need make no modifications. Users familiar with AUTODB2 in the TSO environment will find it identical under MSO.

You can execute AUTODB2 and AUTOSQL in batch mode for single-table structures by supplying the necessary execution parameters at invocation, eliminating the need for input screens. For AUTODB2, batch mode execution is possible in the MSO and TSO environments as well as in MVS batch. See AUTODB2 in Batch Mode for an explanation of batch execution.

AUTODB2 Support for DDF

AUTODB2 supports retrieval from and Master File creation for tables from secondary locations. When a location is specified, the TABLENAME attribute in the Access File consists of three parts: location.creator.tablename.

During installation, a list of valid locations is included in the AUTODB2 utility. The list appears on the main menu, just below the row in which the user can enter the location. The first value in the list appears by default in the main menu. The user can enter any one of the values in the list. Entering a value not on the list generates the following error message:

PLEASE ENTER A VALID LOCATION.

Table, column, and index information is retrieved from the selected location's catalog tables. The location is included in a three-part table name in the Access File if it is not blank.

Note: The menu option 'Use Creator Name in AFD?=N' is ignored when a non-blank location is provided. That is, the creator is included in the three-part table name even when you specify to not include it on the main menu.

The value for location that you include on the menu is logged to the parameter log file when you press PF4 to log parameters. The next session of AUTODB2/SQL will display the logged value.

Procedure: How to Install AUTODB2 DDF Support

Create a list of valid locations by editing the following lines in the AUTODB2 FOCEXEC. Uncomment the -DEFAULT command and enter up to six location names. The start and end of the list must be enclosed in single quotation marks, and each name must be eight characters long, padded on the right with blanks if necessary:

-*=======================================================================
-* Change &LOC_LIST to contain possible location values, padded to 8
-* characters, separated by commas.  The entire string is enclosed in
-* single quotes.  Include a maximum of 6 locations.  The first entry is
-* the default. Example:
-* -DEFAULT &LOC_LIST='PROD    ,TEST    ,DEVELOPM'
-*                  <------>,<------>,<------>,<------>,<------>,<------>
-DEFAULT &LOC_LIST='

A blank location name designates the location where the plan was bound.

Example: Creating a Location List

With the following list, blank will be the default value that appears on the main menu.

-DEFAULT &LOC_LIST='        ,LOCDSNA ,LOCDSNC '

Note: Specifying blank (' ') as the first option indicates that the default is the location where the plan was bound.

How to Use AUTODB2 and AUTOSQL

Before starting AUTODB2 or AUTOSQL, it is helpful to know the names of the tables or views you will be using (including, if possible, their creator names and, for DB2, their database and location names). Having this information in advance can avert a costly search of the RDBMS catalogs using wildcard characters from the Main Menu. Get this information from your RDBMS database administrator, or query the system table SYSCOLUMNS using Master File DB2CAT for DB2 or SYSCOL for DB2 for VM. (See Additional Topics, for a sample request.)

In this section: The Main Menu Main Menu PFkeys The Table Selection Screen The Child Selection Screen The Common Column Selection Screen Completing the Description Using PFkeys From non-Main Menu Screens Retaining the List of Master Files Generated Changing the AUTODB2 Default Data Sets The MVS Parameter Log File AUTODB2/SQL Usage Notes

The first time you execute AUTODB2 or AUTOSQL, many of the entry fields on the Main Menu screen display default values. You can customize the default values for your application and use PF4 to store them in a parameter log file for future use. The PFkey functions are explained following the description of the Main Menu entry fields.

You also need enough available disk space. The AUTOSQL facility writes the new file descriptions directly to the disk accessed as filemode A. AUTODB2 writes the file descriptions directly to the data sets specified on the Main Menu.

To start AUTODB2 or AUTOSQL, enter the FOCUS environment and issue the following command from the FOCUS command level:

EX {AUTODB2|AUTOSQL}

Press the Enter key.

The Main Menu

The following is an example of the Main Menu for AUTODB2. AUTOSQL displays a similar screen (without the entry fields for the target data set files and without location values). Complete the entry fields on the Main Menu and press Enter to begin processing:

Main Menu Master File Generation Facility for DB2 Master Filename ================> autoemp Location => locdsna Creator => USER1 Table => TIMESTMP Location values: ,LOCDSNA ,LOCDSNC Database Name ================> * Description will be a member of: Master Target PDS => USER1.MASTER.DATA Access Target PDS => USER1.FOCSQL.DATA FOCDEF Target PDS => USER1.FOCDEF.DATA Replace Existing Description?=> Y (Y/N) Read/Write Functionality =====> W (R=Read,W=Write) Date Display Format ==========> YYMD Time Stamp Display Format ====> HYYMDm Time Display Format ==========> HHIS Display Decimal when SCALE=0?=> Y (Y/N) Use LABEL as Column Heading? => N (Y/N) Use Remarks for FOCDEF? ======> N (Y/N) Use Creator Name in AFD? =====> Y (Y/N) Use Long Fieldnames? =========> Y (Y/N) Parm File => USER1.FOCSQL.DATA PF1=Help PF2=Restart PF3=Exit PF4=Log PF5=MFD PF6=AFD PF9=Picture PF10=List

The following list describes the Main Menu entry fields:

Location	Applies to MVS only. Is one of the values on the list of location values displayed immediately below this entry field. The first location on the list is displayed initially. Table, column, and index information is retrieved from the selected location's catalog tables. The location is included in a three-part table name in the Access File if it is not blank. The menu option 'Use Creator Name in AFD?=N' is ignored when a non-blank location is provided. That is, the creator is included in the three-part table name even when you specify to not include it on the main menu. If the first option is blank (' '), the default is the location where the plan was bound.
Master Filename	Is the 1- to 8-character name you select for referring to the data in requests. In MVS, this name must be a valid member name. In CMS, this name must be a valid filename.
Creator Name (or *)	Is the 1- to 8-character creator name of the tables that you want to describe. Specify an asterisk (*) to select tables for all creators. The default is your userid. You can use the asterisk (*) wildcard character in the creator, table, and database name entry fields to create a list based on the provided pattern. Note: You cannot enter a name that contains a dollar sign ($) in the creator, table name, or database name entry fields; however, with the asterisk (*) wildcard character, you can generate a list that includes names containing dollar signs. You can then choose tables from this list.
Table Name (or *)	Is the 1- to 18-character name of an existing table that you want to describe. An asterisk (*), the default, selects all tables.
Database Name (or *)	Applies to MVS only. Is the 1- to 8-character name of the database that contains any or all tables you may select. An asterisk (*), the default, selects all databases. You can omit this value if you provide creator or table.
Master Target PDS	Applies to MVS only. Is the fully qualified data set name of the Master File PDS in which to store the Master File. Do not use quotation marks (single or double) in the data set name. The default is 'userid.MASTER.DATA'.
Access Target PDS	Applies to MVS only. Is the fully qualified data set name of the Access File PDS in which to store the Access File. Do not use quotation marks (single or double) in the data set name. The default is 'userid.FOCSQL.DATA'.
FOCDEF Target PDS	Applies to MVS only and is required only if you specify Yes (Y) in the "Use REMARKS for FOCDEF?" field. Is the fully qualified data set name of the FOCDEF File PDS in which to store the TableTalk® Help file. Do not use quotation marks (single or double) in the data set name. The default is 'userid.FOCDEF.DATA'.
Replace Existing Description?	Specifies whether to overwrite existing Master and Access Files (Y/N). No (N) is the default. Yes (Y) replaces existing descriptions of the same name.
Read/Write Functionality	Indicates read-only or read/write access in the Access File. Read/Write (W), the default, allows MODIFY and MAINTAIN to update the RDBMS table. Read (R) is for reporting only. Note: If the data adapter was installed for read-only access, this field displays an R and cannot be changed.
Date Display Format	Is a valid FOCUS USAGE date format for RDBMS columns described as dates. The default is YYMD.
Time Stamp Display Format	Is HYYMDm by default. A26 is also acceptable, for compatibility with prior releases.
Time Display Format	Is HHIS by default. A8 is also acceptable, for compatibility with prior releases.
Display Decimal when SCALE=0?	Yes (Y), the default, displays the decimal point for DECIMAL values with no fractional component (for example 123.); No (N) excludes the decimal point (for example, 123).
Use LABEL as Column Heading?	Selects FOCUS report column headings. No (N), the default, uses the column name for headings; Yes (Y) uses the RDBMS LABEL.
Use Remarks for FOCDEF?	Indicates whether to include RDBMS REMARKS as HELP for TableTalk. No (N), the default, excludes the remarks; Yes (Y) includes them. In MVS, you must specify a FOCDEF Target PDS in order to select Y.
Use Creator Name in AFD?	Indicates whether to include the creator name in the TABLENAME keyword of the Access File. Yes (Y), the default, includes the creator name; No (N) includes only the table name.

Main Menu PFkeys

You can implement the following functions from the Main Menu with PFkeys:

Key	Function	Description
PF1	Help	Accesses on-line help.
PF2	Refresh the List of Tables	Clears the existing list of tables maintained by AUTODB2/SQL for this session. When you select tables from the Main Menu, information is gathered from the system catalogs. Each time you change the selection criteria, the new tables are appended to the existing list. Pressing PF2 purges this list without exiting AUTODB2/SQL. You receive the message "Enter new table selection criteria" when the list is successfully purged. No message is displayed if you have not yet created a list of tables.
PF3	Exit	Ends the AUTODB2/SQL session and returns to FOCUS.
PF4	Log Default Menu Parameters	Saves the values that you want to see displayed as defaults on the Main Menu in future executions of AUTODB2/SQL. In MVS, your defaults are saved in member DB2$PARM in the parm data set indicated on the menu. This data set is either: the PDS pre-allocated to DDNAME DB2$PARM, 'userid.FOCSQL.DATA', or the first data set allocated to DDNAME FOCSQL, whichever the system finds first (see The MVS Parameter Log File for more detailed information on the search order). In CMS, your defaults are saved to filename SQL$PARM FOCSQL A. The following information is logged: Location Creator Name Table Name Database Name (MVS only) MFD Partitioned Data set Name (MVS only) AFD Partitioned Data set Name (MVS only) FOCDEF Partitioned Data set Name (MVS only) Replace existing description Read/Write Functionality Date Display Format Time Stamp Display Format Time Display Format Display Decimal when SCALE=0 Use LABEL as Column Heading Use REMARKS for FOCDEF Use Creator Name in AFD Note: The values you enter must pass all validation tests in order for the new default values to be logged.
PF5 PF6	TED MFD TED AFD	Allows you to edit, using TED, the Master (PF5) or Access (PF6) File whose name you entered (as mastername) in the Master Filename entry field on the Main Menu. In MVS, you access member mastername in the data set entered as either Master Target PDS or Access Target PDS. In CMS, you access 'mastername MASTER A' or 'mastername FOCSQL A'. Note: You can edit these files even if they were not created with AUTODB2/SQL.
PF9	Picture of MFD	Generates a diagram of the file entered in the Master Filename entry field on the Main Menu. After the picture is displayed, type any character and press Enter to return to the menu. To generate the picture in MVS, the mastername entered as Master Filename must be a member of a data set allocated to DDNAME MASTER (the Master Target PDS is not used).
PF10	Table List	Displays a list of all tables that meet the screening criteria provided in Creator Name, Table Name, and Database Name.

Note: The PFkey options are available only if the values you enter on the screen pass all validation tests. See Common Errors for a discussion of common errors. See Using PFkeys From non- Main Menu Screens for PFkey options available on other screens.

After you specify the appropriate values on the initial screen, press Enter. AUTODB2/SQL informs you that it is creating a list of tables with the following message:

**=============================================================** ** AUTODB2 is retrieving TABLE information from catalog. ** ** Please wait... ** **===============================================================**

It displays this message only for the first retrieval per AUTODB2/SQL session, or when the selection criteria have changed since the previous retrieval within the session. AUTODB2/ SQL does not access the catalog a second time for the same immediate selections in a single session.

The Table Selection Screen

If you specified a location on MVS, the table selection screen displays the location parameters for the list of tables generated by your selections on the main menu:

Master: Master File Generation Facility for DB2 TIMSTMP ==Table Selection== Place an 'R' next to the Table to be the root of the Master. Place a 'C' next to all other Tables to be described as children. Enter 'Y' next to all selected Tables that will be updated. Location Creator Name B2 Table Name Select (R/C) Write (Y/N) -------- ------------ -------------- ------------ ------------ LOCDSNA USER1 TIMESTMP r Y PF1=Help PF3=End PF4=Add Tables PF7=Up PF8=Down

When table information retrieval is complete, choose the tables to include in your Master and Access Files:

Master: Master File Generation Facility for DB2 AUTOEMP ==Table Selection== Place an 'R' next to the Table to be the root of the Master. Place a 'C' next to all other Tables to be described as children. Enter 'Y' next to all selected Tables that will be updated. Location Creator Name DB2 Table Name Select (R/C) Write (Y/N) -------- ------------ -------------- ------------ ----------- USER1 ADDRESS c Y USER1 COURSE Y USER1 DEDUCT Y USER1 EMPINFO r Y USER1 FUNDTRAN Y USER1 PAYINFO c Y USER1 SALINFO Y PF1=Help PF3=End PF4=Add Tables PF7=Up F8=Down

The Table Selection Screen displays, in alphabetical order, the names of all creator/table combinations that pass the selection criteria you provided on the Main Menu. You can choose up to 64 tables to include in the description.

Identify the root table by placing r in its Select column. Choose all other tables to be included in the Master File by placing c in their Select columns. Indicate those tables that can be updated in this view by placing y in their Write columns.

Note: If the data adapter was installed for read-only access, the Write column displays an N and cannot be changed.

The following message displays after you complete the table selections:

**=============================================================** ** AUTODB2 is retrieving COLUMN information from catalog. ** ** Please wait... ** **===============================================================**

Note: If you selected only a root table, the preceding message does not appear; instead, AUTODB2/SQL creates the description and returns to the Main Menu.

AUTODB2/SQL retrieves column information from the catalog only the first time you select a particular table from the Table Selection Screen. You will not see this message when you make subsequent selections using the same tables. To erase this list and create a new one, return to the Main Menu with PF3, and restart with PF2.

The Child Selection Screen

When column information retrieval is complete, specify descendants, if any, for each table. To give you the opportunity to identify all parent-child relationships, every table on your list, in turn, presents its own Child Selection Screen:

Master: Master File Generation Facility for DB2 AUTOEMP ==Child Selection== Place a 'C' next to the descendants of Parent: USER1 EMPINFO Location Creator Name DB2 Table Name Select (C) -------- ------------ -------------- ------------ USER1 ADDRESS c USER1 PAYINFO c PF1=Help PF2=Restart PF3=End PF4=None PF5=Picture PF7=Up PF8=Down

If the parent segment named at the top of the screen has no children, press PF4. Otherwise, place c in the Select column for each table that is a child of the parent table named at the top of the screen, and press Enter. Next, AUTODB2 or AUTOSQL displays a Common Column Selection Screen for each parent-child pair so you can identify the columns they share.

The Common Column Selection Screen

For each parent-child pair, identify the primary keys from the parent table and the foreign keys from the related table on the Common Column Selection Screen:

Master: Master File Generation Facility for DB2 AUTOEMP ==Common Column Selection== Number the primary key columns | Number the corresponding foreign (in sequence) in the Parent Table: | key columns in the Child Table: USER1 EMPINFO | USER1 ADDRESS | Key Column Name Format | Key Column Name Format ----------------------------------------------------------------------- 1 EID A9 | 1 EID A9 LN A15 | AT A4 FN A10 | LN1 A20 HDT YYMD | LN2 A20 DPT A10 | LN3 A20 CSAL P9.2 | ANO I9 CJC A3 | OJT F9.2 | BONUS_PLAN I9 | HDTT HYYMDm | HT HHIS | | PF1=Help PF2=Restart PF3=End PF4=Skip PF7=Up PF8=Down

Number the key fields from each table in sequence (from 1 to 16). Each primary key field must have the same format as its corresponding foreign key field. Use PF4 to skip this table if it was selected in error. This does not affect previous or subsequent selections; however, the "skipped" segments appear in subsequent lists when you return to the Child Selection Screen to define any additional paths in the hierarchy.

AUTODB2/SQL guides you in describing the table relationships in top down, left to right order. Initially, it displays the root table and all of its selected children.

Completing the Description

After you complete the Common Column Selection Screen for the root table, AUTODB2/ SQL displays a Child Selection Screen for the first child of the root. Assign children, if any, to this table.

Child selection continues down this first path until you press PF4 to select no descendants, or you exhaust the list of descendants. Only then does AUTODB2/SQL display a Child Selection Screen for the second child of the root. This process continues until all tables have been assigned children or all possible descendants have been exhausted.

At this point, AUTODB2 or AUTOSQL generates the Master and Access Files and returns to the Main Menu; the message "DESCRIPTION CREATED" displays at the bottom of this Status Screen with an indication, if necessary, of how many duplicate fieldnames were generated and how many unsupported data types were found.

Note: If duplicate fieldnames were created, either edit them to be unique, or qualify them with the segment name when referencing them in requests.

For information about the newly generated file descriptions, see Results of the Master File Generation Facilities.

Using PFkeys From non-Main Menu Screens

For each screen other than the Main Menu and Table Selection screens, you can erase your current selections and back up one screen with PF2. Pressing PF3 returns you to the Main Menu with all selections intact. To erase your selections from the Table Selection Screen, return to the Main Menu with PF3, and then restart with PF2.

From the Child Selection Screen, use PF5 to generate a diagram of your file structure. The description is created on disk and remains there even if you end the program with PF3. After the picture is displayed, type any character and press the Enter key to return to the menu. To generate the picture in MVS, you must allocate the target master PDS to DDNAME MASTER. If a member with the selected master name exists in a data set concatenated in front of the target data set, the picture is generated from that member.

Retaining the List of Master Files Generated

AUTODB2/SQL maintains a temporary list of the Master Files generated during any one session. This list is refreshed at the beginning of each session and erased at the end of the session. You may retain the list by executing AUTODB2/SQL (either on-line or in the background) with the following syntax:

EX {AUTODB2|AUTOSQL} MFDLIST=Y

In MVS, the list resides in a temporary data set allocated to DDNAME AUTODB2L, with a disposition of MOD and record length of 114. In CMS, the list resides in the file AUTOSQLL FOCTEMP A with a record length of 26. It is the user's responsibility to free or erase this file when it is no longer required. The file layout is:

Length	Columns	Description
8	1 - 8	Master Filename
8	9 - 16	Number of duplicate fieldnames
5	17 - 21	Number of unsupported data types
5	22 - 26	Number of long decimal fields truncated. This entry, required in prior releases, exists for upward compatibility.
44	27 - 70	Master Target PDS name (MVS only)
44	71 - 114	Access Target PDS name (MVS only)

Changing the AUTODB2 Default Data Sets

With both AUTODB2 and AUTOSQL, you can save custom Main Menu defaults in a parameter log file for repeated use. For AUTODB2, you can also change the default data sets that display on the Main Menu.

To change the default MVS data set names that appear the first time you execute AUTODB2, customize the following lines of code near the top of the AUTODB2 FOCEXEC. These are the only permanent data sets that AUTODB2 uses. All other data sets are temporary and are named by the system.

-SET &DSNP0=&USERID ||'.FOCSQL.DATA                     ';
-SET &DSNM0=&USERID ||'.MASTER.DATA                     ';
-SET &DSNF0=&USERID ||'.FOCSQL.DATA                     ';
-SET &DSND0=&USERID ||'.FOCDEF.DATA                      ';

Note: You must preserve the length of the data set name for each variable (the result of concatenating the userid with the string between the single quotation marks) at 44 characters. If necessary, pad the name with blanks to maintain the correct length. You may not change any other lines in the FOCEXEC.

The MVS Parameter Log File

The parameter log file, if there is one, is always a data set allocated to DDNAME DB2$PARM in MVS. MVS identifies the parameter log file with the following steps:

1. If DDNAME DB2$PARM is allocated to a PDS prior to execution of AUTODB2, AUTODB2 uses member DB2$PARM as the parameter log file; if the member does not exist, AUTODB2 creates it. This allows the user to identify the "profile" data set prior to execution of AUTODB2 and is recommended for sites that have non-standard data set naming conventions.

If this DDNAME is allocated to a sequential data set, AUTODB2 frees it, generates a message, and disables parameter logging.

If DDNAME DB2$PARM is not allocated, AUTODB2 continues searching and attempts to allocate it in the steps that follow. AUTODB2 does not free this DDNAME upon exiting, assuming that it may be used again.

2. AUTODB2 allocates data set name 'userid.FOCSQL.DATA', the default name provided in the code as &DSNP0, as the parameter log file. If the default has been changed, it uses the new data set name. This assumes standard Information Builders naming conventions.

This data set must be a PDS. If it is not, AUTODB2 displays a message and disables parameter logging.

3. If the first two steps fail to identify a parameter log file, AUTODB2 allocates the first data set allocated to DDNAME FOCSQL as the parameter log file. This assumes that the user's data set is allocated first in the concatenation of data sets to DDNAME FOCSQL.

If the data set allocated to DDNAME FOCSQL is sequential, AUTODB2 displays a message and disables parameter logging.

Note:

AUTODB2 cannot function properly if the data set is not a PDS.

Parameter logging assumes that the user has write access to the target data set. An attempt to log parameters to a data set without write access results in a security abend.

AUTODB2/SQL Usage Notes

• AUTODB2/SQL is a FOCEXEC that has a corresponding Master File. The FOCEXEC and Master File must be from the same release of FOCUS. If you attempt to use the old version of the Master File with the new version of the FOCEXEC, the following message is generated:

PROGRAM AND FILE DESCRIPTION DATES DO NOT MATCH: AUTODB2 date
UNABLE TO EXECUTE AUTODB2 - PLEASE REINSTALL

FOCEXEC execution is terminated, and you return to the FOCUS prompt.

• AUTODB2 no longer needs the DB2CAT Master and Access Files and AUTOSQL no longer needs the SYSCOL Master File or INDEXES Access File. These Master and Access Files remain on the distribution tape. They are copied as part of the installation on VM; MVS instructions tell you to copy them also. However, Information Builders no longer certifies the accuracy of these Master and Access Files with future RDBMS catalog table changes.

AUTODB2 in Batch Mode

You can create a single-table Master File by executing AUTODB2 in the background with an argument list that supplies the values normally entered on the Main Menu. You can invoke AUTODB2 batch mode processing in the MVS batch, MSO, or TSO environments. The syntax is

EX AUTODB2 BATCH=Y,MASTER=master,CREATOR=creator,TABLENAME=table 
    [,option1=value1 ...] 

where:

master

Is the 1- to 8-character name of the Master File that will be generated.

creator

Is the 1- to 8-character name of the table's creator.

table

Is the 1- to 18-character name of the RDBMS table.

option1 ...

Is an option listed in the following chart.

value1 ...

Is an acceptable value for the corresponding option.

All options from the Main Menu are available. Specify options on the command line by entering name=value pairs separated by commas. The list can extend over several lines. The following chart presents the available options:

Option Name	Values	Description	Default
LOC	location	Location value	First value in the location list
REPLACE	Y=Yes,N=No	Replace existing description	N
FUNC	R=Read, W=Write	Read/Write Functionality	W
DATEDISP	format	Date Display Format	YYMD
TIMESTMP	format	Time Stamp Display Format	HYYMDm
TIME	format	Time Display Format	HHIS
DECIMAL	Y=Yes,N=No	Display Decimal when SCALE=0?	Y
LABELS	Y=Yes,N=No	Use Labels as Column Heading?	N
REMARKS	Y=Yes,N=No	Use Remarks for FOCDEF?	N
CREATAFD	Y=Yes,N=No	Use Creator Name in AFD?	Y
LONG	Y=Yes,N=No	Use Long Fieldnames?	Y
USERID	userid	High level qualifier of output data sets (required if target data set names not provided - MVS only)
MFDLIST	Y=Yes,N=No	Store list of Master Files created per session	N
MASTERDATA	dsn	Master Target PDS (MVS only)	&USERID.MASTER.DATA
FOCSQLDATA	dsn	Access Target PDS (MVS only)	&USERID.FOCSQL.DATA
FOCDEFDATA	dsn	FOCDEF Target PDS (MVS only)	&USERID.FOCDEF.DATA

The default for LOC is the first value in LOC_LIST (provided at installation time). If you want a value of blank, use blank as the first value in LOC_LIST or execute AUTODB2 with the following syntax:

EX AUTODB2 LOC=' '