|
|
| (39 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | See the installation page for the version of Model 204 you are installing, and the operating system you use. The list of supported operating systems for each version of Model 204 is [[Model 204 operating system support|shown on its own page]]. |
|
| |
|
| This page is [[under construction]].
| | ==Version 7.5 and later (z/OS)== |
| | [[Model 204 installation on IBM z/OS]] |
|
| |
|
| ==z/OS installation== | | <div id="7.5"></div> |
|
| |
|
| This section is [[under construction]].
| | ==Version 7.5 and later (VSE)== |
| | <!--Caution: <div> above--> |
| | [[Model 204 installation on IBM z/VSE]] |
|
| |
|
| ===Downloading the object library in z/OS=== | | ==Version 7.4== |
| | The version 7.4 installation guides provide useful reference information: |
|
| |
|
| 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.
| | <ul><var class="book"> |
| | <li>[[Media:M204_InstallzOS_V74.pdf|Rocket Model 204 Installation Guide for IBM z/OS, version 7.4]]</li> |
|
| |
|
| <div id="FUNU"></div> | | <li>[[Media:M204_InstallzVM_V74.pdf|Rocket Model 204 Installation Guide for IBM z/VM, version 7.4]] </li> |
| ===FUNU===
| |
|
| |
|
| | <li>[[Media:M204_InstallzVSE_V74.pdf|Rocket Model 204 Installation Guide for IBM z/VSE, version 7.4]] </li> |
| | </var></ul> |
|
| |
|
| This section lists installation considerations if you have your own user-written $functions module (FUNU).
| |
|
| |
|
| <ol>
| | [[Category:Installation]] |
| <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.
| |
| <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 an INCLUDE statement for FUNU; there is already one in the INCLUDE member (LKSQLONL or LKNOSONL) provided in the downloaded object library.
| |
| </ul>
| |
| | |
| ====Version 7.5 and later====
| |
| | |
| Starting with version 7.5 of <var class="product">Model 204</var>, all $functions are entered in AMODE 64. This requires you to modify the ENTER macro for each $function, and may require you to modify the code for proper addressing in AMODE 64.
| |
| <ul>
| |
| <li>The default ENTER macro (that is, without the ZMODE= operand) will not function in AMODE 64 - it will issue a BUG message (<i>label<i> <code>Bad AMODE, expect 31</code>) and produce a snap.
| |
| <li>In order to exploit QTBL above the 2G bar, any $functions which has arguments must be in AMODE 64. The ENTER macro should use ZMODE=GQ (the AMODE will remain as 64) and the code must be changed for proper addressing.
| |
| <li>If the $function does not have any arguments or if you will not exploit QTBL above the bar, and if your $function does not access any other data structures which may be above the bar, you can use the ZMODE=31 operand on the ENTER macro. This will cause your $function to switch to AMODE 31 at entry (and restore the AMODE upon exit).
| |
| <li>In any case, the AMODE issues need to be accounted for in any routines which your $function routine does a CCALL to.
| |
| </ul>
| |
| | |
| <div id="zOS_link_onl"></div>
| |
| | |
| ===Linking the Model 204 ONLINE load module===
| |
| <!--Warning: <div> above-->
| |
| | |
| After [[#Downloading the object library in z/OS|downloading the object library]], one of the members of ROKOB204 is
| |
| named [[#JZLONLN|JZLONLN - the basic ONLINE link JCL]]. You can use this 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>Only one modification 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>
| |
| </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 do, you must:
| |
| <ul>
| |
| <li>Prepare the appropriate xxxPARM object file (e.g., RACFPARM orACF2PARM), adding that to a *different* object library (with the same
| |
| DCB attributes as ROKOB204). We refer to this as your local object libary (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, 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 ROKOB204 DSN 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 *do not* need to apply any maintenance.
| |
| </ul>
| |
| </blockquote>
| |
| | |
| <div id="JZLONLN"></div>
| |
| | |
| ===Basic JCL to link ONLINE===
| |
| <!--Warning: <div> above-->
| |
| | |
| {{Template:JZLONLN}}
| |