Model 204 installation on IBM z/VSE: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
Line 28: Line 28:
Review the following high-level summary of steps before you begin downloading the <var class="product">Model 204</var> version 7.5 files.
Review the following high-level summary of steps before you begin downloading the <var class="product">Model 204</var> version 7.5 files.
   
   
For an example, see [[#Example_workflow_for_7.5:_download_through_installation|Example workflow for 7.5: download through installation]].
For an example, see [[Example workflow for 7.5: download through installation]].
   
   
<ol>
<ol>
Line 41: Line 41:
<li>[[#FUNU_7.5|modify FUNU for 64-bit addressing]] considerations and store the modified source in your V750 sublibrary.</li>  
<li>[[#FUNU_7.5|modify FUNU for 64-bit addressing]] considerations and store the modified source in your V750 sublibrary.</li>  
<li>If you have any user-defined messages (MSGU), store them in your V750 sublibrary.</li>
<li>If you have any user-defined messages (MSGU), store them in your V750 sublibrary.</li>
<li>[[#asmFUNU|Assemble]] FUNU (and MSGU, if applicable), with the output object file stored in your V750 sublibrary.</li>
<li>[[Assemble]] FUNU (and MSGU, if applicable), with the output object file stored in your V750 sublibrary.</li>
</ol>
</ol>
</li>
</li>
   
   
<li>If you use an external authorizer (such as RACF) for <var class="product">Model 204</var>, [[#secparm|assemble the <i>xxxx</i>PARM security module]] (such as RACFPARM). The object file is then stored in your local object library.</li>
<li>If you use an external authorizer (such as RACF) for <var class="product">Model 204</var>, [[assemble the <i>xxxx</i>PARM security module]] (such as RACFPARM). The object file is then stored in your local object library.</li>


<li>If you use other customized modules, such as CDTB, modify them as needed and [[#asm|assemble]] them.</li>
<li>If you use other customized modules, such as CDTB, modify them as needed and [[assemble]] them.</li>
   
   
<li>Link the [[#lkonln|ONLINE]] phase.</li>
<li>Link the [[ONLINE]] phase.</li>


<li>If you use the [[#link_ifam1|IFAM1]] phase, link it.</li>
<li>If you use the [[IFAM1]] phase, link it.</li>
   
   
<li>Link the <var class="product">Model 204</var> [[#lkutils|utility programs]].</li>
<li>Link the <var class="product">Model 204</var> [[utility programs]].</li>
   
   
<li>If you use the [[#cics|CICS interface]], customize it, and then assemble and link the CICS modules.</li>
<li>If you use the [[CICS interface]], customize it, and then assemble and link the CICS modules.</li>


<li>If you use [[#softspy|SoftSpy]], upgrade it for 7.5.</li>
<li>If you use [[SoftSpy]], upgrade it for 7.5.</li>
</ol>
</ol>




[[Category:Installation]]
[[Category:Installation]]

Revision as of 20:26, 17 December 2014

Note: This page is currently under construction.

This page describes the steps required to upgrade from Rocket Model 204 version 7.4 to version 7.5, on the IBM z/VSE operating system.

In order to upgrade to Model 204 version 7.5, you must have version 7.4 and the latest Autofix set of Early Warnings installed on your system.

To upgrade to version 7.5 simply download, upload, and link the 7.5 object modules available from the downloads page to install the 7.5 components.

Before you begin

  • In order to upgrade to version 7.5, you must have version 7.4 and Autofix release EW3044 installed on your system.

    Autofix release EW3044 includes:

    • Early Warnings for Model 204 through 740EW172
    • Early Warnings for Dictionary/204 through 740DI016
    For information on Early Warnings, log in to the Rocket Customer Portal.

  • For system requirements for version 7.5, see the 7.5 Release notes.
  • You must have either a Rocket M204 user ID or a Sirius user ID to download the installation files.
  • The sublibrary containing the object has the authorization zap (covering your licensed processors) preapplied, so you do not need to get a new authorization zap from the website.
    (The preapplied zap will authorize Model 204 itself and any separately purchased products such as MQ/204 and SirScan.)
  • The object files also have the maintenance zaps (as of the time the stream was prepared) preapplied, so you do not need to apply any maintenance as part of this installation. (You will only need to apply any new maintenance when it becomes available for this release.)

Overview of upgrading steps

Review the following high-level summary of steps before you begin downloading the Model 204 version 7.5 files.

For an example, see Example workflow for 7.5: download through installation.

  1. Use your Rocket M204 user ID to download the Model 204 object source and JCL, including M204CATP.

  2. Upload (FTP) the downloaded components to the z/VSE system on the IBM mainframe.
  3. Submit the M204CATP job to allocate VSAM managed space for the Model 204 library, define the sublibraries, and catalog the procedures.
  4. If you have your own user $functions (FUNU), you must do the following steps:
    1. modify FUNU for 64-bit addressing considerations and store the modified source in your V750 sublibrary.
    2. If you have any user-defined messages (MSGU), store them in your V750 sublibrary.
    3. Assemble FUNU (and MSGU, if applicable), with the output object file stored in your V750 sublibrary.
  5. If you use an external authorizer (such as RACF) for Model 204, [[assemble the xxxxPARM security module]] (such as RACFPARM). The object file is then stored in your local object library.
  6. If you use other customized modules, such as CDTB, modify them as needed and assemble them.
  7. Link the ONLINE phase.
  8. If you use the IFAM1 phase, link it.
  9. Link the Model 204 utility programs.
  10. If you use the CICS interface, customize it, and then assemble and link the CICS modules.
  11. If you use SoftSpy, upgrade it for 7.5.
Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Model_204_installation_on_IBM_z/VSE&oldid=74285"