Dictionary/204 installation guide: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (wordsmithing v7.7 changes)
 
(202 intermediate revisions by 7 users not shown)
Line 1: Line 1:
<var class="product">[[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 aid programmers, DBAs, and system managers to handle the complexities of <var class="product">User Language</var> and file and system management.
==Overview==
<var class="product">[[:Category:Dictionary/204|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.
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&nbsp;204</var> files, and verifying that the environment has the appropriate parameter settings.


Upgrades to <var class="product">UL/SPF</var> can almost always be handled by restoring a fresh copy of the <code>M204PROC</code> file. <br/><br/>
<p class="note"><b>Note:</b> As of Model&nbsp;204 version 7.7, the <code>M204PROC</code> file is the container for the [[RKTools]] version 7.7 product, and <var class="product">Dictionary/204</var> is accessible from the RKTools interfaces ([[RKTools#mainmenu|TN3270]] and [[RKWeb#Dictionary|web]]), as well as from the usual [[Dictionary/204 overview#d204main|Dictionary main menu]]. </p>
 
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==
==A summary of the Dictionary/204 installation steps==
The following checklist specifies in brief the steps to follow installing
The following checklist specifies in brief the steps to follow installing
<var class="product">Dictionary/204</var>, whether for MVS, CMS or VSE.
<var class="product">Dictionary/204</var>, whether for z/VM CMS, z/OS, or z/VSE.
The sections [[#Installing Dictionary/204 under VSE|Installing Dictionary/204 under VSE]] [[#Installing Dictionary/204 under CMS|Installing UL/SPF under CMS]] and [[#Installing Dictionary/204 under MVS|Installing UL/SPF under MVS]] describe these steps in greater detail for each operating system.
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>
<ol>
<li>Allocate the space required for the <code>M204PROC</code> data set,
<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.
and <var>RESTORE</var> it from the <var>DUMP</var> files [[#Obtaining product installation files|found on the website]].
<p>
<p>
In addition, there may be any number of other data sets required for
In addition, there might be any number of other data sets required for
the <var class="product">Dictionary/204</var> components you are installing.
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>
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</i> files. </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>


</ul>
<li> If this is an upgrade, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB. </li>
<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>
<li>Verify the online has at least 10 [[Sdaemons|SDAEMON]] threads (each typically defined as an <var>IODEV15</var>). </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>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>Verify the success of the installation by compiling each Dictionary/204 subsystem. </li>


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


==Preparing for Dictionary/204 installation==   
==Preparing for Dictionary/204 installation==   
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model 204</var> subsystems.   
The <var class="product">Dictionary/204</var> products are implemented as <var class="product">Model&nbsp;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.
The code for all the component subsystems resides in the file named <code>M204PROC</code> which is typically downloaded from the Support section of the Rocket Software website.
   
   
===Obtaining product installation files===
===Obtaining product installation files===
The files necessary for the installation are available from
The files necessary for the installation are available from the Rocket Software website:
the Rocket Software website.
 
To download product files from the Rocket website:
<ol>
<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>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 "Dictionary/204 products in one file" followed by a version number).
<li>After providing your registered customer login information, download the latest version of the Dictionary/204 file, <code>M204PROC</code>. The <code>M204PROC</code> file to download for versions higher than 7.5 of Model&nbsp;204 is the file in the <code>RKTools V7.7</code> product row. As described in [[Dictionary/204 logon and commands#Overview|Dictionary/204 logon and commands]], Dictionary/204 is packaged with RKTools as of RKTools V7.7.
<p>
<p>
A "Click here" link on this page provides Help on downloading format, some information about
A "Click here" link in the text at the beginning of this page provides Help on downloading format, some information about
different browser behaviors, file sizing information, and more.</p></li>
different browser behaviors, file sizing information, and more.</p></li>
</ol>
</ol>
Line 70: Line 51:
If a product does not appear on your download page and you believe it should,
If a product does not appear on your download page and you believe it should,
contact Technical Support.
contact Technical Support.
   
   
===System requirements===
===System requirements===
<ul>
<ul>
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model 204</var> Online region.
<li><var class="product">Dictionary/204</var> operates in a <var class="product">Model&nbsp;204</var> Online region.
<p>  
<p>  
In the rest of this document, "Online" refers to a region of
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
<var class="product">Model&nbsp;204</var> running an <var>ONLINE</var> load module containing version 7.5 or higher.
</p></li>
</p></li>
</ul>


===User privileges===
===User privileges===
The installing user '''must have''':
The installing user <i>must</i> have:
<ul>
<ul>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>
<li>Update access to the JCL or EXECs that bring up the host Online.</li>
   
   
<li>System Manager privileges, as well as access to the SUBSYSMGMT facility and the JCL or EXEC that
<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.
runs the Online <var class="product">Model&nbsp;204</var> region. </li>
</ul>
</ul>
 
===Full Install or Quick Install===
===New installation or reinstallation===
<ul>
<ul>
<li>Sites that have never installed <var class="product">UL/SPF</var> ''must'' use the full
<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
installation, as there are a number of files to allocate and <var
class="product">Model&nbsp;204</var> parameters to update.</li>
class="product">Model 204</var> parameters to update.</li>


<li>Sites that are re-installing the latest version of <var class="product">UL/SPF</var>
<li>Sites that are re-installing the latest version of <var class="product">Dictionary/204</var>
may use the [[#A "Quick Install" for existing UL/SPF sites|quick-install]] or the full installation (some of whose steps would already be complete,
can [[#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.
such as the allocation and initialization of <code>SIRLOCAL</code>).


<li>If you are upgrading from a previous version or maintenance level,
<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>
your site already has a <code>SIRLOCAL</code> file, which holds users' profiles and other local customizations.
Your existing <code>SIRLOCAL</code> should be left intact and allocated to the Online,
as the installation process uses <code>SIRLOCAL</code> information to determine which features should be upgraded.
</ul>
</ul>


==A "Quick Install" for existing UL/SPF sites==
==New installation==
You can verify the <var class="product">UL/SPF</var> version either in the title of any <var class="product">UL/SPF</var> Help screen, or by looking at the content of the <code>VERSION</code> procedure in the <code>SIRIUS</code> file.
<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.
Here are the "Quick Install" steps:
The installation steps are as follows:
 
<ol>
<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=SIRIUS "Download SOUL files" link] in the "Downloads and Uploads" section to access the "SOUL files for Sirius Software Inc." page. </li>
<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>SIRIUS</code> file (which is labeled "All UL/SPF
<li>Download the appropriate version of the <code>M204PROC</code> file for your version of Model&nbsp;204 (for version 7.7, <code>M204PROC</code> is the container for, and Dictionary/204 is a member of, [[RKTools]]).</li>
products in one file" followed by a version number).</li>


<li>Verify that the Online in which you are installing contains a version of the <var class="product">Sirius Mods</var> equal to or greater than the <var class="product">UL/SPF</var> version.</li>
<li>Verify that the Online in which you are installing contains a version of <var class="product">Model&nbsp;204</var> equal to or greater than the <var class="product">Dictionary/204</var> version.</li>


<li>Restore the <code>SIRIUS</code> file into a 4200-page file on your mainframe.
<li>Restore the <code>M204PROC</code> file into a file on your mainframe. (This file must be 6000 pages for 7.6 or earlier, or 9800 pages for 7.7 or later.)
The DDNAME for this file in your <var class="product">Model 204</var> regions is also <code>SIRIUS</code>.
The DDNAME for this file in your <var class="product">Model&nbsp;204</var> regions is also <code>M204PROC</code>.
<p>
If you are upgrading from a previous release, simply overlay your old <code>SIRIUS</code> file.</p></li>


<li>If your site uses the web version of <var class="product">[[SirMon]]</var>, there is a change between Version 7.7 and 8.1 to the file that holds historical performance information. You should delete from the <var class="product">SirMon</var> APSY definition the file <code>MONDATA</code>, and add the file <code>SIRSTATS</code>, allocated with at least 5000 pages.
<p>
<p>
In file <code>SIRIUS</code>, run the procedure <code>CREATE.SIRSTATS</code> to define the fields in the <code>SIRSTATS</code> file.</p></li>
<li>Using the JCL from RKOBJLIB <code>DDINST</code>, run the procedure <code>DICN.DDINST</code> to install the downloaded release.</p></li>
</ol>
</ol>


The <var class="product">UL/SPF</var> APSYs can be set to <code>AUTOSTART</code> if you like. <var class="product">SirScan</var>, <var class="product">SirMon</var>, and <var class="product">SirLib</var> have SCLASS-sensitive code, so SCLASSes should not be renamed or redefined for these systems. 
The <var class="product">Dictionary/204</var> APSYs can be set to <code>AUTOSTART</code> if you prefer.


Use the APSY utility <code>SIRADMIN</code> to customize <var class="product">UL/SPF</var> settings.
==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:


==Installing UL/SPF under CMS==
<ol>
This section gives instructions for installing <var class="product">UL/SPF</var> under CMS,
<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>
including general system and software requirements.
 
It assumes you have reviewed [[#Preparing for UL/SPF installation|Preparing for UL/SPF installation]] for details about <var class="product">UL/SPF</var> system requirements.
<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>
 
The <code>SIRIUS</code> <var class="product">Model 204</var> file, which contains the <var class="product">[[SOUL]]</var> code that runs <var class="product">UL/SPF</var>, [[#Obtaining product installation files|can be obtained from the Rocket website]] or from a UL/SPF distribution tape. If working from a tape, it is shipped with a single tape file in VMFPLC2 DUMP format that includes these files:
<li>Restore that dump data set into an <code>M204PROC</code> file on your mainframe. (This file must be 6000 pages for 7.6 or earlier, or 9800 pages for 7.7 or later.)
<table class="thJustBold">
<p>
<tr class="head"><th>File name</th>
If you are upgrading from a previous release, simply overlay your old <code>M204PROC</code> file. </p></li>
<th>Contents</th></tr>
 
<li>Submit the Dictionary/204 re-installation job, member <code>DDRINST</code> in RKOBJLIB. This is a single-user, Model&nbsp;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. 


<tr><th><i>various</i></th>
<p class="note"><b>Note:</b> Running the installation job (<code>DDRINST</code>) creates backups of the upgraded Dictionary files.</p></li>
<td>Files required for the installation of <var class="product">Sirius Mods</var>. See the <var class="book">[[Media:SiriNew.pdf|Sirius Mods Installation Guide]]</var> for more details. </td></tr>
</ol>


<tr><th nowrap>ULSPF DUMPSIRI</th>
==Installing Dictionary/204 on IBM z/VM CMS==
<td>A <var class="product">Model 204</var> dump of the <code>SIRIUS</code> file, which is required for all the subsystems. </td></tr>
This section gives instructions for installing <var class="product">Dictionary/204</var> on z/VM CMS,
including z/VM CMS system and software requirements.


<tr><th>ULSPF DUMPFIX</th>
Review [[#Preparing for Dictionary/204 installation|Preparing for Dictionary/204 installation]] for details about general <var class="product">Dictionary/204</var> system requirements.
<td>A <var class="product">Model 204</var> dump of the <code>SIRFIXES</code> file, (the use of which is now deprecated).
</td></tr></table>
   
   
Installation steps:
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>


<ol>
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.
<li>Install the <var class="product">Sirius Mods</var>.
<p>
<var class="product">UL/SPF</var> requires a matching or greater version number of the <var class="product">Sirius Mods</var>.
For information about installing the <var class="product">Sirius Mods</var>, see the <var class="book">Sirius Mods Installation Guide</var>.</p>


<li>Allocate space for the <var class="product">UL/SPF</var> files, and restore them from
===Installation checklist (z/VM CMS)===
the distribution tape or from the dump files [[#Obtaining product installation files|downloaded from the Rocket website]].


<ol type="A">
<ol>
<li>Define and format a minidisk to hold the <var class="product">UL/SPF</var> installation files.
<li>Define and format a minidisk to hold the <var class="product">Dictionary/204</var> installation files.
3400 4096-byte CMS blocks should be sufficient in all cases.
1500 4096-byte z/VM CMS blocks should be sufficient in all cases.
This requires a 44-cylinder CMS minidisk on a 3390.
This requires a 22-cylinder z/VM CMS minidisk on a 3390. </li>
   
   
<li>Attach a tape drive at virtual address 181 to the owner of the
<li>Allocate space for the required <var class="product">Dictionary/204</var> data sets. A skeleton exec,
installation minidisk defined in step A.
<code>D204FDEF</code>, is provided for this purpose.
Mount the <var class="product">UL/SPF</var> distribution tape on this tape drive.
<li>Load the files appropriate to your site with the <var>VMFPLC2 LOAD</var> command.
This can be done most simply with the following sequence of commands:
<p class="code">TAPE REW
VMFPLC2 LOAD (EOT
</p>
<li>Allocate space for the required <var class="product">Model 204</var> data sets. A skeleton exec,
<code>ULSPFAL</code>, is provided for this purpose.
Modify this exec to perform the allocations on the appropriate minidisks.
Modify this exec to perform the allocations on the appropriate minidisks.
Allocate space for the following data sets:
<p>Allocate space for the following data sets:</p>
<table class="thJustBold">
<table class="thJustBold">
<tr><th>SIRIUS
<tr><th>M204PROC
</th><td>4200 pages; must always be allocated.</td></tr>
</th><td>6000 pages (7.6 or earlier), 9800 pages (7.7 or later); must always be allocated.</td></tr>
 
<tr><th>SIRLOCAL
</th><td>1200 pages; must always be allocated.</td></tr>


<tr><th>SIRSTATS or MONDATA
<tr><th>METADATA
</th><td>60000 pages; only if you are installing <var class="product">SirMon</var>.  Use <code>MONDATA</code> for versions 7.7 and earlier.  Use <code>SIRSTATS</code> for versions 8.1 and later.</td></tr>
</th><td>400 pages; must always be allocated.</td></tr>


<tr><th>SIRFILED
<tr><th>DATALINK
</th><td>1200 pages; only if you are installing <var class="product">SirFile</var>.</td></tr>
</th><td>400 pages; must always be allocated.</td></tr>


<tr><th>SIRLIBD
<tr><th>M204TEMP
</th><td>1200 pages; only if you are installing <var class="product">SirLib</var>.</td></tr>
</th><td>400 pages; must always be allocated.</td></tr>


<tr><th>SIRLIBP
<tr><th>D204RPT
</th><td>1200 pages; only if you are installing <var class="product">SirLib</var>.</td></tr>
</th><td>400 pages; must always be allocated.</td></tr>


<tr><th>SIRTPROC
<tr><th>D204SYS
</th><td>2000 pages; only if you are installing <var class="product">SirLib</var>.
</th><td>400 pages; must always be allocated.</td></tr>
This file can and should be sized much larger if you maintain hundreds or thousands of concurrent change decks in <var class="product">SirLib</var>.</td></tr>


<tr><th>JANCAT
<tr><th>M204DCTL
</th><td>1200 pages; only if you are installing Janus OMNI.</td></tr>
</th><td>400 pages; must always be allocated.</td></tr>
 
<tr><th>JANSSL
</th><td>1200 pages; only if you are installing Janus Network Security.</td></tr>
</table>
</table>
   
   
<blockquote class="warn">
<blockquote class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copy of <code>SIRLOCAL</code> and any
'''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.
application-specific data files, like <code>JANCAT</code>, <code>SIRLIBD</code>, <code>SIRFILED</code>, or <code>SIRSTATS</code>.
<p>
The installation process uses these files to determine whether to
The installation process uses these files to install a new version of Dictionary/204.
perform upgrade actions or new-installation actions.  
</p>
</blockquote>
</blockquote> </li>


<li>Restore the <code>SIRIUS</code> file with the <var>LOADPROC</var> exec.
<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>
<p>
To restore, customize the FILEDEF inside the <var>LOADPROC</var> exec to conform to local standards.
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>LOADPROC CCAIN</var> to contain a valid login ID and password.
In addition, modify <var>LOGONSM CCAIN</var> to contain a valid login ID and password.
If, for example, you are using the <code>SIRIUS</code> file for the first time,
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>
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p></li>
<p>
To run the <var>LOADPROC</var> exec, make sure the Online execs and load modules
are on an accessed disk, then enter this command: </p>
<p class="code">ONLINE LOADPROC
</p>
</ol>
<li>Complete [[#updateJCL|steps 3 through the end]] in the "Installing UL/SPF under MVS" section, below.
</ol>


==Installing UL/SPF under MVS==
<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:
This section gives instructions for installing <var class="product">UL/SPF</var> under MVS,
<p class="code">EXEC D204 INSTALL</p></li>
including the general system and software requirements.
If you received your product on tape, the following instructions apply.
If like most sites, you download products and updates from the Rocket website,
see the instructions in [[#A "Quick Install" for existing UL/SPF sites|A "Quick Install" for existing UL/SPF sites]].


<blockquote class="note">
<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>'''Note:''' The product installation tape for MVS has an internal label of <code>SIRIUS</code>, and it contains
<p class="code">EXEC D204 REINSTALL</p></li>
<var class="product">UL/SPF</var> files in an IEBCOPY-unloaded PDS on file 3 of the tape.
Before continuing, unless you have downloaded the product files from the website,
''you must load to disk the unloaded PDS before you can <var><i>RESTORE</i></var> the individual members to <var class="product">Model 204</var> files.'' </p>
   
   
The following JCL loads the <var class="product">UL/SPF</var> files to disk:
<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>
<p class="code">//LOADSIR  JOB  0,CLASS=A,MSGCLASS=X,NOTIFY=ME
</ol>
//*
//*        Load UL/SPF products from tape
//*
//LIB      EXEC PGM=IEBCOPY,REGION=0M
//T1      DD  UNIT=TAPE,LABEL=(1,SL),DSN=SIRIUS.LIB,
//            DISP=(OLD,PASS),VOL=SER=SIRIUS
//T2      DD  UNIT=TAPE,LABEL=(2,SL),DSN=SIRIUS.LOAD,
//            DISP=(OLD,PASS),VOL=SER=SIRIUS
//T3      DD  UNIT=TAPE,LABEL=(3,SL),DSN=SIRIUS.ULSPF,
//            DISP=(OLD,PASS),VOL=SER=SIRIUS
//*
//D1      DD  DISP=(,CATLG),SPACE=(CYL,(10,0,5),
//            DSN=SIRIUS.LIB,UNIT=SYSDA
//D2      DD  DISP=(,CATLG),SPACE=(CYL,(5,0,2),
//            DSN=SIRIUS.LOAD,UNIT=SYSDA
//D3      DD  DISP=(,CATLG),SPACE=(CYL,(44,0,2),
//             DSN=SIRIUS.ULSPF,UNIT=SYSDA
//SYSPRINT DD  SYSOUT=*
//SYSIN    DD  *
COPY INDD=T1,OUTDD=D1
COPY INDD=T2,OUTDD=D2
COPY INDD=T3,OUTDD=D3
/*
</p>
The JCL includes references to these files:
<table class="thJustBold">
<tr class="head"><th>File Num / Name</th>
<th>Contents</th></tr>


<tr><th>1 / SIRIUS.LIB</th>
==Installing Dictionary/204 on IBM z/OS==
<td>File required for the installation of <var class="product">Sirius Mods</var>. See the <var class="book">[[Media:SiriNew.pdf|Sirius Mods Installation Guide]]</var> for more details.
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/OS, including the z/OS system and software requirements.
</td></tr>
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]].


<tr><th nowrap>3 / SIRIUS.ULSPF(DUMPSIRI)
===Installation checklist (z/OS)===
</th><td>A <var class="product">Model 204</var> DUMP of the <code>SIRIUS</code> file that is required for all the subsystems.
<ol>
</td></tr>
<li>Allocate the space required for the M204PROC file: 


<tr><th>3 / SIRIUS.ULSPF(DUMPFIX)
<table class="thJustBold">
</th><td>A <var class="product">Model 204</var> DUMP of the <code>SIRFIXES</code> file.  This file is deprecated and not necessary for this installation.
<tr><th>M204PROC</th>
</td></tr></table>
<td>6000 pages (7.6 or earlier), 9800 pages (7.7 or later)</td></tr>
</blockquote>
</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>.  
===Installation checklist (MVS)===
<p>
<ol>
An example command sequence follows:</p>
<li>Install the <var class="product">Sirius Mods</var>.
<p class="code">CREATE FILE M204PROC
Refer to the <var class="book">[[Media:SiriNew.pdf|Sirius Mods Installation Guide]]</var> for details.
<p class="note">
'''Note:''' The Online in
which <var class="product">UL/SPF</var> will run must point to a load module containing the <var class="product">Sirius Mods</var>.
Also, <var class="product">UL/SPF</var> releases require a matching or greater version number of the <var class="product">Sirius Mods</var>. </p>
<li>Allocate the space required for the UL/SPF files.  Note that the <code>SIRIUS</code> file has X'0221' privileges, which does ''not'' allow <var>RESTORE</var>. If you are creating a new <code>SIRIUS</code> file from scratch, this will not be a problem. But if you are restoring into your existing <code>SIRIUS</code> file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>. The command sequence is something like:
<p class="code">CREATE FILE SIRIUS
END CREATE
END CREATE
OPEN FILE SIRIUS
OPEN FILE M204PROC
IN SIRIUS RESTORE 192 FROM <''whatever''>
IN M024PROC RESTORE 192 FROM ''whatever''
</p>
</p>


<table class="thJustBold">
<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of Dictionary/204 files (see list of files in a following step). The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>
<tr><th>SIRIUS</th>
<td>4200 pages; must always be allocated.</td></tr>


<tr><th>SIRLOCAL
<li>Restore <code>M204PROC</code>, noting the following:
</th><td>1200 pages; must always be allocated.</td></tr>
<ul>
 
<tr><th nowrap>SIRSTATS or MONDATA
</th><td>4000 pages; only if you are installing <var class="product">SirMon</var>.  Use <code>MONDATA</code> for versions 7.7 and earlier.  Use <code>SIRSTATS</code> for versions 8.1 and later.</td></tr>
 
<tr><th>SIRFILED</th>
<td>1200 pages; only if you are installing <var class="product">SirFile</var>.</td></tr>
 
<tr><th>SIRLIBD</th>
<td>1200 pages; only if you are installing <var class="product">SirLib</var>.</td></tr>
 
<tr><th>SIRLIBP</th>
<td>1200 pages; only if you are installing <var class="product">SirLib</var>.</td></tr>


<tr><th>SIRTPROC</th>
<td>2000 pages; only if you are installing <var class="product">SirLib</var>.
This file can and should be sized much larger if you maintain hundreds or thousands of concurrent change decks in <var class="product">SirLib</var>.</td></tr>
<tr><th>JANCAT</th>
<td>1200 pages; only if you are installing Janus OMNI.</td></tr>
<tr><th>JANSSL</th>
<td>1200 pages; only if you are installing Janus SSL.</td></tr>
</table>
<p class="warn">
'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of <code>SIRLOCAL</code> and any application-specific data files, like <code>JANCAT</code>, <code>SIRLIBD</code>, <code>SIRFILED</code>, or <code>SIRSTATS</code>.
The installation process uses these files to determine whether to
perform upgrade actions or new-installation actions. </p>
<li>Restore <code>SIRIUS</code>, noting the following:
<ul>
<li>Modify <var>LOADPROC</var> in the JCL library created during the $functions
installation (usually <code>SIRIUS.V<i>xxx</i>.LIB</code>, where <var class="term">xxx</var>
is a version number) to refer to an appropriate load module and CCA<i>xxxxx</i> files.
Note that <var>LOADPROC</var> may have been customized for your site to include only those files relevant to your installation process. </li>
<li>Rename database DSNs to conform to local standards. </li>
<li>Rename database DSNs to conform to local standards. </li>
</ul> </li>
<li>Provide a valid logon ID and password for the CCAIN stream for this job.
If, for example, you are using the <code>SIRIUS</code> file for the first time,
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul>


<div id="updateJCL"></div>
<li id="updateJCL">Update the Online JCL or EXEC:
<li>Update the Online JCL or EXEC:
<p>
<ol type="A">
Add DD cards for the Dictionary/204 files that the installation job allocates and creates.  
<li>Add DD (MVS) cards or FILEDEFs (CMS) for the UL/SPF files.
The following list identifies the files for which DD cards might be needed:</p>
The following list identifies the files for which DD cards or FILEDEFs may be needed:


<table class="thJustBold">
:M204PROC
<tr><th>SIRIUS</th>
:METADATA
<td>Must always be allocated.</td></tr>
:DATALINK
 
:M204TEMP
<tr><th>SIRLOCAL
:M204DCTL
</th><td>Must always be allocated.</td></tr>
:D204SYS
 
:D204RPT
<tr><th>SIRSTATS or MONDATA
</th><td>If installing <var class="product">SirMon</var> and using the web interface.  Use <code>MONDATA</code> for UL/SPF versions 7.7 and prior. Use <code>SIRSTATS</code> for UL/SPF versions 8.1 and later.</td></tr>
 
<tr><th>SIRFILED
</th><td>If installing <var class="product">SirFile.</var></td></tr>
 
<tr><th nowrap>SIRLIBD, SIRLIBP, SIRTPROC
</th><td>If installing <var class="product">SirLib.</var></td></tr>
 
<tr><th>JANCAT
</th><td>If installing JANUS OMNI Access Module.</td></tr>
 
<tr><th>JANSSL
</th><td>If installing JANUS SSL Module.</td></tr>
</table> </li>


<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<li>Verify that the Online environment allows the use of file groups and APSY subsystems.
<ul>
<ul>
<li>To use permanent file groups, the Online must have allocated an
<li>To use permanent file groups, the Online must have a <code>CCAGRP</code> file defined to the run, and the <var>[[SYSOPT parameter|SYSOPT]]</var> parameter must contain the <code>2</code> bit. </li>
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
<li>To use APSYs, an Online must have a [[System requirements for Application Subsystems#Overview of CCASYS|CCASYS]] file
(with all fields defined), and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit. </li>
defined to the run, and the <var>SYSOPT</var> parameter must contain the <code>1</code> bit.  
</ul>
<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]]. </li>
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>
</ol> </li>
</ul> </li>
 
<li>Verify the Online has a minimum of 10 [[Sdaemons|Sdaemon]] threads allocated.  Each of these threads is typically defined as <code>IODEV15</code>. </li>


<li>Modify the User 0 stream.
<li>Modify the User 0 stream.
Line 405: Line 256:
<table class="thJustBold">
<table class="thJustBold">
<tr><th>NFILES
<tr><th>NFILES
</th><td>Increase by the number of <var class="product">UL/SPF</var> files.</td></tr>
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>


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


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


<tr><th>NORQS
<tr><th>NORQS
</th><td>Verify setting is at least 5.</td></tr>
</th><td>Verify setting is at least 10.</td></tr>
</table> </li>
</table> </li>
   
   
<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
<li>To install Dictionary/204 for the first time, use the JCL provided in <code>DDINST</code>, which is stored in the RKOBJLIB. </li>
to a load module containing the <var class="product">Sirius Mods</var>. </li>


<li>Issue <code>OPEN FILE SIRIUS</code> (no password is required), and execute the following command:
<li>To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the <code>DDRINST</code> job in RKOBJLIB.
<p class="code">INCLUDE SETUP.EXE
<p>  
</p>
This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
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.
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.
If any problems are encountered while running this procedure, correct the problem and re-execute. </p>
<p>  
The procedure SETUP.EXE also builds an APSY subsystem called <code>SETUP.EXE</code>.
During APSY execution, some error messages are not suppressed, to aid in diagnosing any installation problems.
If installations need to be re-run, the subsystem may be invoked rather than the procedure.
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>
 
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, etc. </li>
   
   
<li>Add users to the appropriate SCLASSes for any private or semi-public UL/SPF APSYs.  
<li>Add users to the appropriate [[SCLASS|SCLASSes]] for any private or semi-public Dictionary/204 subsystems.  
<p>  
<p>  
The installing user is automatically added to the administration SCLASS in all UL/SPF APSYs.</p> </li>
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.
<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
Line 444: Line 289:
</th></tr>
</th></tr>


<tr><th>SIRSCAN START
<tr><th>START SUBSYS DICTIONARY
</th><td>Journal scanner</td></tr>
</th><td>Dictionary main menu</td></tr>


<tr><th>SIRFILE START
<tr><th>START SUBSYS DICTADMIN
</th><td>File monitoring subsystem</td></tr>
</th><td>Dictionary Administration</td></tr>


<tr><th>SIRPRO START
<tr><th>START SUBSYS DOCUMENT
</th><td>Developers' environment</td></tr>
</th><td>Documentation environment</td></tr>


<tr><th>SIRMON START
<tr><th>START SUBSYS FILEMGMT
</th><td>Online performance monitor</td></tr>
</th><td>File building tool</td></tr>


<tr><th>SIRLIB START
<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Change management system</td></tr>
</th><td>Defining APSY subsystems</td></tr>


<tr><th>JANCAT START
<tr><th>START SUBSYS DICTREPORT
</th><td>Janus OMNI Table manager</td></tr>
</th><td>Dictionary report subsystem</td></tr>


<tr><th>JANSSL START
<tr><th>START SUBSYS XREF
</th><td>Janus SSL certificate management system</td></tr>
</th><td>Cross reference reporting subsystem</td></tr>
</table>
</table>
<p>  
<p>  
If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under <code>TEST DEBUG</code> mode.
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>
For example, to determine why SIRSCAN failed to compile, enter: </p>
<p class="code">TEST DEBUG DICTIONARY
<p class="code">TEST DEBUG SIRSCAN
</p> </li>
</p> </li>
   
   
<li>This step is optional.
<li>This step is optional.
Modify the online input stream so User 0 initializes (compiles) the <var class="product">UL/SPF</var> subsystems.
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:
Do this by placing one or more of the following in User 0's input stream:
<p class="code">SIRSCAN START
<p class="code">START SUBSYS DICTIONARY
SIRFILE START
START SUBSYS DOCUMENT
SIRPRO START
START SUBSYS DICTADMIN
SIRMON START
START SUBSYS FILEMGMT
SIRLIB START
START SUBSYS SUBSYSMGMT
JANMAN START
START SUBSYS DICTREPORT
JANCAT START
START SUBSYS XREF
START SUBSYSTEM ULSPF
</p>
</p>
<p>
<p>
Line 488: Line 331:
computing period. </p></li>
computing period. </p></li>
   
   
<li>Review the [[#UL/SPF server size and additional customization|UL/SPF server size and additional customization]] section, below, for specific requirements of individual APSY components of <var class="product">UL/SPF</var>.</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>
</ol>
<p class="note">
<p class="note">'''Note:''' CCATEMP usage may increase with <var class="product">Dictionary/204</var>.
'''Note:''' CCATEMP usage may increase with <var class="product">UL/SPF</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>
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>


===UL/SPF server size and additional customization===
==Installing Dictionary/204 on IBM z/VSE==
The minimum <var class="product">UL/SPF</var> server size requirements are listed below.
This section gives instructions for installing <var class="product">Dictionary/204</var> on IBM z/VSE,
The actual server size requirements may vary slightly, because of table
including z/VSE system and software requirements.
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>.
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">
<table class="thJustBold">
<tr class="head"><th>Subsystem name
<tr><th>M204PROC</th>
</th><th>Minimum server
<td>6000 pages (7.6 or earlier), 9800 pages (7.7 or later)</td></tr>
</th></tr>
 
<tr><th>METADATA
</th><td>400 pages</td></tr>
 
<tr><th nowrap>DATALINK</th><td>400 pages


<tr><th>SIRSCAN
<tr><th>M204TEMP</th>
</th><td>180K</td></tr>
<td>400 pages</td></tr>


<tr><th>SIRDBA
<tr><th>D204RPT</th>
</th><td>180K</td></tr>
<td>400 pages</td></tr>


<tr><th>SIRFILE
<tr><th>D204SYS</th>
</th><td>230K</td></tr>
<td>400 pages</td></tr>


<tr><th>SIRPRO
<tr><th>M204DCTL</th>
</th><td>380K</td></tr>
<td>400 pages
</td></tr>
</table>


<tr><th>SIRLIB
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>.
</th><td>135K</td></tr>
<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>


<tr><th>SIRADMIN
<p class="warn">'''Attention:''' <i>If you are upgrading from a previous release</i>, keep your old copies of Dictionary/204 files (see list of files in a following step). The installation process uses these files to determine whether to perform upgrade actions or new-installation actions. </p> </li>
</th><td>150K</td></tr>


<tr><th>SIRMON
<li>Restore <code>M204PROC</code>, noting the following:
</th><td>120K</td></tr>
<ul>


<tr><th>ULSPF
<li>Rename database DSNs to conform to local standards. </li>
</th><td>135K</td></tr>
</table>
   
   
====UTABLE and other parameter settings====
<li>Provide a valid logon ID and password for the CCAIN stream for this job.
As of <var class="product">UL/SPF</var> version 8.1 (June 2013), all <var class="product">UL/SPF</var> subsystems can be set to bypass <var>[[UTABLE command|UTABLE]]</var> resets.  Use the <code>SIRADMIN</code> subsystem to set this feature.
If, for example, you are using the <code>M204PROC</code> file for the first time,
For versions prior to 8.1, and for those who choose to leave the <var>UTABLE</var> resets in place, <var class="product">UL/SPF</var> will capture local <var>UTABLE</var> settings before they reset them to those required by <var class="product">UL/SPF</var>.
make sure it is created, opened, and initialized before the <var>RESTORE</var>. </li>
</ul> </li>
Initial problems with <var class="product">UL/SPF</var> subsystems are usually associated with one or two extremely small default <var>UTABLE</var> settings.
 
Running the failing APSY in <code>TEST DEBUG</code> mode will highlight <var>UTABLE</var> parameters that need to be increased.
<li id="updateJCL">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


<blockquote class="note"><b>Note:</b> One parameter that must be set for <code>SIRMON, SIRPRO, and SIRSCAN</code> is <var>[[SCRNSTBL parameter|SCRNSTBL]]</var>, which is necessary for the use of screen objects.  
<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 a <code>CCAGRP</code> file defined to the run, 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 a [[System requirements for Application Subsystems#Overview of CCASYS|CCASYS]] file
defined to the run, 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">
<table class="thJustBold">
<tr class="head"><th colspan="2">UL/SPF required parameter minimums</th></tr>
<tr><th>NFILES
<tr><th>Parameter</th><th>Value</th></tr>
</th><td>Increase by the number of <var class="product">Dictionary/204</var> files.</td></tr>


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


====Additional setup for SirLib====
<tr><th>NORQS
Read and follow the instructions in the appendix "Getting
</th><td>Verify that the setting is at least 5.</td></tr>
Started" in the <var class="book">[[Media:LibrNew.pdf|SirLib User's Guide]]</var>.
</table> </li>
   
   
====Additional setup for SirScan====
<li>Start the <var class="product">Model 204</var> Online region, verifying that it points
The <var class="product">SirScan</var> administrator may use SIRADMIN option 4 to set default I/O
to a load module containing the <var class="product">Model204 Online</var>. </li>
and record maximums for users in the various <var class="product">SirScan</var> SCLASSes.
 
This is described at the beginning of the
<li>Issue <code>OPEN FILE M204PROC</code> (no password is required), and execute the following command:
<var class="book">[[Media:ScanrNew.pdf|SirScan User's Guide]]</var>.
<p class="code">INCLUDE DICN.DDRINST
====Additional setup for SirMon====
When users are added to SCLASSes, note that there is a special <var>BUMP</var> SCLASS.
Any user added to this SCLASS gains the ability to <var>BUMP</var> other users.
This class does not provide access to customizing options in <var class="product">SirMon</var>.
Only users in the ADMIN SCLASS are able to add custom screen definitions to <var class="product">SirMon</var>.
If the <var class="product">SirMon</var> background monitor is to be used,
add the following line to User 0's input stream:
<p class="code">SIRMON BACKGROUND
</p>
</p>
The background monitor may also be started automatically in a BATCH2 thread or an sdaemon thread.
<p>
Consult the <var class="book">[[Media:MonrNew.pdf|SirMon User's Guide]]</var>
This procedure performs all installation functions for new users and all upgrade functions for reinstalling users.
for details.
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>
   
   
You can customize statistic thresholds or use the supplied defaults to establish problem conditions.
<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>
   
   
As of <var class="product">UL/SPF</var> Version 6.8, <var class="product">SirMon</var> has a feature to send warnings to
<li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
e-mail addresses and cell phones (via e-mail).
<table class="thJustBold">
This feature requires <var class="product">[[Janus Sockets]]</var> and a started <var class="product">Janus Sockets</var> port.
<tr class="head"><th>Enter ...
</th><th>To test the ...
====Additional setup for SirFile====
</th></tr>
If the <var class="product">SirFile</var> background monitor is to be used, add the following line to User 0's input stream:
<p class="code">SIRFILE BACKGROUND
</p>
As with <var class="product">SirMon</var>, the background monitor may be started automatically in a BATCH2 thread or in an sdaemon thread, and you can consult the
<var class="book">[[Media:FilrNew.pdf|SirFile User's Guide]]</var> for details.
You can customize the system and file-specific thresholds or use the
supplied defaults to establish problem conditions.


====UL/SPF access privileges and SCLASSes====
<tr><th>START SUBSYS DICTIONARY
Each component application of <var class="product">UL/SPF</var> has its own APSY definition and
</th><td>Dictionary main menu</td></tr>
privileges associated with SCLASSes.
If you have a good reason for doing so, you can redefine any of the <var class="product">UL/SPF</var> APSYs as <var>PUBLIC</var>,
<var>SEMI-PUBLIC</var>, or <var>PRIVATE</var>.
[[Contacting Rocket Software Technical Support|Contact Rocket Software]] if you are unsure of the effect of a proposed change.


==UL/SPF on the Web==
<tr><th>START SUBSYS DICTADMIN
Web-specific versions of the <var class="product">UL/SPF</var> subsystems are actively being developed and supported, and they are available to sites that own <var class="product">[[Janus Web Server]]</var>.
</th><td>Dictionary Administration</td></tr>


All the <var class="product">UL/SPF</var> APSYs can be used on the web via <var class="product">Janus Web Legacy Support</var>, which simply translates the 3270 screens of the underlying product into HTML.  Web-specific versions of both <var class="product">SirScan</var> and <var class="product">SirMon</var> can be invoked by setting up some <var class="product">Janus Web Server</var> web rules.
<tr><th>START SUBSYS DOCUMENT
</th><td>Documentation environment</td></tr>


===Setup for web-based SirScan===
<tr><th>START SUBSYS FILEMGMT
Web-based <var class="product">SirScan</var> is very lightweight, and requires a minimum of web rules to run.
</th><td>File building tool</td></tr>
<ol>
<li>Define a <var class="product">Janus Web Server</var> port.


<li>Define the following rule to invoke <var class="product">SirScan</var>:
<tr><th>START SUBSYS SUBSYSMGMT
</th><td>Defining APSY subsystems</td></tr>


<p class="code">JANUS WEB <var class="term">portname</var> ON /SIRSCAN/* CMD 'SIRSCAN *'
<tr><th>START SUBSYS DICTREPORT
</p>
</th><td>Dictionary report subsystem</td></tr>


<li>The above rule will make <var class="product">SirScan</var> available, but it will not necessarily require a logon to the system, so you will need to add rules to force users to log in as well:
<tr><th>START SUBSYS XREF
 
</th><td>Cross reference reporting subsystem</td></tr>
<p class="code">JANUS WEB <var class="term">portname</var> DISALLOW /SIRSCAN/*
</table>
JANUS WEB <var class="term">portname</var> ALLOW /SIRSCAN/* USER *
<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>
<li>Because the above rules force users to login, the port on which <var class="product">SirScan</var> runs should either:
<ul>
<li>Be only on a company intranet. </li>
<li>Be SSL protected, to prevent userids and passwords from being sent over the internet in clear text format. </li>
</ul>
<p>
<p>
The above rules will work on an unprotected port, but it is '''very strongly recommended''' that this feature only be used when SSL protection is in effect.</p> </li>
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>
</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>


===Setup for web-based SirMon===
===Dictionary/204 server size===
This applies only to <var class="product">UL/SPF</var> Version 8.1 and later.
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>


Because web-based <var class="product">SirMon</var> employs XML, XSLT, Javascript, a stylesheet and some graphics,
<tr><th>DICTIONARY
the web rules needed to run <var class="product">SirMon</var> on the web are a little more complex:
</th><td>455K</td></tr>
<ol>
 
<li>Define a <var class="product">Janus Web Server</var> port. </li>
<tr><th>DOCUMENT
</th><td>455K</td></tr>


<li>Define the following rules to invoke <var class="product">SirMon</var>:
<tr><th>DICTADMIN
</th><td>455K</td></tr>


<p class="code">JANUS WEB <var class="term">portname</var> TYPE ANY *.PNG IMAGE/PNG           
<tr><th>FILEMGMT
JANUS WEB <var class="term">portname</var> TYPE ANY *.CSS TEXT/CSS   
</th><td>455K</td></tr>
JANUS WEB <var class="term">portname</var> TYPE ANY *.JS APPLICATION/X-JAVASCRIPT 
JANUS WEB <var class="term">portname</var> ON /*.CSS OPEN SIRIUS SEND *.CSS
JANUS WEB <var class="term">portname</var> ON /SIRMON/* CMD SIRMON       
JANUS WEB <var class="term">portname</var> ON /SIRMON/*.GIF OPEN SIRIUS SEND *.GIF EXPIRE +2147483   
JANUS WEB <var class="term">portname</var> ON /SIRMON/*.PNG OPEN SIRIUS SEND *.PNG EXPIRE +2147483   
JANUS WEB <var class="term">portname</var> ON /SIRMON/*.JS OPEN SIRIUS SEND *.JS BINARY EXPIRE +2147483
JANUS WEB <var class="term">portname</var> ON /AJAX/* OPEN SIRIUS SEND *
JANUS WEB <var class="term">portname</var> ON /AJAX/*.JS OPEN SIRIUS SEND *.JS TEXT
JANUS WEB <var class="term">portname</var> ON /AJAX/*.UL OPEN SIRIUS CMD 'INCLUDE *.UL'
JANUS WEB <var class="term">portname</var> DISALLOW /SIRMON/*     
JANUS WEB <var class="term">portname</var> ALLOW /SIRMON/* USER * 
JANUS WEB <var class="term">portname</var> TYPE ANY *.XML TEXT/XML
JANUS WEB <var class="term">portname</var> TYPE ANY *.XSL TEXT/XSL 
JANUS WEB <var class="term">portname</var> ON /SIRMON/*.XSL OPEN SIRIUS SEND *.XSL EXPIRE +2147483   
JANUS WEB <var class="term">portname</var> ON /SIRMON/*.CSS OPEN SIRIUS SEND *.CSS EXPIRE +2147483   
JANUS WEB <var class="term">portname</var> ON /SIRMON/TEXTJS/*.JS OPEN SIRIUS SEND *.JS TEXT EXPIRE +2147483       
JANUS WEB <var class="term">portname</var> ON /SIRMON/BUILDJS/*.JS CMD SIRMON                         


OPEN SIRSTATS
<tr><th>SUBSYSMGMT
IN SIRSTATS INITIALIZE KEEPDEFS                                         
</th><td>455K</td></tr>
</p> </li>


<li>The above rules will make <var class="product">SirMon</var> available, but they will not necessarily require a logon to the system, so you will need to add rules to force users to log in as well:
<tr><th>DICTREPORT
</th><td>455K</td></tr>


<p class="code">JANUS WEB <var class="term">portname</var> DISALLOW /SIRMON/*
<tr><th>XREF
JANUS WEB <var class="term">portname</var> ALLOW /SIRMON/* USER *
</th><td>455K</td></tr>
</p> </li>
</table>


<li>Because the above rules force users to login, the port on which <var class="product">SirMon</var> runs should either:  
==For more information about Dictionary/204==
After completing the installation, see the [[:Category:Dictionary/204|Dictionary/204 topics]] for instructions on how to:
<ul>
<ul>
<li>Be only on a company intranet.
<li>Start, stop, and test Dictionary/204 subsystems</li>
 
<li>Set Dictionary/204 facility parameters</li>
<li>Be SSL protected, to prevent userids and passwords from being sent over the internet in clear text format. 
<li>Define Dictionary/204 users</li>
<li>Customize the Dictionary/204 structure</li>
<li>Use the Dictionary/204 facilities</li>
</ul>
</ul>


The above rules will work on an unprotected port, but it is '''very strongly recommended''' that this feature only be used when SSL protection is in effect.
[[Category:Installation]]


<p class="note"><b>Note:</b> Using <var class="product">SirMon</var> on the web also requires the <code>SIRSTATS</code> file. As shown in the above web rules, <code>SIRSTATS</code> can be re-initialized each time the Online comes up. <code>SIRSTATS</code> contains historical snapshots of system performance, and the file will fill up if not archived or reinitialized on occasion.</p> </li>
[[Category:Dictionary/204]]
</ol>

Latest revision as of 16:12, 26 September 2017

Overview

Dictionary/204 Is a set of application subsystems (known as APSYs) running inside a Model 204 Online that provide full-screen and web-based tools to help programmers, DBAs, and system managers handle the complexities of User Language and file and system management.

Installing Dictionary/204 requires downloading the M204PROC file and restoring it to your environment, setting up some subsidiary Model 204 files, and verifying that the environment has the appropriate parameter settings.

Note: As of Model 204 version 7.7, the M204PROC file is the container for the RKTools version 7.7 product, and Dictionary/204 is accessible from the RKTools interfaces (TN3270 and web), as well as from the usual Dictionary main menu.

Upgrades to Dictionary/204 can almost always be handled by restoring a fresh copy of the M204PROC file.

A summary of the Dictionary/204 installation steps

The following checklist specifies in brief the steps to follow installing Dictionary/204, 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/OS, and Installing Dictionary/204 on IBM z/VSE describe these steps in greater detail for each operating system.

  1. Allocate the space required for the M204PROC data set, and RESTORE it from the DUMP files found on the website.

    In addition, there might be any number of other data sets required for the Dictionary/204 components you are installing. These are listed in Installation checklist (z/VM CMS), Installation checklist (z/OS), and Installation checklist (z/VSE).

  2. If this is an upgrade, create backups of all Dictionary/204 files.
  3. If Dictionary/204 has never been installed, use JCL provided in the DDINST job in RKOBJLIB.
  4. If this is an upgrade, run DICN.DDRINST using the JCL provided in the DDRINST job in RKOBJLIB.
  5. Verify the success of the installation by compiling each Dictionary/204 subsystem.
  6. Use the subsystem named DICTADMIN to customize the Dictionary/204 environment.

Preparing for Dictionary/204 installation

The Dictionary/204 products are implemented as Model 204 subsystems. The code for all the component subsystems resides in the file named M204PROC which is typically downloaded from the Support section of the Rocket Software website.

Obtaining product installation files

The files necessary for the installation are available from the Rocket Software website:

  1. On the Rocket M204 Customer Care page, click the Download SOUL files link.
  2. After providing your registered customer login information, download the latest version of the Dictionary/204 file, M204PROC. The M204PROC file to download for versions higher than 7.5 of Model 204 is the file in the RKTools V7.7 product row. As described in Dictionary/204 logon and commands, Dictionary/204 is packaged with RKTools as of RKTools V7.7.

    A "Click here" link in the text at the beginning of this page provides Help on downloading format, some information about different browser behaviors, file sizing information, and more.

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 (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

  • Dictionary/204 operates in a Model 204 Online region.

    In the rest of this document, "Online" refers to a region of Model 204 running an ONLINE load module containing version 7.5 or higher.

User privileges

The installing user must have:

  • Update access to the JCL or EXECs that bring up the host Online.
  • System Manager privileges, as well as access to all of the Dictionary/204 subsystems and the JCL or EXEC that runs the Online Model 204 region.

New installation or reinstallation

  • Sites that have never installed Dictionary/204 must use the new installation, as there are a number of files to allocate and Model 204 parameters to update.
  • Sites that are re-installing the latest version of Dictionary/204 can reinstall Dictionary/204 (using DDRINST) or perform a new installation (using DDINST) to create a new set of Dictionary/204 files.

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

New installation

Note: 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.

You can verify the Dictionary/204 version in the title of any Dictionary/204 screen. The installation steps are as follows:

  1. In the Rocket M204 Customer Care page of the Rocket website, click the Download SOUL files link.
  2. Download the appropriate version of the M204PROC file for your version of Model 204 (for version 7.7, M204PROC is the container for, and Dictionary/204 is a member of, RKTools).
  3. Verify that the Online in which you are installing contains a version of Model 204 equal to or greater than the Dictionary/204 version.
  4. Restore the M204PROC file into a file on your mainframe. (This file must be 6000 pages for 7.6 or earlier, or 9800 pages for 7.7 or later.) The DDNAME for this file in your Model 204 regions is also M204PROC.

  5. Using the JCL from RKOBJLIB DDINST, run the procedure DICN.DDINST to install the downloaded release.

The Dictionary/204 APSYs can be set to AUTOSTART if you prefer.

Reinstallation for existing Dictionary/204 sites

You can verify the Dictionary/204 version in the title of any Dictionary/204 screen. The reinstallation steps are as follows:

  1. In the Rocket M204 Customer Care page of the Rocket website, click the Download SOUL files link.
  2. Download the latest version of the M204PROC file (which is followed by a version number). This is a dump of M204PROC.
  3. Restore that dump data set into an M204PROC file on your mainframe. (This file must be 6000 pages for 7.6 or earlier, or 9800 pages for 7.7 or later.)

    If you are upgrading from a previous release, simply overlay your old M204PROC file.

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

    Note: Running the installation job (DDRINST) creates backups of the upgraded Dictionary files.

Installing Dictionary/204 on IBM z/VM CMS

This section gives instructions for installing Dictionary/204 on z/VM CMS, including z/VM CMS system and software requirements.

Review Preparing for Dictionary/204 installation for details about general Dictionary/204 system requirements.

The M204PROC Model 204 file, which contains the SOUL code that runs Dictionary/204, can be obtained from the Rocket website.

The following files are required to complete an installation of Dictionary/204:

  • METADATA
  • DATALINK
  • M204TEMP
  • D204RPT
  • D204SYS
  • M204DCTL

Allocate space for the Dictionary/204 files, and restore them from the dump files downloaded from the Rocket website, as described in the following steps.

Installation checklist (z/VM CMS)

  1. Define and format a minidisk to hold the Dictionary/204 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.
  2. Allocate space for the required Dictionary/204 data sets. A skeleton exec, D204FDEF, is provided for this purpose. Modify this exec to perform the allocations on the appropriate minidisks.

    Allocate space for the following data sets:

    M204PROC 6000 pages (7.6 or earlier), 9800 pages (7.7 or later); must always be allocated.
    METADATA 400 pages; must always be allocated.
    DATALINK 400 pages; must always be allocated.
    M204TEMP 400 pages; must always be allocated.
    D204RPT 400 pages; must always be allocated.
    D204SYS 400 pages; must always be allocated.
    M204DCTL 400 pages; must always be allocated.

    Attention: If you are upgrading from a previous release, modify the D204FDEF EXEC to use the old Dictionary/204 files for the upgrade.

    The installation process uses these files to install a new version of Dictionary/204.

  3. Modify the RESPROC EXEC to specify the M204PROC dump file and M204PROC file to be loaded.
  4. Restore the M204PROC file with the D204 RESPROC exec.

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

  5. To run the D204 exec for a new install, make sure the Online execs and load modules are on an accessed disk, then enter this command:

    EXEC D204 INSTALL

  6. To run the D204 exec for a REINSTALL, make sure the Online execs and load modules are on an accessed disk, then enter this command:

    EXEC D204 REINSTALL

  7. Complete steps 3 through the end in the Installing Dictionary/204 on IBM z/OS section.

Installing Dictionary/204 on IBM z/OS

This section gives instructions for installing Dictionary/204 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.

Installation checklist (z/OS)

  1. Allocate the space required for the M204PROC file:
    M204PROC 6000 pages (7.6 or earlier), 9800 pages (7.7 or later)

    If you are creating a new M204PROC file from scratch, this will not be a problem. But if you are restoring into your existing M204PROC file, you will have to CREATE the file first (to wipe out existing content) before you execute the RESTORE.

    An example command sequence follows:

    CREATE FILE M204PROC END CREATE OPEN FILE M204PROC IN M024PROC RESTORE 192 FROM whatever

    Attention: If you are upgrading from a previous release, keep your old copies of Dictionary/204 files (see list of files in a following step). The installation process uses these files to determine whether to perform upgrade actions or new-installation actions.

  2. Restore M204PROC, noting the following:
    • Rename database DSNs to conform to local standards.
  3. Update the Online JCL or EXEC:

    Add DD cards for the Dictionary/204 files that the installation job allocates and creates. The following list identifies the files for which DD cards might be needed:

    M204PROC
    METADATA
    DATALINK
    M204TEMP
    M204DCTL
    D204SYS
    D204RPT
  4. Verify that the Online environment allows the use of file groups and APSY subsystems.
    • To use permanent file groups, the Online must have a CCAGRP file defined to the run, and the SYSOPT parameter must contain the 2 bit.
    • To use APSYs, an Online must have a CCASYS file defined to the run, and the SYSOPT parameter must contain the 1 bit.

      For more information about APSYs and file groups, see File groups and System requirements for Application Subsystems.

  5. Modify the User 0 stream.

    Adjust these parameters:

    NFILES Increase by the number of Dictionary/204 files.
    NDCBS Increase by the number of Dictionary/204 files.
    NDIR Increase by the number of Dictionary/204 files.
    NORQS Verify setting is at least 10.
  6. To install Dictionary/204 for the first time, use the JCL provided in DDINST, which is stored in the RKOBJLIB.
  7. To upgrade your existing Dictionary/204, run DICN.DDRINST using the JCL provided in the DDRINST job in RKOBJLIB.

    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.

    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.

  8. Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 subsystems.

    The installing user is automatically added to the administration SCLASS in all Dictionary/204 subsystems.

  9. Verify the installation of the subsystem(s) by compiling all of the subsystems.
    Enter ... To test the ...
    START SUBSYS DICTIONARY Dictionary main menu
    START SUBSYS DICTADMIN Dictionary Administration
    START SUBSYS DOCUMENT Documentation environment
    START SUBSYS FILEMGMT File building tool
    START SUBSYS SUBSYSMGMT Defining APSY subsystems
    START SUBSYS DICTREPORT Dictionary report subsystem
    START SUBSYS XREF Cross reference reporting subsystem

    If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under TEST DEBUG mode. For example, to determine why DICTIONARY failed to compile, enter:

    TEST DEBUG DICTIONARY

  10. This step is optional. Modify the online input stream so User 0 initializes (compiles) the Dictionary/204 subsystems. Do this by placing one or more of the following in User 0's input stream:

    START SUBSYS DICTIONARY START SUBSYS DOCUMENT START SUBSYS DICTADMIN START SUBSYS FILEMGMT START SUBSYS SUBSYSMGMT START SUBSYS DICTREPORT START SUBSYS XREF

    This ensures that the subsystems are started for non-administrative users, and it shifts the overhead of compilation to a non-peak computing period.

  11. Review the Dictionary/204 server size section, below, for specific requirements of individual APSY components of Dictionary/204.

Note: CCATEMP usage may increase with Dictionary/204. CCATEMP should be monitored (VIEW TEMPSIZE, VIEW TEMPMAX) to ensure that sufficient space is allocated to accommodate the additional activity.

Installing Dictionary/204 on IBM z/VSE

This section gives instructions for installing Dictionary/204 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.

Installation checklist (z/VSE)

  1. Allocate the space required for the Dictionary/204 files:
    M204PROC 6000 pages (7.6 or earlier), 9800 pages (7.7 or later)
    METADATA 400 pages
    DATALINK400 pages
    M204TEMP 400 pages
    D204RPT 400 pages
    D204SYS 400 pages
    M204DCTL 400 pages

    If you are creating a new M204PROC file from scratch, this will not be a problem. But if you are restoring into your existing M204PROC file, you will have to CREATE the file first (to wipe out existing content) before you execute the RESTORE.

    A sample command sequence follows:

    CREATE FILE M204PROC END CREATE OPEN FILE M204PROC IN M024PROC RESTORE 192 FROM whatever

    Attention: If you are upgrading from a previous release, keep your old copies of Dictionary/204 files (see list of files in a following step). The installation process uses these files to determine whether to perform upgrade actions or new-installation actions.

  2. Restore M204PROC, noting the following:
    • Rename database DSNs to conform to local standards.
    • Provide a valid logon ID and password for the CCAIN stream for this job. If, for example, you are using the M204PROC file for the first time, make sure it is created, opened, and initialized before the RESTORE.
  3. Update the Online JCL or EXEC:

    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:

    M204PROC
    METADATA
    DATALINK
    M204TEMP
    M204DCTL
    D204SYS
    D204RPT
  4. Verify that the Online environment allows the use of file groups and application subsystems.
    • To use permanent file groups, the Online must have a CCAGRP file defined to the run, and the UPSI parameter must contain the 00000010 bit.
    • To use application subsystems, an Online must have a CCASYS file defined to the run, and the UPSI parameter must contain the 00000001 bit.

      For more information about application subsystems and file groups, see File groups and System requirements for Application Subsystems.

  5. Modify the User 0 stream.

    Adjust these parameters:

    NFILES Increase by the number of Dictionary/204 files.
    NDCBS Increase by the number of Dictionary/204 files.
    NDIR Increase by the number of Dictionary/204 files.
    NORQS Verify that the setting is at least 5.
  6. Start the Model 204 Online region, verifying that it points to a load module containing the Model204 Online.
  7. Issue OPEN FILE M204PROC (no password is required), and execute the following command:

    INCLUDE DICN.DDRINST

    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.

    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.

  8. Add users to the appropriate SCLASSes for any private or semi-public Dictionary/204 APSYs.

    The installing user is automatically added to the administration SCLASS in all Dictionary/204 APSYs.

  9. Verify the installation of the subsystem(s) by compiling all of the subsystems.
    Enter ... To test the ...
    START SUBSYS DICTIONARY Dictionary main menu
    START SUBSYS DICTADMIN Dictionary Administration
    START SUBSYS DOCUMENT Documentation environment
    START SUBSYS FILEMGMT File building tool
    START SUBSYS SUBSYSMGMT Defining APSY subsystems
    START SUBSYS DICTREPORT Dictionary report subsystem
    START SUBSYS XREF Cross reference reporting subsystem

    If any of these subsystems fails to compile, ensure that the subsystem is STOPped, and run it under TEST DEBUG mode. For example, to determine why DICTIONARY failed to compile, enter:

    TEST DEBUG DICTIONARY

  10. This step is optional. Modify the online input stream so User 0 initializes (compiles) the Dictionary/204 subsystems. Do this by placing one or more of the following in User 0's input stream:

    START SUBSYS DICTIONARY START SUBSYS DOCUMENT START SUBSYS DICTADMIN START SUBSYS FILEMGMT START SUBSYS SUBSYSMGMT START SUBSYS DICTREPORT START SUBSYS XREF

    This ensures that the subsystems are started for non-administrative users, and it shifts the overhead of compilation to a non-peak computing period.

  11. Review Dictionary/204 server size for specific requirements of individual APSY components of Dictionary/204.

Note: CCATEMP usage might increase with Dictionary/204. CCATEMP should be monitored (VIEW TEMPSIZE, VIEW TEMPMAX) to ensure that sufficient space is allocated to accommodate the additional activity.

Dictionary/204 server size

The minimum Dictionary/204 server size requirements are listed below. The actual server size requirements might vary slightly because of table settings in the local Online Model 204 regions, and because of slight differences between UTABLE requirements in different versions of Model 204.

Subsystem name Minimum server
DICTIONARY 455K
DOCUMENT 455K
DICTADMIN 455K
FILEMGMT 455K
SUBSYSMGMT 455K
DICTREPORT 455K
XREF 455K

For more information about Dictionary/204

After completing the installation, see the Dictionary/204 topics for instructions on how to:

  • Start, stop, and test Dictionary/204 subsystems
  • Set Dictionary/204 facility parameters
  • Define Dictionary/204 users
  • Customize the Dictionary/204 structure
  • Use the Dictionary/204 facilities
Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Dictionary/204_installation_guide&oldid=104314"