|
|
| (521 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 <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 <b>example of the complete download/installation workflow</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 [[#link_onln|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> [[#link_utils|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 nor extracted]].
| |
|
| |
| <p> </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>after you [[#link_utils|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>link the [[#link_XDM|XDM load modules]] from the downloaded object library</li></ul>
| |
|
| |
| <li>if you have your own user $functions (FUNU),
| |
| <ul><li>modify [[#FUNU_7.5|FUNU for 64-bit addressing]] considerations</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.ROKOB204.DISTRIB</code>
| |
| <li><code>M204.V75.ROKOB204.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.ROKOB204.DISTRIB
| |
| // LIB=M204.V75.ROKOB204.OBJLIB
| |
| </p>
| |
| </ul>
| |
|
| |
| <li>Download object file from web site (M204V75.OBJ)
| |
|
| |
| <li>Upload to mainframe, Binary, FB/80/3120, as <code>M204.V75.ROKOB204.DISTRIB</code>
| |
|
| |
| <li>Run MYBLDOB from my TSO library; this deletes and then creates <code>M204.V75.ROKOB204.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> <b>(or INSTALL.LOADLIB?)</b> 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 JZLONLN from <code>M204.V75.ROKOB204.OBJLIB</code> to my TSO libary, and follow instructions there 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 JZLONLN 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>Create and submit following jobstream to link the utility load modules:
| |
|
| |
| <p class="code">//name JOB jobCardParameters
| |
| // JCLLIB ORDER=(M204.V75.ROKOB204.OBJLIB)
| |
| //LKALLUT EXEC LKALLUT,
| |
| // ROKOB204=M204.V75.ROKOB204.OBJLIB
| |
| // SYSLMOD=M204.V75.LOADLIB
| |
| </p>
| |
|
| |
| <li>Ensure that any JCL which performs deferred index sorting
| |
| for <var class="product">Model 204</var> version 7.5 use
| |
| (typically, file load (FLOD/FILELOD) jobs) uses the new <code>M204.V75.LOADLIB</code> for the E15 (OI15OS)and E35 (OI35OS) sort exits.
| |
|
| |
| </ol>
| |
|
| |
| <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 ROKOB204 in the documentation to refer to the downloaded object library.
| |
|
| |
| <div id="notouch"></div>
| |
| ===Do not modify ROKOB204===
| |
| <!--Caution: <div> above-->
| |
| Once you have created the object library ("ROKOB204") on your z/OS system, do not update it in any way (except via a new download for the same version of <var class="product">Model 204</var>). Also, you will <b>not need to copy</b> any of the members anywhere to submit jobs, with the exception of copying the [[#link_onln|online link step]] (or [[#link_ifam1|IFAM1 link step]] or [[#link_ifam4|IFAM4 link step]]) to modify it for submission.
| |
|
| |
| 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). Note that this object library should have the same DCB characteristics as ROKOB204.
| |
|
| |
| <div id="link_onln"></div>
| |
| ==Linking the Model 204 ONLINE load module==
| |
| <!--Caution: <div> above-->
| |
|
| |
| <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 ROKOB204 is
| |
| named [[#JZLONLN|JZLONLN - the basic ONLINE link JCL]]. You can use copy this into a job to link-edit the <var class="product">Model 204</var> online. It contains a number of choices which you can make to modify this basic JCL; each choice is indicated in the JCL by a line which ends with <code><<</code>.
| |
|
| |
| <p>Most of the choices are "optional", in the sense that a working ONLINE does not require the indicated modification, although, for many customers' environments, a modification will be needed, for example, to select an external authorizer.
| |
| </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 ROKOB204(<b>LKSQLONL</b>) statement.
| |
| <li>To link an ONLINE which <b>does not</b> use RSQL, you must un-comment the INCLUDE ROKOB204(<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 ROKOB204). 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 - with the same DCB attributes as ROKOB204 - if you have not already created one 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 ROKOB204.
| |
| </td></tr>
| |
|
| |
| <tr><th>4</th><td>Hence, there are two choices for the ROKOB204 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 ROKOB204 library for the second concatenation.
| |
| <li>If you do not have a local object library, there is only one dataset for the ROKOB204 DD - your ROKOB204 library.
| |
| </ul>
| |
| </td></tr>
| |
|
| |
| <tr><th>5</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="JZLONLN"></div>
| |
| ===Basic JCL to link ONLINE===
| |
| <!--Caution: <div> above-->
| |
|
| |
| The following exhibits the JCL to link the ONLINE load module; however, since it is present (and up to date) in the object library as member <code>JZLONLN</code>, you should copy it from there to use to submit the ONLINE link job.
| |
|
| |
| {{Template:JZLONLN}}
| |
|
| |
| <div id="link_utils"></div>
| |
| ==Linking the Model 204 utility load modules==
| |
| <!--Caution: <div> above-->
| |
|
| |
| {{Template:Linking utility load modules intro}}
| |
|
| |
| The downloaded object library contains a member, named <code>LKLALLUT</code>, which is a JCL PROC to link the <var class="product">Model 204</var> utility load modules. This PROC is invoked as follows; place your <i>downloadObjectLib</i> and <i>m204LoadLib</i> dataset names on the three lines indicated with <code><<</code>:
| |
|
| |
| <p class="code">//name JOB jobCardParameters
| |
| // JCLLIB ORDER=(<i>downloadObjectLib</i>) <<
| |
| //LKALLUT EXEC LKALLUT,
| |
| // ROKOB204=<i>downloadObjectLib</i>, <<
| |
| // SYSLMOD=<i>m204LoadLib</i> <<
| |
| </p>
| |
|
| |
| The exact contents of <code>LKLALLUT</code> in the object library will depend on the version of <var class="product">Model 204</var> being installed — you do <b>not</b> need to modify it. A prototype copy of it is shown here; the download process provides the proper concatenation of ROKOB204 members for the <code>SYSLIN DD</code>:
| |
|
| |
| {{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 ROKOB204 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]]
| |