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

From m204wiki
Jump to navigation Jump to search
No edit summary
 
(409 intermediate revisions by 8 users not shown)
Line 1: Line 1:
This page describes the installation steps for <var class="product">Model 204</var> version 7.5 on the IBM z/OS operating system.
#REDIRECT [[Model 204 installation on IBM z/OS]]
 
<table><tr><td><b>Model 204 version 7.5 is an upgrade</b> to Model 204 version 7.4.
<p>In order to install version 7.5, <b>you must have version 7.4 and the latest Autofix set of Early Warnings installed</b> on your system.</p> </td></tr></table>
With 7.4 and all Early Warnings installed, to upgrade to version 7.5 simply download, upload, and link the 7.5 object modules available from the downloads page. Details are provided below.
<div class="toclimit-3">__TOC__</div>
==Before you begin==
<ul>
<li>For system requirements for this installation, see the [[Release notes for Model 204 version 7.5#Operating system requirements|7.5 Release notes]].</li>
<li>Ensure that you have a [[Rocket M204 user ID|user ID]] to use for downloads (if you have a Sirius user ID, that is sufficient).</li>
</ul>
<div id="steps"></div>
==Overview of installation steps==
This section summarizes the steps for upgrading to <var class="product">Model 204</var> version 7.5. Details for each step are provided later on the page.
 
An [[#Example_workflow_for_7.5:_download_through_installation|example workflow]] is provided at the end of the page.
<ol>
<li>Using your [[Rocket M204 user ID]], [https://model204.rocketsoftware.com/maint/objlist download the components].
[[#notouch|<b>Do not</b> modify the object library]].
<li>If you have your own user $functions (FUNU), you must [[#FUNU_7.5|modify FUNU for 64-bit addressing]] considerations; the object file is stored in your [[#local|local object library]]. Then assemble FUNU and user-defined messages (if any), MSGU.</li>
<li>Allocate an authorized <var class="product">Model 204</var> load library for the version you are installing (in almost all installations).
<li>If you use an external authorizer (such as RACF) for <var class="product">Model 204</var>, [[#secparm|assemble xxxPARM]]; the object file is stored in your [[#local|local object library]].  If you use the dynamic xxxPARM configuration, link xxxPARM into the <var class="product">Model 204</var> load library.
<li>Link the [[#lkonln|ONLINE]] (and, if you use them, the [[#link_ifam1|IFAM1]] and [[#link_ifam4|IFAM4]]) load modules.
<li>Link the <var class="product">Model 204</var> [[#lkutils|utility load modules]].
</ol>
 
==Components for installation==
{{Template:Model 204 installation components}}
==Building the object and macro libraries==
<!--Caution: <div> above-->
(back to [[#steps|installation overview]])
===Downloading===
<p>
On the [https://model204.rocketsoftware.com/maint/objlist Model 204 object file download page], click the <b>Download object file</b> link beside the object that you want.</p>
 
===Uploading===
 
Once the object files are downloaded to the workstation, ftp them to the z/OS system on the IBM mainframe.
 
Specify these characteristics for the upload files:
 
<table>
<tr><th>transfer format</th> <td>binary</td></tr>
<tr><th>record format</th> <td>FB</td></tr>
<tr><th>record size</th> <td>80 for object and macro libraries</td></tr>
<tr><th>block size</th> <td>6400 for object and macro libraries</td></tr>
<tr><th>storage size</th><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===
<!--Caution: <div> above-->
Once you have uploaded the object and macro library input streams to the mainframe, use the following approach to build the object and macro libraries:
<ol>
<li>Cut and paste the following jobstream into your local TSO library:
{{Template:Building RKOBJ204 and RKMAC204}}
<li>On the first line, modify the JOB card according to your local standards.
<li>On the final two lines:
<ul>
<li>Modify the <code>INP=</code> parameter, using the DSN of the file you uploaded to the mainframe.
<li>Modify the <code>OBJLIB=</code> parameter, choosing the DSN for your <var class="product">Model 204</var> object library.
<li>Modify the <code>MACLIB=</code> parameter, choosing the DSN for your <var class="product">Model 204</var> macro library.
</ul>
You can, of course, use whatever dataset names you want
&mdash; note that in our documentation, we refer to the object
library as <b>RKOBJ204</b> and to the macro
library as <b>RKMAC204</b>.
</ol>
<div id="notouch"></div>
 
===Do not modify RKOBJ204===
<!--Caution: <div> above-->
Once you have built the object library ("RKOBJ204") on your z/OS system, <b>do not</b> modify it in any way.
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.  For those object files which you might assemble (for example, FUNU or RACFPARM), you should place those into a [[#local|local object library]].
<div id="lkonln"></div>
 
==Linking the Model 204 ONLINE load module==
<!--Caution: <div> above-->
(back to [[#steps|installation overview]])
<div id="onlnTable"></div>
<blockquote class="note"><b>Note:</b> If you have your own FUNU, it must be [[#FUNU|assembled]] <b>before linking the ONLINE/IFAM1/IFAM4</b> load modules.</blockquote>
After [[#Downloading the object library|downloading the object library]], one of the members of RKOBJ204 is
named LKONLN2; it is the ONLINE link jobstream.  Copy this into a local TSO library, modify it and submit it
to link-edit the <var class="product">Model 204</var> ONLINE load module.
The items in LKONLN2 (on lines indicated with <code>&lt;&lt;</code>) which
can be changed in the copy in your local TSO library are described in the following table.
The comments in <code>LKONLN2</code> are complete so that you may not need to refer to the instructions below.  The
<code>LKONLN2 PROC</code> is shown in a [[#LKONLN2| sub-section below]]; it also has a set of instructions, which are more
succinct than the instructions in this table.
<blockquote class="note"><b>Note: Must revise! ??</b>The following table describes the old approach, which did not contain a JCL PROC.  The "succinct instructions" are up to date, and should be used to update this table.</blockquote>
<table class="thJustBold">
<tr><th>1</th><td>One of the modifications is <b>always required</b>, based on whether the ONLINE is to use RSQL (for Connect*) or not:
<ul>
<li>To link an ONLINE which <b>does</b> use RSQL, you must uncomment  the INCLUDE RKOBJ204(<b>LKSQLONL</b>) statement.
<li>To link an ONLINE which <b>does not</b> use RSQL, you must uncomment the INCLUDE RKOBJ204(<b>LKNOSONL</b>) statement.
</ul>
<b>Do not</b> uncomment both of them.
</td></tr>
<tr><th>2</th><td>The other modification frequently needed is to use an external authorizer such as RACF or ACF2.  If you use and external authorizer, you must:
<ul>
<li>[[#secparm|Assemble the xxxPARM]] for your external authorizer, adding the object file (e.g., RACFPARM or ACF2PARM) to your [[#local|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 upon your configuration.<li>If you use ACF2, there are two INCLUDE statements to be un-commented; one refers to your system ACF2 library.  You must un-comment the ACF2 DD as well, and fill in the DSN for that library.</ul></blockquote>
</ul>
</td></tr>
<tr><th>3</th><td>If you have other programs which you assemble for your Model 204 ONLINE module, for example, [[#FUNU|FUNU]], they should be assembled into your local object library (creating one, if you have not already done so for the external authorizer xxxxPARM object file).  You do *not* need to add additional INCLUDE statements for FUNU or other locally assembled object files - they are already present in the include streams from RKOBJ204.
</td></tr>
<tr><th>4</th><td>Hence, there are two choices for the RKOBJ204 DD statement:
<ul>
<li>If you have a local object library, fill that in for the first concatenation, and fill in the DSN of the RKOBJ204 library for the second concatenation.
<li>If you do not have a local object library, there is only one dataset for the RKOBJ204 DD - your RKOBJ204 library.
</ul>
<tr><th>5</th><td>If you have an MQ series load library, you should un-comment the <code>MQOLIB</code> DD statement, and provide the correct DSN.  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 re-linking of the load module.
</td></tr>
<tr><th>6</th><td>Finally, change the DSN of the SYSLMOD DD to the load module library you have allocated for it.
</td></tr>
</table>
The modified JCL is now ready to run.
<blockquote class="note"><b>Notes:</b>
<ul>
<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>The object library has the authorization zap pre-applied, so you <b>do not</b> need to get a new one from the web site. (The preapplied zap will authorize Model 204 itself and any separately purchased products such as MP/204 and SirScan.)
<li>It also has the maintenance zaps (as of the time the stream was
prepared) pre-applied, so you <b>do not</b> need to apply any maintenance.
</ul>
</blockquote>
<div id="LKONLN2"></div>
===Jobstream to link ONLINE===
<!--Caution: <div> above-->
The downloaded object library contains a member named <code>LKONLN2</code>, which is a jobstream to link the <var class="product">Model 204</var> ONLINE load module.
<ol>
<li>Copy <code>LKONLN2</code> into a local TSO library.
<li>Edit <code>LKONLN2</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the lines, near the top of the jobstream, marked with 1-6 followed by <code>&lt;&lt;</code>. The numbers correspond to numbered steps in the comments following these lines.
<li>As needed, edit the lines after <code>SYSLIN DD *</code> which 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>LKONLN2</code> job to link the ONLINE load module.
</ol>
The instructions in <code>LKONLN2</code> should be sufficient to explain the edits you need to make. Those instructions make use of the numbers (1-6) and letters (A-D) marking lines which need to be edited, or examined for editing. More expansive instructions are shown in the [[#onlnTable|table above]] which further explain link-editing the ONLINE load module. 
<div id="lkutils"></div>
 
==Linking the Model 204 utility load modules==
<!--Caution: <div> above-->
(back to [[#steps|installation overview]])
 
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>
 
===Jobstream to link utility load modules===
The downloaded object library contains a member named <code>LKALLUT2</code>, which is a jobstream to link the <var class="product">Model 204</var> utility load modules.
<ol>
<li>Copy <code>LKALLUT2</code> into a local TSO library.
<li>Edit <code>LKALLUT2</code> for your configuration:
<ul>
<li>Replace the first line with a JOB card.
<li>Edit the three lines marked with <code>&lt;&lt;</code> by entering your <i>downloadObjectLib</i> (twice) and <i>m204LoadLib</i> dataset names.
</ul>
<li>Submit <code>LKALLUT2</code> to link the utility load modules.
</ol>
For your reference, the <code>LKALLUT2</code> member of the downloaded object library contains the following:
{{Template:JZJALLUT}}
<div id="lkcram"></div>
 
<div id="secparm"></div>
 
==Assembling (and optionally linking) xxxPARM==
<!--Caution: <div> above-->
(back to [[#steps|installation overview]])
This section is [[under construction]].
 
===Assemble xxxPARM===
TBD
 
Jobstream modifications for OBJLIB= points to [[#local|local object library]].
 
===If using dynamic xxxPARM, link it===
TBD
<div id="local"></div>
===Local object library===
<!--Caution: <div> above-->
If you need to assemble a [[#secparm|xxxPARM]] or [[#FUNU|FUNU]] module, the output of those assembly step(s) is kept separate from the downloaded object library.
To assemble the module, allocate a local object library with the following characteristics:
<table>
<tr><th>DCB</th><td><ul><li>LRECL=80</li><li>BLKSIZE=6400</li><li>RECFM=FB</li></ul></td></tr>
<tr><th>SPACE</th><td>TRK,(100,10,10) &mdash; 3390 tracks</td></tr>
</table>
<div id="FUNU"></div>
 
==FUNU and optional MSGU==
<!--Caution: <div> above-->
(back to [[#steps|installation overview]])
This section lists installation considerations if you have your own user-written $functions module (FUNU).
<blockquote class="note">
<b>Notes:</b>
<ul>
<li>If you have your own FUNU, it must be assembled as <b>before linking the ONLINE/IFAM1/IFAM4</b> load modules.
<li>Some customers who have their own FUNU also have their own MSGU module.  If so, MSGU must also be assembled before linking
ONLINE/IFAM1/IFAM4.
</ul>
</blockquote>
<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 assembly===
<!--Caution: <div> above-->
 
<ol>
<li>After making any changes required for the version of <var class="product">Model 204</var> you are installing, run the job to [[#asmFUNU|assemble FUNU]] into your local object library.  (This job will also be used to assemble MSGU, if you have it.)
<li>Modify the [[#JZLONLN|JCL to link ONLINE]] to reference your local object library. (The RKOBJ204 DD statement will be the concatenation of your local object library and the downloaded object library.)
<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>
</ol>
 
<other steps TBD>
 
Jobstream modifications for OBJLIB= points to [[#local|local object library]].
 
==Example workflow for 7.5: download through installation==
<table><tr><th>Reminder: This section shows one typical installation workflow; the previous sections on this page provide the actual installation steps in detail.</th></tr></table>
This is an example for a site which does not use RSQL.
It uses the RACF external authorizer, and does not have its own FUNU. The IBM system MQ loadlib is <code>MQSERIES.SCSQLOAD</code> (this is typical in z/OS).
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>M204.V75.RKOBJ204.DISTRIB.OBJ</code>
<li><code>M204.V75.RKOBJ204.OBJLIB</code>
<li><code>M204.V75.RKMAC204.DISTRIB.MAC</code>
<li><code>M204.V75.RKMAC204.MACLIB</code>
<li><code>M204.V75.LOCAL.OBJLIB</code>
<li><code>M204.V75.LOADLIB</code>
</ul>
===Build RKOBJ204===
<ol>
<li>Download object library from web site (M204V75.OBJ)
<li>Upload to mainframe, Binary, FB/80/6400, as <code>M204.V75.RKOBJ204.DISTRIB.OBJ</code>
<li>Download macro library from web site (M204V75_ZOS.MAC)
<li>Upload to mainframe, Binary, FB/80/6400, as <code>M204.V75.RKMAC204.DISTRIB.MAC</code>
<li>Create member MYBLDOB in my TSO library by copying
the jobstream from [[#bldLibs|"Building the object and macro libraries"]], using the following at the end of the jobstream:
<p class="code">//BLDLIBS EXEC NEW204LB,
//            OBJINP=M204.V75.RKOBJ204.DISTRIB.OBJ,
//            OBJLIB=M204.V75.RKOBJ204.OBJLIB,
//            MACINP=M204.V75.RKMAC204.DISTRIB.MAC,
//            MACLIB=M204.V75.RKMAC204.MACLIB
</p>
<li>Run MYBLDOB from my TSO library; this deletes and then creates <code>M204.V75.RKOBJ204.OBJLIB</code> and
<code>M204.V75.RKMAC204.MACLIB</code>.
</ol>
===Assemble and link===
<ol start="7">
<li>Allocate <code>M204.V75.LOCAL.OBJLIB</code> and copy in:
<ul>
<li>RACFPARM
</ul>
<li>Allocate <code>M204.V75.LOADLIB</code> and APF authorize it.
<blockquote class="note"><b>Note:</b> We need info about allocation (simple, just size info) and APF authorization (maybe link to a page discussing it??)</blockquote>
<li>Copy member LKONLN2 from <code>M204.V75.RKOBJ204.OBJLIB</code> to my TSO libary, customizing the following:
<ul>
<li>Make these changes at the top of the jobstream:
<p class="code">//            JCLLIB ORDER=(M204.V75.RKOBJ204.OBJLIB)
//LKONLN EXEC LKONLN,
//            RKOBJ204=M204.V75.RKOBJ204.OBJLIB,
//            SYSLMOD=M204.V75.LOADLIB,
//            MQ=MQSERIES.SCSQLOAD,
//            LOCALOBJ=M204.V75.LOCAL.OBJLIB    For RACFPARM
</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 your external authorizer module (such as RACFOS and RACFPARM).
<li>Submit LKONLN2 from my TSO library, this creates ONLINE (and BATCH204 alias) in M204.V75.LOADLIB.
</ul>
<li>Perform a simple smoke test: run BATCH204 with 'DISPLAY ZAPS' and 'ROCKET' commands.
<li>To link the utilities, copy member LKALLUT2 from <code>M204.V75.RKOBJ204.OBJLIB</code> to my TSO library, and see all <code>&lt;&lt;</code> lines to customize for my site; submit this jobstream.
<li>Ensure that any JCL which performs deferred index sorting
for <var class="product">Model 204</var> version 7.5
(typically, FLOD jobs)
uses the new <code>M204.V75.LOADLIB</code> for the E15 (OI15OS)and E35 (OI35OS) sort exits.
</ol>
 
<div id="download"></div>
 
==See also==
<ul>
<li>[[Model 204 CMS installation]]
<li>[[Model 204 VSE installation]]
</ul>
 
==Additional information==
Refer to the <i>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