Previous Topic: Creating New SQL TablesNext Topic: JCL Considerations


Coding Considerations

DATABASE

The DATABASE parameter is optional. If it is present, it must always be the first parameter in your CA Culprit syntax.

PROFILE

The PROFILE parameter is also optional. The USER= and PW= clauses should be specified if CA Culprit security is on.

INPUT

Input data can be retrieved from any accessible source: Sequential files, ISAM, VSAM, IMS, DL/I, CA IDMS/DB non-SQL records, ASF tables, CA IDMS/DB SQL tables, and so on. Data retrieval is independent from SQL table creation. Thus, CA Culprit can be used as a migration tool, reading data from one medium and converting it to an SQL table.

OUTPUT

Up to 100 reports can be processed in a single CA Culprit run. Any number of these reports can update SQL tables, using the create, add, replace, and drop functions. Data written to SQL tables can be details-only or totals-only.

DETAIL

DETAIL (Type 5) parameters describe the columns and null indicators for the detail-only SQL table being created. If a totals-only table is being created, type 5 parameters are used to specify automatic subtotals for numeric fields.

TOTAL

TOTAL (Type 6) parameters are only used when creating totals-only SQL tables. They describe the columns and null indicators for the SQL table being created.

PROCESS

Type 7 parameters let the user code processing logic that is executed after each input record is read. Type 8 logic is executed when each control break is encountered at total-time. No changes to these process parameters are needed when writing output to SQL tables.