|
|
| (347 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]] |
| | |
| <span style="color:#BA0000"><b>Note:</b> This page is currently under construction.</span>
| |
| | |
| <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><p>Using your [[Rocket M204 user ID]], go to the object files page and [[#downloading|download]] the components.</p></li>
| |
| | |
| <li>[[#uploading|FTP]] the downloaded components to the z/OS system on the IBM mainframe.</li>
| |
| | |
| <li>[[#bldLibs|Build]] the object library.
| |
| <p>Once you have built the object library, [[#notouch|<b>do not</b> modify it]].</p></li>
| |
| | |
| <li>Submit the job to [[#allocating|allocate additional data sets]] required for installation.</li>
| |
| | |
| <li>If you have your own user $functions (FUNU), you must [[#FUNU_7.5|modify FUNU for 64-bit addressing]] considerations and store the modified source in your local source library. Any user-defined messages (MSGU) should also be stored in your local source library.
| |
| | |
| <p>Then [[#Assembling_into_LOCAL.OBJLIB|assemble]] FUNU (and MSGU, if applicable) with the object file stored in your local object library.</p></li>
| |
| | |
| <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>
| |
| | |
| <li>Link the [[#lkonln|ONLINE]] (and, if you use them, the [[#link_ifam1|IFAM1]] and [[#link_ifam4|IFAM4]]) load modules.</li>
| |
| | |
| <li>Link the <var class="product">Model 204</var> [[#lkutils|utility load modules]].</li>
| |
| | |
| <li>Customize the [[#cics|CICS]] interface, then assemble and link the CICS modules.</li>
| |
| | |
| <li>Assemble and link-edit the [[#tso|TSO]] source modules.</li>
| |
| | |
| <li>Upgrade [[#softspy|SoftSpy]] for 7.5.</li>
| |
| </ol>
| |
| | |
| ==Components for installation==
| |
| {{Template:Model 204 installation components}}
| |
| | |
| ==Building the object and macro libraries==
| |
|
| |
| (back to [[#steps|installation overview]])
| |
| <div id="downloading"></div>
| |
| ===Downloading===
| |
| <!--Caution: <div> above-->
| |
| <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>
| |
| <p>
| |
| On the [https://model204.rocketsoftware.com/maint/maclist Model 204 macro library download page], click the <b>Download macro library</b> link beside the macro library that you want.</p>
| |
| | |
| <div id="uploading"></div>
| |
| ===Uploading (FTP)===
| |
| <!--Caution: <div> above-->
| |
| Once the object file and macro library 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 for both</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>
| |
| ===Job stream to build 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>[http://model204.rocketsoftware.com/download/new204lb.txt Click here to download] the job stream which is also shown here.
| |
| | |
| {{Template:JZNEWLB}}
| |
| | |
| <li>Place the job stream into your local TSO library.
| |
|
| |
| <li>On the first line, modify the JOB card according to your local standards.
| |
|
| |
| <li>On the final four lines, marked <code>2 <<</code> ... <code>5 <<</code> on the right:
| |
| <ol start="2">
| |
| <li>Modify the <code>VERSION=</code> parameter, specifying the two-digit version of <var class="product">Model 204</var> you are installing.
| |
| <li>Modify the <code>HLQ=</code> parameter, specifying the high-level qualifier(s) of all <var class="product">Model 204</var> installation datasets.
| |
| <li>Modify the <code>OBJINP=</code> parameter, using the DSN of the object library input file you uploaded to the mainframe.
| |
| <li>Modify the <code>MACINP=</code> parameter, using the DSN of the macro library input file you uploaded to the mainframe.
| |
| </ol>
| |
|
| |
| </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="allocating"></div>
| |
| ==Allocating data sets==
| |
| <!--Caution: <div> above-->
| |
| You will need to allocate additional data sets needed for the installation.
| |
|
| |
| <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 LKONLNJ; it is the ONLINE link job stream. 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 LKONLNJ (on lines indicated with <code><<</code>) which
| |
| can be changed in the copy in your local TSO library are described in the following table.
| |
|
| |
| The comments in <code>LKONLNJ</code> are complete so that you may not need to refer to the instructions below. The
| |
| <code>LKONLNJ PROC</code> is shown in a [[#LKONLNJ| sub-section below]]; it also has a set of instructions, which are more
| |
| succinct than the instructions in this 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 the downloaded object library, the Model204 load library in addition to the other datasets that are required for installation.
| |
| </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:
| |
| <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>3</th><td>The other modification frequently needed is to use an external authorizer such as RACF or ACF2. If you use an 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 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 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 <strong>do not</strong> 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>5</th><td>If you have an MQ series load library, you should 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 re-linking of the load module. You must also uncomment the INCLUDE MQ statement in the SYSLIN input.
| |
| </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="LKONLNJ"></div>
| |
| ===Job stream to link ONLINE===
| |
| <!--Caution: <div> above-->
| |
|
| |
| The downloaded object library contains a member named <code>LKONLNJ</code>, which is a job stream to link the <var class="product">Model 204</var> ONLINE load module.
| |
| <ol>
| |
| <li>Copy <code>LKONLNJ</code> into a local TSO library.
| |
| <li>Edit <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><<</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><<</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>
| |
|
| |
| The instructions in <code>LKONLNJ</code> should be sufficient to explain the edits you need to make. Those instructions make use of the numbers (1-4) and letters (A-C) 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.
| |
| | |
| For your reference, the <code>LKONLNJ</code> member of the downloaded object library contains the following:
| |
| {{Template:LKONLNJ}}
| |
| <div id="link_ifam1"></div>
| |
| | |
| ==Linking the Model 204 IFAM1 load module==
| |
| <!--Caution: <div> above-->
| |
|
| |
| (back to [[#steps|installation overview]])
| |
|
| |
| After [[#Downloading the object library|downloading the object library]], one of the members of RKOBJ204 is
| |
| named <code>LKIFAM1J</code>; it is the IFAM1 link job stream.
| |
| | |
| Copy this member into a local TSO library, modify this copy, and submit it
| |
| to link-edit the <var class="product">Model 204</var> IFAM1 load module, as described below.
| |
| | |
| ===Job stream to link IFAM1===
| |
|
| |
| The downloaded object library contains a member named <code>LKIFAM1J</code>, which is a job stream to link the <var class="product">Model 204</var> IFAM1 load module.
| |
| <ol>
| |
| <li>Copy <code>LKIFAM1J</code> 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><<</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>
| |
| For your reference, the <code>LKIFAM1J</code> member of the downloaded object library contains the following:
| |
| {{Template:LKIFAM1J}}
| |
| <div id="link_ifam4"></div>
| |
| | |
| ==Linking the Model 204 IFAM4 load module==
| |
| <!--Caution: <div> above-->
| |
|
| |
| (back to [[#steps|installation overview]])
| |
|
| |
| After [[#Downloading the object library|downloading the object library]], one of the members of RKOBJ204 is
| |
| named <code>LKIFAM4J</code>; it is the IFAM4 link job stream.
| |
| | |
| Copy this member into a local TSO library, modify this copy, and submit it
| |
| to link-edit the <var class="product">Model 204</var> IFAM4 load module, as described below.
| |
| | |
| ===Job stream to link IFAM4===
| |
|
| |
| The downloaded object library contains a member named <code>LKIFAM4J</code>, which is a job stream to link the <var class="product">Model 204</var> IFAM4 load module.
| |
| <ol>
| |
| <li>Copy <code>LKIFAM4J</code> 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><<</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-->
| |
|
| |
| (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>
| |
| | |
| ===Job stream to link utility load modules===
| |
|
| |
| The downloaded object library contains a member named <code>LKALLUTJ</code>, which is 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 <code>LKALLUTJ</code> for your configuration:
| |
| <ul>
| |
| <li>Replace the first line with a JOB card.
| |
| <li>Edit the three lines marked with <code><<</code> by entering your <i>downloadObjectLib</i> (twice) and <i>m204LoadLib</i> dataset names.
| |
| </ul>
| |
| <li>Submit <code>LKALLUTJ</code> to link the utility load modules.
| |
| </ol>
| |
|
| |
| For your reference, the <code>LKALLUTJ</code> member of the downloaded object library contains the following:
| |
| {{Template:LKALLUTJ}}
| |
| | |
| <div id="asm"></div>
| |
| | |
| ==Assembling into LOCAL.OBJLIB==
| |
| <!--Caution: <div> above-->
| |
| Use the following job stream to assemble a member from your Model 204 local source library.
| |
| | |
| Edit each line marked with <i>num</i> << (such as 1 <<) as described in the corresponding numbered comment.
| |
| {{Template:JZJASM}}
| |
| | |
| <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
| |
| | |
| Job stream 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) — 3390 tracks</td></tr>
| |
| </table>
| |
|
| |
| <div id="FUNU"></div>
| |
| | |
| ==CICS interface==
| |
| ===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>You must relink any CICS TPROCESS applications using AMODE=31, as AMODE=24 is not supported.</p></li>
| |
| </ul>
| |
| | |
| ===CICS Interface overview information===
| |
| For an overview of the CICS Interface, including storage requirements and a listing of CICS interface components, see [[CICS interface]].
| |
| | |
| <div id="cics"></div>
| |
| ===Installation steps for the CICS interface===
| |
| <!--Caution: <div> above-->
| |
| To install the CICS interface:
| |
| <ol>
| |
| <li>Customize the interface by copying the CICFG copy member into your local maclib 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>Assemble and link the CICS modules. To do this, run job LKCICSJ.</li>
| |
| </ol>
| |
| | |
| ===Updating the CICS System Definition (CSD)===
| |
| You can update the CSD 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><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 CEDAM204 member, then define the transactions and programs 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 example above, 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="tso"></div>
| |
| ==TSO interface==
| |
| <!--Caution: <div> above-->
| |
| The Model 204 TSO Interface enables the TSO Interface to communicate with
| |
| a Model 204 Online, using CRAM.
| |
| <p>(For detailed information on CRAM, see [[Defining the user environment (CCAIN)]].)</p>
| |
| | |
| 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.
| |
| <p>To install TSO:</p>
| |
| <ol>
| |
| <li>If you are using TSO extensions, modify TSFS in the maclib 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 TSO modules, using the LKTSOJ job.</li>
| |
| </ol>
| |
| | |
| ==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>
| |
| | |
| Job stream modifications for OBJLIB= points to [[#local|local object library]].
| |
| | |
| <div id="softspy"></div>
| |
| ==Upgrading SoftSpy for 7.5==
| |
| <!--Caution: <div> above-->
| |
| The SoftSpy procedure file, SPYPROC, is distributed in a dump format that you must download to a workstation file (in binary form), upload to your z/OS system, and then RESTORE into a Model 204 SOUL file.
| |
| | |
| Download SPYPROC from this page:
| |
| https://m204.rocketsoftware.com/maint/ullist?nickname=ROCKET
| |
| | |
| For detailed instructions, see:
| |
| http://m204wiki.rocketsoftware.com/index.php?title=Web_help_download_SOUL_files
| |
| | |
| ==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 it 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 the object library (M204V75.OBJ) from the downloads page.
| |
|
| |
| <li>Upload to the mainframe, in <b>Binary</b> format, with settings FB/80/6400, as <code>M204.V75.RKOBJ204.DISTRIB.OBJ</code>.
| |
|
| |
| <li>Download the macro library (M204V75_ZOS.MAC) from the downloads page.
| |
|
| |
| <li>Upload to the mainframe, in <b>Binary</b> format, with settings FB/80/6400, as <code>M204.V75.RKMAC204.DISTRIB.MAC</code>.
| |
|
| |
| <li>Create the member MYBLDOB in my TSO library by copying
| |
| the job stream from [[#bldLibs|"Job stream to build the object and macro libraries"]], using the following at the end of the job stream:
| |
| <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 the member LKONLNJ from <code>M204.V75.RKOBJ204.OBJLIB</code> to my TSO libary, and customize LKONLN as follows:
| |
| <ul>
| |
| <li>Make these changes at the top of the job stream:
| |
| <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 LKONLNJ 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><<</code> lines to customize for my site; submit this job stream.
| |
|
| |
| <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>M204.V75.LOADLIB</code> for the E15 (OI15OS) and E35 (OI35OS) sort exits.
| |
| </ol>
| |
| | |
| ==See also==
| |
| <ul>
| |
| <li>[[Model 204 z/VM CMS installation]]
| |
| <li>[[Model 204 z/VSE installation]]
| |
| </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]]
| |