SQL catalog - Revision history

ELowell: /* Using the SQL catalog */

2017-10-27T19:03:38Z

Using the SQL catalog

← Older revision		Revision as of 19:03, 27 October 2017
Line 75:		Line 75:

	==Using the SQL catalog==		==Using the SQL catalog==
	The Model 204 SQL catalog contains the SQL definition of the Model 204 files that can be accessed by SQL applications. The SQL catalog is loaded, or populated, with this SQL description of Model 204 files through the Connect<span class="superstar">★</span> Visual Interface utility (CVI). Other Model 204 SQL utilities are available to help you create the DDL for the catalog and to help you monitor the catalog contents.		The Model 204 SQL catalog contains the SQL definition of the Model 204 files that can be accessed by SQL applications. The SQL catalog is loaded, or populated, with this SQL description of Model 204 files through the [[Connect*_to_Model_204_connection#Installing_the_Connect.E2.98.85_Visual_Interface_.28CVI.29\|Connect<span class="superstar">★</span> Visual Interface utility (CVI)]]. Other Model 204 SQL utilities are available to help you create the DDL for the catalog and to help you monitor the catalog contents.

	===Populating the catalog===		===Populating the catalog===

ELowell: /* Model 204 SQL catalog characteristics */

2017-10-27T19:02:39Z

Model 204 SQL catalog characteristics

← Older revision		Revision as of 19:02, 27 October 2017
Line 49:		Line 49:
	</tr>		</tr>
	<tr>		<tr>
	<td>Populated and maintained by the Connect<span class="superstar">★</span> Visual Interface</td>		<td>Populated and maintained by the [[Connect*_to_Model_204_connection#Installing_the_Connect.E2.98.85_Visual_Interface_.28CVI.29\|Connect<span class="superstar">★</span> Visual Interface (CVI)]]</td>
	<td>Input into the CVI, a Connect<span class="superstar">★</span> workstation utility is SQL DDL (data definition language) you create or have generated.		<td>Input into the CVI, a Connect<span class="superstar">★</span> workstation utility is SQL DDL (data definition language) you create or have generated.
	<p class="note"><b>Note:</b> All DDL statements input to the CVI must terminate with a semicolon(;).</p>		<p class="note"><b>Note:</b> All DDL statements input to the CVI must terminate with a semicolon(;).</p>

ELowell: /* Populating the catalog */

2017-10-27T18:55:29Z

Populating the catalog

← Older revision		Revision as of 18:55, 27 October 2017
Line 92:		Line 92:
	<li>DDL that you prepare manually</li>		<li>DDL that you prepare manually</li>
	</ul>		</ul>
	CVI is available to PC clients as part of the Connect<span class="superstar">★</span> Suite.		CVI is available to PC clients as part of the [[Connect*\|Connect<span class="superstar">★</span>]] Suite.

	====Generating DDL with SQL utilities====		====Generating DDL with SQL utilities====

JAL: Dictionary and SQL server from RKTools main menu

2017-06-23T00:21:19Z

Dictionary and SQL server from RKTools main menu

← Older revision		Revision as of 00:21, 23 June 2017
Line 75:		Line 75:

	==Using the SQL catalog==		==Using the SQL catalog==
	The Model 204 SQL catalog contains the SQL definition of the Model 204 files that can be accessed by SQL applications. The SQL catalog is loaded, or populated, with this SQL description of Model 204 files through the Connect<span class="superstar">★</span> Visual Interface utility (CVI). Other Model 204 SQL utilities are available to help you create the DDL for the catalog and to help you monitor the catalog contents.		The Model 204 SQL catalog contains the SQL definition of the Model 204 files that can be accessed by SQL applications. The SQL catalog is loaded, or populated, with this SQL description of Model 204 files through the Connect<span class="superstar">★</span> Visual Interface utility (CVI). Other Model 204 SQL utilities are available to help you create the DDL for the catalog and to help you monitor the catalog contents.

	===Populating the catalog===		===Populating the catalog===
Line 81:		Line 81:
	<ul>		<ul>
	<li>		<li>
	Define or update SQL objects in the catalog that map to Model 204 file data. </li>		Define or update SQL objects in the catalog that map to Model 204 file data. </li>

	<li>		<li>
	Define views of, and the SQL security associated with, these objects.</li>		Define views of, and the SQL security associated with, these objects.</li>
Line 88:		Line 89:
	<ul>		<ul>
	<li>DDL that you generate with mainframe SQL utilities (the Table Specification facility, [[SQL DDL from the Table Specification Facility\|TSF]], or the catalog reporting utility, [[SQL catalog reporting and querying\|CCACATREPT]])</li>		<li>DDL that you generate with mainframe SQL utilities (the Table Specification facility, [[SQL DDL from the Table Specification Facility\|TSF]], or the catalog reporting utility, [[SQL catalog reporting and querying\|CCACATREPT]])</li>

	<li>DDL that you prepare manually</li>		<li>DDL that you prepare manually</li>
	</ul>		</ul>
Line 94:		Line 96:
	====Generating DDL with SQL utilities====		====Generating DDL with SQL utilities====
	<p>		<p>
	The TSF is an interactive Model 204 subsystem that generates DDL statements you can input to the CVI utility. It is available to mainframe users, and as of [[RKTools]] version 7.7, it is accessible from the [[RKWeb]] browser interface. </p>		The TSF is an interactive Model 204 subsystem that generates DDL statements you can input to the CVI utility. It is available to mainframe users, and as of [[RKTools]] version 7.7, it is accessible from the [[RKTools#mainmenu\|RKTools main menu]] and from the [[RKWeb]] browser interface. </p>
	<p>		<p>
	The TSF displays the current Model 204 file definitions, and it simplifies your specification of corresponding SQL characteristics. From these specifications, the TSF generates DDL statements defining SQL objects that map to the Model 204 files.</p>		The TSF displays the current Model 204 file definitions, and it simplifies your specification of corresponding SQL characteristics. From these specifications, the TSF generates DDL statements defining SQL objects that map to the Model 204 files.</p>
Line 100:		Line 102:
	The TSF is described in detail in [[SQL DDL from the Table Specification Facility]].</p>		The TSF is described in detail in [[SQL DDL from the Table Specification Facility]].</p>
	<p>		<p>
	The CCACATREPT subsystem generates DDL statements from the SQL catalog that you can submit to CVI. Also accessible from the RKWeb interface, the CCACATREPT is:</p>		The CCACATREPT subsystem generates DDL statements from the SQL catalog that you can submit to CVI. Also accessible from the RKTools main menu and the RKWeb interface, the CCACATREPT is:</p>
	<ul>		<ul>
	<li>Discussed in [[#Reporting catalog contents\|Reporting catalog contents]]</li>		<li>Discussed in [[#Reporting catalog contents\|Reporting catalog contents]]</li>

JAL: /* Generating DDL with SQL utilities */ mention RKWeb

2017-06-13T23:26:13Z

Generating DDL with SQL utilities: mention RKWeb

← Older revision		Revision as of 23:26, 13 June 2017
Line 93:		Line 93:

	====Generating DDL with SQL utilities====		====Generating DDL with SQL utilities====
	<p>The TSF is an interactive Model 204 subsystem that generates DDL statements you can input to the CVI utility. ~~Available~~ to mainframe users, the TSF displays the current Model 204 file definitions and simplifies your specification of corresponding SQL characteristics. From these specifications, the TSF generates DDL statements defining SQL objects that map to the Model 204 files.</p>		<p>
			The TSF is an interactive Model 204 subsystem that generates DDL statements you can input to the CVI utility. It is available to mainframe users, and as of [[RKTools]] version 7.7, it is accessible from the [[RKWeb]] browser interface. </p>
			<p>
			The TSF displays the current Model 204 file definitions, and it simplifies your specification of corresponding SQL characteristics. From these specifications, the TSF generates DDL statements defining SQL objects that map to the Model 204 files.</p>
	<p>		<p>
	The TSF is described in detail in [[SQL DDL from the Table Specification Facility]].</p>		The TSF is described in detail in [[SQL DDL from the Table Specification Facility]].</p>
	<p>		<p>
	The CCACATREPT generates DDL statements from the SQL catalog that you can submit to CVI. ~~The CCATREPT~~ is:</p>		The CCACATREPT subsystem generates DDL statements from the SQL catalog that you can submit to CVI. Also accessible from the RKWeb interface, the CCACATREPT is:</p>
	<ul>		<ul>
	<li>Discussed in [[#Reporting catalog contents\|Reporting catalog contents]]</li>		<li>Discussed in [[#Reporting catalog contents\|Reporting catalog contents]]</li>

ELowell: /* Populating the catalog */

2016-09-13T20:02:27Z

Populating the catalog

← Older revision		Revision as of 20:02, 13 September 2016
Line 87:		Line 87:
	The CVI utility updates the SQL catalog through DDL statements. The DDL used by CVI can come from the following sources:		The CVI utility updates the SQL catalog through DDL statements. The DDL used by CVI can come from the following sources:
	<ul>		<ul>
	<li>DDL that you generate with mainframe SQL utilities (the Table Specification facility, TSF, or the catalog reporting utility, CCACATREPT)</li>		<li>DDL that you generate with mainframe SQL utilities (the Table Specification facility, [[SQL DDL from the Table Specification Facility\|TSF]], or the catalog reporting utility, [[SQL catalog reporting and querying\|CCACATREPT]])</li>
	<li>DDL that you prepare manually</li>		<li>DDL that you prepare manually</li>
	</ul>		</ul>

ELowell: /* Model 204 SQL catalog characteristics */

2016-09-13T19:53:58Z

Model 204 SQL catalog characteristics

← Older revision		Revision as of 19:53, 13 September 2016
Line 57:		Line 57:
	<td>Independent of the Model 204 Dictionary		<td>Independent of the Model 204 Dictionary
	</td>		</td>
	<td>You cannot create the SQL catalog with Dictionary facilities; CCATSF helps do this. Nor is SQL catalog information reflected in Dictionary metadata. However, you can use the Dictionary to operate on a Model 204 file that has been cataloged for SQL applications.		<td>You cannot create the SQL catalog with Dictionary facilities; [[SQL DDL from the Table Specification Facility\|CCATSF]] helps do this. Nor is SQL catalog information reflected in Dictionary metadata. However, you can use the Dictionary to operate on a Model 204 file that has been cataloged for SQL applications.
	</td>		</td>
	</tr>		</tr>

ELowell: /* Model 204 SQL catalog characteristics */

2015-07-20T22:06:39Z

Model 204 SQL catalog characteristics

← Older revision		Revision as of 22:06, 20 July 2015
Line 17:		Line 17:
	The Model 204 SQL catalog has the following characteristics:		The Model 204 SQL catalog has the following characteristics:
	<table>		<table>
	<tr>		<tr class="head">
	<th>		<th>
	Model 204 SQL catalog is...		Model 204 SQL catalog is...

ELowell: /* CCACAT implementation for BLOB and CLOB data */

2015-07-20T20:37:11Z

CCACAT implementation for BLOB and CLOB data

← Older revision		Revision as of 20:37, 20 July 2015
Line 247:		Line 247:
	<p>		<p>
	This returns the following results showing the new BLOB/CLOB data types.</p>		This returns the following results showing the new BLOB/CLOB data types.</p>
	<p class="~~code~~">TYPE_NAME DATA_TYPE		<p class="syntaxUL">TYPE_NAME DATA_TYPE
	CHAR 1		CHAR 1
	DEC 3		DEC 3

ELowell: /* Consistency and recovery */

2015-07-20T20:10:17Z

Consistency and recovery

← Older revision		Revision as of 20:10, 20 July 2015
Line 206:		Line 206:
	</ul>		</ul>
	<p>		<p>
	The parameter settings are distributed with the CREATE procedure. See [[Creating a file]] for more ~~file creation~~ information.</p>		The parameter settings are distributed with the CREATE procedure. See [[Creating a file]] for more information.</p>

	<p>~~For more about setting FRCVOPT, see the~~ [[FRCVOPT parameter]] ~~topic~~.</p>		<p>See <var>[[FRCVOPT parameter\|FRCVOPT]]</var> for more about its settings.</p>

	===Ongoing CCACAT maintenance===		===Ongoing CCACAT maintenance===