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
 
(503 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This page describes the installation steps for <var class="product">Model 204</var> on the z/OS operating system.  The information applies to installation of <var class="product">Model 204</var> starting with version 7.5.  In substance the information is very similar to installation of previous versions of <var class="product">Model 204</var>, but starting with version 7.5, the installation process is new, and self-contained.  Therefore,
#REDIRECT [[Model 204 installation on IBM z/OS]]
<table><tr><td>Do not use the installation process or materials (object files, link edit jobs, documentation, etc.) for previous versions of <var class="product">Model 204</var> when you are installing version 7.5 or later.</td></tr></table>
The steps for installing <var class="product">Model 204</var> are:
<ol>
<li>Read the section titled "Important instructions for version <i>m.n</i>", for the version of <var class="product">Model 204</var> you are installing.  This section also contains an example of the complete download/installation workflow. <b>You may wish to consult that first.</b>
</ol>
<div id="always"></div><p>In addition to those version-specific considerations, the following items are performed for every version of <var class="product">Model 204</var>:</p>
<ol start="2">
<li>[[#FUNU|Assemble FUNU]] (and optionally MSGU), if you have user-written $functions.
<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>
Step 2 above, [[#FUNU|assembling FUNU]] (and, of course, any FUNU considerations for the version of <var class="product">Model 204</var> being installed), must be performed <b>before linking the ONLINE/IFAM1/IFAM4</b> load modules.  If there are any other ordering requirements in the installation workflow, they will be described in the section titled "Important instructions for version <i>m.n</i>" for the version you are installing.
Before performing the above steps, you will need to [[#download|download the components]] for the installation.  Be sure to read and heed the note that the object library is [[#notouch|not to be modified]].
<p>&nbsp;</p>
<div class="toclimit-3">__TOC__</div>
==Components for installation==
{{Template:Model 204 installation components}}
==Important instructions for version 7.5==
In addition to the steps performed [[#always|for every version]], installation of version 7.5 requires that:
<ul>
<li>if you have your own user $functions (FUNU),
<ul><li>modify [[#FUNU_7.5|FUNU for 64-bit addressing]] considerations (FUNU must be prepared as the first step during installation</li></ul>
<li>after you [[#lkutils|link the utility load modules]], be sure to use your version 7.5 load library for the OI15OS and OI35OS load modules used in the deferred index sort exits for FLOD
<li>if you use XDM CRAM, either:
<ul><li>have installed the version V7R4 XDM load modules</li></ul>
or
<ul><li>have installed the version V7R1 XDM load modules, and applied early warnings 710EW168 and 710EW199.
</li></ul>
or
<ul><li>link the [[#link_XDM|XDM load modules]] from the downloaded object library</li></ul>
</ul>
===Example of complete download/installation workflow===
This is an example for a site which uses the RACF external authorizer, but otherwise requires no customization, e.g., the site does not use MQ/series nor does it have its own FUNU.  The following names are chosen arbitrarily:
<ul>
<li>the member name <code>MYBLDOB</code>
</ul>
and the DSNs
<ul>
<li><code>M204.V75.RKOBJ204.DISTRIB</code>
<li><code>M204.V75.RKOBJ204.OBJLIB</code>
<li><code>M204.V75.LOCAL.OBJLIB</code>
<li><code>M204.V75.LOADLIB</code>.
</ul>
====Download====
<ol>
<li>Select/copy NEWOBJLB PROC from "Download object files" web page (in "Model 204 object library" section of ".. uploaded to the mainframe" help topic)
<ul>
<li>Then paste that proc into MYBLDOB member of my TSO library, adding, after the bottom (<code>PEND</code> statement):
<p class="code">//BLDOBJLB EXEC NEWOBJLB,
//            INP=M204.V75.RKOBJ204.DISTRIB
//            LIB=M204.V75.RKOBJ204.OBJLIB
</p>
</ul>
<li>Download object file from web site (M204V75.OBJ)
<li>Upload to mainframe, Binary, FB/80/3120, as <code>M204.V75.RKOBJ204.DISTRIB</code>
<li>Run MYBLDOB from my TSO library; this deletes and then creates <code>M204.V75.RKOBJ204.OBJLIB</code>
</ol>
====Assemble and link====
<ol start="5">
<li>Allocate <code>M204.V75.LOCAL.OBJLIB</code> and copy in:
<ul>
<li>RACFPARM
</ul>
<p class="note"><b>Note:</b> We need a step to assemble it - or are we going to sleaze out and not instruct them to assemble a new RACFPARM?  In any case this requires downloading the source lib.
</p>
<li>Allocate <code>M204.V75.LOADLIB</code> and APF authorize it.
<p class="note"><b>Note:</b> We need info about allocation (simple, just size info) and APF authorization (maybe link to a page discussing it?)</p>
<li>Copy member LKONLN2 from <code>M204.V75.RKOBJ204.OBJLIB</code> to my TSO libary, and see all <code>&lt;&lt;</code> lines to customize for my site
<ul>
<li>only customization I need is for RACF
<li>use <code>M204.V75.LOADLIB</code> as SYSLMOD DD
<li>Submit LKONLN2 from my TSO library, this creates ONLINE (and BATCH204 alias) in M204.V75.LOADLIB - I don't need IFAM1 nor IFAM4.
</ul>
<li>Simple smoke test - run BATCH204 with 'DISPLAY ZAPS' and 'ROCKET' commands
<li>Copy member LKALLUT2 from <code>M204.V75.RKOBJ204.OBJLIB</code> to my TSO libary, 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.  This is automatic with standard FLOD JCL.
</ol>
<table><tr><th>Reminder: the above section is an example for one typical installation workflow; the remainder of this page explains all installation steps in detail</th></tr></table>
<div id="download"></div>
==Downloading the object library and other components==
<!--Caution: <div> above-->
This section is [[under construction]].  It will be cribbed from the instructions on the download page.  A key thing mentioned is our use of RKOBJ204 in the documentation to refer to the downloaded object library.
<div id="notouch"></div>
===Do not modify RKOBJ204===
<!--Caution: <div> above-->
Once you have created the object library ("RKOBJ204") on your z/OS system, do not update it in any way (unless, in rare circumstances, you download it for the same version of <var class="product">Model 204</var>).
Also, do not 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 separate object library (also designated for use with version 7.5).
<div id="lkonln"></div>
==Linking the Model 204 ONLINE load module==
<!--Caution: <div> above-->
<div id="onlnTable"></div>
<p 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.</p>
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.
<p class="note"><b>Note:</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.</p>
<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 un-comment  the INCLUDE RKOBJ204(<b>LKSQLONL</b>) statement.
<li>To link an ONLINE which <b>does not</b> use RSQL, you must un-comment the INCLUDE RKOBJ204(<b>LKNOSONL</b>) statement.
</ul>
Do not un-comment 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>[[#asm_secparm|Assemble the xxxPARM]] for your external authorizer, adding the object file (e.g., RACFPARM or ACF2PARM) to a *different* object library (with the same DCB attributes as RKOBJ204).  We refer to this as your local object library (it will also be used for other assemble output, such as your FUNU).
<li>In the SYSLIN DD *, un-comment the appropriate INCLUDE statement(s) for your external authorizer. <p class="note"><b>Note:</b> 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.</p>
</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 *do
not* need to get a new one from the web site.
<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 marked with <code>&lt;&lt;</code> and numbers. The numbers correspond to numbered steps in the comments following the code.
</ul>
<li>Submit <code>LKONLN2</code> to link the ONLINE load module.
</ol>
The instructions in <code>LKONLN2</code> should be sufficient to explain the edits you need to make. More expansive instructions are shown in the [[#onlnTable|table above]] which further explain link-editing the ONLINE load module.
{{Template:JZJONLN}}
<div id="lkutils"></div>
==Linking the Model 204 utility load modules==
<!--Caution: <div> above-->
{{Template:Linking utility load modules intro}}
===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 lines marked with <code>&lt;&lt;</code> by entering your <i>downloadObjectLib</i> and <i>m204LoadLib</i> dataset names.
</ul>
<li>Submit <code>LKALLUT2</code> to link the utility load module.
</ol>
{{Template:JZJALLUT}}
<!-- Right now template doesn't exist, but it can be reinstated to LIBWIKI EXEC if it should be...
A prototype copy of the PROC which this JCL invokes is shown
below; the download process provides the proper concatenation of RKOBJ204 members for the <code>SYSLIN DD</code>.
The included member list
depends on the version of <var class="product">Model 204</var> being installed &mdash;
<ul>
<li>you can examine the prototype shown here but you do <b>not</b> need to modify it:
</ul>
{{Template:JZLALLUT}}
-->
<div id="FUNU"></div>
==FUNU and optional MSGU==
<!--Caution: <div> above-->
This section lists installation considerations if you have your own user-written $functions module (FUNU).  These instructions apply to every installation of <var class="product">Model 204</var>.
<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 which have their own FUNU also have their own MSGU module.  If so, MSGU must also be assembled before linking
ONLINE/IFAM1/IFAM4.
</ul>
</blockquote>
If you have your own FUNU, the following items are required for installation of every version of <var class="product">Model 204</var>:
<ol>
<li>After making any changes required for the version of <var class="product">Model 204</var> you are installing, run the job to [[#Assembling FUNU|assemble FUNU]] into your local object library.  (This job will also be used to assemble MSGU, if you have it.)
<li>Be sure that you have modified 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).
<li>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.
</ol>
In addition, see additional FUNU considerations as described in the following sections:
<div id="FUNU_7.5"></div>
===FUNU changes for versions 7.5 and later===
<!--Caution: <div> above-->
{{Template:FUNU changes for 7.5}}
==See also==
<ul>
<li>[[Model 204 CMS installation]]
<li>[[Model 204 VSE installation]]
</ul>
[[Category:Model 204 installation and maintenance]]

Latest revision as of 21:09, 6 February 2017