Upgrading to Model 204 version 7.5 on IBM z/OS

This page describes the installation steps for Model 204 version 7.5 on the IBM z/OS operating system.

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

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.

Before you begin

• For system requirements for this installation, see the 7.5 Release notes.
• Ensure that you have a user ID to use for downloads (if you have a Sirius user ID, that is sufficient).

Overview of installation steps

This section summarizes the steps for upgrading to Model 204 version 7.5. Details for each step are provided later on the page.

An example workflow is provided at the end of the page.

1. Using your Rocket M204 user ID, download the components. Do not modify the object library.
2. If you have your own user $functions (FUNU), you must modify FUNU for 64-bit addressing considerations; the object file is stored in your local object library. Then assemble FUNU and user-defined messages (if any), MSGU.
3. Allocate an authorized Model 204 load library for the version you are installing (in almost all installations).
4. If you use an external authorizer (such as RACF) for Model 204, assemble xxxPARM; the object file is stored in your local object library. If you use the dynamic xxxPARM configuration, link xxxPARM into the Model 204 load library.
5. Link the ONLINE (and, if you use them, the IFAM1 and IFAM4) load modules.
6. Link the Model 204 utility load modules.

Components for installation

Object library (RKOBJLIB)

The object library is used to link the ONLINE and various other Model 204 load modules.

See the object files download page.

JCL job streams

In addition to the object files, the object library contains a number of z/OS JCL job streams. You will copy each job stream that you need to a local TSO library, modify it according to your system, and submit the job to perform the installation steps.

The job streams in RKOBJLIB all have member names ending in the letter "J."

Macro library (RKMACLIB)

The macro library is used if your installation requires assembling of any ASSEMBLE files.

RKMACLIB contains:

• Model 204 macros
• Sample files for: FUNU, MSGU, RACFPARM, ACF2PARM, TOPSPARM, TSFS, ZFIELD proc

See the macro libraries download page.

Building the object and macro libraries

(back to installation overview)

Downloading

On the Model 204 object file download page, click the Download object file link beside the object that you want.

Uploading

Once the object files are downloaded to the workstation, ftp them to the z/OS system on the IBM mainframe.

Specify these characteristics for the upload files:

transfer format	binary
record format	FB
record size	80 for object and macro libraries
block size	6400 for object and macro libraries
storage size	primary: 10 CYL; secondary: 5 CYL

For details on how to download and upload, see Downloading and uploading Model 204 installation components.

Building the object and macro libraries

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:

1. Cut and paste the following jobstream into your local TSO library: Template:Building RKOBJ204 and RKMAC204
2. On the first line, modify the JOB card according to your local standards.
3. On the final two lines:
   • Modify the INP= parameter, using the DSN of the file you uploaded to the mainframe.
   • Modify the OBJLIB= parameter, choosing the DSN for your Model 204 object library.
   • Modify the MACLIB= parameter, choosing the DSN for your Model 204 macro library.

   You can, of course, use whatever dataset names you want — note that in our documentation, we refer to the object library as RKOBJ204 and to the macro library as RKMAC204.

Do not modify RKOBJ204

Once you have built the object library ("RKOBJ204") on your z/OS system, do not modify it in any way.

For example, 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 local object library.

Linking the Model 204 ONLINE load module

(back to installation overview)

Note: If you have your own FUNU, it must be assembled before linking the ONLINE/IFAM1/IFAM4 load modules.

After 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 Model 204 ONLINE load module.

The items in LKONLN2 (on lines indicated with <<) which can be changed in the copy in your local TSO library are described in the following table.

The comments in LKONLN2 are complete so that you may not need to refer to the instructions below. The LKONLN2 PROC is shown in a sub-section below; it also has a set of instructions, which are more succinct than the instructions in this table.

Note: Must revise! ??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.

