Model 204 installation on IBM z/VSE: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(339 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<span style="color:#BA0000"><b>Note:</b> This page is currently under construction.</span>
==Overview==
This topic describes how to install Rocket Model 204 version 7.5 or later on an IBM<sup>&reg;</sup> z/VSE<sup>&reg;</sup> operating system.


This page describes the steps required to upgrade from Rocket Model 204 version 7.4 to version 7.5, on the IBM z/VSE operating system.
For information on the new features available in the Model 204 version that you are installing, see the [[Release notes#Release_notes.2C_wishlists.2C_and_punch_lists|release notes]] for that version.


<table><tr><td><p>In order to upgrade to Model 204 version 7.5, <b>you must have version 7.4</b> and the <b>latest Autofix set of Early Warnings</b> installed on your system.</p> </td></tr></table>
If you are skipping any versions when installing (such as moving from version 7.4 to 7.7), be sure to read the release notes for the skipped versions as well.


To upgrade to version 7.5 simply download, upload, and link the 7.5 object modules available from the downloads page to install the 7.5 components.
===Documentation conventions===
In this topic, the Model 204 version and release that you are installing is referred to by 7.<var class="term">r</var>, where 7.<var class="term">r</var> can be 7.5 or later.
Files, job streams, procedures, and sublibrary versions are referred to by version 7 and release <var class="term">rr</var>; for example, V7<var class="term">rr</var> (V770) or J7<var class="term">rr</var> (J770) for Model 204 version 7.7.
 
===Summary===
To install the new Model 204 version, simply download, upload, and link the 7.<var class="term">r</var> object modules available from the downloads page to install the 7.<var class="term">r</var> components. In addition, you must [[#Procedures that can be cataloged|catalog any procedure files]] in the V7<var class="term">rr</var> sublibrary that include DLBL/EXTENT information for existing or new Model 204 files.


==Before you begin==
==Before you begin==
<ul>
<ul>
<li>In order to upgrade to version 7.5, you must have version 7.4 and Autofix release EW3044 installed on your system.
<li>Model 204 version 7.<var class="term">r</var> does not include new Dictionary/204 files or new CCASTAT and CCASYS files. You will be using your existing 7.4 versions of these files.</li>
<p>Autofix release EW3044 includes:
<li>For system requirements for the new Model 204 version, see the [[Release notes#Release_notes.2C_wishlists.2C_and_punch_lists|release notes]].</li>
<ul>  
<li>You must have either a [[Rocket M204 user ID]] or a preexisting user ID to download the installation files.</li>
<li>Early Warnings for Model 204 through 740EW172</li>  
<li>The sublibrary containing the object has the authorization zap (covering your licensed processors) preapplied, so you do not need to get a new authorization zap from the website. (The preapplied zap will authorize Model 204 itself and any separately purchased products, such as SirScan.)</li>
<li>Early Warnings for Dictionary/204 through 740DI016</li>
</ul>
For information on Early Warnings, log in to the [http://www.rocketsoftware.com/support Rocket Customer Portal].</p></li>
<li>For system requirements for version 7.5, see the [[Release notes for Model 204 version 7.5#Operating system requirements|7.5 Release notes]].</li>
<li>You must have either a [[Rocket M204 user ID]] or a Sirius user ID to download the installation files.</li>
<li>The sublibrary containing the object has the authorization zap (covering your licensed processors) preapplied, so you do not need to get a new authorization zap from the website. <br />(The preapplied zap will authorize Model 204 itself and any separately purchased products such as MQ/204 and SirScan.)</li>
<li>The object files also have the maintenance zaps (as of the time the stream was
<li>The object files also have the maintenance zaps (as of the time the stream was
prepared) preapplied, so you do not need to apply any maintenance as part of this installation. (You will only need to apply any new maintenance when it becomes available for this release.)</li>
prepared) preapplied, so you do not need to apply any maintenance as part of this installation. (You will only need to apply any [https://m204.rocketsoftware.com/maint/fixlist new maintenance] when it becomes available for this version.)</li>
</ul>
</ul>
<div id="steps"></div>
<div id="steps"></div>


==Overview of upgrading steps==
==Overview of upgrading steps==
<!--Caution: <div> above-->
Review the following high-level summary of steps before you begin downloading the <var class="product">Model 204</var> version 7.5 files.
Review the following high-level summary of steps before you begin downloading the <var class="product">Model 204</var> files.
 
For an example, see [[Example workflow for 7.5: download through installation]].
Each step links to a section with detailed instructions. Note that some steps (such as assembling custom modules) might not apply to your installation. Once you have started, you can proceed directly through the steps (detail sections are consecutive) or return to this list for context.
   
   
<ol>
<ol>
<li><p>Use your [[Rocket M204 user ID]] to [[#downloading|download]] the Model 204 object source and JCL, including M204CATP.</p></li>
<li>[[#M204CATP|Allocate and initialize]] the Model 204 library.


<li>[[#uploading|Upload]] (FTP) the downloaded components to the z/VSE system on the IBM mainframe.</li>
<li>[[#downloading|Download]] the Model 204 object file and macro library. You will need your [[Rocket M204 user ID]].</li>
 
<li>[[#populating|Populate]] the Model 204 library from the downloaded streams in the previous step.


<li>Submit the M204CATP job to allocate VSAM managed space for the Model 204 library, define the sublibraries, and catalog procedures.</li>
<li>If you have your own user $functions (FUNU), you must do the following steps:
<li>If you have your own user $functions (FUNU), you must do the following steps:
<ol style="list-style-type:lower-alpha;">
<ol style="list-style-type:lower-alpha;">
<li>[[#FUNU_7.5|modify FUNU for 64-bit addressing]] considerations and store the modified source in your V750 sublibrary.</li>  
<li>[[#FUNU_7.5|Modify FUNU for 64-bit addressing]] considerations and store the modified source in your V7<var class="term">rr</var> sublibrary.</li>  
<li>If you have any user-defined messages (MSGU), store them in your V750 sublibrary.</li>
<li>If you have any user-defined messages (MSGU), store them in your V7<var class="term">rr</var> sublibrary.</li>
<li>[[Assemble]] FUNU (and MSGU, if applicable), with the output object file stored in your V750 sublibrary.</li>
<li>[[#FUNU_7.5_assemble|Assemble]] FUNU (and MSGU, if applicable).</li>
</ol>
</ol>
</li>
</li>


<li>If you use customized modules, such as CDTB, modify them as needed and [[assemble]] them.</li>
<li>If you use customized modules, such as CDTB, modify them as needed and [[#FUNU_7.5_assemble|assemble]] them.</li>


<li>Create the system history file.</li>
<li>Link the following phases and utility programs:
<ol style="list-style-type:lower-alpha;">
<li>[[#Linking the ONLINE phase|ONLINE]] phase</li>
<li>[[#Linking the IFAM1 phase|IFAM1]] phase, if you use it</li>
<li>[[#Linking the BATCH204 phase|BATCH204]] phase, if you use it</li>
<li><var class="product">Model 204</var> [[#link_phases|phases and utility programs]], such as [[#Linking the CRAM phases|CRAM]] phases</li>
</ol>


<li>Apply the CPU ID zap.</li>
<li>If you use the [[CICS interface configuration|CICS interface]], customize it, and then [[#cics|assemble and link]] the CICS modules.</li>


<li>If your z/VSE site runs under z/VM, copy and link the [[#bvp204|$$BVP204]] phase.</li>
<li>If your z/VSE site runs under z/VM, copy and link the [[#bvp204|$$BVP204]] phase.</li>


<li>Upload, modify, and submit the [[#m204catp|M204CATP]] job.</li>
<li>[[#Allocating CCATEMP|Allocate CCATEMP]], a required data set used by Model 204 as the system scratch file.  


<li>Upload (FTP) the CATV750 job to the POWER RDR queue, CLASS=0, in binary format. This job will catalog object, source, and JCL into each Model 204 sublibrary: D<var class="term">rrr</var>, J<var class="term">rrr</var>, and V<var class="term">rrr</var>.</li>
<li>Install [[Dictionary/204 installation guide|Dictionary/204]].</li>  


<li>From the VSE console, release each job from the RDR queue. For example, R rdr,catv740. At the pause, enter the DLBL statements for your Model 204 library.</li>
<li>If you use [[#softspy|SoftSpy]], upgrade it for version 7.<var class="term">r</var>.</li>


<li>If you use the [[CICS interface]], customize it, and then [[#cics|assemble and link]] the CICS modules.</li>
<li>[[#Verifying Model 204 on your system|Verify]] that your installation was successful.</li>
</ol>


<li>Link the [[#Linking the ONLINE phase|ONLINE]] phase.</li>
==Space and partition requirements==
===Model 204 disk space requirements===
Use the minimum disk space requirements for the libraries when calculating EXTENT information for Model 204 files.


<li>If you use the [[#Linking the IFAM1 phase|IFAM1]] phase, link it.</li>
Rocket recommends a minimum library size of 1200 tracks for disk type 3390.
<li>Link the <var class="product">Model 204</var> [[utility programs]].</li>


<li>If you use [[#softspy|SoftSpy]], upgrade it for 7.5.</li>
===Reserving a partition===
</ol>
Rocket recommends a minimum partition size of eight megabytes (8M) when installing Model 204.


==Model 204 disk space requirements==
Some Model 204 installation JCL might assign system files/devices (such as SYSIPT and SYSPCH) to disk. z/VSE requires that this JCL be run in a static partition.
The following table summarizes the minimum disk space requirements for the libraries
<div id="M204CATP"></div>
as well as other information to help you calculate EXTENT information for Model 204 files.
<p class="caption">Minimum disk space requirements</p>
<table>
<th>Disk type</th> <th>Minimum Model 204 library requirement</th> <th>Bytes/track</th> <th>Model 204 pages/track</th>
<tr><td>3380</td> <td>720 tracks</td> <td>47476</td> <td>7</td></tr>
<tr><td>3390</td> <td>604 tracks</td> <td>56664</td> <td>8</td></tr>
<tr><td>9345</td> <td>736 tracks</td> <td>46456</td> <td>6</td></tr>
<tr><td>FBA</td> <td>67000 blocks</td> <td>512 bytes/block</td> <td>13 blocks/page</td></tr>
</table>


==Building the object and macro libraries==
==Preparing the Model 204 environment==
To build the object and macro libraries, you must download the object library and macro library and upload (FTP) each library to the mainframe.
<div id="downloading"></div>
===Downloading===
<!--Caution: <div> above-->
<!--Caution: <div> above-->
To prepare the Model 204 environment: run the M204CATP job, allocate CCATEMP, and catalog frequently used procedures.
===Running M204CATP===
The M204CATP job performs the following tasks:
<ul>
<li>allocates VSAM managed space for the Model 204 library (M204LIB)</li>
<li>defines the sublibraries V7<var class="term">rr</var> and J7<var class="term">rr</var> (such as V770 and J770)</li>
<li>catalogs two Model 204 procedures, M204V7<var class="term">rr</var> (such as M204V770) and M204JCL, which help facilitate access to the Model 204 sublibraries</li>
</ul>
To run the M204CATP job:
<ol>
<ol>
<li>Using your [[Rocket M204 user ID]] and password, log in to the [https://model204.rocketsoftware.com/maint/objlist Model 204 object file download page].</li>
<li>Access the [https://m204.rocketsoftware.com/download/m204catp.txt M204CATP job stream] text file and save it on your workstation.</li>
<li>Click the <b>Download object file</b> link beside the object library that you want to download.</li>
<li>Upload the job stream to the mainframe in ASCII format.</li>
<li>Go to the [https://model204.rocketsoftware.com/maint/maclist Model 204 macro library download page].</li>
<li>Modify the M204CATP job as noted in the file.</li>
<li>Click the <b>Download macro library</b> link beside the macro library that you want to download.</li>
<li>Submit the M204CATP job.</li>
</ol>
</ol>
<div id="uploading"></div>


===Uploading (FTP)===
===Allocating CCATEMP===
<!--Caution: <div> above-->
CCATEMP is a required data set used by Model 204 as the system scratch file.
Once the object file and macro library are downloaded to your workstation, FTP them to the z/VSE system on the IBM mainframe.
Specify these characteristics for the upload files:
<table class="noBorder">
<tr><td><b>transfer format:</b></td> <td>binary</td></tr>
<tr><td><b>record format:</b></td> <td>FB</td></tr>
<tr><td><b>record size:</b></td> <td>80 for object and macro libraries</td></tr>
<tr><td><b>block size:</b></td> <td>6400 for object and macro libraries</td></tr>
<tr><td><b>storage size for both:</b></td> <td>primary: 10 CYL; secondary: 5 CYL</td></tr>
</table>
For details on how to download and upload, see [[Downloading and uploading Model 204 installation components]].
<div id="bldLibs"></div>


==Reserving a partition==
Allocate CCATEMP before running jobs that execute an ONLINE, BATCH204, or IFAM1 program.
Rocket recommends a minimum partition size of eight megabytes (8M) when installing Model 204.


Some Model 204 installation JCL might assign system files/devices (SYSIPT, SYSPCH, etc.) to disk; z/VSE requires that this JCL be run in a static partition.
===Space requirement for the Model 204 library===
The M204CATP job distributed with the Model 204 software will allocate the appropriate space for the Model 204 library. In the sublibrary name, rrr
represents the release level, such as 750.
<table>
<th>Sublibrary</th> <th>Required library blocks</th>
<tr><td>J<var class="term">rrr</var></td> <td>700</td></tr>
<tr><td>V<var class="term">rrr</var></td> <td> 17,800</td></tr>
<tr><td>D<var class="term">rrr</var></td> <td> 700</td></tr>
</table>
==Overview of the Model 204 library==
M204LIB contains all the materials needed to run the Model 204 z/VSE configurations (ONLINE, BATCH204, BATCH2, and IFAM1), and utilities.   
M204LIB is composed of sublibraries: J<var class="term">rrr</var>, V<var class="term">rrr</var>, E<var class="term">rrr</var>, and D<var class="term">rrr</var>, where <var class="term">rrr</var> is the release level, such as 750.
Model 204 does not contain pre-linked phases. You must link all phases that you want to use.
<div id="M204CATP"></div>
==Allocating library space, defining sublibraries, and cataloging procedures==
<!--Caution: <div>above-->
The [[Model 204 M204CATP job stream for IBM z/VSE|M204CATP]] job allocates VSAM managed space for the Model 204 library, defines the sublibraries, and catalogs the two Model 204 procedures.
<ol>
<ol>
<li>FTP the m204catp.jcl file to the mainframe in ASCII format.</li>
<li>Calculate the size of CCATEMP:
<li>Modify the M204CATP job as noted in the m204catp.jcl file.</li>
<p>Allocate a minimum of 25 pages per user if your site uses file groups, otherwise
<li>Submit the M204CATP job.</li>
allocate 20 pages per user.</p></li>
<li>Allocate CCATEMP by modifying and submitting the ALOCTEMP job.</li>
<li>Modify the M204SYS procedure to point to the newly allocated CCATEMP.</li>
</ol>
</ol>
<div id="cics"></div>


==CICS interface installation==
===Cataloging additional procedures===
<!--Caution: <div> above-->
The Model 204 CICS interface allows CICS complete access to Model 204 facilities and supports CICS pseudo conversational programs.
<p class="note"><b>Note:</b> It is not necessary to install the CICS interface if it has been installed for a previous version of Model 204. The load modules from the older version are compatible with version 7.5 of Model 204.</p>


===Requirements===
You can store some of the more frequently used JCL in the form of cataloged procedures. The jobs to catalog these procedures are distributed in the J7<var class="term">rr</var> sublibrary.
To catalog procedures, modify each procedure as follows:
<ul>
<ul>
<li>CICS Transaction Server support
<li>Add POWER JCL</li>
<p>Rocket M204 supports the CICS Transaction Server versions 3.1, 3.2, 4.1, and 4.2.</p></li>
<li>Add the appropriate DLBL, EXTENT, and ASSGN information</li>
<li>Supporting TPROCESS COBOL applications
<p>If your CICS TPROCESS application was originally linked with AMODE=24, you must relink the CICS TPROCESS application specifying AMODE=31 because AMODE=24 is not supported.</p></li>
</ul>
</ul>
===CICS interface overview===
For an overview of the CICS interface, including storage requirements and a listing of CICS interface components, see [[CICS interface]].
   
   
===Installing the CICS interface===
The jobs assume that the M204JCL procedure is in the system library (IJSYSRS.SYSLIB). All other Rocket-supplied procedures are cataloged into the V7<var class="term">rr</var> sublibrary. <br />Determine the new file, library volumes, and extents; then modify the procedures before cataloging them.
 
====Procedures that can be cataloged====
The following shows the procedures that can be cataloged and the job that must be modified for each procedure.
<ol>
<ol>
<li>Customize the interface by editing the CICFG copy member and replacing it in the distribution library as CICFG.A. then proceed with the CICSASM and CICSLINK jobs.
<li>Determine the files, library volumes, and extents that you need for the procedures.</li>
<p>For information on customizations needed for using the CICS Standard Mapping Service, see [[CICS interface]].</p></li>
<li>Modify the catalog jobs with this information.</li>
<li>Update the CICS System Definition (CSD) using one of the following methods:
<li>Catalog the procedures.</li>
<ul><li>Resource Definition Online (CEDA).</li>
<li>The IBM DFHSCDUP offline utility, to process the definitions in batch.</li>
<li>Processing the CICS Program Control Table (PCT) and Program Processing Table (PPT)</li>
</ul>
<li>Assemble, translate, and catalog the Model 204 CICS Interface modules, using the following jobs:
  <ul>
  <li>[[Model 204 CRPSASM job stream for IBM z/VSE|CRPSASM]]</li>
  <li>[[Model 204 ENTPSASM job stream for IBM z/VSE|ENTPSASM]]</li>
  <li>[[Model 204 OPLTASMC job stream for IBM z/VSE|OPLTASMC]]</li>
  <li>[[Model 204 PPCIASM job stream for IBM z/VSE|PPCIASM]]</li>
  <li>[[Model 204 PRNTASMC job stream for IBM z/VSE|PRNTASMC]]</li>
  <li>[[Model 204 PSFASM job stream for IBM z/VSE|PSFASM]]</li>
  <li>[[Model 204 PSFSASM job stream for IBM z/VSE|PSFSASM]]</li>
  </ul>
</li>
<li>Relink the IFAM2 transactions requiring pseudo conversational support with IFENTPS.</li>
<li>Relink all user process-to-process partners with IFPPCI.</li>
</ol>
</ol>


===Updating the CICS System Definition (CSD)===
You can update the CSD by using CEDA, by using the DFHCSDUP utility, or by processing the CICS Program Control Table (PCT). Use the values in the following table, where appropriate, for the method you choose. Information about
using CEDA follows the table.
<b>CICS System Definition values</b>
<table>
<table>
<tr><th>User program</th> <th>Program name</th> <th>Transaction ID</th> <th>Modifiable <br>CICFG symbol</th>
<caption>Jobs for cataloging frequently used procedures</caption>
<th>TWA size</th></tr>
<tr class="head"><th>Procedure name</th> <th>Catalog job</th> <th>Description</th></tr>
<tr><td>IFAM2 pseudo conversational</td> <td>DFHPSF</td> <td>DFHPSF is accessed by using a CICS LINK. It is never
 
invoked with a transaction ID from a terminal.</td> <td /> <td /><tr>
<tr><td>M204WRK1</td> <td>CATWRK1</td> <td>Work file for translation and assembly</td></tr>
<tr><td>Full-screen interface</td> <td>M204PSFS</td> <td>M204</td> <td>&TRN</td> <td>88</td></tr>
 
<tr><td>Screen copy transaction</td> <td>M204CRPS</td> <td>U204</td> <td /> <td /></tr>
<tr><td>M204WRK2</td> <td>CATWRK2</td> <td>Work file for translation and assembly</td></tr>
<tr><td>Screen print transaction</td> <td>M204PRNT</td> <td>P204</td> <td>&COP</td> <td>88</td></tr>
 
<tr><td>M204SYS</td> <td>CATSYS</td> <td>System files (CCASTAT and CCATEMP)</td></tr>
 
<tr><td>M204DD</td> <td>CATDD</td> <td>Dictionary/204 files and CCASYS</td></tr>
</table>
</table>
CEDA (the Resource Definition Online transaction) or the DFHCSDUP utility defines the transactions and programs to the CSD file.
If you are not using <span style="color:#FF0000">tables</span>, then define the transactions and programs by using CEDA
and the values in the previous table, as in the following example:
<p class="syntax">CEDA DEFine PROG(program_name)
  GRoup(group_name)
  LANGuage(ASSEMBLER)
  RELoad(NO)
  RESident(NO) (Except for DFHPSF, RESident(YES))
  <span style="color:#FF0000">RSL(PUBLIC)</span>
  STatus(ENABLED)
CEDA DEFine TRANsaction(trans_ID)
  GRoup(group_name)
  PROgram(program_name)
  TWASIZE(twa_size_value)
  .
  .
  .
  <span style="color:#FF0000">RSL(PUBLIC)</span>
  .
  .
  .
CEDA CHeck GRoup(group_name)
<span style="color:#FF0000">CEDA INstall GRoup(group_name)</span>
</p>
You can use a transaction ID for a user program that is different from the value
shown in the previous table. However, if you do so, you must change the associated
CICFG symbol shown in the table.
As shown in the preceding example, group_name is any valid group name for the
user site.
<p class="note"> <b>Note:</b> Remember to add the groups to the GRPLIST for the particular CICS
region. If the groups are not added, they are not installed during each CICS initialization.</p>


==Processing the PCT and PPT==
====Work file procedures====
The JCL library members PCTNTRY and PPTNTRY have the Program Control Table (PCT) and the Program Processing Table (PPT) default values shown in the following code. You can update the CSD by adding to or modifying these default values and then assembling the tables.
You must catalog work file procedures in the CATWRK1 and CATWRK2 jobs for the following jobs that perform translation or assembly:
===PCT: Program Control Table===
The Program Control Table (PCT) assigns user programs to their related CICS transaction identifiers (the transaction codes). Entries are required for both the 3270 full-screen interface and the screen print transaction.


The JCL library member PCTNTRY contains the PCT default values shown in the following code:
<ul>
<p class="code">DFHPCT TYPE=ENTRY,PROGRAM=M204PSFS,TRANSID=M204,TWASIZE=88
<li>CICS jobs</li>
DFHPCT TYPE=ENTRY,PROGRAM=M204PRNT,TRANSID=P204,TWASIZE=88
<li>CDBTASMC, FUNUASMC, MSGUASMC jobs</li>
DFHPCT TYPE=ENTRY,PROGRAM=M204CRPS,TRANSID=U204</p>
</ul>
The CCASTAT and CCASYS files from Model 204 version 7.4 are compatible with Model 204 version 7.<var class="term">r</var>.


The following entry in the PCT is required for all user IFAM2 transactions:
==Building the object and macro sublibrary==
To build the object and macro sublibrary, you must download the object file and macro library and upload each to the mainframe.


<p class="syntax">DFHPCT TYPE=ENTRY,PROGRAM=program_name,TRANSID=xxxx,TWASIZE=88</p>
<div id="downloading"></div>
===Downloading===
<!--Caution: <div> above-->
<ol>
<li>Using your [[Rocket M204 user ID]] and password, log in to the [https://m204.rocketsoftware.com/maint/objlist Model 204 object file download page].</li>
<li>Click the <b>Download object file</b> link beside the object library that you want to download. It contains the CATV7<var class="term">rr</var> (such as CATV770) job stream and is saved on your workstation as M204V7<var class="term">r</var>.OBJ (such as M204V77.OBJ).</li>
<li>Go to the [https://m204.rocketsoftware.com/maint/maclist Model 204 macro library download page].</li>
<li>Click the <b>Download macro library</b> link beside the macro library that you want to download. It contains the M204VSE job stream and is saved on your workstation as M204V7<var class="term">r</var>_VSE.MAC (such as M204V77_VSE.MAC).</li>
</ol>
For details on how to download, see [[Downloading and uploading Model 204 installation components]].


Use the values in the previous table if you are updating the PCT. If you use a transaction ID for a user program that is different from the value shown in that table, you must change the associated CICFG symbol.
Once the object and macro files are downloaded to your workstation, upload them to the z/VSE system on the IBM mainframe.


===PPT: Program Processing Table===
<div id="uploading"></div>
The Program Processing Table (PPT) stores program attributes. Entries are required for the 3270 full-screen interface, direct printer support, and the IFAM2 interface.
====Upload format and size====  
<!--Caution: <div> above-->
You can use any file transfer mechanism to upload the files, including FTP and IND$FILE.  


The JCL library member [[PPTNTRY job stream for IBM z/VSE|PPTNTRY]] contains the PPT default values shown in the following code.
Specify these characteristics for the upload files:
<table class="noBorder">
<tr><td><b>transfer format:</b></td> <td>binary</td></tr>
<tr><td><b>record format:</b></td> <td>FB</td></tr>
<tr><td><b>record size:</b></td> <td>80 for each downloaded file</td></tr>
<tr><td><b>block size:</b></td> <td>6400 for each downloaded file</td></tr>
<tr><td><b>storage size for both:</b></td> <td>primary: 10 CYL; secondary: 5 CYL</td></tr>
</table>


<p class="note"><b>Note:</b> In the first line of the PPT, be sure to set the RES parameter to YES, otherwise, the transaction does not complete successfully.</p>
<div id="populating"></div>


<p class="code">DFHPPT TYPE=ENTRY,PROGRAM=DFHPSF,RES=YES,PGMLANG=ASSEMBLER
===Populating the library===
DFHPPT TYPE=ENTRY,PROGRAM=M204CRPS,PGMLANG=ASSEMBLER
<!--Caution: <div> above-->
DFHPPT TYPE=ENTRY,PROGRAM=M204PRNT,PGMLANG=ASSEMBLER
<ol>
DFHPPT TYPE=ENTRY,PROGRAM=M204PSFS,PGMLANG=ASSEMBLER
<li>Upload the M204V7<var class="term">r</var>.OBJ (such as M204V77.OBJ) file to the POWER RDR queue, CLASS=0, in binary format. This file contains the CATV7<var class="term">rr</var> job stream, which catalogs object and JCL into the Model 204 sublibrary, V7<var class="term">rr</var>.</li>
DFHPPT TYPE=ENTRY,PROGRAM=OBPLTSD,PGMLANG=ASSEMBLER</p>
<li>From the VSE console, release the CATV7<var class="term">rr</var> job stream from the RDR queue (such as <code>r rdr,catv770</code>). At the pause, enter the DLBL statements for your Model 204 library.</li>
<li>Upload the M204V7<var class="term">r</var>_VSE.MAC (such as M204V77_VSE.MAC) file to the POWER RDR queue, CLASS=0, in binary format. This file contains the M204VSE job stream, which catalogs source and macros into the Model 204 sublibrary, V7<var class="term">rr</var>.</li>
<li>From the VSE console, release the M204VSE job stream from the RDR queue (<code>r rdr,m204vse</code>). At the pause, enter the DLBL statements for your Model 204 library.</li>
</ol>
<div id="bldLibs"></div>


==Assembling the CICS Interface modules==
<div id="cics"></div>
Assemble, in the sequence listed, the CICS Interface modules listed in the
assembly step in the CICS installation steps table.


Some assemblies display a warning message (DFHEIMSG 4) because the
==Preparing site-specific FUNU, MSGU, and CDTB modules==
CSA address is release-dependent. If the interface program is running in the
<div id="FUNU_7.5"></div>
release under which it was assembled, ignore the warning.


After the modules are successfully built, relink as directed in "CICS installation steps."
===FUNUASMC, MSGUASMC, and CDTBASMC jobs===
<div id="CICS_alloc"></div>


==Preparing site-specific CDTB, FUNU, and MSGU modules==
If you use translation tables or user-written functions, you must change the source code in the FUNU.A, MSGU.A, and CDTB.A sublibrary members to accommodate the requirements of your site, as shown in the following table.  
===CDTBASMC, FUNUASMC, and MSGUASMC jobs===
If you use translation tables or user-written functions, you must change the source code in the CDTB.A, FUNU.A, and MSGU.A sublibrary members to accommodate the requirements of your site, as shown in the following table.  
<p class="caption">Customizable user modules</p>
<table>
<table>
<th>If you use...</th> <th>Then do this...</th> <th>Using this job</th>
<caption>Customizable user modules</caption>
<tr><td>$CODE and $DECODE functions to encode and decode character strings</td> <td>Edit your own translation tables into the CDTB.A member</td> <td>CDTBASMC</td> </tr>
<tr class="head"><th>If you use...</th> <th>Then do this...</th> <th>Using this job</th></tr>
<tr><td>Your own User Language functions</td> <td>Add them to the FUNU.A member</td> <td>FUNUASMC</td></tr>
 
<tr><td>Error messages with your own User Language functions</td> <td>Modify the MSGU.A member</td> <td>MSGUASMC</td></tr>
<tr><td>Your own User Language functions</td>  
<td>Add them to the FUNU.A member</td>  
<td>FUNUASMC</td></tr>
 
<tr><td>Error messages with your own User Language functions</td>  
<td>Modify the MSGU.A member</td>  
<td>MSGUASMC</td></tr>
 
<tr><td>$CODE and $DECODE functions to encode and decode character strings</td>  
<td>Edit your own translation tables into the CDTB.A member</td>  
<td>CDTBASMC</td> </tr>
</table>
</table>


Line 293: Line 227:
It is recommended that if you think your site will make use of the TCP/IP Sockets Interface for Model 204, link the FUNU.A member during the installation process, even if you have not yet developed your own functions. This ensures access to the $ASCII and $EBCDIC functions.
It is recommended that if you think your site will make use of the TCP/IP Sockets Interface for Model 204, link the FUNU.A member during the installation process, even if you have not yet developed your own functions. This ensures access to the $ASCII and $EBCDIC functions.


===Assembling CDTB, FUNU, and MSGU===
<div id="FUNU_7.5_assemble"></div>
The following table identifies the JCL to assemble CDTB, FUNU, and MSGU and catalog the object decks into the Model 204 sublibrary.
===Assembling FUNU, MSGU, and CDTB===
<p class="caption">JCL library member for user modules</p>
<!--Caution: <div> above-->
The following table identifies the JCL to assemble FUNU, MSGU, and CDTB, and catalog the object decks into the Model 204 sublibrary.
<table>
<table>
<th>Member</th> <th>Assembles and catalogs user modules</th>
<caption>JCL library member for user modules</caption>
<tr><td>CDTBASMC</td> <td>CDTB (code table)</td></tr>
<tr class="head"><th>Member</th> <th>Assembles and catalogs user modules</th></tr>
<tr><td>FUNUASMC</td> <td>FUNU (functions)</td></tr>
<tr><td>FUNUASMC</td> <td>FUNU (functions)</td></tr>
<tr><td>MSGUASMC</td> <td>MSGU (messages)</td></tr>
<tr><td>MSGUASMC</td> <td>MSGU (messages)</td></tr>
<tr><td>CDTBASMC</td> <td>CDTB (code table)</td></tr>
</table>
</table>


Once the modules are assembled and cataloged, link the Model 204 phases to
Once the modules are assembled and cataloged, link the Model 204 phases to contain user code tables and/or user functions, specifying the V7<var class="term">rr</var> sublibrary (which contains the FUNU, MSGU, and CDTB modules) in the search list.
contain user code tables and/or user functions, specifying the M204LIB.Vrrr
sublibrary containing the CDTB, FUNU, and MSGU modules in the search list.
 
The M204LIB.Vrrr sublibrary members LKONLN and LKB204 distributed with
this version contain the INCLUDE statements for CDTB, FUNU, and MSGU.


===Assembly considerations for FUNU and MSGU===
===Assembly considerations for FUNU and MSGU===
Line 371: Line 302:
referencing symbols that are undefined due to an assembler error.
referencing symbols that are undefined due to an assembler error.


<div id="bvp204"></div>
<div id="link_phases"></div>
==Linking the $$BVP204 phase==
<!--Caution: <div> above-->
The following information applies only to z/VSE sites running under z/VM.
 
The $$BVP204 phase is a transient: it is required for the z/VM-directed output
feature, and it is invoked by Model 204 to issue diagnostic instructions in order
to pass CP commands to z/VM. $$BVP204 is used to obtain the CPU ID.
 
Linking $$BVP204 to the system library improves performance.
 
===LINK$BVP SPJCL job===
To link $$BVP204, use the LINK$BVP SPJCL job from the JCL library.
 
This is a required step in a Model 204 installation on z/VSE running under z/VM.
 
===COPYVMPR job===
To copy $$BVP204 to the System Residence Library, use the COPYVMPR job from the JCL library.
 
This is a required step in a Model 204 installation on z/VSE running under z/VM.
 
==Installing terminal access methods and communications features==
This section presents basic steps for installing these terminal access methods
and communications features:
<ul>
<li>Model 204 Virtual Telecommunications Access Method (VTAM) Interface.</li>
<li>Horizon intersystem communication feature, which is required for Connect* support. This feature is provided in a limited edition without encryption. See “Installation considerations.”</li>
<li>Parallel Query Option/204, which enables distributed file processing.</li>
</ul>
===General VTAM installation steps===
The basic steps for installing these features with Model 204 are:
<ol>
<li>Link edit Model 204 with the appropriate object modules after commenting out the INCLUDEs for any features (PQO, Horizon, VTAM) not used at your site.
<p class="note"><b>Note:</b> The installation task list for each feature includes this step; however, you need to link edit Model 204 only once, after you apply the CPU ID zap and apply all available Early Warnings.</p></li>
<li>Complete the Model 204 installation.</li>
</ol>
 
==Installing the VTAM Interface==
Installing Model 204 with VTAM requires defining Model 204 as a VTAM application program. Model 204 provides 3270 support, as well as VTAM support for full-screen terminals that are not 3270-compatible, by providing a mechanism for writing exit routines to convert data outside of the VTAM 3270 interface.
 
Rules governing data conversion exit routine coding are described in [[System management]].
To install the VTAM Interface, perform these steps:
<table>
<th>Step</th> <th>Task</th> <th>Job</th>
<tr><td>1.</td> <td>Make sure that the link job contains INCLUDE LKVTAM.</td> <td>LINKONLN</td></tr>
<tr><td>2.</td> <td>Define Model 204 as a VTAM application node using an
APPL statement in VTMAPPL.B.</td> <td /> </tr>
<tr><td>3.</td> <td>Apply all early warnings and then link edit the Model 204 ONLINE phase.</td> <td>LINKONLN</td></tr>
</table>
 
===Specifying a VTAMNAME===
The network name of the Model 204 run is specified for VTAM in the Model 204 system parameter VTAMNAME. The VTAMNAME parameter in CCAIN is the same as the APPL statement name field.
 
The value of VTAMNAME is a string composed of 1-8 characters. The default is M204. VTAMNAME can be specified by the system manager on the User 0 parameter line.
 
For more information on VTAM parameters, see [[System management]] and [[Commands]].
 
==Installing the Horizon Interface==
The Horizon intersystem communication feature is required for Connect* and TCP/IP support.
 
To install the Horizon Interface, perform these steps:
<table>
<th>Step</th> <th>Task</th> <th>Job</th>
<tr><td>1.</td> <td>Make sure that the link job contains INCLUDE LKHRZN.</td> <td>LINKONLN</td></tr>
<tr><td>2.</td> <td>Apply all early warnings and then link edit the Model 204 ONLINE phase.</td> <td>LINKONLN</td> </tr>
</table>
 
For more information about Horizon, see the <var class="book">Rocket Model 204 Horizon: Intersystem Processing Guide</var>.
 
==Installing Parallel Query Option/204==
Parallel Query Option/204 (PQO) enables distributed file processing.
 
To install PQO, perform these steps:
 
<table>
<th>Step</th> <th>Task</th> <th>Job</th>
<tr><td>1.</td> <td>Make sure that the link job contains INCLUDE LKPQO.</td> <td>LINKONLN</td></tr>
<tr><td>2.</td> <td>Apply all early warnings and then link edit the Model 204 ONLINE phase.</td> <td>LINKONLN</td> </tr>
</table>
 
For more information about PQO, see the <var class="book">Parallel Query Option/204 User’s Guide</var>.
 
==Installing CRAM==
The Cross-Region Access Method (CRAM) lets two or more Model 204 users in two or more partitions communicate with each other.
CRAM is used by:
<ul>
<li>BATCH2</li>
<li>CICS Interface</li>
<li>IFAM2</li>
</ul>
See [[Defining the user environment (CCAIN)]] for more information about CRAM.
 
===Linking the CRAM phases===
To link the CRAM phases (CRAMSWT, CRAMZWT, IGCLM244, and SNAPCRAM), use the [[Model 204 LINKCRAM job stream for IBM z/VSE|LINKCRAM]] job from the JCL library.
 
==Cataloging procedures==
After you have upgraded to Model 204 7.5, you can store some of the more frequently used JCL in the form of cataloged procedures. The jobs to catalog these procedures are distributed in the JCL sublibrary.
To catalog procedures, modify each procedure as follows:
<ul>
<li>Add POWER JCL</li>
<li>Add the appropriate DLBL, EXTENT, and ASSGN information</li>
</ul>
The jobs assume that the M204JCL procedure is in the system library (IJSYSRS.SYSLIB). All other Rocket-supplied procedures are cataloged into the JCL sublibrary. The JCL to catalog frequently used procedures follows. Determine the new file, library volumes, and extents; then modify the procedures before cataloging them.
 
===Procedures that can be cataloged===
As needed, you can modify and catalog the following procedures using the jobs
listed in the following table.
<p class="caption">Jobs for cataloging frequently used procedures</p>
<table>
<th>Procedure name</th> <th>Catalog job</th> <th>Description</th>
<tr><td>M204DECR</td> <td>CATDECR</td> <td>Decryption files</td></tr>
<tr><td>M204MSHP</td> <td>CATMSHP</td> <td>System history file</td></tr>
<tr><td>M204WRK1</td> <td>CATWRK1</td> <td>Work file for decryption, translation, and assembly</td></tr>
<tr><td>M204WRK2</td> <td>CATWRK2</td> <td>Work file for decryption, translation, and assembly</td></tr>
<tr><td>M204SYS</td> <td>CATSYS</td> <td>System files (CCASYS, CCASTAT, CCATEMP)</td></tr>
<tr><td>M204DD</td> <td>DDINST, DDRINST</td> <td>Dictionary/204 files</td></tr>
</table>
====Cataloging procedures for end-user products====
For end-user products, such as Dictionary/204, you catalog the procedure that contains file information specific to that product as part of the installation procedure. <br />For example, the M204DD procedure, which contains file information about Dictionary/204, is cataloged in the DDINST job.


==Link editing the Model 204 phases==
==Link editing the Model 204 phases==
 
<!--Caution: <div> above-->
You must link all required phases and any optional phases that you want to use,
You must link all required phases and any optional phases that you want to use,
including utilities and sort exits.
including utilities and sort exits.


When applying maintenance (Early Warnings), you must link or relink the phase affected by the Early Warning.
To link any of the Model 204 phases, run the job listed for that phase in the following table. This table also lists utilities you might need and the jobs used to link or relink them.  


To link any of the Model 204 phases, run the job listed for that phase in the following table. This table also lists utilities you might need and the jobs used to link or relink them.
Most of the utility phases from Model 204 version 7.4 will continue to perform correctly when used with Model 204 version 7.<var class="term">r</var>. Phases that you must relink for 7.<var class="term">r</var> are listed as Required in the following table.
<table>
<caption>Executable phases and jobs used for linking or relinking</caption>
<tr class="head"><th>Phase or utility</th>
<th>Required / Optional</th>
<th>Purpose / Notes</th>
<th>Job</th>
<th>For more details, see ...</th></tr>


Phases listed as Optional might be needed at your site depending on your
<tr><td>$$BVP204</td> <td>Required (for z/VSE under z/VM)</td> <td>z/VM-directed output logical transient. Required on z/VSE
installation requirements.
<p class="caption">Executable phases and jobs used for linking or relinking</p>
<table>
<th>Phase or utility</th>
<th>Purpose / Notes</th> <th>Job</th> <th>For more details, see ...</th>
<tr><td>$$BVP204</td> <td>z/VM-directed output logical transient. Required on z/VSE
systems running under z/VM.</td> <td>LINK$BVP</td> <td>[[#Linking the $$BVP204 phase|Linking the $$BVP204 phase]]</td></tr>
systems running under z/VM.</td> <td>LINK$BVP</td> <td>[[#Linking the $$BVP204 phase|Linking the $$BVP204 phase]]</td></tr>


<tr><td>ALLOCATE</td> <td>Initializes Model 204 database files
<tr><td>ALLOCATE</td> <td>Required</td> <td>Initializes Model 204 database files
<p>Required for Installation JCL, Dictionary/204, and SQL installation</p></td> <td>LINKALOC</td> <td>[[ALLOCATE utility in z/VSE]]</td></tr>
<p>Required for Installation JCL, SQL installation, and Dictionary/204</p></td> <td>LINKALOC</td> <td>[[ALLOCATE utility in z/VSE]]</td></tr>


<tr><td>AUDIT204</td> <td>Generates an audit trail for printing out later, and produces statistical
<tr><td>AUDIT204</td> <td>Required</td> <td>Generates an audit trail for printing out later, and produces statistical
reports and analysis</td> <td>
reports and analysis</td> <td>
LINKAUDT</td> <td>[[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#AUDIT204 utility|AUDIT204 utility]]</td></tr>
LINKAUDT</td> <td>[[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#AUDIT204 utility|AUDIT204 utility]]</td></tr>


<tr><td>BATCH2</td> <td><p>Establishes a User Language connection to a Model 204 ONLINE running in a separate region</p>
<tr><td>BATCH2</td> <td>Optional</td> <td><p>Establishes a User Language connection to a Model 204 ONLINE running in a separate region</p>
Optional; recommended for CRAM testing.</td> <td>
Optional; recommended for CRAM testing.</td> <td>
LINKBAT2</td> <td>[[BATCH2 (TCP/IP)]]</td></tr>
LINKBAT2</td> <td>[[BATCH2 (TCP/IP)]]</td></tr>


<tr><td>BATCH204</td> <td><p>Handles a single user in batch mode</p> <p>Required to complete installation</p>
<tr><td>BATCH204</td> <td>Required</td> <td><p>Handles a single user in batch mode</p> <p>Required to complete installation</p>
Link or relink when:
<ul>
<ul>
<li>Applying a CPU ID zap</li>
<li>Installing user modules FUNU, MSGU, CDTB</li>
<li>Installing user modules CDTB,
<li>Installing or upgrading to a new release of Model 204</li>
FUNU, MSGU</li>
<li>Moving to a different release of CICS (M204 CICS Interface)</li>
<li>Installing a new release of
Model 204</li>
<li>Moving to a different release of
CICS (M204 CICS Interface)</li>
</ul></td><td>LINKB204</td> <td>[[#Linking the BATCH204 phase|Linking the BATCH204 phase]]</tr>
</ul></td><td>LINKB204</td> <td>[[#Linking the BATCH204 phase|Linking the BATCH204 phase]]</tr>


<tr><td>
<tr><td>
CRAMSWT</td> <td>CRAM non-master subtask</td> <td>LINKCRAM</td> <td>[[#Installing CRAM|Installing CRAM]]</td></tr>
CRAMSWT</td> <td>Optional</td> <td>CRAM non-master subtask</td> <td>LINKCRAM</td> <td>[[#Linking the CRAM phases|Linking the CRAM phases]]</td></tr>


<tr><td>
<tr><td>
CRAMZWT</td> <td>CRAM master subtask</td> <td>LINKCRAM</td> <td>[[#Installing CRAM|Installing CRAM]]</td></tr>
CRAMZWT</td> <td>Optional</td> <td>CRAM master subtask</td> <td>LINKCRAM</td> <td>[[#Linking the CRAM phases|Linking the CRAM phases]]</td></tr>


<tr><td>
<tr><td>
DFHPSF</td> <td>CICS/IFAM2 Interface</td> <td>PSFASM</td> <td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>
DFHPSF</td> <td>Optional</td> <td>CICS/IFAM2 Interface</td> <td>PSFASM</td> <td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>


<tr><td>
<tr><td>
HASH15</td> <td>Sort exit for M204HASH</td> <td>LINKHA15</td> <td>[[Hash key files#Using M204HASH in the z/VSE environment|Using M204HASH in the z/VSE environment]]</td></tr>
HASH15</td> <td>Optional</td> <td>Sort exit for M204HASH</td> <td>LINKHA15</td> <td>[[Hash key files#Using M204HASH in the z/VSE environment|Using M204HASH in the z/VSE environment]]</td></tr>


<tr><td>
<tr><td>
IFAM1</td> <td>Host Language Interface single-thread configuration
IFAM1</td> <td>Optional</td> <td>Host Language Interface single-thread configuration
<p>Link or relink when:</p>
<p>Link or relink when installing or upgrading to a new release of Model 204. (You can ignore UNRESOLVED ADCON
<ul>
messages.)</p></td>  
<li>Applying a CPU ID zap</li>
<td>LINKIFM1</td> <td>[[Using HLI and batch configurations#IFAM1|IFAM1]]</td></tr>
<li>Installing a new release of
Model 204 (You can ignore
UNRESOLVED ADCON
messages.)</li>
</ul></td> <td>LINKIFM1</td> <td>[[Using HLI and batch configurations#IFAM1|IFAM1]]</td></tr>


<tr><td>
<tr><td>
IGCLM244</td><td>CRAM load module</td><td>LINKCRAM</td><td>[[#Installing CRAM|Installing CRAM]]</td></tr>
IGCLM244</td> <td>Optional</td> <td>CRAM load module</td><td>LINKCRAM</td><td>[[#Linking the CRAM phases|Linking the CRAM phases]]</td></tr>


<tr><td>
<tr><td>
LISTDOS</td><td>Dictionary/204 Cross-Reference
M204CRPS</td> <td>Optional</td> <td>CICS full-screen printer routine</td><td>CRPSASM</td><td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>
Required only for the Dictionary/204
Cross Reference utility</td><td>LINKXREF</td><td>“Installing the Cross-Reference
facility” on page 75</td></tr>


<tr><td>
<tr><td>
M204CRPS</td><td>CICS full-screen printer routine</td><td>CRPSASM</td><td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>
M204L</td> <td>Optional</td> <td>Loads a Model 204 phase above the line</td><td>LINKMLOD</td><td>[[#Link editing the M204L phase|Link editing the M204L phase]]</td></tr>


<tr><td>
<tr><td>
M204PRNT</td><td>CICS 3270 print routine</td><td>PRNTASMC</td><td>“CICS IFAM2 applications” on
M204PRNT</td> <td>Optional</td> <td>CICS 3270 print routine</td><td>PRNTASMC</td><td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>
page 31</td></tr>


<tr><td>
<tr><td>
M204PSFS</td><td>CICS full-screen remote User Language interface routine</td><td>PSFSASM</td><td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>
M204PSFS</td> <td>Optional</td> <td>CICS full-screen remote User Language interface routine</td><td>PSFSASM</td><td>[[#Updating the CICS System Definition (CSD)|Updating the CICS System Definition (CSD)]]</td></tr>
<tr><td>
 
MERGEJ</td><td>Media recovery journal merge utility</td><td>LINKMRGJ</td><td>[[System and media recovery#Using the MERGEJ utility|Using the MERGEJ utility]]</td></tr>
<tr><td>MERGEJ</td> <td>Required</td> <td>Media recovery journal merge utility</td><td>LINKMRGJ</td><td>[[System and media recovery#Using the MERGEJ utility|Using the MERGEJ utility]]</td></tr>


<tr><td>
<tr><td>OI15</td> <td>Optional</td> <td>File Load utility sort exits</td><td>LINKOI15</td><td>[[Deferred update feature]]</td></tr>
OI15</td><td>File Load utility sort exits</td><td>LINKOI15</td><td>[[Deferred update feature]]</td></tr>


<tr><td>OI35</td><td>File Load utility sort exits</td><td>LINKOI35</td><td>[[Deferred update feature]]</td></tr>
<tr><td>OI35</td> <td>Optional</td> <td>File Load utility sort exits</td><td>LINKOI35</td><td>[[Deferred update feature]]</td></tr>


<tr><td>ONLINE</td><td>Link online; Required.
<tr><td>ONLINE</td><td>Required</td> <td>Link online.
<p>Link or relink when:</p>
<p>Link or relink when:</p>
<ul><li>Installing VTAM, Horizon, or
<ul>
Parallel Query Option/204</li>
<li>Installing user modules FUNU, MSGU, CDTB</li>
<li>Applying a CPU ID zap</li>
<li>Installing or upgrading to a new release of Model 204</li>
<li>Installing user modules CDTB, FUNU, MSGU</li>
<li>Installing a new release of Model 204</li>
<li>Moving to a different release of
<li>Moving to a different release of
CICS (M204 CICS Interface)</li></ul></td><td>LINKONLN</td><td>[[#Linking the ONLINE phase|Linking the ONLINE phase]]</td></tr>
CICS (M204 CICS Interface)</li></ul></td>
 
<td>LINKONLN</td><td>[[#Linking the ONLINE phase|Linking the ONLINE phase]]</td></tr>
<tr><td>
SNAPCRAM</td><td>CRAM control block SNAP dump
routine</td><td>LINKCRAM</td><td>[[#Installing CRAM|Installing CRAM]]</td></tr>
 
<tr><td>UTILC</td><td>Prints the Model 204 checkpoint file</td><td>LINKUTLC</td><td>[[Checkpoints: Storing before-images of changed pages#Obtaining checkpoint information (UTILC)|Obtaining checkpoint information (UTILC)]]</td></tr>


<tr><td>UTILJ</td><td>Prints and copies Model 204 journal files</td><td>LINKUTLJ</td><td>[[System and media recovery#Using the UTILJ utility|Using the UTILJ utility]]</td></tr>
<tr><td>SNAPCRAM</td> <td>Optional</td> <td>CRAM control block SNAP dump
routine</td><td>LINKCRAM</td><td>[[#Linking the CRAM phases|Linking the CRAM phases]]</td></tr>


<tr><td>UTLA</td><td>Prints the Model 204 audit trail</td><td>LINKUTLA</td><td>[[Tracking_system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#z/VSE and the audit trail|z/VSE and the audit trail]]</td></tr>
<tr><td>UTILC</td> <td>Required</td> <td>Prints the Model 204 checkpoint file</td><td>LINKUTLC</td><td>[[Checkpoints: Storing before-images of changed pages#Obtaining checkpoint information (UTILC)|Obtaining checkpoint information (UTILC)]]</td></tr>


<tr><td>XDECDOS</td><td><p>Decryption utility</p>
<tr><td>UTILJ</td> <td>Required</td> <td>Prints and copies Model 204 journal files</td><td>LINKUTLJ</td><td>[[System and media recovery#Using the UTILJ utility|Using the UTILJ utility]]</td></tr>
Required only if you purchased special features that require decryption</td><td>LINKXDEC</td><td>“Errr sublibrary” on page 12, “CATDECR job” on page 18</td></tr>


<tr><td>XREFDOS</td><td>Dictionary/204 Cross-reference facility<p>Required only for the Dictionary/204 Cross Reference utility</p></td><td>LINKXREF</td><td>“Installing the Cross-Reference facility” on page 75 which describes how to define the D<var class="term">rrr</var> sublibrary before running the LINKXREF job.</td></tr>
<tr><td>UTLA</td> <td>Optional</td> <td>Prints the Model 204 audit trail</td><td>LINKUTLA</td><td>[[Tracking_system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#z/VSE and the audit trail|z/VSE and the audit trail]]</td></tr>


<tr><td>ZBLDTAB</td><td>Initializes the Model 204 password table. Required to allocate and
<tr><td>ZBLDTAB</td> <td>Optional</td> <td>Initializes the Model 204 password table. Required to allocate and
initialize CCASTAT.</td><td>LINKZBTB</td><td>[[Storing security information (CCASTAT)]]</td></tr>
initialize CCASTAT.</td><td>LINKZBTB</td><td>[[Storing security information (CCASTAT)]]</td></tr>


<tr><td>ZCTLTAB</td><td>Convert CCASTAT for the Password Expiration feature. Required to convert an existing CCASTAT data set to allow data control of passwords.</td><td>LINKZCTB</td><td>[[Storing security information (CCASTAT)]]</td></tr>
<tr><td>ZCTLTAB</td> <td>Optional</td> <td>Convert CCASTAT for the Password Expiration feature. Required to convert an existing CCASTAT data set to allow data control of passwords.</td><td>LINKZCTB</td><td>[[Storing security information (CCASTAT)]]</td></tr>
</table>
</table>


===Linking the ONLINE phase===
===Linking the ONLINE phase===
LINKONLN is the JCL member for linking the ONLINE phase and contains INCLUDE statements for a base loadlist and for each feature, as shown in the following table.  
[[Model 204 LINKONLN job stream for IBM z/VSE|LINKONLN]] is the JCL member for linking the ONLINE phase and contains INCLUDE statements for the Model 204 core and all features. Uncomment the features that you are going to use.  
<p class="caption">Loadlists for ONLINE and features</p>


<table>
Because the features for CICS do not affect the ONLINE phase, there are no INCLUDE statements for CICS.
<th>Loadlist</th> <th>ONLINE or feature</th>
<tr><td>LKHRZN</td> <td>Horizon</td></tr>
<tr><td>LKONLN</td> <td>Modules common across all features</td></tr>
<tr><td>LKPQO</td> <td>Parallel Query Option/204</td></tr>
<tr><td>LKVTAM</td> <td>VTAM</td></tr>
</table>
Because the features for CICS do not affect the ONLINE phase, no specific loadlists are necessary for this feature. The [[Model 204 LINKONLN job stream for IBM z/VSE|sample LINKONLN JCL]] is prepared to link ONLINE with Horizon and VTAM.


===Linking the IFAM1 phase===
===Linking the IFAM1 phase===
LINKIFM1 is the JCL member for linking the IFAM1 phase and contains
LINKIFM1 is the JCL member for linking the IFAM1 phase and contains an INCLUDE statement for the Model 204 core.
INCLUDE statements for a base loadlist as shown in the following table.  
 
The following sample LINKIFM1 JCL is used to link IFAM1.
{{Template:VSE_LINKIFM1}}
 
===Linking the BATCH204 phase===
LINKB204 is the JCL member for linking the BATCH204 phase and contains
an INCLUDE statement for the Model 204 core and all features. Uncomment the features that you are going to use.
 
The EVCP module is a subset of the RSQL module.  The code in EVCP contains code to process complex pattern matching.  The code in RSQL contains the modules in EVCP along with the modules to support the SQL engine. 
To link an ONLINE with RSQL and not EVCP, uncomment the following line in the JCL:
 
<p class="code">* INCLUDE LKSQLONL  /* Uncomment for Remote SQL and Pattern</p>
 
To link an ONLINE with EVCP instead of RSQL, uncomment the following line:
 
<p class="code">* INCLUDE LKNOSONL  /* Uncomment for Pattern Matcher</p>
 
The following sample LINKB204 JCL is used to link BATCH204.
 
====LINKB204 JCL example====
{{Template:VSE_LINKB204}}
 
===Link editing the M204L phase===
To run above the line (in 31-bit addressing space), you need to link the M204L program, which acts as an intermediary to load Model 204 phases above the line.
 
In the PARM clause of the EXEC statement, indicate the Model 204 load module that M204L will load above the line.  


<p class="caption">Loadlists for IFAM1 and features</p>
In the following example, ONLINE will be loaded above the line and then invoked:
<table>
<th>Loadlist</th> <th>IFAM1 or feature</th>
<tr><td>LKIFM1</td> <td>IFAM1</td></tr>
</table>


The sample LINKIFM1 JCL is prepared to link IFAM1.
<code>// EXEC M204L,SIZE=AUTO,PARM='ONLINE'</code>


<p class="syntax"><nowiki>LINKIFM1 JCL example
The following sample LINKMLOD JCL is used to link M204L.  
// EXEC PROC=M204JCL DLBL for JCL sublibrary
{{Template:VSE_LINKMLOD}}
// LIBDEF PROC,SEARCH=M204LIB.Vrrr
// EXEC PROC=M204Vrrr DLBL for Vrrr M204 library
// LIBDEF PHASE,CATALOG=M204LIB.Vrrr
// LIBDEF OBJ,SEARCH=M204LIB.Vrrr
// OPTION CATAL
PHASE IFAM1,* REPLACE=YES
INCLUDE LKIFM1
ENTRY IFII1
/*
// EXEC LNKEDT
/*
/&
</nowiki></p>
where <var class="term">rrr</var> is the release level, such as 750.


Linking the BATCH204 phase
===Linking the CRAM phases===
LINKB204 is the JCL member for linking the BATCH204 phase and contains
The Cross-Region Access Method (CRAM) lets two or more Model 204 users in two or more partitions communicate with each other.
INCLUDE statements for a base loadlist, as shown in the following table.
CRAM is used by:
<ul>
<li>BATCH2</li>
<li>CICS Interface</li>
<li>IFAM2</li>
</ul>
See [[Defining the user environment (CCAIN)#CRAM (IODEV=11, 23, 29)|CRAM (IODEV=11, 23, 29)]] for more information about CRAM.
 
To link the CRAM phases (CRAMSWT, CRAMZWT, IGCLM244, and SNAPCRAM), use the [[Model 204 LINKCRAM job stream for IBM z/VSE|LINKCRAM]] job from the J7<var class="term">rr</var> sublibrary.


<p class="caption">Loadlists for BATCH204 and features</p>
===Linking the Model 204 utility phases===
Most of the utility phases from Model 204 version 7.4 will continue to perform correctly when used with Model 204 version 7.<var class="term">r</var>.
However, you must use the 7.<var class="term">r</var> version of the following utilities, which are sensitive to the Model 204 journal and checkpoint format.
The link jobs are available in the J7<var class="term">rr</var> sublibrary.
<table>
<table>
<th>Loadlist</th> <th>BATCH204 or feature</th>
<tr class="head"><th>Utility</th><th>Description</th><th>Link job</th></tr>
<tr><td>LKBTCH</td> <td>BATCH204</td></tr>
<tr><td><b>[[ALLOCATE utility in z/VSE|ALLOCATE]]</b></td> <td>Initialize Model 204 database files</td> <td>LINKALOC</td></tr>
<tr><td><b>[[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#AUDIT204_utility|AUDIT204]]</b></td> <td>Extract from journal, with report stats and analysis</td> <td>LINKAUDT</td></tr>
<tr><td><b>[[System and media recovery#Using the MERGEJ utility|MERGEJ]]</b></td> <td>Merge concurrent journal streams</td><td>LINKMRGJ</td></tr>
<tr><td><b>[[Checkpoints: Storing before-images of changed pages#Obtaining checkpoint information (UTILC)|UTILC]]</b></td> <td>Information from checkpoint stream</td><td>LINKUTLC</td></tr>
<tr><td><b>[[System and media recovery#Using the UTILJ utility|UTILJ]]</b></td> <td>Information from journal stream; add EOF markers</td><td>LINKUTLJ</td></tr>
</table>
</table>
The following sample LINKB204 JCL is prepared to link BATCH204.
====LINKB204 JCL example====
<p class="syntax"><nowiki>// EXEC PROC=M204JCL DLBL for JCL sublibrary
// LIBDEF PROC,SEARCH=M204LIB.Vrrr
// EXEC PROC=M204Vrrr DLBL for Vrrr M204 library
// LIBDEF PHASE,CATALOG=M204LIB.Vrrr
// LIBDEF OBJ,SEARCH=M204LIB.Vrrr
// OPTION CATAL
PHASE BATCH204,* REPLACE=YES
INCLUDE LKBTCH
ENTRY MAINTASK
/*
// EXEC LNKEDT
/*
/&
</nowiki></p>
where <var class="term">rrr</var> is the release level, such as 750.


===Link editing messages===
===Link editing messages===
Line 689: Line 480:
2158I NO CSECT LENGTH SUPPLIED</p>
2158I NO CSECT LENGTH SUPPLIED</p>


These messages result from the linkage editor flagging any duplicate CSECT as an error in a new release of system software. If the message reads exactly as above, you can ignore it. If, however, the error message displays anything
These messages result from the linkage editor flagging any duplicate CSECT as an error in a new release of system software. If the message reads exactly as above, you can ignore it. However, if the error message displays anything
other than COPR, contact Technical Support.
other than COPR, [[Contacting Rocket Software Technical Support|contact Technical Support]].


Also, you will typically see Unresolved External warnings for the following references, which you may ignore: FORTRAN modules such as DTRNH, DSQRT, and so on.
Also, you will typically see Unresolved External warnings for the following references, which you may ignore: FORTRAN modules such as DTRNH, DSQRT, and so on.


==Creating password and file group data sets==
==CICS interface installation==
Before running ONLINE, BATCH204, or IFAM1 programs, prepare the
The Model 204 CICS interface allows CICS complete access to Model 204 facilities and supports CICS pseudo conversational programs.
following files:
<p class="note"><b>Note:</b> It is not necessary to install the CICS interface if it has been installed for a previous version of Model 204. The phases from the older version are compatible with version 7.<var class="term">r</var> of Model 204.</p>
 
===Requirements===
<ul>
<li>CICS Transaction Server support
<p>Rocket M204 supports the CICS Transaction Server versions 3.1, 3.2, 4.1, and 4.2.</p></li>
<li>Supporting TPROCESS COBOL applications
<p>If your CICS TPROCESS application was originally linked with AMODE=24, you must relink the CICS TPROCESS application specifying AMODE=31 because AMODE=24 is not supported.</p></li>
</ul>
 
===CICS interface overview===
For an overview of the CICS interface, including storage requirements and a listing of CICS interface components, see [[CICS interface configuration#Overview of the CICS Interface|Overview of the CICS Interface]].
===<b id="cics_install"></b>Installing the CICS interface===
<ol>
<li>Customize the interface by editing the CICFG copy member and replacing it in the distribution library as CICFG.A. Then proceed with the CICSASM and CICSLINK jobs.
<p>
For information on customizations needed for using the CICS Standard Mapping Service, see [[CICS interface configuration]].</p></li>
<li>Update the CICS System Definition (CSD) using one of the following methods:
<ul>
<li>Resource Definition Online (CEDA).</li>
<li>The IBM DFHSCDUP offline utility, to process the definitions in batch.</li>
<li>Processing the CICS Program Control Table (PCT) and Program Processing Table (PPT).</li>
</ul></li>


<li>Assemble, translate, and catalog the Model 204 CICS Interface modules, using the following jobs:
  <ul>
  <li>[[Model 204 CRPSASM job stream for IBM z/VSE|CRPSASM]]</li>
  <li>[[Model 204 ENTPSASM job stream for IBM z/VSE|ENTPSASM]]</li>
  <li>[[Model 204 OPLTASMC job stream for IBM z/VSE|OPLTASMC]]</li>
  <li>[[Model 204 PPCIASM job stream for IBM z/VSE|PPCIASM]]</li>
  <li>[[Model 204 PRNTASMC job stream for IBM z/VSE|PRNTASMC]]</li>
  <li>[[Model 204 PSFASM job stream for IBM z/VSE|PSFASM]]</li>
  <li>[[Model 204 PSFSASM job stream for IBM z/VSE|PSFSASM]]</li>
  </ul></li>
<li>Relink the IFAM2 transactions requiring pseudo conversational support with IFENTPS.</li>
<li>Relink all user process-to-process partners with IFPPCI.</li>
</ol>
===Updating the CICS System Definition (CSD)===
You can update the CSD by using CEDA, by using the DFHCSDUP utility, or by processing the CICS Program Control Table (PCT). Use the values in the following table, where appropriate, for the method you choose. Information about
using CEDA follows the table.
<table>
<table>
<th>File</th> <th>Type of data set</th>
<caption>CICS System Definition values</caption>
<tr><td>CCAGRP</td> <td>File group data set (required for file groups)</td></tr>
<tr class="head"><th>User program</th> <th>Program name</th> <th>Transaction ID</th> <th>Modifiable <br>CICFG symbol</th>
<tr><td>CCASTAT</td> <td>Password data set (required)</td></tr>
<th>TWA size</th></tr>
<tr><td>CCATEMP</td> <td>Scratch data set (required). See [[#Allocating CCATEMP|Allocating CCATEMP]] for information about the scratch data set.</td></tr>
 
<tr><td>IFAM2 pseudo conversational</td> <td>DFHPSF</td> <td>DFHPSF is accessed by using a CICS LINK. <br />It is never
invoked with a transaction ID from a terminal.</td> <td>N/A</td> <td>N/A</td><tr>
<tr><td>Full-screen interface</td> <td>M204PSFS</td> <td>M204</td> <td>&TRN</td> <td>88</td></tr>
<tr><td>Screen copy transaction</td> <td>M204CRPS</td> <td>U204</td> <td>N/A</td> <td>N/A</td></tr>
<tr><td>Screen print transaction</td> <td>M204PRNT</td> <td>P204</td> <td>&COP</td> <td>88</td></tr>
</table>
</table>
===CCAGRP—Using permanent file groups===
Before you can define permanent file groups in Model 204, you must allocate and initialize the CCAGRP file. See the Model 204 documentation wiki for information about [[Storing and using file group definitions (CCAGRP)]].


====ALOCGRUP job====
CEDA (the Resource Definition Online transaction) or the DFHCSDUP utility defines the transactions and programs to the CSD file.
Follow these steps to name and size the CCAGRP file:
<ol>
If you are not using tables, then define the transactions and programs by using CEDA
<li>Allocate CCAGRP with the ALOCGRUP job.</li>
and the values in the previous table, as in the following example:
<li>Modify the ONLINE, BATCH204, and IFAM1 JCL streams.</li>
<p class="syntax">CEDA DEFine PROG(program_name)
<li>Issue the CREATEG command to initialize CCAGRP.</li>
  GRoup(group_name)
</ol>
  LANGuage(ASSEMBLER)
  RELoad(NO)
  RESident(NO) (Except for DFHPSF, RESident(YES))
  STatus(ENABLED)
CEDA DEFine TRANsaction(trans_ID)
  GRoup(group_name)
  PROgram(program_name)
  TWASIZE(twa_size_value)
  .
  .
  .
CEDA CHeck GRoup(group_name)
CEDA INstall GRoup(group_name)
</p>
You can use a transaction ID for a user program that is different from the value
shown in the previous table. However, if you do so, you must change the associated
CICFG symbol shown in the table.
As shown in the preceding example, group_name is any valid group name for the
user site.
<p class="note"> <b>Note:</b> Remember to add the groups to the GRPLIST for the particular CICS
region. If the groups are not added, they are not installed during each CICS initialization.</p>
 
===Processing the PCT and PPT===
The JCL sublibrary members PCTNTRY and PPTNTRY have the Program Control Table (PCT) and the Program Processing Table (PPT) default values shown in the following sections. You can update the CSD by adding to or modifying these default values and then assembling the tables.
 
====PCT: Program Control Table====
The Program Control Table (PCT) assigns user programs to their related CICS transaction identifiers (the transaction codes). Entries are required for both the 3270 full-screen interface and the screen print transaction.
 
The JCL sublibrary member, PCTNTRY, contains the PCT default values shown in the following code:
<p class="code">DFHPCT TYPE=ENTRY,PROGRAM=M204PSFS,TRANSID=M204,TWASIZE=88
DFHPCT TYPE=ENTRY,PROGRAM=M204PRNT,TRANSID=P204,TWASIZE=88
DFHPCT TYPE=ENTRY,PROGRAM=M204CRPS,TRANSID=U204</p>
 
The following entry in the PCT is required for all user IFAM2 transactions:
 
<p class="syntax">DFHPCT TYPE=ENTRY,PROGRAM=program_name,TRANSID=xxxx,TWASIZE=88</p>
 
Use the values in the previous table if you are updating the PCT. If you use a transaction ID for a user program that is different from the value shown in that table, you must change the associated CICFG symbol.
 
====PPT: Program Processing Table====
The Program Processing Table (PPT) stores program attributes. Entries are required for the 3270 full-screen interface, direct printer support, and the IFAM2 interface.
 
The JCL sublibrary member, [[PPTNTRY job stream for IBM z/VSE|PPTNTRY]], contains the PPT default values shown in the following code.
 
<p class="note"><b>Note:</b> In the first line of the PPT, be sure to set the RES parameter to YES; otherwise, the transaction does not complete successfully.</p>
 
<p class="code">DFHPPT TYPE=ENTRY,PROGRAM=DFHPSF,RES=YES,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=M204CRPS,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=M204PRNT,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=M204PSFS,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=OBPLTSD,PGMLANG=ASSEMBLER</p>
 
===Assembling the CICS Interface modules===
Assemble, in the sequence listed, the CICS Interface modules listed in the
assembly step in the [[#cics_install|CICS interface installation]] section.
 
Some assemblies display a warning message (DFHEIMSG 4) because the
CSA address is release-dependent. If the interface program is running in the
release under which it was assembled, ignore the warning.
 
After the modules are successfully built, relink as directed in the [[#cics_install|CICS interface installation]] section.
 
==<b id="bvp204"></b>Linking the $$BVP204 phase==
<p class="note"><b>Notes:</b> Information about linking $$BVP204 applies only to z/VSE sites running under z/VM. <br />
It is not necessary to link the $$BVP204 phase if it has been installed for a previous version of Model 204. The phases from the older version are compatible with version 7.<var class="term">r</var> of Model&nbsp;204.</p>
 
The $$BVP204 phase is a transient: it is required for the z/VM-directed output
feature, and it is invoked by Model 204 to issue diagnostic instructions in order
to pass CP commands to z/VM.  
 
Linking $$BVP204 to the system library improves performance.
 
===LINK$BVP job===
To link $$BVP204, use the LINK$BVP job from the J7<var class="term">rr</var> sublibrary.
 
This is a required step in a Model 204 installation on z/VSE running under z/VM.
 
===COPYVMPR job===
To copy $$BVP204 to the System Residence Library, use the COPYVMPR job from the J7<var class="term">rr</var> sublibrary.


===CCASTAT—Building the Model 204 password table===
This is a required step in a Model 204 installation on z/VSE running under z/VM.
If your site intends to use Model 204 security features, you must build the password table in the [[Storing security information (CCASTAT)|CCASTAT]] file. To access CCASTAT, modify the ONLINE, BATCH204, and IFAM1 JCL streams.
====ZBTBRUN job====
Follow these steps to build the password table by creating CCASTAT:
<ol>
<li>Allocate and initialize the CCASTAT file by running the ZBTBRUN job, which executes the ZBLDTAB utility program. The amount of disk storage allocated must be sufficient to contain:
<ul>
<li>Two Model 204 pages (each page is 6184 bytes) for CKD devices.</li>
<li>Minimum allocation of 26 blocks for FBA devices.</li>
</ul>
<li>ZBTBRUN does not usually produce a return code. Look at the listing for any indication of a problem.</li>
<li>Modify ONLINE, BATCH204, and IFAM1 JCL streams. When executing the ONLINE, BATCH204, or user-written IFAM1 program that uses this security file, add this label information in the execution JCL
stream:
<p class="syntax"><nowiki>// DLBL CCASTAT,'M204.CCASTAT',0,SD
// EXTENT SYSnnn,volser,,,start,length
</nowiki></p>
</ol>


====Updating the password table====
==<b id="softspy"></b>Installing SoftSpy==
You must provide the full CCASTAT file information for the execution of ONLINE or BATCH204 if you plan to update the password table with the LOGCTL command. When you update the password table, Model 204 opens the file as an output data set and completely rewrites it. It is suggested that you set the [[Storing security information (CCASTAT)#z/VSE security considerations|retention period]] for the CCASTAT data set at zero to avoid operator intervention.
See the [[SoftSpy installation guide]] for instructions on installing SoftSpy version 7.<var class="term">r</var>.


====Activating security====
==Verifying Model 204 on your system==
In addition, to activate the security facilities of Model 204, turn on UPSI switch 3 (SYSOPT=16):
To perform an initial verification that your installation of Model&nbsp;204 was successful, issue the following commands from the Model 204 command line.
<p class="syntax">// UPSI <span class="term">xxx</span>1<span class="term">xxxx</span></p>
<table>
You can [[Storing security information (CCASTAT)#Password table maintenance|use the LOGCTL command to create entries]] in the password table.
<tr class="head"><th>Command</th> <th>You should see...</th></tr>


===Creating a Password Expiration CCASTAT===
<tr><td>ROCKET</td>
If your site would like to use the optional security feature that allows date control of passwords, you must convert an existing CCASTAT data set. This conversion may be run at any time and is irreversible.
<td>A list of authorized Model 204 products (including 7.<var class="term">r</var>) currently on your system.</td></tr>
<p class="note"><b>Note:</b> It is strongly recommended that you save a copy of the original CCASTAT file before converting it.</p>
(If you need to create a CCASTAT file, consult the wiki topic on [[Storing security information (CCASTAT)|CCASTAT]].)


====Running the ZCTBRUN job====
<tr><td>DISPLAY ZAPS</td>  
Follow these steps to convert a CCASTAT data set using the ZCTLTAB utility.
<td>A list of Model 204 zaps (including 7.<var class="term">r</var> zaps) on your system.</td></tr>
<ol>
<li>Read the [[Storing security information (CCASTAT)#Understanding the ZCTLTAB utility|description of ZCTLTAB options]], and read the comments found in the job ZCTBRUN.</li>
<li>Save a copy of the original, unconverted CCASTAT file.</li>
<li>Modify job ZCTBRUN as needed and run it. This will run ZCTLTAB to convert the CCASTAT data set.</li>
</ol>


==Allocating CCATEMP==
<tr><td>DICTADMIN</td>
CCATEMP is a required data set used by Model 204 as the system scratch file.
<td>The Dictionary Administration subsystem, displaying <code>Release 7.<var class="term">r</var></code> on its menu screens.</td></tr>


Allocate CCATEMP before running jobs that execute an ONLINE, BATCH204, or IFAM1 program.
<tr><td>SUBSYSMGMT</td>
<td>The Application Subsystem facility, displaying <code>VER <var class="term">V</var> REL <var class="term">R</var></code> on its menu screens.</td></tr>
</table>


<ol>
==Dictionary/204 installation==
<li>Calculate the size of CCATEMP:
For details on installing Dictionary/204, see the [[Dictionary/204_installation_guide|Dictionary/204 installation guide]].
<p>Allocate a minimum of 25 pages per user if your site uses file groups, otherwise
==See also==
allocate 20 pages per user.</p></li>
<ul>
<li>Allocate CCATEMP with the ALOCTEMP job.</li>
<li>[[Model 204 installation on IBM z/OS]]</li>
</ol>
</ul>


<div id="softspy"></div>
==Additional information==
==Upgrading SoftSpy for 7.5==
Refer to the <var class="book">[[Media:M204_InstallzVSE_V74.pdf|Rocket Model 204 Installation Guide for IBM z/VSE, version 7.4]]</var>, for additional installation information.
<!--Caution: <div> above-->
To upgrade SoftSpy for version 7.5, download, upload, and restore the SoftSpy procedure file, SPYPROC, which is distributed in a dump format.
<ol>
<li>Download SPYPROC, in binary form, from the [https://m204.rocketsoftware.com/maint/ullist?nickname=ROCKET SOUL files download page] to a workstation file.</li>
<li>Upload (FTP) the file from your workstation to your z/VSE system.</li>
<li>RESTORE the file into a Model 204 SOUL file.</li>
</ol>  
For detailed instructions, see [http://m204wiki.rocketsoftware.com/index.php?title=Web_help_download_SOUL_files#How_can_the_dump_file_be_uploaded_to_the_mainframe.3F Downloading and restoring SOUL files].


[[Category:Installation]]
[[Category:Installation]]

Latest revision as of 18:18, 1 June 2017

Overview

This topic describes how to install Rocket Model 204 version 7.5 or later on an IBM® z/VSE® operating system.

For information on the new features available in the Model 204 version that you are installing, see the release notes for that version.

If you are skipping any versions when installing (such as moving from version 7.4 to 7.7), be sure to read the release notes for the skipped versions as well.

Documentation conventions

In this topic, the Model 204 version and release that you are installing is referred to by 7.r, where 7.r can be 7.5 or later. Files, job streams, procedures, and sublibrary versions are referred to by version 7 and release rr; for example, V7rr (V770) or J7rr (J770) for Model 204 version 7.7.

Summary

To install the new Model 204 version, simply download, upload, and link the 7.r object modules available from the downloads page to install the 7.r components. In addition, you must catalog any procedure files in the V7rr sublibrary that include DLBL/EXTENT information for existing or new Model 204 files.

Before you begin

  • Model 204 version 7.r does not include new Dictionary/204 files or new CCASTAT and CCASYS files. You will be using your existing 7.4 versions of these files.
  • For system requirements for the new Model 204 version, see the release notes.
  • You must have either a Rocket M204 user ID or a preexisting user ID to download the installation files.
  • The sublibrary containing the object has the authorization zap (covering your licensed processors) preapplied, so you do not need to get a new authorization zap from the website. (The preapplied zap will authorize Model 204 itself and any separately purchased products, such as SirScan.)
  • The object files also have the maintenance zaps (as of the time the stream was prepared) preapplied, so you do not need to apply any maintenance as part of this installation. (You will only need to apply any new maintenance when it becomes available for this version.)

Overview of upgrading steps

Review the following high-level summary of steps before you begin downloading the Model 204 files.

Each step links to a section with detailed instructions. Note that some steps (such as assembling custom modules) might not apply to your installation. Once you have started, you can proceed directly through the steps (detail sections are consecutive) or return to this list for context.

  1. Allocate and initialize the Model 204 library.
  2. Download the Model 204 object file and macro library. You will need your Rocket M204 user ID.
  3. Populate the Model 204 library from the downloaded streams in the previous step.
  4. If you have your own user $functions (FUNU), you must do the following steps:
    1. Modify FUNU for 64-bit addressing considerations and store the modified source in your V7rr sublibrary.
    2. If you have any user-defined messages (MSGU), store them in your V7rr sublibrary.
    3. Assemble FUNU (and MSGU, if applicable).
  5. If you use customized modules, such as CDTB, modify them as needed and assemble them.
  6. Link the following phases and utility programs:
    1. ONLINE phase
    2. IFAM1 phase, if you use it
    3. BATCH204 phase, if you use it
    4. Model 204 phases and utility programs, such as CRAM phases
  7. If you use the CICS interface, customize it, and then assemble and link the CICS modules.
  8. If your z/VSE site runs under z/VM, copy and link the $$BVP204 phase.
  9. Allocate CCATEMP, a required data set used by Model 204 as the system scratch file.
  10. Install Dictionary/204.
  11. If you use SoftSpy, upgrade it for version 7.r.
  12. Verify that your installation was successful.

Space and partition requirements

Model 204 disk space requirements

Use the minimum disk space requirements for the libraries when calculating EXTENT information for Model 204 files.

Rocket recommends a minimum library size of 1200 tracks for disk type 3390.

Reserving a partition

Rocket recommends a minimum partition size of eight megabytes (8M) when installing Model 204.

Some Model 204 installation JCL might assign system files/devices (such as SYSIPT and SYSPCH) to disk. z/VSE requires that this JCL be run in a static partition.

Preparing the Model 204 environment

To prepare the Model 204 environment: run the M204CATP job, allocate CCATEMP, and catalog frequently used procedures.

Running M204CATP

The M204CATP job performs the following tasks:

  • allocates VSAM managed space for the Model 204 library (M204LIB)
  • defines the sublibraries V7rr and J7rr (such as V770 and J770)
  • catalogs two Model 204 procedures, M204V7rr (such as M204V770) and M204JCL, which help facilitate access to the Model 204 sublibraries

To run the M204CATP job:

  1. Access the M204CATP job stream text file and save it on your workstation.
  2. Upload the job stream to the mainframe in ASCII format.
  3. Modify the M204CATP job as noted in the file.
  4. Submit the M204CATP job.

Allocating CCATEMP

CCATEMP is a required data set used by Model 204 as the system scratch file.

Allocate CCATEMP before running jobs that execute an ONLINE, BATCH204, or IFAM1 program.

  1. Calculate the size of CCATEMP:

    Allocate a minimum of 25 pages per user if your site uses file groups, otherwise allocate 20 pages per user.

  2. Allocate CCATEMP by modifying and submitting the ALOCTEMP job.
  3. Modify the M204SYS procedure to point to the newly allocated CCATEMP.

Cataloging additional procedures

You can store some of the more frequently used JCL in the form of cataloged procedures. The jobs to catalog these procedures are distributed in the J7rr sublibrary.

To catalog procedures, modify each procedure as follows:

  • Add POWER JCL
  • Add the appropriate DLBL, EXTENT, and ASSGN information

The jobs assume that the M204JCL procedure is in the system library (IJSYSRS.SYSLIB). All other Rocket-supplied procedures are cataloged into the V7rr sublibrary.
Determine the new file, library volumes, and extents; then modify the procedures before cataloging them.

Procedures that can be cataloged

The following shows the procedures that can be cataloged and the job that must be modified for each procedure.

  1. Determine the files, library volumes, and extents that you need for the procedures.
  2. Modify the catalog jobs with this information.
  3. Catalog the procedures.
Jobs for cataloging frequently used procedures
Procedure name Catalog job Description
M204WRK1 CATWRK1 Work file for translation and assembly
M204WRK2 CATWRK2 Work file for translation and assembly
M204SYS CATSYS System files (CCASTAT and CCATEMP)
M204DD CATDD Dictionary/204 files and CCASYS

Work file procedures

You must catalog work file procedures in the CATWRK1 and CATWRK2 jobs for the following jobs that perform translation or assembly:

  • CICS jobs
  • CDBTASMC, FUNUASMC, MSGUASMC jobs

The CCASTAT and CCASYS files from Model 204 version 7.4 are compatible with Model 204 version 7.r.

Building the object and macro sublibrary

To build the object and macro sublibrary, you must download the object file and macro library and upload each to the mainframe.

Downloading

  1. Using your Rocket M204 user ID and password, log in to the Model 204 object file download page.
  2. Click the Download object file link beside the object library that you want to download. It contains the CATV7rr (such as CATV770) job stream and is saved on your workstation as M204V7r.OBJ (such as M204V77.OBJ).
  3. Go to the Model 204 macro library download page.
  4. Click the Download macro library link beside the macro library that you want to download. It contains the M204VSE job stream and is saved on your workstation as M204V7r_VSE.MAC (such as M204V77_VSE.MAC).

For details on how to download, see Downloading and uploading Model 204 installation components.

Once the object and macro files are downloaded to your workstation, upload them to the z/VSE system on the IBM mainframe.

Upload format and size

You can use any file transfer mechanism to upload the files, including FTP and IND$FILE.

Specify these characteristics for the upload files:

transfer format: binary
record format: FB
record size: 80 for each downloaded file
block size: 6400 for each downloaded file
storage size for both: primary: 10 CYL; secondary: 5 CYL

Populating the library

  1. Upload the M204V7r.OBJ (such as M204V77.OBJ) file to the POWER RDR queue, CLASS=0, in binary format. This file contains the CATV7rr job stream, which catalogs object and JCL into the Model 204 sublibrary, V7rr.
  2. From the VSE console, release the CATV7rr job stream from the RDR queue (such as r rdr,catv770). At the pause, enter the DLBL statements for your Model 204 library.
  3. Upload the M204V7r_VSE.MAC (such as M204V77_VSE.MAC) file to the POWER RDR queue, CLASS=0, in binary format. This file contains the M204VSE job stream, which catalogs source and macros into the Model 204 sublibrary, V7rr.
  4. From the VSE console, release the M204VSE job stream from the RDR queue (r rdr,m204vse). At the pause, enter the DLBL statements for your Model 204 library.

Preparing site-specific FUNU, MSGU, and CDTB modules

FUNUASMC, MSGUASMC, and CDTBASMC jobs

If you use translation tables or user-written functions, you must change the source code in the FUNU.A, MSGU.A, and CDTB.A sublibrary members to accommodate the requirements of your site, as shown in the following table.

Customizable user modules
If you use... Then do this... Using this job
Your own User Language functions Add them to the FUNU.A member FUNUASMC
Error messages with your own User Language functions Modify the MSGU.A member MSGUASMC
$CODE and $DECODE functions to encode and decode character strings Edit your own translation tables into the CDTB.A member CDTBASMC

The FUNU.A member contains one user function, $SEP, which adds separators when a date is entered in the format mm/dd/yy. MSGU.A also contains one sample error message.

You can use FUNU.A and MSGU.A to write your own user functions. The steps for installing the modules, as well as assembly considerations, are provided here.

It is recommended that if you think your site will make use of the TCP/IP Sockets Interface for Model 204, link the FUNU.A member during the installation process, even if you have not yet developed your own functions. This ensures access to the $ASCII and $EBCDIC functions.

Assembling FUNU, MSGU, and CDTB

The following table identifies the JCL to assemble FUNU, MSGU, and CDTB, and catalog the object decks into the Model 204 sublibrary.

JCL library member for user modules
Member Assembles and catalogs user modules
FUNUASMC FUNU (functions)
MSGUASMC MSGU (messages)
CDTBASMC CDTB (code table)

Once the modules are assembled and cataloged, link the Model 204 phases to contain user code tables and/or user functions, specifying the V7rr sublibrary (which contains the FUNU, MSGU, and CDTB modules) in the search list.

Assembly considerations for FUNU and MSGU

Some of the Model 204 macros and copy code needed to assemble FUNU and MSGU contain assembly language statements that are not supported by the z/VSE assembler. An assembly error occurs in the following circumstances:

  • EQU statement specifies a length attribute or type attribute. The following example from the VARDEFS copy book illustrates the error:

    VISLVL EQU 0,1 FIELD SECURITY LEVEL

    The error generated for this statement is:

    IPK122 INVALID DELIMITER, ',1'

  • EQU statement specifies a value that is too long or too large by assembler rules. The following example from the STARTS macro illustrates the error:

    MAXFS EQU 16777216/(4096*8) .MAX NUMBER OF INTERNAL FILE SEGMENTS

    The error generated for this statement is:

    IPK117 VALUE OF SELF-DEFINING TERM '16777216' TOO LARGE

    See the z/VSE assembler error message IPK117 for more information.

  • Symbol defined by an EQU statement of the type described above is referenced in a subsequent assembler statement. The following example from the STARTS macro illustrates the error:

    IVBN EQU ((MAXFS+7)/8). MAX # OF BYTES IN SEGMENT BIT PATTERN

    Where the error occurs because MAXFS is undefined (see the example in the second bullet, above), the error generated for this statement is:

    IPK149 SYMBOL 'MAXFS' NOT PREVIOUSLY DEFINED

  • In FUNU, some undefined symbols generate the following statement:

    QW9 ***** UNDEFINED *****

    The error generated for this statement is:

    IPK149 SYMBOL 'QW9' NOT PREVIOUSLY DEFINED

The text generated is executable and executes properly (barring logic errors) unless code that references an undefined symbol is executed.

Assembling FUNU and MSGU generates the errors described. However, in FUNU, no assembly errors occur within the FUNUTAB table entries or within the code for a user function (between the $name ENTER statement that begins the function and the LEAVENUM, LEAVESTR, or LEAVEF0 macro that terminates it). In MSGU, no assembly errors occur after the MSGU$ CSECT statement. CDTB receives no assembly errors.

z/VSE assembler errors

Rocket Software takes no responsibility for the errors generated by the z/VSE assembler. It is your responsibility to ensure that you do not code user functions referencing symbols that are undefined due to an assembler error.

Link editing the Model 204 phases

You must link all required phases and any optional phases that you want to use, including utilities and sort exits.

To link any of the Model 204 phases, run the job listed for that phase in the following table. This table also lists utilities you might need and the jobs used to link or relink them.

Most of the utility phases from Model 204 version 7.4 will continue to perform correctly when used with Model 204 version 7.r. Phases that you must relink for 7.r are listed as Required in the following table.

Executable phases and jobs used for linking or relinking
Phase or utility Required / Optional Purpose / Notes Job For more details, see ...
$$BVP204 Required (for z/VSE under z/VM) z/VM-directed output logical transient. Required on z/VSE systems running under z/VM. LINK$BVP Linking the $$BVP204 phase
ALLOCATE Required Initializes Model 204 database files

Required for Installation JCL, SQL installation, and Dictionary/204

 LINKALOC ALLOCATE utility in z/VSE
AUDIT204 Required Generates an audit trail for printing out later, and produces statistical reports and analysis LINKAUDT AUDIT204 utility
BATCH2 Optional

Establishes a User Language connection to a Model 204 ONLINE running in a separate region

Optional; recommended for CRAM testing.		 LINKBAT2 BATCH2 (TCP/IP)
BATCH204 Required

Handles a single user in batch mode

Required to complete installation

Link or relink when:

  • Installing user modules FUNU, MSGU, CDTB
  • Installing or upgrading to a new release of Model 204
  • Moving to a different release of CICS (M204 CICS Interface)
LINKB204 Linking the BATCH204 phase
CRAMSWT Optional CRAM non-master subtask LINKCRAM Linking the CRAM phases
CRAMZWT Optional CRAM master subtask LINKCRAM Linking the CRAM phases
DFHPSF Optional CICS/IFAM2 Interface PSFASM Updating the CICS System Definition (CSD)
HASH15 Optional Sort exit for M204HASH LINKHA15 Using M204HASH in the z/VSE environment
IFAM1 Optional Host Language Interface single-thread configuration

Link or relink when installing or upgrading to a new release of Model 204. (You can ignore UNRESOLVED ADCON messages.)

 LINKIFM1 IFAM1
IGCLM244 Optional CRAM load moduleLINKCRAMLinking the CRAM phases
M204CRPS Optional CICS full-screen printer routineCRPSASMUpdating the CICS System Definition (CSD)
M204L Optional Loads a Model 204 phase above the lineLINKMLODLink editing the M204L phase
M204PRNT Optional CICS 3270 print routinePRNTASMCUpdating the CICS System Definition (CSD)
M204PSFS Optional CICS full-screen remote User Language interface routinePSFSASMUpdating the CICS System Definition (CSD)
MERGEJ Required Media recovery journal merge utilityLINKMRGJUsing the MERGEJ utility
OI15 Optional File Load utility sort exitsLINKOI15Deferred update feature
OI35 Optional File Load utility sort exitsLINKOI35Deferred update feature
ONLINERequired Link online.

Link or relink when:

  • Installing user modules FUNU, MSGU, CDTB
  • Installing or upgrading to a new release of Model 204
  • Moving to a different release of CICS (M204 CICS Interface)
 LINKONLNLinking the ONLINE phase
SNAPCRAM Optional CRAM control block SNAP dump routineLINKCRAMLinking the CRAM phases
UTILC Required Prints the Model 204 checkpoint fileLINKUTLCObtaining checkpoint information (UTILC)
UTILJ Required Prints and copies Model 204 journal filesLINKUTLJUsing the UTILJ utility
UTLA Optional Prints the Model 204 audit trailLINKUTLAz/VSE and the audit trail
ZBLDTAB Optional Initializes the Model 204 password table. Required to allocate and initialize CCASTAT.LINKZBTBStoring security information (CCASTAT)
ZCTLTAB Optional Convert CCASTAT for the Password Expiration feature. Required to convert an existing CCASTAT data set to allow data control of passwords.LINKZCTBStoring security information (CCASTAT)

Linking the ONLINE phase

LINKONLN is the JCL member for linking the ONLINE phase and contains INCLUDE statements for the Model 204 core and all features. Uncomment the features that you are going to use.

Because the features for CICS do not affect the ONLINE phase, there are no INCLUDE statements for CICS.

Linking the IFAM1 phase

LINKIFM1 is the JCL member for linking the IFAM1 phase and contains an INCLUDE statement for the Model 204 core.

The following sample LINKIFM1 JCL is used to link IFAM1.

// JOB LINKIFM1 * LINKIFM1 links the IFAM1 phase /* /* To adapt this procedure to your installation: /* 1. Modify JOB statement /* 2. Modify the following in the job stream: /* ASSGN - this jcl assumes standard assignments /* for the logical units (SYS000) referenced /* in EXTENT statements. Add as needed: /* (e.g., // ASSGN SYS000,cuu) /* DATE - expiration date of dataset /* LENGTH - length of dataset in blocks/tracks /* if a MODEL 204 distribution file, see installation /* guide for number of 6184 byte pages /* START - starting location of dataset /* VOLSER - volume serial of dataset /* /* (-- For Rocket Support only: filename=LINKIFM1 7.7 2016/11/14 --) /* // EXEC PROC=M204JCL DLBL for JCL sublibrary // LIBDEF PROC,SEARCH=M204LIB.V770 // EXEC PROC=M204V770 DLBL for V770 M204 library // LIBDEF PHASE,CATALOG=M204LIB.V770 // LIBDEF OBJ,SEARCH=M204LIB.V770 // OPTION CATAL PHASE IFAM1,* REPLACE=YES INCLUDE LKIFM1 ENTRY IFII1 /* // EXEC LNKEDT /* /&

Linking the BATCH204 phase

LINKB204 is the JCL member for linking the BATCH204 phase and contains an INCLUDE statement for the Model 204 core and all features. Uncomment the features that you are going to use.

The EVCP module is a subset of the RSQL module. The code in EVCP contains code to process complex pattern matching. The code in RSQL contains the modules in EVCP along with the modules to support the SQL engine.

To link an ONLINE with RSQL and not EVCP, uncomment the following line in the JCL:

* INCLUDE LKSQLONL /* Uncomment for Remote SQL and Pattern

To link an ONLINE with EVCP instead of RSQL, uncomment the following line:

* INCLUDE LKNOSONL /* Uncomment for Pattern Matcher

The following sample LINKB204 JCL is used to link BATCH204.

LINKB204 JCL example

// JOB LINKB204 * LINKB204 links/catalogs the MODEL 204 BATCH204 phase /* /* Note: if using LE functions in MODEL 204, /* - add INCLUDE statements for LE modules /* - concatenate appropriate sublibrary to search. /* /* (-- For Rocket Support only: filename=LINKB204 7.7 2016/11/14 --) /* // EXEC PROC=M204JCL DLBL for JCL sublibrary // LIBDEF PROC,SEARCH=M204LIB.V770 // EXEC PROC=M204V770 DLBL for V770 M204 library // LIBDEF PHASE,CATALOG=M204LIB.V770 // LIBDEF OBJ,SEARCH=M204LIB.V770 // OPTION CATAL PHASE BATCH204,* REPLACE=YES * INCLUDE LKNOSONL /* Uncomment for Pattern Matcher * INCLUDE LKSQLONL /* Uncomment for Remote SQL and Pattern Matcher ENTRY MAINTASK /* // EXEC LNKEDT /* /&

Link editing the M204L phase

To run above the line (in 31-bit addressing space), you need to link the M204L program, which acts as an intermediary to load Model 204 phases above the line.

In the PARM clause of the EXEC statement, indicate the Model 204 load module that M204L will load above the line.

In the following example, ONLINE will be loaded above the line and then invoked:

// EXEC M204L,SIZE=AUTO,PARM='ONLINE'

The following sample LINKMLOD JCL is used to link M204L.

// JOB LINKMLOD * LINKMLOD links/catalogs the MODEL 204 M204L phase * * (-- For Rocket Support only: filename=LINKMLOD 7.7 2016/11/14 --) * // EXEC PROC=M204JCL DLBL for JCL sublibrary // LIBDEF PROC,SEARCH=M204LIB.V770 // EXEC PROC=M204V770 DLBL for V770 M204 library // LIBDEF PHASE,CATALOG=M204LIB.V770 // LIBDEF OBJ,SEARCH=M204LIB.V770 // OPTION CATAL ACTION ERRLMT(500) PHASE M204L,* REPLACE=YES INCLUDE M204L ENTRY M204L /* // EXEC LNKEDT /* /&

Linking the CRAM phases

The Cross-Region Access Method (CRAM) lets two or more Model 204 users in two or more partitions communicate with each other. CRAM is used by:

  • BATCH2
  • CICS Interface
  • IFAM2

See CRAM (IODEV=11, 23, 29) for more information about CRAM.

To link the CRAM phases (CRAMSWT, CRAMZWT, IGCLM244, and SNAPCRAM), use the LINKCRAM job from the J7rr sublibrary.

Linking the Model 204 utility phases

Most of the utility phases from Model 204 version 7.4 will continue to perform correctly when used with Model 204 version 7.r.

However, you must use the 7.r version of the following utilities, which are sensitive to the Model 204 journal and checkpoint format. The link jobs are available in the J7rr sublibrary.

UtilityDescriptionLink job
ALLOCATE Initialize Model 204 database files LINKALOC
AUDIT204 Extract from journal, with report stats and analysis LINKAUDT
MERGEJ Merge concurrent journal streamsLINKMRGJ
UTILC Information from checkpoint streamLINKUTLC
UTILJ Information from journal stream; add EOF markersLINKUTLJ

Link editing messages

When link editing any Model 204 programs, the following messages appear one or more times in the output listing:

2139I DUPLICATE SECTION DEFINITION: COPR *** SECTION IGNORED *** 2158I NO CSECT LENGTH SUPPLIED

These messages result from the linkage editor flagging any duplicate CSECT as an error in a new release of system software. If the message reads exactly as above, you can ignore it. However, if the error message displays anything other than COPR, contact Technical Support.

Also, you will typically see Unresolved External warnings for the following references, which you may ignore: FORTRAN modules such as DTRNH, DSQRT, and so on.

CICS interface installation

The Model 204 CICS interface allows CICS complete access to Model 204 facilities and supports CICS pseudo conversational programs.

Note: It is not necessary to install the CICS interface if it has been installed for a previous version of Model 204. The phases from the older version are compatible with version 7.r of Model 204.

Requirements

  • CICS Transaction Server support

    Rocket M204 supports the CICS Transaction Server versions 3.1, 3.2, 4.1, and 4.2.

  • Supporting TPROCESS COBOL applications

    If your CICS TPROCESS application was originally linked with AMODE=24, you must relink the CICS TPROCESS application specifying AMODE=31 because AMODE=24 is not supported.

CICS interface overview

For an overview of the CICS interface, including storage requirements and a listing of CICS interface components, see Overview of the CICS Interface.

Installing the CICS interface

  1. Customize the interface by editing the CICFG copy member and replacing it in the distribution library as CICFG.A. Then proceed with the CICSASM and CICSLINK jobs.

    For information on customizations needed for using the CICS Standard Mapping Service, see CICS interface configuration.

  2. Update the CICS System Definition (CSD) using one of the following methods:
    • Resource Definition Online (CEDA).
    • The IBM DFHSCDUP offline utility, to process the definitions in batch.
    • Processing the CICS Program Control Table (PCT) and Program Processing Table (PPT).
  3. Assemble, translate, and catalog the Model 204 CICS Interface modules, using the following jobs:
  4. Relink the IFAM2 transactions requiring pseudo conversational support with IFENTPS.
  5. Relink all user process-to-process partners with IFPPCI.

Updating the CICS System Definition (CSD)

You can update the CSD by using CEDA, by using the DFHCSDUP utility, or by processing the CICS Program Control Table (PCT). Use the values in the following table, where appropriate, for the method you choose. Information about using CEDA follows the table.

CICS System Definition values
User program Program name Transaction ID Modifiable
CICFG symbol		 TWA size
IFAM2 pseudo conversational DFHPSF DFHPSF is accessed by using a CICS LINK.
It is never invoked with a transaction ID from a terminal.		 N/A N/A
Full-screen interface M204PSFS M204 &TRN 88
Screen copy transaction M204CRPS U204 N/A N/A
Screen print transaction M204PRNT P204 &COP 88

CEDA (the Resource Definition Online transaction) or the DFHCSDUP utility defines the transactions and programs to the CSD file.

If you are not using tables, then define the transactions and programs by using CEDA and the values in the previous table, as in the following example:

CEDA DEFine PROG(program_name) GRoup(group_name) LANGuage(ASSEMBLER) RELoad(NO) RESident(NO) (Except for DFHPSF, RESident(YES)) STatus(ENABLED) CEDA DEFine TRANsaction(trans_ID) GRoup(group_name) PROgram(program_name) TWASIZE(twa_size_value) . . . CEDA CHeck GRoup(group_name) CEDA INstall GRoup(group_name)

You can use a transaction ID for a user program that is different from the value shown in the previous table. However, if you do so, you must change the associated CICFG symbol shown in the table.

As shown in the preceding example, group_name is any valid group name for the user site.

Note: Remember to add the groups to the GRPLIST for the particular CICS region. If the groups are not added, they are not installed during each CICS initialization.

Processing the PCT and PPT

The JCL sublibrary members PCTNTRY and PPTNTRY have the Program Control Table (PCT) and the Program Processing Table (PPT) default values shown in the following sections. You can update the CSD by adding to or modifying these default values and then assembling the tables.

PCT: Program Control Table

The Program Control Table (PCT) assigns user programs to their related CICS transaction identifiers (the transaction codes). Entries are required for both the 3270 full-screen interface and the screen print transaction.

The JCL sublibrary member, PCTNTRY, contains the PCT default values shown in the following code:

DFHPCT TYPE=ENTRY,PROGRAM=M204PSFS,TRANSID=M204,TWASIZE=88 DFHPCT TYPE=ENTRY,PROGRAM=M204PRNT,TRANSID=P204,TWASIZE=88 DFHPCT TYPE=ENTRY,PROGRAM=M204CRPS,TRANSID=U204

The following entry in the PCT is required for all user IFAM2 transactions:

DFHPCT TYPE=ENTRY,PROGRAM=program_name,TRANSID=xxxx,TWASIZE=88

Use the values in the previous table if you are updating the PCT. If you use a transaction ID for a user program that is different from the value shown in that table, you must change the associated CICFG symbol.

PPT: Program Processing Table

The Program Processing Table (PPT) stores program attributes. Entries are required for the 3270 full-screen interface, direct printer support, and the IFAM2 interface.

The JCL sublibrary member, PPTNTRY, contains the PPT default values shown in the following code.

Note: In the first line of the PPT, be sure to set the RES parameter to YES; otherwise, the transaction does not complete successfully.

DFHPPT TYPE=ENTRY,PROGRAM=DFHPSF,RES=YES,PGMLANG=ASSEMBLER DFHPPT TYPE=ENTRY,PROGRAM=M204CRPS,PGMLANG=ASSEMBLER DFHPPT TYPE=ENTRY,PROGRAM=M204PRNT,PGMLANG=ASSEMBLER DFHPPT TYPE=ENTRY,PROGRAM=M204PSFS,PGMLANG=ASSEMBLER DFHPPT TYPE=ENTRY,PROGRAM=OBPLTSD,PGMLANG=ASSEMBLER

Assembling the CICS Interface modules

Assemble, in the sequence listed, the CICS Interface modules listed in the assembly step in the CICS interface installation section.

Some assemblies display a warning message (DFHEIMSG 4) because the CSA address is release-dependent. If the interface program is running in the release under which it was assembled, ignore the warning.

After the modules are successfully built, relink as directed in the CICS interface installation section.

Linking the $$BVP204 phase

Notes: Information about linking $$BVP204 applies only to z/VSE sites running under z/VM.
It is not necessary to link the $$BVP204 phase if it has been installed for a previous version of Model 204. The phases from the older version are compatible with version 7.r of Model 204.

The $$BVP204 phase is a transient: it is required for the z/VM-directed output feature, and it is invoked by Model 204 to issue diagnostic instructions in order to pass CP commands to z/VM.

Linking $$BVP204 to the system library improves performance.

LINK$BVP job

To link $$BVP204, use the LINK$BVP job from the J7rr sublibrary.

This is a required step in a Model 204 installation on z/VSE running under z/VM.

COPYVMPR job

To copy $$BVP204 to the System Residence Library, use the COPYVMPR job from the J7rr sublibrary.

This is a required step in a Model 204 installation on z/VSE running under z/VM.

Installing SoftSpy

See the SoftSpy installation guide for instructions on installing SoftSpy version 7.r.

Verifying Model 204 on your system

To perform an initial verification that your installation of Model 204 was successful, issue the following commands from the Model 204 command line.

Command You should see...
ROCKET A list of authorized Model 204 products (including 7.r) currently on your system.
DISPLAY ZAPS A list of Model 204 zaps (including 7.r zaps) on your system.
DICTADMIN The Dictionary Administration subsystem, displaying Release 7.r on its menu screens.
SUBSYSMGMT The Application Subsystem facility, displaying VER V REL R on its menu screens.

Dictionary/204 installation

For details on installing Dictionary/204, see the Dictionary/204 installation guide.

See also

Additional information

Refer to the Rocket Model 204 Installation Guide for IBM z/VSE, version 7.4, for additional installation information.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Model_204_installation_on_IBM_z/VSE&oldid=103230"