m204wiki - User contributions [en]

Dictionary/204 installation guide

2016-12-14T16:10:51Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINST</code> job in RKOBJLIB. </li>

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB. </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINST</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of <code>M204PROC</code>. </li>

<li>Restore that dump data set into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINST</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i>, because the upgrade process requires the redefinition of two fields, <code>APSUNM</code> and <code>APSCLSS</code> to <var>ORDERED CHARACTER</var>, in CCASYS.

<p class="note"><b>Note:</b> Running the installation job (<code>DDRINST</code>) creates backups of the upgraded Dictionary files.</p></li>
</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following files are required to complete an installation of Dictionary/204:
<ul>
<li>METADATA</li>
<li>DATALINK</li>
<li>M204TEMP</li>
<li>D204RPT</li>
<li>D204SYS</li>
<li>M204DCTL</li>
</ul>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>
</table>
If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINST</code>, which is stored in the RKOBJLIB. </li>

<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-12-14T16:09:45Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINST</code> job in RKOBJLIB. </li>

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB. </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINST</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of <code>M204PROC</code>. </li>

<li>Restore that dump data set into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINST</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i>, because the upgrade process requires the redefinition of two fields, <code>APSUNM</code> and <code>APSCLSS</code> to <var>ORDERED CHARACTER</var>, in CCASYS.

<p class="note"><b>Note:</b> Running the installation job (<code>DDRINST</code>) creates backups of the upgraded Dictionary files.</p></li>
</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following files are required to complete an installation of Dictionary/204:
<ul>
<li>METADATA</li>
<li>DATALINK</li>
<li>M204TEMP</li>
<li>D204RPT</li>
<li>D204SYS</li>
<li>M204DCTL</li>
</ul>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>
</table>
If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code>, which is stored in the RKOBJLIB. </li>

<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-12-14T16:09:23Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINST</code> job in RKOBJLIB. </li>

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB. </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINST</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of <code>M204PROC</code>. </li>

<li>Restore that dump data set into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i>, because the upgrade process requires the redefinition of two fields, <code>APSUNM</code> and <code>APSCLSS</code> to <var>ORDERED CHARACTER</var>, in CCASYS.

<p class="note"><b>Note:</b> Running the installation job (<code>DDRINST</code>) creates backups of the upgraded Dictionary files.</p></li>
</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following files are required to complete an installation of Dictionary/204:
<ul>
<li>METADATA</li>
<li>DATALINK</li>
<li>M204TEMP</li>
<li>D204RPT</li>
<li>D204SYS</li>
<li>M204DCTL</li>
</ul>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>
</table>
If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code>, which is stored in the RKOBJLIB. </li>

<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-12-14T16:08:42Z

Lrenton: /* New installation */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINST</code> job in RKOBJLIB. </li>

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB. </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINST</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of <code>M204PROC</code>. </li>

<li>Restore that dump data set into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i>, because the upgrade process requires the redefinition of two fields, <code>APSUNM</code> and <code>APSCLSS</code> to <var>ORDERED CHARACTER</var>, in CCASYS.

<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>
</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following files are required to complete an installation of Dictionary/204:
<ul>
<li>METADATA</li>
<li>DATALINK</li>
<li>M204TEMP</li>
<li>D204RPT</li>
<li>D204SYS</li>
<li>M204DCTL</li>
</ul>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>
</table>
If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code>, which is stored in the RKOBJLIB. </li>

<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-12-14T16:08:12Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINST</code> job in RKOBJLIB. </li>

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB. </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of <code>M204PROC</code>. </li>

<li>Restore that dump data set into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i>, because the upgrade process requires the redefinition of two fields, <code>APSUNM</code> and <code>APSCLSS</code> to <var>ORDERED CHARACTER</var>, in CCASYS.

<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>
</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following files are required to complete an installation of Dictionary/204:
<ul>
<li>METADATA</li>
<li>DATALINK</li>
<li>M204TEMP</li>
<li>D204RPT</li>
<li>D204SYS</li>
<li>M204DCTL</li>
</ul>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>
</table>
If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code>, which is stored in the RKOBJLIB. </li>

<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-12-14T16:07:27Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINST</code> job in RKOBJLIB. </li>

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST=J</code> job in RKOBJLIB. </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of <code>M204PROC</code>. </li>