1	One of the modifications is always required, based on whether the ONLINE is to use RSQL (for Connect*) or not: To link an ONLINE which does use RSQL, you must uncomment the INCLUDE RKOBJ204(LKSQLONL) statement. To link an ONLINE which does not use RSQL, you must uncomment the INCLUDE RKOBJ204(LKNOSONL) statement. Do not uncomment both of them.
2	The other modification frequently needed is to use an external authorizer such as RACF or ACF2. If you use and external authorizer, you must: Assemble the xxxPARM for your external authorizer, adding the object file (e.g., RACFPARM or ACF2PARM) to your local object library. In the SYSLIN DD *, uncomment the appropriate INCLUDE statement(s) for your external authorizer. Notes: Uncomment either the "static" or "dynamic" INCLUDE statement, depending upon your configuration. 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.
3	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, 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.
4	Hence, there are two choices for the RKOBJ204 DD statement: 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. If you do not have a local object library, there is only one dataset for the RKOBJ204 DD - your RKOBJ204 library.
5	If you have an MQ series load library, you should un-comment the MQOLIB DD statement, and provide the correct DSN. This allows you to use the MQ Series feature of Model 204, either if you are already authorized for it, or to support a trial of it, without requiring re-linking of the load module.
6	Finally, change the DSN of the SYSLMOD DD to the load module library you have allocated for it.

The modified JCL is now ready to run.

Notes:

• 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.
• The object library has the authorization zap pre-applied, so you do not 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.)
• 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.

Jobstream to link ONLINE

The downloaded object library contains a member named LKONLN2, which is a jobstream to link the Model 204 ONLINE load module.

1. Copy LKONLN2 into a local TSO library.
2. Edit LKONLN2 for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines, near the top of the jobstream, marked with 1-6 followed by <<. The numbers correspond to numbered steps in the comments following these lines.
   • As needed, edit the lines after SYSLIN DD * which are marked with <<. See the comments at the top of the SYSLIN sections (A-C) for instructions.
3. Submit the LKONLN2 job to link the ONLINE load module.

The instructions in LKONLN2 should be sufficient to explain the edits you need to make. Those instructions make use of the numbers (1-6) and letters (A-D) marking lines which need to be edited, or examined for editing. More expansive instructions are shown in the table above which further explain link-editing the ONLINE load module.

Linking the Model 204 utility load modules

(back to 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:

AUDIT204	Extract from journal, with report stats and analysis
MERGEJ	Merge concurrent journal streams
UTILC	Information from checkpoint stream
UTILJ	Information from journal stream; add EOF markers

Jobstream to link utility load modules

The downloaded object library contains a member named LKALLUT2, which is a jobstream to link the Model 204 utility load modules.

1. Copy LKALLUT2 into a local TSO library.
2. Edit LKALLUT2 for your configuration:
   • Replace the first line with a JOB card.
   • Edit the three lines marked with << by entering your downloadObjectLib (twice) and m204LoadLib dataset names.
3. Submit LKALLUT2 to link the utility load modules.

For your reference, the LKALLUT2 member of the downloaded object library contains the following:

//name JOB jobCardParameters //* // JCLLIB ORDER=(hlq.M204V77.RKOBJLIB) 1 << //* //* Jobstream to link Model 204 utility load modules. //* //* In a copy from the downloaded object library, modify all //* lines marked '<<' on the right, and submit the job: //* //* 1: Change 'hlq' to the same value provided in (2) - the value //* inside parentheses will then be the DSN of the downloaded //* object library //* //* 2: Provide the high level qualifier(s) of all Model 204 //* installation DSNs //* //* For detailed explanations, see //* //* http://m204wiki.rocketsoftware.com/index.php/M204_inst_zOS#lkutils //* //* (-- For Rocket Support only: filename=JZJALLUT 7.7 2016/11/14 --) //* //LKALLUT EXEC LKALLUTP, // HLQ= 2 <<

Assembling (and optionally linking) xxxPARM

(back to installation overview)

This section is under construction.

Assemble xxxPARM

TBD

Jobstream modifications for OBJLIB= points to local object library.

If using dynamic xxxPARM, link it

TBD

Local object library

If you need to assemble a xxxPARM or 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:

DCB	LRECL=80 BLKSIZE=6400 RECFM=FB
SPACE	TRK,(100,10,10) — 3390 tracks

FUNU and optional MSGU

(back to installation overview)

This section lists installation considerations if you have your own user-written $functions module (FUNU).

Notes:

• If you have your own FUNU, it must be assembled as before linking the ONLINE/IFAM1/IFAM4 load modules.
• 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.

FUNU changes for version 7.5

Starting with version 7.5 of Model 204, 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.

• 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.
• For the ENTER macro, the ZMODE operand default value (for FUNU only) is ZMODE=31. So if the $function does not have any arguments or if you will not exploit QTBL above the bar, and if the $function does not access any data structures above the bar, either specify ZMODE=31 or omit the ZMODE operand. (Note that most Model 204 data structures can be above the bar, including $function arguments.) The ZMODE=31 value will be used, causing your $function to switch to AMODE 31 at entry (and restore the AMODE upon exit).
• In any case, the AMODE issues need to be accounted for in any routines which your $function routine does a CCALL to.

FUNU assembly

1. After making any changes required for the version of Model 204 you are installing, run the job to assemble FUNU into your local object library. (This job will also be used to assemble MSGU, if you have it.)
2. Modify the 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.)

   You do not 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.

