Upgrading to Model 204 version 7.5 on IBM z/OS: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(27 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<div class="toclimit-3">__TOC__</div>
#REDIRECT [[Model 204 installation on IBM z/OS]]
==Overview==
This page describes the steps required to upgrade from Rocket Model 204 version 7.4 to version 7.5, on the IBM z/OS operating system.
<table><tr><td><p>In order to upgrade to Model 204 version 7.5, <b>you must have version 7.4</b> and [[#Before you begin|various Early Warnings]] installed on your system..</p> </td></tr></table>
 
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.
 
==Before you begin==
<ul>
<li>In order to upgrade to version 7.5, you must have version 7.4 and Autofix release EW3044 installed on your system.
<p>Autofix release EW3044 includes:
<ul>
<li>Early Warnings for Model 204 through 740EW172</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 object library 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 MP/204 and SirScan.)</li>
<li>The object library also has 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>
</ul>
<div id="steps"></div>
 
==Overview of upgrading steps==
Review the following high-level summary of steps before you begin downloading the <var class="product">Model 204</var> version 7.5 files.
For an example, see [[#Example_workflow_for_7.5:_download_through_installation|Example workflow for 7.5: download through installation]].
<ol>
<li><p>Use your [[Rocket M204 user ID]] to [[#downloading|download]] the Model 204 object library and the Model 204 macro library.</p></li>
 
<li>[[#uploading|Upload]] (FTP) the downloaded components to the z/OS system on the IBM mainframe.</li>
<li>[[#bldLibs|Build]] the RKOBJLIB object library and RKMACLIB macro library. (Once you have built these libraries, do not modify them.)</li>
<li>Submit the job to [[#allocating|allocate the other data sets]] required for installation.</li>
<li>If you have your own user $functions (FUNU), you must do the following steps:
<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 local source library.</li>
<li>If you have any user-defined messages (MSGU), store them in your local source library.</li>
<li>[[#asmFUNU|Assemble]] FUNU (and MSGU, if applicable), with the output object file stored in your local object library.</li>
</ol>
</li>
<li>If you use an external authorizer (such as RACF) for <var class="product">Model 204</var>, [[#secparm|assemble the <i>xxxx</i>PARM security module]] (such as RACFPARM). The object file is then stored in your local object library.</li>
 
<li>If you use the [[#ul_db2|UL/DB2 interface]], preprocess and assemble the USQL module.</li>
 
<li>If you use other customized modules, such as CDTB, modify them as needed and [[#asm|assemble]] them.</li>
<li>Link the [[#lkonln|ONLINE]] load module.</li>
 
<li>If you use the [[#link_ifam1|IFAM1]] and [[#link_ifam4|IFAM4]] load modules, link them.</li>
<li>Link the <var class="product">Model 204</var> [[#lkutils|utility load modules]].</li>
<li>If you use the [[#cics|CICS interface]], customize it, and then assemble and link the CICS modules.</li>
<li>If you use the [[#tso|TSO]] interface, assemble and link-edit the TSO source modules.</li>
<li>If you use [[#softspy|SoftSpy]], upgrade it for 7.5.</li>
</ol>
 
==Object and macro libraries==
{{Template:Model 204 installation components}}
 
==Building the object and macro libraries==
To build the object and macro libraries, you must download the object library and macro library; upload (FTP) each library to the mainframe; and copy, modify, and run the NEW204LB job.
<div id="downloading"></div>
===Downloading===
<!--Caution: <div> above-->
<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>Click the <b>Download object file</b> link beside the object library that you want to download.</li>
<li>Go to the [https://model204.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.</li>
</ol>
<div id="uploading"></div>
 
===Uploading (FTP)===
<!--Caution: <div> above-->
Once the object file and macro library are downloaded to your workstation, FTP them to the z/OS 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>
 
===Building the object and macro libraries (NEW204LB job stream)===
<!--Caution: <div> above-->
After you upload the object and macro library input streams to the mainframe, build the object and macro libraries:
<ol>
<li>Access the [http://sirius.sirius-software.com/download/new204lb.txt NEW204LB job stream] text file.
<li>Copy the job stream file into a local TSO library for editing.
<li>On the first line of the job stream, modify the JOB card according to your local job card parameters.
<li>On the final four lines, marked <code>2 &lt;&lt;</code> ... <code>5 &lt;&lt;</code> on the right:
<ol style="list-style-type:lower-alpha;">
<li>Modify the <code>VERSION=</code> parameter, specifying the two-digit version of <var class="product">Model 204</var> you are installing, such as 75.
<li>Modify the <code>HLQ=</code> parameter, specifying the high-level qualifiers of all <var class="product">Model 204</var> installation data sets.
<li>Modify the <code>OBJINP=</code> parameter, using the DSN of the object library input file that you uploaded to the mainframe.
<li>Modify the <code>MACINP=</code> parameter, using the DSN of the macro library input file that you uploaded to the mainframe.
</ol>
<li>Submit the <code>NEW204LB</code> job to build the object library ("RKOBJLIB") and macro library ("RKMACLIB") on your z/OS system.</li>
</ol>
<div id="notouch"></div>
<p class="warn"><b>Attention:</b> Once you have built RKOBJLIB and RKMACLIB on your z/OS system, <b>do not</b> modify them in any way.<br />
For example, <b>do not</b> store other members into the object library; it should only contain the members as supplied in a download from the web site. Place object files that you might assemble (such as FUNU or RACFPARM) into your local object library.</p>
====RKOBJLIB README file====
README, a member of RKOBJLIB, contains details on the object files and installation steps. Once you have built RKOBJLIB, you can use README as an installation checklist if desired.
 
<div id="allocating"></div>
 
==Data sets for Model 204 upgrading==
<!--Caution: <div> above-->
There are three data sets used when upgrading to Model 204 7.5:
<ul>
<li>data set for the Model 204 load modules
<li>data set for the local source library
<li>data set for the local object library
</ul>
The data set for the load modules will contain, after linking, the modules for the Model 204 product, including: ONLINE, IFAM1, and IFAM4.
 
The local source library is used to store the customized source for modules such as FUNU, MSGU, and ACF2PARM, RACFPARM, or TOPSPARM.
 
When the source is assembled, it is stored in the local object library.
 
One of the members of the RKOBJLIB object library is named [[Model 204 data set allocation job stream for IBM z/OS|JALINSJ]], which is a job stream to allocate data sets for the installation. <code>JALINSJ</code> contains information about naming conventions for the data sets.
 
===Allocating data sets (JALINSJ job stream)===
 
<ol>
<li>Copy <code>JALINSJ</code> into a local TSO library.
<li>Edit your copy of <code>JALINSJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the lines, near the top of the job stream, marked with numbers followed by <code>&lt;&lt;</code>. The numbers correspond to numbered steps in the comments following these lines.
</ul>
<li>Submit the <code>JALINSJ</code> job to allocate the data set.
</ol>
<div id="lkonln"></div>
 
==Linking the Model 204 ONLINE load module==
<!--Caution: <div> above-->
<div id="onlnTable"></div>
<blockquote class="note">
<p><b>Notes:</b> </p>
<ul>
<li>If you use customized modules (such as FUNU, MSGU, ACF2PARM, RACFPARM, TOPSPARM, CDTB, or UL/DB2), you must [[#FUNU_7.5|modify]] them (if needed) and [[#asm|assemble]] them <b>before you link the ONLINE/IFAM1/IFAM4</b> load modules.</li>
<li>There is not a separate link step for BATCH204.  It is not maintained as a separate module; the same module as ONLINE is used, with a BATCH204 alias.</li>
</ul>
</blockquote>
One of the members of the RKOBJLIB object library is [[Model 204 ONLINE link job stream for z/OS|LKONLNJ]], which is a job stream to link the <var class="product">Model 204</var> ONLINE load module.
 
<div id="LKONLNJ"></div>
===Linking ONLINE (LKONLNJ job stream)===
<!--Caution: <div> above-->
 
<ol>
<li>Copy the <code>LKONLNJ</code> job stream from RKOBJLIB into a local TSO library.
<li>Edit your copy of <code>LKONLNJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the lines, near the top of the job stream, marked with 1-4 followed by <code>&lt;&lt;</code>. The numbers correspond to numbered steps in the comments.
<li>As needed, edit the lines after <code>SYSLIN DD *</code> that are marked with <code>&lt;&lt;</code>.  See the comments at the top of the <code>SYSLIN</code> sections (<b>A</b>-<b>C</b>) for instructions.
</ul>
<li>Submit the <code>LKONLNJ</code> job to link the ONLINE load module.
</ol>
Concise editing instructions are provided in the <code>LKONLNJ</code> file itself. More details about link-editing the ONLINE load module are provided in the following table.
<table class="thJustBold">
<tr><th>1</th><td>You must specify a value for the HLQ symbolic parameter in the EXEC LKM204P statement.  The value of HLQ corresponds to the high-level qualifier used for the DSN for:
<ul>
<li> the downloaded object library</li>
<li>the Model204 load library</li>
<li>other data sets that are required for installation</li>
</ul></td></tr>
<tr><th>2</th><td>One of the modifications is <b>always required</b>, based on whether the ONLINE is to use RSQL (for Connect*) or not.
 
Uncomment only one of the following statements:
<ul>
<li>To link an ONLINE that uses RSQL, you must uncomment  the INCLUDE RKOBJ204(<b>LKSQLONL</b>) statement.
<li>To link an ONLINE that does not use RSQL, you must uncomment the INCLUDE RKOBJ204(<b>LKNOSONL</b>) statement.
</ul>
</td></tr>
<tr><th>3</th><td>If you use an external authorizer, such as RACF or ACF2, you must:
<ul>
<li>[[#asm|Assemble the xxxPARM]] for your external authorizer to add the object file (such as RACFPARM or ACF2PARM) to your local object library.
<li>In the SYSLIN DD *, uncomment the appropriate INCLUDE statement(s) for your external authorizer. <blockquote class="note"><b>Notes:</b>
<ul><li>Uncomment either the "static" or "dynamic" INCLUDE statement, depending on your configuration.<li>If you use ACF2, there are two INCLUDE statements to be uncommented; one refers to your system ACF2 library.  You must also provide the DSN for the ACF2 library in the ACF2 symbolic parameter in the EXEC LKM204P statement.</ul>
</blockquote>
</ul>
</td></tr>
<tr><th>4</th><td>If you have other programs that you assemble for your Model 204 ONLINE module, for example, [[#FUNU|FUNU]], assemble them into your local object library.  You <strong>do not</strong> need to add additional INCLUDE statements for FUNU or other locally assembled object files; they are already in the include streams from RKOBJLIB.
</td></tr>
<tr><th>5</th><td>If you have an MQ series load library, set the MQ symbolic parameter to the correct DSN in the EXEC LKM204P statement. This allows you to use the MQ Series feature of <var class="product">Model 204</var>, either if you are already authorized for it, or to support a trial of it, without requiring relinking of the load module. You must also uncomment the INCLUDE MQ statement in the SYSLIN input.
</td></tr>
</table>
 
<div id="link_ifam1"></div>
 
==Linking the Model 204 IFAM1 load module==
<!--Caution: <div>*s* above-->
One of the members of the RKOBJLIB object library is <span class="plainlinks">[http://m204wiki.rocketsoftware.com/index.php/Model_204_IFAM1_link_job_stream_for_IBM_z/OS?title=Model_204_IFAM1_link_job_stream_for_IBM_z/OS&target=blank LKIFAM1J]</span>, which is a job stream to link the <var class="product">Model 204</var> IFAM1 load module.
 
===Linking IFAM1 (LKIFAM1J job stream)===
<ol>
<li>Copy the <code>LKIFAM1J</code> job stream from RKOBJLIB into a local TSO library.
<li>Edit your copy of <code>LKIFAM1J</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the lines, near the top of the job stream, marked with numbers followed by <code>&lt;&lt;</code>. The numbers correspond to numbered steps in the comments following these lines.
</ul>
<li>Submit the <code>LKIFAM1J</code> job to link the IFAM1 load module.
</ol>
 
<div id="link_ifam4"></div>
 
==Linking the Model 204 IFAM4 load module==
<!--Caution: <div>*s* above-->
 
One of the members of the RKOBJLIB object library is <span class="plainlinks">[http://m204wiki.rocketsoftware.com/index.php/Model_204_IFAM4_link_job_stream_for_IBM_z/OS?title=Model_204_IFAM4_link_job_stream_for_IBM_z/OS&target=blank LKIFAM4J]</span>, which is a job stream to link the <var class="product">Model 204</var> IFAM4 load module.
===Linking IFAM4 (LKIFAM4J job stream)===
 
<ol>
<li>Copy the <code>LKIFAM4J</code> job stream from RKOBJLIB into a local TSO library.
<li>Edit your copy of <code>LKIFAM4J</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the lines, near the top of the job stream, marked with numbers followed by <code>&lt;&lt;</code>. The numbers correspond to numbered steps in the comments following these lines.
</ul>
<li>Submit the <code>LKIFAM4J</code> job to link the IFAM4 load module.
</ol>
<div id="lkutils"></div>
<!--Caution: <div> above-->
 
==Linking the Model 204 utility load modules==
<!--Caution: <div> above-->
Most of the utility load modules from Model 204 version 7.4 will continue to perform correctly when used with version 7.5.
However, you must use the 7.5 version of the following utilities, which are sensitive to the Model 204 journal and checkpoint format:
<table>
<tr><td><b>AUDIT204</b></td> <td>Extract from journal, with report stats and analysis</td></tr>
<tr><td><b>MERGEJ</b></td> <td>Merge concurrent journal streams</td></tr>
<tr><td><b>UTILC</b></td> <td>Information from checkpoint stream</td></tr>
<tr><td><b>UTILJ</b></td> <td>Information from journal stream; add EOF markers</td></tr>
</table>
===Linking the utility load modules (LKALLUTJ job stream)===
One of the members of the RKOBJLIB object library is [[Model 204 utilities link job stream for IBM z/OS|LKALLUTJ]], a job stream to link the <var class="product">Model 204</var> utility load modules.
<ol>
<li>Copy <code>LKALLUTJ</code> into a local TSO library.
<li>Edit your copy of <code>LKALLUTJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Supply your installation high level qualifier(s) in the following lines marked with <code>&lt;&lt;</code>:
<ul>
<li>for <code>hlq</code> in the <code>JCLLIB ORDER=(hlq.</code>... line after the <code>JOB</code> card
<li>after <code>HLQ=</code>, on the line after <code>EXEC LKALLUTP</code> at the bottom of the job stream
</ul>
</ul>
<li>Submit the <code>LKALLUTJ</code> job to link the utility load modules.
</ol>
<div id="asm"></div>
==Assembling customized modules into your local object library (LOCAL.OBJLIB)==
<!--Caution: <div> above-->
Copy the module (such as FUNU, MSGU, ACF2PARM, RACFPARM, TOPSPARM, CDTB, or UL/DB2) into your local source library, if you have not already done so. (The local source library is not version-specific, so modules copied into it can be used for future installations.)
 
One of the members of the RKOBJLIB object library is [[Model 204 local member assembly job stream for IBM z/OS|JASMJ]], a job stream to assemble a member from your Model 204 local source library into your local object library (LOCAL.OBJLIB).
 
===Assembling customized modules (JASMJ job stream)===
<ol>
<li>Copy <code>JASMJ</code> into a local TSO library.
<li>Edit your copy of <code>JASMJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Supply your installation high level qualifier(s) in the following lines marked with <code>&lt;&lt;</code>:
<ul>
<li>for <code>hlq</code> in the <code>JCLLIB ORDER=(hlq.</code>... line after the <code>JOB</code> card
<li>after <code>HLQ=</code>, on the ASM line at the bottom of the job stream
</ul>
<li>Provide the member name to assemble (such as FUNU, MSGU, RACFPARM) on the <code>MEM=</code> line.
</ul>
<li>Submit the <code>JASMJ</code> job to assemble the module into your local object library.
</ol>
<div id="lkcram"></div>
<div id="secparm"></div>
 
==Setting up the security module==
<!--Caution: <div> above-->
If you use a [[Security_interfaces_overview|security interface]] such as ACF2, RACF, or Top Secret:
 
<ol>
<li> [[#asm|Assemble]] the security module:
ACF2PARM, RACFPARM, or TOPSPARM.</li>
<li>Optional. Link the security module as described below if you want it to be dynamically loaded.</li>
</ol>
 
===Linking the security module (LKSECRJ job stream)===
 
Dynamic loading lets you modify the security parameters without having to relink Model 204, which would be required if the parameter module were linked into Model 204 directly.
 
If you want Model 204 to dynamically load your security module during Model 204 ACF2, RACF, or TOPSECRET interface initialization, then you must link the corresponding security parameter module.
 
One of the members of the RKOBJLIB object library is <code>LKSECRJ</code>, a job stream to link-edit the security parameter module.
 
<ol>
<li>Copy [[Model 204 security module link job stream for IBM z/OS|LKSECRJ]] into a local TSO library.
<li>Edit your copy of <code>LKSECRJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the lines, near the top of the job stream, marked with numbers followed by <code>&lt;&lt;</code>. The numbers correspond to numbered steps in the comments following these lines.
</ul>
<li>Submit the <code>LKSECRJ</code> job to link-edit the security parameter module (ACF2PARM, RACFPARM, or TOPSPARM).
</ol>
<div id="cics"></div>
 
==CICS interface installation==
<!--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===
<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]].
===Installing the CICS interface===
 
<ol>
<li>Customize the interface by copying the CICFG copy member from RKMACLIB into your local source library and editing it as needed.
<p>For information on customizations needed for using the CICS Standard Mapping Service, see [[CICS interface]].</p></li>
<li>Update the CICS System Definition (CSD) using one of the following methods:
<ul><li>Resource Definition Online (CEDA). The supplied member CEDAM204 in RKMACLIB provides an example of the required PCT, PPT, and PLT definitions.</li>
<li>The IBM DFHSCDUP offline utility, to process the definitions in batch.</li>
</ul>
<li>[[#CICS_alloc|Allocate]] a CICS user library.</li>
<li>[[#CICS_asm|Assemble and link]] the CICS modules.</li>
</ol>
 
===Updating the CICS System Definition (CSD)===
You can update the CSD by using either CEDA or the DFHCSDUP utility and the CEDAM204 member of RKMACLIB. 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>
<tr class="head"><th>User program</th> <th>Program name</th> <th>Transaction ID</th> <th>Modifiable <br>CICFG symbol</th>
<th>TWA size</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>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>Screen print transaction</td> <td>M204PRNT</td> <td>P204</td> <td>&COP</td> <td>88</td></tr>
</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 the CEDAM204 member, 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))
  RSL(PUBLIC)
  STatus(ENABLED)
CEDA DEFine TRANsaction(trans_ID)
  GRoup(group_name)
  PROgram(program_name)
  TWASIZE(twa_size_value)
  .
  .
  .
  RSL(PUBLIC)
  .
  .
  .
CEDA CHeck 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>
 
<div id="CICS_alloc"></div>
 
===Allocating a CICS user library (JALCICSJ job stream)===
<!--Caution: <div> above-->
One of the members of the RKOBJLIB object library is [[Model 204 CICS user library allocation job stream for IBM z/OS|JALCICSJ]], a job stream to allocate an empty CICS user library. You must allocate the CICS user library before assembling and linking the CICS modules.
<ol>
<li>Copy <code>JALCICSJ</code> into a local TSO library.</li>
<li>Edit your copy of <code>JACICSJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.</li>
<li>Supply your installation high level qualifier(s) in the following lines marked with <<:
<ul>
<li>for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card </li>
<li>after HLQ=, on the line after EXEC LKALLUTP at the bottom of the job stream </li>
</ul>
</ul>
</li>
<li>Submit the <code>JALCICSJ</code> job to allocate the CICS user library.</li>
</ol>
 
<div id="CICS_asm"></div>
===Assembling and linking CICS modules (LKCICSJ job stream)===
<!--Caution: <div> above-->
One of the members of the RKOBJLIB object library is [[Model 204 CICS module assembly job stream for_ IBM z/OS|LKCICSJ]], a job stream to assemble and link the <var class="product">Model 204</var> CICS modules.
<ol>
<li>Copy <code>LKCICSJ</code> into a local TSO library.
<li>Edit your copy of <code>LKCICSJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Supply your Model 204 installation high level qualifier(s) in the following lines marked with <code>&lt;&lt;</code>:
<ul>
<li>for <code>hlq</code> in the <code>JCLLIB ORDER=(hlq.</code>... line after the <code>JOB</code> card
<li>after <code>HLQ=</code>, on the line after <code>EXEC JALCICSP</code> at the bottom of the job stream
</ul>
</ul>
<li>Submit the <code>LKCICSJ</code> job to assemble and link the CICS module.
</ol>
 
<div id="tso"></div>
 
==TSO interface installation==
<!--Caution: <div> above-->
<p class="note"><b>Note:</b> It is not necessary to install the TSO 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>
 
The Model 204 TSO Interface enables the TSO user to communicate with a Model 204 Online.
 
The TSO Interface consists of two assembly language modules, TSFS and TSUL, whose source is located in the macro library. The modules are completely reentrant, reusable, and refreshable. Installation requires assembly and link-editing of the TSO source modules.
 
===Installing the TSO interface===
 
<ol>
<li>If you are using TSO extensions, modify TSFS in the local source library by changing:
<p class="code">&TSOV SETC 'TSO' </p>
<p>to:</p>
<p class="code">&TSOV SETC 'TSOE'</p></li>
<p>Changing the &TSOV SETC 'TSO' code in TSFS causes assembly of the NOEDIT form of the TPUT macro in the TSFS module. The NOEDIT form, required for 3270 extended data streams, allows proper handling of colors or highlighting in TSO extensions. NOEDIT is recommended for all TSO extensions.</p>
<li>Assemble and link the TSO modules, using the <code>LKTSOJ</code> job.</li>
</ol>
 
===Assembling TSO modules (LKTSOJ job stream)===
 
One of the members of the RKOBJLIB object library is [[Model 204 utilities link job stream for IBM z/OS|LKTSOJ]], a job stream to assemble and link the <var class="product">Model 204</var> TSO modules.
<ol>
<li>Copy <code>LKTSOJ</code> into a local TSO library.
<li>Edit your copy of <code>LKTSOJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Supply your installation high level qualifier(s) in the following lines marked with <code>&lt;&lt;</code>:
<ul>
<li>for <code>hlq</code> in the <code>JCLLIB ORDER=(hlq.</code>... line after the <code>JOB</code> card
<li>after <code>HLQ=</code>, on the line after <code>EXEC LKALLUTP</code> at the bottom of the job stream
</ul>
</ul>
<li>Submit the <code>LKTSOJ</code> job to assemble and link the TSO modules.
</ol>
<div id="FUNU"></div>
 
==CRAM==
RKOBJLIB also contains LKCRAMJ, the job stream to link the CRAM load modules.  Versions 7.4 and later of the CRAM load modules are completely compatible with version 7.5 of Model 204. Deploying a new version of CRAM can be an intensive process, and because you have version 7.4 installed, it is not necessary. You can safely bypass linking the 7.5 CRAM modules.
 
==FUNU and optional MSGU==
<!--Caution: <div> above-->
This section lists installation considerations if you have your own user-written $functions module (FUNU).
<p class="note"><b>Note:</b> If you have your own FUNU or MSGU module, you must assemble it <b>before linking the ONLINE/IFAM1/IFAM4</b> load modules.</p>
<div id="FUNU_7.5"></div>
===FUNU changes for version 7.5===
<!--Caution: <div> above-->
{{Template:FUNU changes for 7.5}}
<div id="asmFUNU"></div>
===FUNU (and MSGU) assembly===
<!--Caution: <div> above-->
Copy the source from RKMACLIB into your local source library.
After making any changes required for this version of <var class="product">Model 204</var>, run <code>JASMJ</code> to [[#asm|assemble]] FUNU into your local object library. 
 
If needed, modify and run <code>JASMJ</code> to assemble MSGU.
 
<p>You do <b>not</b> need to insert any INCLUDE statements for either FUNU nor MSGU; they are already present in the INCLUDE member (LKSQLONL or LKNOSONL) provided in the downloaded object library.</p>
<div id="ul_db2"></div>
 
==Installing the UL/DB2 interface (JAUSQLJ job stream)==
<!--Caution: <div> above-->
To support the UL/DB2 interface, USQL code is delivered in source for you to preprocess for your version of DB2. If you use the UL/DB2 interface, assemble the source as described below <b>before linking the ONLINE/IFAM1/IFAM4</b> load modules.
 
<ol>
<li>Copy [[Model 204 UL/DB2 job stream for IBM z/OS|JAUSQLJ]] into a local TSO library.
<li>Edit your copy of <code>JAUSQLJ</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Supply your installation high level qualifier(s) in the following lines marked with <code>&lt;&lt;</code>:
<ul>
<li>for <code>hlq</code> in the <code>JCLLIB ORDER=(hlq.</code>... line after the <code>JOB</code> card
<li>on the line after <code>EXEC JAUSQLP</code> at the bottom of the job stream set:
<ul>
<li><code>HLQ=</code>high level qualifier of all Model 204 installation DSNs</li>
<li><code>DB2HLQ=</code>high level qualifier for your DB2 maclib.</li>
</ul>
</ul>
</ul>
<li>Submit the <code>JAUSQLJ</code> job to preprocess and assemble the USQL module.  The JAUSQLJ job executes the following two steps:
<ul>
<li>Run USQL (contained in RKMACLIB) through the DB2 preprocessor to process the EXEC SQL statements.  This step produces two data sets: the DBRM and the expanded USQL source.  The DBRM is saved as USQLDBRM in the local object library.  The expanded USQL source is passed to step two for assembly.</li>
<li>Assemble expanded USQL source into local object library.</li>
</ul>
<li>Bind the DBRM as the plan with a site-specific plan name.</li>
</ol>
For more information on UL/DB2, see the <var class="book">Rocket Model 204 User Language/DATABASE 2 Interface Guide</var>.
 
<div id="softspy"></div>
 
==Upgrading SoftSpy for 7.5==
<!--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/OS 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].
 
==Verifying Model 204 7.5 on your system==
To perform an initial verification that your upgrade to 7.5 was successful, issue the following commands from the Model 204 command line.
<table>
<tr class="head"><th>Command</th> <th>You should see...</th></tr>
<tr><td>ROCKET</td> <td>A list of authorized M204 products (including 7.5) currently on your system.</td></tr>
<tr><td>DISPLAY ZAPS</td> <td>A list of Model 204 zaps (including 7.5 zaps) on your system.</td></tr>
<tr><td>DICTADMIN</td> <td>The Dictionary Administration subsystem, displaying <code>Release 7.5</code> on its menu screens.</td></tr>
<tr><td>SUBSYSMGMT</td> <td>The Application Subsystem facility, displaying <code>VER 7 REL 5</code> on its menu screens.</td></tr>
</table>
 
==Example workflow for 7.5: download through installation==
This example shows one typical installation workflow: the site does not use RSQL, it uses the RACF external authorizer, and it does not have its own FUNU. The IBM system MQ loadlib is <code>MQSERIES.SCSQLOAD</code> (this is typical in z/OS).
The high-level qualifier in this example is MYBUILD.
The other item needed is the member name <code>MYBLDOB</code>, which is chosen arbitrarily for this example, and the following DSNs:
<ul>
<li><code>MYBUILD.M204V75.RKOBJLIB.DISTRIB</code>
<li><code>MYBUILD.M204V75.RKOBJLIB</code>
<li><code>MYBUILD.M204V75.RKMACLIB.DISTRIB</code>
<li><code>MYBUILD.M204V75.RKMACLIB</code>
<li><code>MYBUILD.M204V75.LOCAL.OBJLIB</code>
<li><code>MYBUILD.M204V75.LOADLIB</code>
</ul>
===Build RKOBJLIB===
<ol>
 
<li>Download the object library (M204V75.OBJ) from the downloads page.
<li>Upload to the mainframe, in binary format, with settings FB/80/6400, as <code>MYBUILD.M204V75.RKOBJLIB.DISTRIB</code>.
<li>Download the macro library (M204V75_ZOS.MAC) from the downloads page.
<li>Upload to the mainframe, in binary format, with settings FB/80/6400, as <code>MYBUILD.M204V75.RKMACLIB.DISTRIB</code>.
<li>Create the member MYBLDOB in my TSO library from a [http://sirius-software.com/download/new204lb.txt download] of the job stream to build the object and macro libraries, using the following at the end of the job stream:
<p class="code">//BLD EXEC NEW204LB,VERSION=75,
//        HLQ=MYBUILD,
//        OBJINP=MYBUILD.M204V75.RKOBJLIB.DISTRIB,
//        MACINP=MYBUILD.M204V75.RKMACLIB.DISTRIB
</p>
<li>Run MYBLDOB from my TSO library. MYBLDOB deletes and then creates <code>MYBUILD.M204V75.RKOBJLIB</code> and
<code>MYBUILD.M204V75.RKMACLIB</code>.
 
<li>Upload to the mainframe, in binary format, with settings FB/80/6400, as <code>MYBUILD.M204V75.RKMACLIB.DISTRIB</code>.
<li>Create the member MYBLDDS in my TSO library by copying
the job stream from [[Model 204 data set allocation job stream for IBM z/OS|JALINSJ]], using the following at the end of the job stream:
<p class="code">//BLD EXEC JALINSP,
// HLQ=MYBUILD
</p>
 
<li>Run MYBLDDS from my TSO library. MYBLDDS allocates an empty loadlib data set for the Model 204 load modules, an empty local source library for the customized source files, and an empty local object library for the customized local object modules, with the following names: <code>MYBUILD.M204V75.LOADLIB</code>,  <code>MYBUILD.M204.LOCAL.SRCLIB</code> and <code>MYBUILD.M204V75.LOCAL.OBJLIB</code>.
 
</ol>
 
===Assemble and link===
<ol >
<li>Copy the RACFPARM source to the <code>MYBUILD.M204.LOCAL.SRCLIB</code> and make any necessary modifications.
<li>Create the member JASMSECJ in my TSO library by copying
the job stream from [[Model 204 local member assembly job stream for IBM z/OS|JASMJ]], using the following at the end of the job stream:
<p class="code">//ASM    EXEC JASMP,HLQ=MYBUILD,   
//            MEM=RACFPARM         
</p>
<li>Run JASMSECJ from my TSO library; this assembles the RACFPARM source file in the <code>MYBUILD.M204.LOCAL.SRCLIB</code> and stores the object in <code>MYBUILD.M204V75.LOCAL.OBJLIB</code>.
<li>Copy the member LKONLNJ from <code>MYBUILD.M204V75.RKOBJLIB</code> to my TSO library, and customize LKONLN as follows:
<ul>
<li>Make these changes at the top of the job stream:
<p class="code">//            JCLLIB ORDER=(MYBUILD.M204V75.RKOBJLIB)
//LKONLN EXEC LKM204P,
//            HLQ=MYBUILD,
//            MQ=MQSERIES.SCSQLOAD
</p>
<li>Uncomment the <code>INCLUDE</code> line for LKNOSONL (that is, without RSQL).
<li>Uncomment the <code>INCLUDE</code> line for MQ.
<li>Uncomment the <code>INCLUDE</code> line for my external authorizer module (such as RACFOS and RACFPARM).
<li>Submit the LKONLNJ job from my TSO library, this creates ONLINE (and BATCH204 alias) in MYBUILD.M204V75.LOADLIB.
</ul>
<li>Perform a simple smoke test: run BATCH204 with 'DISPLAY ZAPS' and 'ROCKET' commands.
<li>To link the utilities, copy member LKALLUTJ from <code>MYBUILD.M204V75.RKOBJLIB</code> to my TSO library, and see all <code>&lt;&lt;</code> lines to customize for my site; submit the LKALLUTJ job.
<li>Ensure that any JCL that performs deferred index sorting for <var class="product">Model 204</var> version 7.5
(typically, FLOD jobs) uses the new <code>MYBUILD.M204V75.LOADLIB</code> for the E15 (OI15OS) and E35 (OI35OS) sort exits.
</ol>
 
==See also==
<ul>
<li>[[Upgrading to Model 204 version 7.5 on IBM z/VM CMS]]
<li>[[Upgrading to Model 204 version 7.5 on IBM z/VSE]]
</ul>
 
==Additional information==
Refer to the <i>[http://m204wiki.rocketsoftware.com/images/d/de/M204_V7R4_zOS_Install.pdf Rocket Model 204 Installation Guide for IBM z/OS, version 7.4]</i>, for additional installation information.
[[Category:Installation]]

Latest revision as of 21:09, 6 February 2017