<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CAST DB2 zOS Extractor on Documentation - V2</title><link>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/</link><description>Recent content in CAST DB2 zOS Extractor on Documentation - V2</description><generator>Hugo</generator><language>en</language><atom:link href="https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/index.xml" rel="self" type="application/rss+xml"/><item><title>CAST and zOS</title><link>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/cast-and-zos/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/cast-and-zos/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The CAST DB2 Analyzer does not support direct connections to a &lt;strong&gt;DB2 z/OS server&lt;/strong&gt; and is instead delivered with a utility that provides the means to extract information related to database structure, types and routines from the DB2 system catalog and then save the results into flat files. These files will then form the input for the CAST DB2 Analyzer.&lt;/p&gt;
&lt;p&gt;The extractor is delivered as a &lt;strong&gt;JCL file&lt;/strong&gt; containing a sequence of JCL code. There are various different versions of the extractor, each dedicated to a specific version of DB2:&lt;/p&gt;</description></item><item><title>DB2 zOS extractor - installation and configuration</title><link>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/db2-zos-extractor-installation-and-configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/db2-zos-extractor-installation-and-configuration/</guid><description>&lt;h3 id="installation"&gt;Installation&lt;/h3&gt;
&lt;p&gt;The first step is to upload the extractor source code onto the z/OS execution environment. &lt;strong&gt;Please make sure you use the source code of the extractor that corresponds&lt;/strong&gt; &lt;strong&gt;to the version of the DB2 server you are working on.&lt;/strong&gt; You then need to adapt the JCL source code to the environment in which it is going to be executed and, perhaps, to the version of DB2. This operation MUST be completed before you run the z/OS job.&lt;/p&gt;</description></item><item><title>Using the DB2 zOS extractor</title><link>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/using-the-db2-zos-extractor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/doccom/source-code-extractors/cast-db2-zos-extractor/using-the-db2-zos-extractor/</guid><description>&lt;h2 id="running-the-extractor-job"&gt;Running the extractor job&lt;/h2&gt;
&lt;div class="alert alert-info" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Info&lt;/div&gt;
&lt;p&gt;The CAST DB2 for z/OS extractor always saves its results in the same data sets. As a result, if you want to save several extractions, then you must make sure you transfer the results of each extraction into different directories prior to carrying out the next extraction. This will avoid overwriting the previous results with new results.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Once the JCL script has been adapted to the execution environment, it can then be submitted.&lt;/p&gt;</description></item></channel></rss>