<other steps TBD>

Jobstream modifications for OBJLIB= points to local object library.

Example workflow for 7.5: download through installation

Reminder: This section shows one typical installation workflow; the previous sections on this page provide the actual installation steps in detail.

This is an example for a site which does not use RSQL. It uses the RACF external authorizer, and does not have its own FUNU. The IBM system MQ loadlib is MQSERIES.SCSQLOAD (this is typical in z/OS). The other item needed is the member name MYBLDOB, which is chosen arbitrarily for this example, and the following DSNs:

• M204.V75.RKOBJ204.DISTRIB.OBJ
• M204.V75.RKOBJ204.OBJLIB
• M204.V75.RKMAC204.DISTRIB.MAC
• M204.V75.RKMAC204.MACLIB
• M204.V75.LOCAL.OBJLIB
• M204.V75.LOADLIB

Build RKOBJ204

1. Download object library from web site (M204V75.OBJ)
2. Upload to mainframe, Binary, FB/80/6400, as M204.V75.RKOBJ204.DISTRIB.OBJ
3. Download macro library from web site (M204V75_ZOS.MAC)
4. Upload to mainframe, Binary, FB/80/6400, as M204.V75.RKMAC204.DISTRIB.MAC
5. Create member MYBLDOB in my TSO library by copying the jobstream from "Building the object and macro libraries", using the following at the end of the jobstream:

   //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

6. Run MYBLDOB from my TSO library; this deletes and then creates M204.V75.RKOBJ204.OBJLIB and M204.V75.RKMAC204.MACLIB.

Assemble and link

7. Allocate M204.V75.LOCAL.OBJLIB and copy in:
   • RACFPARM
8. Allocate M204.V75.LOADLIB and APF authorize it.

   Note: We need info about allocation (simple, just size info) and APF authorization (maybe link to a page discussing it??)

9. Copy member LKONLN2 from M204.V75.RKOBJ204.OBJLIB to my TSO libary, customizing the following:
   • Make these changes at the top of the jobstream:

     // 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

   • Uncomment the INCLUDE line for LKNOSONL (that is, without RSQL).
   • Uncomment the INCLUDE line for MQ.
   • Uncomment the INCLUDE line for your external authorizer module (such as RACFOS and RACFPARM).
   • Submit LKONLN2 from my TSO library, this creates ONLINE (and BATCH204 alias) in M204.V75.LOADLIB.
10. Perform a simple smoke test: run BATCH204 with 'DISPLAY ZAPS' and 'ROCKET' commands.
11. To link the utilities, copy member LKALLUT2 from M204.V75.RKOBJ204.OBJLIB to my TSO library, and see all << lines to customize for my site; submit this jobstream.
12. Ensure that any JCL which performs deferred index sorting for Model 204 version 7.5 (typically, FLOD jobs) uses the new M204.V75.LOADLIB for the E15 (OI15OS)and E35 (OI35OS) sort exits.

See also

• Model 204 CMS installation
• Model 204 VSE installation

Additional information

Refer to the Rocket Model 204 Installation Guide for IBM z/OS, version 7.4, for additional installation information.