<li>Restore that dump data set into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i>, because the upgrade process requires the redefinition of two fields, <code>APSUNM</code> and <code>APSCLSS</code> to <var>ORDERED CHARACTER</var>, in CCASYS.

<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>
</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following files are required to complete an installation of Dictionary/204:
<ul>
<li>METADATA</li>
<li>DATALINK</li>
<li>M204TEMP</li>
<li>D204RPT</li>
<li>D204SYS</li>
<li>M204DCTL</li>
</ul>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>
</table>
If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code>, which is stored in the RKOBJLIB. </li>

<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files:

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM ''whatever''
</p>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:52:26Z

Lrenton: /* Installing Dictionary/204 on IBM z/OS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<p>
<li> To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code> which is stored in the RKOBJLIB.

<li> To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:50:48Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code> which is stored in the RKOBJLIB.

<li> To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:49:20Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code> which is stored in the RKOBJLIB.

<li> To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:48:25Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code> which is stored in the RKOBJLIB.

<li> To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:47:43Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the M204PROC file. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code> which is stored in the RKOBJLIB.

<li> To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:46:10Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> To install Dictionary/204 for the first time, use the JCL provided in <code>DDINSTJ</code> which is stored in the RKOBJLIB.

<li> To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:36:55Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINSTJ</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINSTJ</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:35:27Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 6000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINST</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINST</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T18:26:28Z

Lrenton: /* New installation */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>Using the JCL from RKOBJLIB <code>DDINSTJ</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number). This is a dump of M204PROC.</li>

<li>Restore that dump dataset into a 4000 page <code>M204PROC</code> file on your mainframe.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.
</p>
</li>

<li>Submit the Dictionary/204 re-installation job, member <code>DDRINST</code> in RKOBJLIB. This is a single-user, Model 204 job with the <var>SYSOPT</var> X'01' bit turned <i>off</i> because the upgrade process requires the redefinition of two fields, APSUNM and APSCLSS to ORDERED CHARACTER, in CCASYS.
</li>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINST</code>) creates backups of the upgraded Dictionary files.</p></li>

</ol>

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T15:15:25Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|If this is an upgrade, Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>
</ol>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-29T15:07:16Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>[[Dictionary/204 operation and file maintenance#Backing up Dictionary.2F204 files|Create backups]] of all Dictionary/204 files. </li>

<li> If Dictionary/204 has never been installed, use JCL provided in the <code>DDINSTJ</code> job in RKOBJLIB.

<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>
</ol>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<li>Start, stop, and test Dictionary/204 subsystems</li>
<li>Set Dictionary/204 facility parameters</li>
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-22T15:46:24Z

Lrenton: /* Installation checklist (z/VSE) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-22T15:44:46Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<p>
<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-22T15:41:51Z

Lrenton: /* Installation checklist (z/VM CMS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>400 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-21T22:00:18Z

Lrenton: /* Installation checklist (z/OS) */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>400 pages</td></tr>

<tr><th>D204RPT</th>
<td>400 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>400 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-21T21:57:12Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
</li>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-21T21:56:21Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.</p></li>
</ol>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-21T21:52:13Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.</p>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-21T21:51:42Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li>To install an update to Dictionary/204,

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.
</li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.</p>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-11-21T21:51:06Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Create backups of all Dictionary/204 files. </li>

<li>To install an update to Dictionary/204,

<li> Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p> </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.</p>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in the <code>DDRINSTJ</code> job in RKOBJLIB.</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

[[Category:Installation]]

[[Category:Dictionary/204]]

Dictionary/204 installation guide

2016-10-21T16:37:24Z

Lrenton: /* Installing Dictionary/204 on IBM z/OS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs, or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <code>ONLINE</code> load module that contains <var class="product">Model 204</var> version 7.5 or higher. </li>

<li>Make sure that the Online has dump files allocated for backing up the Dictionary files. </li>

<li>Create backups of all Dictionary/204 files. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p> </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p>

<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-21T16:35:25Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs, or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <code>ONLINE</code> load module that contains <var class="product">Model 204</var> version 7.5 or higher. </li>

<li>Make sure that the Online has dump files allocated for backing up the Dictionary files. </li>

<li>Create backups of all Dictionary/204 files. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p> </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-21T16:34:29Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs, or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <code>ONLINE</code> load module that contains <var class="product">Model 204</var> version 7.5 or higher. </li>

<li>Make sure that the Online has dump files allocated for backing up the Dictionary files. </li>

<li>Create backups of all Dictionary/204 files. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p> </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p> </li>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-21T16:21:58Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs, or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <code>ONLINE</code> load module that contains <var class="product">Model 204</var> version 7.5 or higher. </li>

<li>Make sure that the Online has dump files allocated for backing up the Dictionary files. </li>

<li>Create backups of all Dictionary/204 files. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Run DICN.DDRINST using the JCL provided in RKOBJLIB called DDRINSTJ.</p> </li>

<li>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>

<li>Use the subsystem named <code>DICTADMIN</code> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p></li>

<li>Since this update process requires updating CCASYS, you must bring up a single user Online,
or run the installation as a batch process with the <var>SYSOPT</var> X'01' bit turned <i>off</i>. </li>

<li>Make sure that dump files are allocated to the Online, as shown below:

<p class="code">//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
<p class="note"><b>Note:</b> No dump data set is required for M204TEMP or M204PROC. </p>
<p>
The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB is: </p>
<p class="code">DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)</p>
<p>
Make sure these DD statements are also part of that JCL: </p>
<p class="code">//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

<p class="note"><b>Note:</b> Running the installation job (<code>DICN.DDRINST</code>) creates the backups of the Dictionary files.</p></li>

<li>Run the procedure <code>DICN.DDRINST</code> (file <code>M204PROC</code>) to install the downloaded release.</li>
</ol>

The <var class="product">Dictionary/204</var> subsystems can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th>METADATA</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>DATALINK</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204TEMP</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204RPT</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>D204SYS</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th>M204DCTL</th>
<td>Required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>METADATA
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>DATALINK
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204TEMP
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204RPT
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204SYS
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204DCTL
</th><td>100 pages; must always be allocated.</td></tr>
</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>
An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

:M204PROC
:METADATA
:DATALINK
:M204TEMP
:M204DCTL
:D204SYS
:D204RPT

<li>Verify that the Online environment allows the use of file groups and application subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use application subsystems, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about application subsystems and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:22:00Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li> Since this update process requires updating CCASYS, you must bring up a single user online
or run the install as a batch process with SYSOPT=1 turned off.
<li>Make sure that dump files as shown below are allocated to the online.
</p>

<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
<p class="code">
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:10:14Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.
</p>

<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
<p class="code">
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:08:39Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.
</p>

<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
<p class="code">
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:07:33Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.
</p>

<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
<p class="code">
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:06:39Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.

<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
<p class="code">
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:05:47Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.
</ol>
<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
<p class="code">
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp
</p>

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:03:25Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.
</li>
<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T19:02:21Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.
</ol>
<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T18:58:32Z

Lrenton: /* Reinstallation for existing Dictionary/204 sites */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.

<p class="code"> //DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
</p>
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T18:52:54Z

Lrenton:

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
<li>Make sure that dump files as shown below are allocated to the online.

//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T18:09:31Z

Lrenton:

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
Make sure that dump files as shown below are allocated to the online.

//DUMPCSYS DD DISP=SHR,DSN=ccasys.dump.dataset
//DUMPLINK DD DISP=SHR,DSN=datalink.dump.dataset
//DUMPDCTL DD DISP=SHR,DSN=d204dctl.dump.dataset
//DUMPRPT DD DISP=SHR,DSN=d204rpt.dump.dataset
//DUMPDSYS DD DISP=SHR,DSN=d204sys.dump.dataset
//DUMPMETA DD DISP=SHR,DSN=metadata.dump.dataset
Note: no dump dataset is required for M204TEMP or M204PROC.

The size of each dump data set should be equal to the size of the corresponding Dictionary file. The DCB
is DCB=(LRECL=6184,BLKSIZE=6184,RECFM=F)

Make sure these DD statements are also part of that JCL:
//CCASYS DD DISP=SHR,DSN=your.current.ccasys
//DATALINK DD DISP=SHR,DSN=your.current.datalink
//D204RPT DD DISP=SHR,DSN=your.current.d204rpt
//D204SYS DD DISP=SHR,DSN=your.current.d204sys
//METADATA DD DISP=SHR,DSN=your.current.metadata
//M204DCTL DD DISP=SHR,DSN=your.current.m204dctl
//M204PROC DD DISP=SHR,DSN=v76.version.m204proc
//M204TEMP DD DISP=SHR,DSN=your.current.m204temp

Note: Running the install job (DICN.DDRINST) will create the backups of the Dictionary files.

In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2016-10-06T17:59:39Z

Lrenton:

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (known as APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 on IBM z/VM CMS|Installing Dictionary/204 on IBM z/VM CMS]], [[#Installing Dictionary/204 on IBM z/OS|Installing Dictionary/204 on IBM z/OS]], and [[#Installing Dictionary/204 on IBM z/VSE|Installing Dictionary/204 on IBM z/VSE]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]], [[#Installation checklist (z/OS)|Installation checklist (z/OS)]], and [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains <var class="product">Model 204 Version 7.5 or higher</var>. </li>
<li>Make sure that the online has dump files allocated for backing up the Dictionary files.
<li>Create backups of all Dictionary/204 files.
<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "M204PROC" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user <i>must</i> have:
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[#New installation|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, click the [https://m204.rocketsoftware.com/maint/ullist Download SOUL files] link.</li>

<li>Download the latest version of the <code>M204PROC</code> file (which is followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

===Installation checklist (z/VM CMS)===

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>

<li>Modify the RESPROC EXEC to specify the <code>M204PROC</code> dump file and <code>M204PROC</code> file to be loaded.</li>

<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 INSTALL</p></li>

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:
<p class="code">EXEC D204 REINSTALL</p></li>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-25T19:50:49Z

Lrenton: /* New installation */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/OS, z/VM CMS or z/VSE.
The sections [[#Installing Dictionary/204 under z/VSE|Installing Dictionary/204 under z/VSE]], [[#Installing Dictionary/204 under z/VM CMS|Installing Dictionary/204 under z/VM CMS]], and [[#Installing Dictionary/204 under z/OS|Installing Dictionary/204 under z/OS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]] ,[[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]] and [[#Installation checklist (z/OS)|Installation checklist (z/OS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

Installation steps:

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL </p>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-25T19:49:33Z

Lrenton: /* A summary of the Dictionary/204 installation steps */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for z/OS, z/VM CMS or z/VSE.
The sections [[#Installing Dictionary/204 under z/VSE|Installing Dictionary/204 under z/VSE]], [[#Installing Dictionary/204 under z/VM CMS|Installing Dictionary/204 under z/VM CMS]], and [[#Installing Dictionary/204 under z/OS|Installing Dictionary/204 under z/OS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (z/VSE)|Installation checklist (z/VSE)]] ,[[#Installation checklist (z/VM CMS)|Installation checklist (z/VM CMS)]] and [[#Installation checklist (z/OS)|Installation checklist (z/OS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DICN.DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation==
<p class="note"><b>Note:</b> If you have never installed Dictionary/204 before, you must use these instructions. If you have installed Dictionary before, you can do a new install using these instructions if desired.</p>
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM z/VM CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]], as described in the following steps.

Installation steps:

<ol>
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL </p>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (z/OS) cards or FILEDEFs (z/VM CMS) or DLBLs (z/VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-23T17:05:24Z

Lrenton: /* Installing Dictionary/204 on IBM zVM/CMS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]], [[#Installing Dictionary/204 under CMS|Installing Dictionary/204 under CMS]], and [[#Installing Dictionary/204 under MVS|Installing Dictionary/204 under MVS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (VSE)|Installation checklist (VSE)]] ,[[#Installation checklist (CMS)|Installation checklist (CMS)]] and [[#Installation checklist (MVS)|Installation checklist (MVS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation for customers who have never installed Dictionary/204==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM zVM/CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on VM/CMS,
including VM/CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Installation steps:

<ol>
<li>Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from
the dump files [[#Obtaining product installation files|downloaded from the Rocket website]]:

<ol type="a">
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte CMS blocks should be sufficient in all cases.
This requires a 22-cylinder CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-23T17:04:48Z

Lrenton: /* Installing Dictionary/204 on IBM zVM/CMS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]], [[#Installing Dictionary/204 under CMS|Installing Dictionary/204 under CMS]], and [[#Installing Dictionary/204 under MVS|Installing Dictionary/204 under MVS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (VSE)|Installation checklist (VSE)]] ,[[#Installation checklist (CMS)|Installation checklist (CMS)]] and [[#Installation checklist (MVS)|Installation checklist (MVS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation for customers who have never installed Dictionary/204==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM zVM/CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on VM/CMS,
including VM/CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Installation steps:

<ol>
<li>Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from
the dump files [[#Obtaining product installation files|downloaded from the Rocket website]]:

<ol type="a">
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte CMS blocks should be sufficient in all cases.
This requires a 22-cylinder CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL

<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-23T17:03:47Z

Lrenton: /* Installing Dictionary/204 on IBM zVM/CMS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]], [[#Installing Dictionary/204 under CMS|Installing Dictionary/204 under CMS]], and [[#Installing Dictionary/204 under MVS|Installing Dictionary/204 under MVS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (VSE)|Installation checklist (VSE)]] ,[[#Installation checklist (CMS)|Installation checklist (CMS)]] and [[#Installation checklist (MVS)|Installation checklist (MVS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation for customers who have never installed Dictionary/204==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM zVM/CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on VM/CMS,
including VM/CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Installation steps:

<ol>
<li>Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from
the dump files [[#Obtaining product installation files|downloaded from the Rocket website]]:

<ol type="a">
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte CMS blocks should be sufficient in all cases.
This requires a 22-cylinder CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL
</<p>
<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL
</li>

</ol>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-23T17:02:41Z

Lrenton: /* Installing Dictionary/204 on IBM zVM/CMS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]], [[#Installing Dictionary/204 under CMS|Installing Dictionary/204 under CMS]], and [[#Installing Dictionary/204 under MVS|Installing Dictionary/204 under MVS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (VSE)|Installation checklist (VSE)]] ,[[#Installation checklist (CMS)|Installation checklist (CMS)]] and [[#Installation checklist (MVS)|Installation checklist (MVS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation for customers who have never installed Dictionary/204==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM zVM/CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on VM/CMS,
including VM/CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Installation steps:

<ol>
<li>Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from
the dump files [[#Obtaining product installation files|downloaded from the Rocket website]]:

<ol type="a">
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte CMS blocks should be sufficient in all cases.
This requires a 22-cylinder CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>

<li>To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL
</<p>
<li>To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL
</p> p> </li>

</ol>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-23T17:00:01Z

Lrenton: /* Installing Dictionary/204 on IBM zVM/CMS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]], [[#Installing Dictionary/204 under CMS|Installing Dictionary/204 under CMS]], and [[#Installing Dictionary/204 under MVS|Installing Dictionary/204 under MVS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (VSE)|Installation checklist (VSE)]] ,[[#Installation checklist (CMS)|Installation checklist (CMS)]] and [[#Installation checklist (MVS)|Installation checklist (MVS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation for customers who have never installed Dictionary/204==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM zVM/CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on VM/CMS,
including VM/CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Installation steps:

<ol>
<li>Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from
the dump files [[#Obtaining product installation files|downloaded from the Rocket website]]:

<ol type="a">
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte CMS blocks should be sufficient in all cases.
This requires a 22-cylinder CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>
<p class="code">
To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
EXEC D204 INSTALL
</<p>
To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL
</p> p> </li>

</ol>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>

Dictionary/204 installation guide

2015-09-23T16:57:49Z

Lrenton: /* Installing Dictionary/204 on IBM zVM/CMS */

==Overview==
<var class="product">[[Media:M204_DictionaryGuide_V75.pdf | Dictionary/204]]</var> Is a set of application subsystems (aka APSYs) running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of <var class="product">User Language</var> and file and system management.

Installing <var class="product">Dictionary/204</var> requires downloading the <code>M204PROC</code> file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.

Upgrades to <var class="product">Dictionary/204</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file.

==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]], [[#Installing Dictionary/204 under CMS|Installing Dictionary/204 under CMS]], and [[#Installing Dictionary/204 under MVS|Installing Dictionary/204 under MVS]] describe these steps in greater detail for each operating system.
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
and <var>RESTORE</var> it from the <var>DUMP</var> files found on the website.
<p>
In addition, there may be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
These are listed in [[#Installation checklist (VSE)|Installation checklist (VSE)]] ,[[#Installation checklist (CMS)|Installation checklist (CMS)]] and [[#Installation checklist (MVS)|Installation checklist (MVS)]]. </p> </li>

<li>Update the Online JCL or EXEC:
<ul>
<li>Add the DD cards, FILEDEFs or DLBLs for the Dictionary/204 files. </li>
</ul>

<li>Update CCAIN parameters:
<ul>
<li>Increase <var>[[NFILES parameter|NFILES]]</var>, <var>[[NDCBS parameter|NDCBS]]</var>, and <var>[[NDIR parameter|NDIR]]</var> for the Dictionary/204 files. </li>

</ul> </li>

<li>Start the Online, using an <var>ONLINE</var> load module that contains the
<var class="product">Model 204 Version 7.5 or higher</var>. </li>

<li>To install an update to Dictionary/204,
open file <code>M204PROC</code> and execute the following command:
<p class="code">INCLUDE DDRINST</p>
<p>
Follow the instructions presented on the installation screen (and in the Help
text for the screen).</p> </li>

<li>Verify success of the installation by compiling each Dictionary/204 APSY. </li>

<li>Use the APSY named <var>DICTADMIN</var> to customize the <var class="product">Dictionary/204</var> environment. </li>
</ol>

==Preparing for Dictionary/204 installation==
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the product section of the website.

===Obtaining product installation files===
The files necessary for the installation are available from the Rocket Software website.

To download product files from the Rocket website:
<ol>
<li>On the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=SIRIUS "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>After providing your registered customer login information, download the latest version of the <code>Dictionary/204</code> file (which is labeled "Dictionary/204 products in one file" followed by a version number).
<p>
A "Click here" link on this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
</ol>

===Determining eligible products===
To download files or maintenance from the Rocket M204 Customer Care area of the Rocket website, you must have a registered Rocket user ID ([[Contacting Rocket Software Technical Support|contact Technical Support]] if you need an ID).
The website will show only products for which your organization is up to date on maintenance or rental payments.
If a product does not appear on your download page and you believe it should,
contact Technical Support.

===System requirements===
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<p>
In the rest of this document, "Online" refers to a region of
<var class="product">Model 204</var> running an <var>ONLINE</var> load module containing Version 7.5 or higher
</p></li>
</ul>

===User privileges===
The installing user '''must have''':
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>

<li>System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that
runs the Online <var class="product">Model 204</var> region. </li>
</ul>

===New installation or reinstallation===
<ul>
<li>Sites that have never installed <var class="product">Dictionary/204</var> ''must'' use the new installation, as there are a number of files to allocate and <var
class="product">Model 204</var> parameters to update.</li>

<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
can either [[#Reinstallation for existing Dictionary/204 sites|reinstall]] Dictionary/204 (using DDRINST) or perform a [[New installation for new Dictionary/204 sites|new installation]] (using DDINST) to create a new set of Dictionary/204 files.

<p>If you are upgrading from a previous version or maintenance level, your site already has the Dictionary files that contain information about your environment.</p> </li>
</ul>

==New installation for customers who have never installed Dictionary/204==
You can verify the <var class="product">Dictionary/204</var> version in the title of any <var class="product">Dictionary/204</var> screen.
The installation steps are as follows:
<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.

<li>Download and restore the Dictionary/204 supporting files.</li>
<table class="thJustBold">

<tr><th>METADATA
</th><td>400 pages.</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages.

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages</td></tr>
</table>
<p>
<li>In file <code>M204PROC</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Reinstallation for existing Dictionary/204 sites==
You can verify the <var class="product">Dictionary/204</var> version either in the title of any <var class="product">Dictionary/204</var> screen.
The reinstallation steps are as follows:

<ol>
<li>In the [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page of the Rocket website, select the [https://m204.rocketsoftware.com/maint/ullist?nickname=M204 "Download Dictionary/204 files" link] in the "Downloads and Uploads" section to access the "Dictionary/204 files for Rocket Software Inc." page. </li>

<li>Download the latest version of the <code>M204PROC</code> file (which is labeled "All Dictionary/204
products in one file" followed by a version number).</li>

<li>Verify that the Online in which you are installing contains a version of <var class="product">Model204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>

<li>Restore the <code>M204PROC</code> file into a 6000-page file on your mainframe.
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file.</p>
<p>
In file <code>M204PROC</code>, run the procedure <code>DICN.DDRINST</code> to install the downloaded release.</p></li>
</ol>

The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you like.

==Installing Dictionary/204 on IBM zVM/CMS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on VM/CMS,
including VM/CMS system and software requirements.

Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.

The <code>M204PROC</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">Dictionary/204</var>, can be [[#Obtaining product installation files|obtained from the Rocket website]].

The following table lists the required files needed to complete an installation of Dictionary/204.
<table class="thJustBold">
<tr class="head"><th>File name</th>
<th>Contents</th></tr>

<tr><th><i>Metadata</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>Datalink</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204temp</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204rpt</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>D204sys</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>

<tr><th><i>M204dctl</i></th>
<td>File required for the installation of <var class="product">Dictionary/204</var>. </td></tr>
</table>

Installation steps:

<ol>
<li>Allocate space for the <var class="product">Dictionary/204</var> files, and restore them from
the dump files [[#Obtaining product installation files|downloaded from the Rocket website]]:

<ol type="a">
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
1500 4096-byte CMS blocks should be sufficient in all cases.
This requires a 22-cylinder CMS minidisk on a 3390. </li>

<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
<code>D204FDEF</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<table class="thJustBold">
<tr><th>M204PROC
</th><td>6000 pages; must always be allocated.</td></tr>

<tr><th>Metadata
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>Datalink
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204temp
</th><td>150 pages; must always be allocated.</td></tr>

<tr><th>D204rpt
</th><td>110 pages; must always be allocated.</td></tr>

<tr><th>D204sys
</th><td>400 pages; must always be allocated.</td></tr>

<tr><th>M204dctl
</th><td>100 pages; must always be allocated.</td></tr>

</table>

<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.
<p>
The installation process uses these files to install a new version of Dictionary/204.
</p>
</blockquote> </li>
<li>Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.</li>
<li>Restore the <code>M204PROC</code> file with the <var>D204 RESPROC</var> exec.
<p>
To carry out the install, you must customize the FILEDEF inside the <var>D204FDEF</var> exec to conform to local standards.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
<p>
To run the <var>D204</var> exec for a new install, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 INSTALL
</<p>
To run the <var>D204</var> exec for a REINSTALL, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">EXEC D204 REINSTALL
</p> p> </li>

</ol>

<li>Complete [[#updateJCL|steps 3 through the end]] in the [[#Installing Dictionary/204 on IBM z/OS|"Installing Dictionary/204 on IBM z/OS"]] section. </li>
</ol>

==Installing Dictionary/204 on IBM z/OS==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
If, like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/OS)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>An example command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:

<p>Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review the [[#Dictionary/204 server size |Dictionary/204 server size]] section, below, for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

==Installing Dictionary/204 on IBM z/VSE==
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
including z/VSE system and software requirements.

If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#Reinstallation for existing Dictionary/204 sites|Reinstallation for existing Dictionary/204 sites]].

===Installation checklist (z/VSE)===
<ol>
<li>Allocate the space required for the Dictionary/204 files. If you are creating a new <code>M204PROC</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>M204PROC</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>.
<p>A sample command sequence follows:</p>
<p class="code">CREATE FILE M204PROC
END CREATE
OPEN FILE M204PROC
IN M024PROC RESTORE 192 FROM <''whatever''>
</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
<td>6000 pages</td></tr>

<tr><th>METADATA
</th><td>400 pages</td></tr>

<tr><th nowrap>DATALINK</th><td>400 pages

<tr><th>M204TEMP</th>
<td>150 pages</td></tr>

<tr><th>D204RPT</th>
<td>110 pages</td></tr>

<tr><th>D204SYS</th>
<td>400 pages</td></tr>

<tr><th>M204DCTL</th>
<td>100 pages
</td></tr>
</table>

<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <b>Dictionary/204 files</b>. The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>

<li>Restore <code>M204PROC</code>, noting the following:
<ul>

<li>Rename database DSNs to conform to local standards. </li>

<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>M204PROC</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>

<div id="updateJCL"></div>
<li>Update the Online JCL or EXEC:
<p>
Add DD (MVS) cards or FILEDEFs (CMS) or DLBLs (VSE) for the Dictionary/204 files.
The following list identifies the files for which DD cards or FILEDEFs might be needed:</p>

<table class="thJustBold">
<tr><th>M204PROC</th>
</tr>

<tr><th>METADATA
</th></tr>

<tr><th>DATALINK
</th></tr>

<tr><th>M204TEMP</th>
</tr>

<tr><th nowrap>M204DCTL</th></tr>

<tr><th>D204SYS
</th></tr>

<tr><th>D204RPT
</th></tr>
</table>

<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<li>To use permanent file groups, the Online must have allocated an
initialized <code>CCAGRP</code> file, and the <var>[[SYSOPT parameter|UPSI]]</var> parameter must contain the <code>00000010</code> bit. </li>

<li>To use APSYs, an Online must have allocated an initialized CCASYS file
(with all fields defined), and the <var>UPSI</var> parameter must contain the <code>00000001</code> bit.
<p>
For more information about APSYs and file groups, see [[Storing and using file group definitions (CCAGRP)#File groups|File groups]] and [[System requirements for Application Subsystems]]. </p></li>
</ul> </li>

<li>Modify the User 0 stream.
<p>
Adjust these parameters: </p>
<table class="thJustBold">
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDCBS
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NDIR
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>

<tr><th>NORQS
</th><td>Verify that the setting is at least 5.</td></tr>
</table> </li>

<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
to a load module containing the <var class="product">Model204 Online</var>. </li>

<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<p class="code">INCLUDE DICN.DDRINST
</p>
<p>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
No user profiles or other site-specific customization will be lost.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
For example, you will be able to see if an installation failed because a file was enqueued in a different Online, and so on. </p></li>

<li>Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.
<p>
The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.</p> </li>

<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
<table class="thJustBold">
<tr class="head"><th>Enter ...
</th><th>To test the ...
</th></tr>

<tr><th>START SUBSYS DICTIONARY
</th><td>DICTIONARY MENU</td></tr>

<tr><th>START SUBSYS DICTADMIN
</th><td>DICTIONARY ADMINISTRATION</td></tr>

<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>

<tr><th>START SUBSYS FILEMGMT
</th><td>File building tool</td></tr>

<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>

<tr><th>START SUBSYS DICTREPORT
</th><td>Dictionary report subsystem</td></tr>

<tr><th>START SUBSYS XREF
</th><td>Cross reference reporting subsystem</td></tr>
</table>
<p>
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode. For example, to determine why DICTIONARY failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
</p> </li>

<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">Dictionary/204</var> subsystems.
Do this by placing one or more of the following in User 0's input stream:
<p class="code">START SUBSYS DICTIONARY
START SUBSYS DOCUMENT
START SUBSYS DICTADMIN
START SUBSYS FILEMGMT
START SUBSYS SUBSYSMGMT
START SUBSYS DICTREPORT
START SUBSYS XREF
</p>
<p>
This ensures that the subsystems are started for non-administrative
users, and it shifts the overhead of compilation to a non-peak
computing period. </p></li>

<li>Review [[#Dictionary/204 server size|Dictionary/204 server size]] for specific requirements of individual APSY components of <var class="product">Dictionary/204</var>.</li>
</ol>
<p class="note">'''Note:''' CCATEMP usage might increase with <var class="product">Dictionary/204</var>.
CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that sufficient space is allocated to accommodate the additional activity. </p>

===Dictionary/204 server size===
The minimum <var class="product">Dictionary/204</var> server size requirements are listed below.
The actual server size requirements might vary slightly because of table
settings in the local Online <var class="product">Model 204</var> regions, and because of slight
differences between <var>UTABLE</var> requirements in different versions of <var class="product">Model 204</var>.
<table class="thJustBold">
<tr class="head"><th>Subsystem name
</th><th>Minimum server
</th></tr>

<tr><th>DICTIONARY
</th><td>455K</td></tr>

<tr><th>DOCUMENT
</th><td>455K</td></tr>

<tr><th>DICTADMIN
</th><td>455K</td></tr>

<tr><th>FILEMGMT
</th><td>455K</td></tr>

<tr><th>SUBSYSMGMT
</th><td>455K</td></tr>

<tr><th>DICTREPORT
</th><td>455K</td></tr>

<tr><th>XREF
</th><td>455K</td></tr>
</table>