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.

Note: This page is currently under construction.

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

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.
For system requirements for this installation, 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.

Overview of installation steps

Review the following high-level summary of the installation steps before you install Model 204 version 7.5.

You can refer to the sample installation in Example workflow for 7.5: download through installation.

Use your Rocket M204 user ID to download the Model 204 object library and the Model 204 macro library.
Upload (FTP) the downloaded components to the z/OS system on the IBM mainframe.
Build the RKOBJLIB object library and RKMACLIB macro library. (Once you have built these libraries, do not modify them.)
Submit the job to allocate the other data sets required for installation.
If you have your own user $functions (FUNU), you must modify FUNU for 64-bit addressing considerations and store the modified source in your local source library.
Also store any user-defined messages (MSGU) in your local source library.

Then assemble FUNU (and MSGU, if applicable), with the output object file stored in your local object library.
If you use an external authorizer (such as RACF) for Model 204, the security module is named xxxxPARM. Assemble xxxxPARM; the object file is stored in your local object library. If you use the dynamic xxxxPARM configuration, link xxxxPARM into the Model 204 load library.
If you use other customized modules, such as CDTB or UL/DB2, modify them as needed and assemble them.
Link the ONLINE.
If you use the IFAM1 and IFAM4 load modules, link them.
Link the Model 204 utility load modules.
If you use the CICS interface, customize the interface and then assemble and link the CICS modules.
If you use the TSO interface, assemble and link-edit the TSO source modules.
If you use SoftSpy, upgrade SoftSpy for 7.5.

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

Downloading

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

On the Model 204 macro library download page, click the Download macro library link beside the macro library that you want.

Uploading (FTP)

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:

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

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

Job stream to build 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:

Click here to access the NEW204LB job stream.
Place the job stream into your local TSO library.
On the first line, modify the JOB card according to your local standards.
On the final four lines, marked 2 << ... 5 << on the right:
1. Modify the VERSION= parameter, specifying the two-digit version of Model 204 you are installing.
2. Modify the HLQ= parameter, specifying the high-level qualifier(s) of all Model 204 installation datasets.
3. Modify the OBJINP= parameter, using the DSN of the object library input file you uploaded to the mainframe.
4. Modify the MACINP= parameter, using the DSN of the macro library input file you uploaded to the mainframe.

Attention: Once you have built the object library ("RKOBJLIB") and macro library ("RKMACLIB") on your z/OS system, do not modify them 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. Place object files that you might assemble (such as FUNU or RACFPARM) into your local object library.

RKOBJLIB README file

README, a member of RKOBJLIB, contains details on the object files and installation steps. Once you have built RKOBJLIB, you can use README as an installation checklist if desired.

Allocating data sets

There are three data sets used during Model 204 installation:

data set for the Model 204 load modules
data set for the local source library
data set for the local object library

The data set for the load modules will contain, after linking, the modules for the Model 204 product, including: ONLINE, IFAM1, and IFAM4. The local source library is used to store the customized source for modules such as FUNU, MSGU, and ACF2PARM, RACFPARM, or TOPSPARM. When the source is assembled, it is stored in the local object library.

One of the members of the RKOBJLIB object library is named JALINSJ.

Job stream to allocate data sets

JALINSJ is a job stream to allocate data sets for the installation.

Copy JALINSJ into a local TSO library.
Edit your copy of JALINSJ for your configuration:
- Replace the first line with a JOB card.
- Edit the lines, near the top of the job stream, marked with numbers followed by <<. The numbers correspond to numbered steps in the comments following these lines.
Submit the JALINSJ job to allocate the data set.

Linking the Model 204 ONLINE load module

Note: If you use customized modules (such as FUNU, MSGU, ACF2PARM, RACFPARM, TOPSPARM, CDTB, or UL/DB2), you must modify them (if needed) and assemble them before you link the ONLINE/IFAM1/IFAM4 load modules.

One of the members of the RKOBJLIB object library is named LKONLNJ.

LKONLNJ is a job stream to link the Model 204 ONLINE load module.

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 (covering your licensed processors) preapplied, so you do not need to get a new one from the website.
(The preapplied zap will authorize Model 204 itself and any separately purchased products such as MP/204 and SirScan.)
The object library also has 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.)

Linking ONLINE

Copy the LKONLNJ job stream from RKOBJLIB into a local TSO library.
Edit your copy of LKONLNJ for your configuration:
- Replace the first line with a JOB card.
- Edit the lines, near the top of the job stream, marked with 1-4 followed by <<. The numbers correspond to numbered steps in the comments.
- As needed, edit the lines after SYSLIN DD * that are marked with <<. See the comments at the top of the SYSLIN sections (A-C) for instructions.
Submit the LKONLNJ job to link the ONLINE load module.

Concise editing instructions are provided in the LKONLNJ file itself. More details about link-editing the ONLINE load module are provided in the following table.

1	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 data sets that are required for installation.
2	One of the modifications is always required, based on whether the ONLINE is to use RSQL (for Connect) or not. Uncomment only one of the following statements: To link an ONLINE that uses RSQL, you must uncomment the INCLUDE RKOBJ204(LKSQLONL) statement. To link an ONLINE that does not use RSQL, you must uncomment the INCLUDE RKOBJ204(LKNOSONL*) statement.
3	If you use an external authorizer, such as RACF or ACF2, you must: Assemble the xxxPARM for your external authorizer to add the object file (such as 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 on your configuration. If you use ACF2, there are two INCLUDE statements to be uncommented; 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.
4	If you have other programs that you assemble for your Model 204 ONLINE module, for example, FUNU, assemble them into your local object library. You do not need to add additional INCLUDE statements for FUNU or other locally assembled object files; they are already in the include streams from RKOBJLIB.
5	If you have an MQ series load library, set the MQ symbolic parameter to the correct DSN in the EXEC LKM204P statement. 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 relinking of the load module. You must also uncomment the INCLUDE MQ statement in the SYSLIN input.

Linking the Model 204 IFAM1 load module

One of the members of the RKOBJLIB object library is named LKIFAM1J.

LKIFAM1J is a job stream to link the Model 204 IFAM1 load module.

Linking IFAM1

Copy the LKIFAM1J job stream from RKOBJLIB into a local TSO library.
Edit your copy of LKIFAM1J for your configuration:
- Replace the first line with a JOB card.
- Edit the lines, near the top of the job stream, marked with numbers followed by <<. The numbers correspond to numbered steps in the comments following these lines.
Submit the LKIFAM1J job to link the IFAM1 load module.

Linking the Model 204 IFAM4 load module

One of the members of the RKOBJLIB object library is named LKIFAM4J.

LKIFAM4J is a job stream to link the Model 204 IFAM4 load module.

Linking IFAM4

Copy the LKIFAM4J job stream from RKOBJLIB into a local TSO library.
Edit your copy of LKIFAM4J for your configuration:
- Replace the first line with a JOB card.
- Edit the lines, near the top of the job stream, marked with numbers followed by <<. The numbers correspond to numbered steps in the comments following these lines.
Submit the LKIFAM4J job to link the IFAM4 load module.

Linking the Model 204 utility load modules

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

Job stream to link utility load modules

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

Copy LKALLUTJ into a local TSO library.
Edit your copy of LKALLUTJ for your configuration:
- Replace the first line with a JOB card.
- Supply your installation high level qualifier(s) in the following lines marked with <<:
  - for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card
  - after HLQ=, on the line after EXEC LKALLUTP at the bottom of the job stream
Submit the LKALLUTJ job to link the utility load modules.

Assembling customized modules into your local object library (LOCAL.OBJLIB)

Copy the module (such as FUNU, MSGU, ACF2PARM, RACFPARM, TOPSPARM, CDTB, or UL/DB2) into your local source library, if you have not already done so. (The local source library is not version-specific, so modules copied into it can be used for future installations.)

The downloaded object library contains a member named JASMJ.

JASMJ is a job stream to assemble a member from your Model 204 local source library into your local object library (LOCAL.OBJLIB).

Job stream to assemble modules into your local object library

Copy JASMJ into a local TSO library.
Edit your copy of JASMJ for your configuration:
- Replace the first line with a JOB card.
- Supply your installation high level qualifier(s) in the following lines marked with <<:
  - for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card
  - after HLQ=, on the ASM line at the bottom of the job stream
- Provide the member name to assemble (such as FUNU, MSGU, RACFPARM) on the MEM= line.
Submit the JASMJ job to assemble the module.

Setting up the security module

If you use a security interface, such as ACF2, RACF, or Top Secret:

Assemble the security module: ACF2PARM, RACFPARM, or TOPSPARM.
(Optional) Link the security module as described below if you want it to be dynamically loaded.

Linking security modules

If you want Model 204 to dynamically load your security module during Model 204 ACF2, RACF, or TOPSECRET interface initialization, then you must link the corresponding security parameter module.

Copy LKSECRJ into a local TSO library.
Edit your copy of LKSECRJ for your configuration:
- Replace the first line with a JOB card.
- Edit the lines, near the top of the job stream, marked with numbers followed by <<. The numbers correspond to numbered steps in the comments following these lines.
Submit the LKSECRJ job to link-edit the security parameter module (ACF2PARM, RACFPARM, or TOPSPARM).

Dynamic loading lets you modify the security parameters without having to relink Model 204, which would be required if the parameter module were linked into Model 204 directly.

CICS interface

Requirements

CICS Transaction Server support
Rocket M204 supports the CICS Transaction Server versions 3.1, 3.2, 4.1, and 4.2.
Supporting TPROCESS COBOL applications
You must relink any CICS TPROCESS applications using AMODE=31, as AMODE=24 is not supported.

CICS Interface overview information

For an overview of the CICS Interface, including storage requirements and a listing of CICS interface components, see CICS interface.

Installing the CICS interface

Note: It is not necessary to install the CICS interface if it has been installed for a previous version of Model 204. The load modules from the older version are completely compatible with version 7.5 of Model 204.

To install the CICS interface:

Customize the interface by copying the CICFG copy member into your local source library and editing it as needed.
For information on customizations needed for using the CICS Standard Mapping Service, see CICS interface.
Update the CICS System Definition (CSD) using one of the following methods:
- Resource Definition Online (CEDA). The supplied member CEDAM204 in RKMACLIB provides an example of the required PCT, PPT, and PLT definitions.
- The IBM DFHSCDUP offline utility, to process the definitions in batch.
Allocate a CICS user library.
Assemble and link the CICS modules.

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.

CICS System Definition values

User program	Program name	Transaction ID	Modifiable CICFG symbol	TWA size
IFAM2 pseudo conversational	DFHPSF	DFHPSF is accessed by using a CICS LINK. It is never invoked with a transaction ID from a terminal.
Full-screen interface	M204PSFS	M204	&TRN	88
Screen copy transaction	M204CRPS	U204
Screen print transaction	M204PRNT	P204	&COP	88

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:

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)

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.

Note: 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.

Allocating a CICS user library

The downloaded object library contains a member named JALCICSJ. JALCICSJ is a job stream to allocate an empty CICS user library. You must allocate the CICS user library before assembling and linking the CICS modules.

Copy JALCICSJ into a local TSO library.
Edit your copy of JACICSJ for your configuration:
- Replace the first line with a JOB card.
- Supply your installation high level qualifier(s) in the following lines marked with <<:
  - for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card
  - after HLQ=, on the line after EXEC LKALLUTP at the bottom of the job stream
Submit the JALCICSJ job to allocate the CICS user library.

Assembling and linking CICS modules

The downloaded object library contains a member named LKCICSJ. LKCICSJ is a job stream to assemble and link the Model 204 CICS modules.

Copy LKCICSJ into a local TSO library.
Edit your copy of LKCICSJ for your configuration:
- Replace the first line with a JOB card.
- Supply your Model 204 installation high level qualifier(s) in the following lines marked with <<:
  - for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card
  - after HLQ=, on the line after EXEC JALCICSP at the bottom of the job stream
Submit the LKCICSJ job to assemble and link the CICS module.

TSO interface

The Model 204 TSO Interface enables the TSO user to communicate with a Model 204 Online.

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.

Installing the TSO interface

Note: It is not necessary to install the TSO interface if it has been installed for a previous version of Model 204. The load modules from the older version are completely compatible with version 7.5 of Model 204.

To install the TSO interface:

If you are using TSO extensions, modify TSFS in the local source library by changing:
&TSOV SETC 'TSO'

to:

&TSOV SETC 'TSOE'

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.

Assemble and link the TSO modules, using the LKTSOJ job.

Job stream to assemble TSO modules

The downloaded object library contains a member named LKTSOJ, which is a job stream to assemble and link the Model 204 TSO modules.

Copy LKTSOJ into a local TSO library.
Edit your copy of LKTSOJ for your configuration:
- Replace the first line with a JOB card.
- Supply your installation high level qualifier(s) in the following lines marked with <<:
  - for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card
  - after HLQ=, on the line after EXEC LKALLUTP at the bottom of the job stream
Submit the LKTSOJ job to assemble and link the TSO modules.

CRAM

RKOBJLIB also contains LKCRAMJ, the jobstream to link the CRAM load modules. Versions 7.4 and later of the CRAM load modules are completely compatible with version 7.5 of Model 204. Deploying a new version of CRAM can be an intensive process, and because you have version 7.4 installed, it is not necessary. You can safely bypass linking the 7.5 CRAM modules.

FUNU and optional MSGU

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

Copy the source into your local source library.

After making any changes required for this version of Model 204, run JASMJ to assemble FUNU into your local object library. (This job will also be used to assemble MSGU, if you have it.)

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.

Installing the UL/DB2 interface

USQL is delivered in source for you to customize on site. If you use the UL/DB2 interface, assemble the source as described below before linking the ONLINE/IFAM1/IFAM4 load modules.

To install UL/DB2:

Copy JAUSQLJ into a local TSO library.
Edit your copy of JAUSQLJ for your configuration:
- Replace the first line with a JOB card.
- Supply your installation high level qualifier(s) in the following lines marked with <<:
  - for hlq in the JCLLIB ORDER=(hlq.... line after the JOB card
  - on the line after EXEC JAUSQLP at the bottom of the job stream set:
    - HLQ=high level qualifier of all Model 204 installation DSNs
    - DB2HLQ=high level qualifier for your DB2 maclib.
Submit the JAUSQLJ job to preprocess and assemble the USQL module. The JAUSQLJ job executes the following two steps:
- Run USQL (contained in RKMACLIB) through the DB2 preprocessor to process the EXEC SQL statements. Outputs are two data sets: the DBRM and the expanded USQL source.
- Assemble expanded USQL source into local object library.
Bind the DBRM as the plan with a site-specific plan name.

For more information on UL/DB2, see the Rocket Model 204 User Language/DATABASE 2 Interface Guide.

Upgrading SoftSpy for 7.5

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 the SOUL files download page.

For detailed instructions, see Downloading and restoring SOUL files.

Verifying your Model 204 7.5 installation

To perform an initial verification that your 7.5 installation was successful, perform the following tasks:

Issue the ROCKET command
Issue the DISPLAY ZAPS command
Invoke DICTADMIN
Invoke SUBSYSMGMT

Example workflow for 7.5: download through installation

This example shows one typical installation workflow: the site does not use RSQL, it uses the RACF external authorizer, and it does not have its own FUNU. The IBM system MQ loadlib is MQSERIES.SCSQLOAD (this is typical in z/OS). The high-level qualifier in this example is MYBUILD.

The other item needed is the member name MYBLDOB, which is chosen arbitrarily for this example, and the following DSNs:

MYBUILD.M204V75.RKOBJLIB.DISTRIB
MYBUILD.M204V75.RKOBJLIB
MYBUILD.M204V75.RKMACLIB.DISTRIB
MYBUILD.M204V75.RKMACLIB
MYBUILD.M204V75.LOCAL.OBJLIB
MYBUILD.M204V75.LOADLIB

Build RKOBJLIB

Download the object library (M204V75.OBJ) from the downloads page.
Upload to the mainframe, in binary format, with settings FB/80/6400, as MYBUILD.M204V75.RKOBJLIB.DISTRIB.
Download the macro library (M204V75_ZOS.MAC) from the downloads page.
Upload to the mainframe, in binary format, with settings FB/80/6400, as MYBUILD.M204V75.RKMACLIB.DISTRIB.
Create the member MYBLDOB in my TSO library from a download of the job stream to build the object and macro libraries, using the following at the end of the job stream:
//BLD EXEC NEW204LB,VERSION=75, // HLQ=MYBUILD, // OBJINP=MYBUILD.M204V75.RKOBJLIB.DISTRIB, // MACINP=MYBUILD.M204V75.RKMACLIB.DISTRIB
Run MYBLDOB from my TSO library. MYBLDOB deletes and then creates MYBUILD.M204V75.RKOBJLIB and MYBUILD.M204V75.RKMACLIB.
Upload to the mainframe, in binary format, with settings FB/80/6400, as MYBUILD.M204V75.RKMACLIB.DISTRIB.
Create the member MYBLDDS in my TSO library by copying the job stream from JALINSJ, using the following at the end of the job stream:
//BLD EXEC JALINSP, // HLQ=MYBUILD
Run MYBLDDS from my TSO library. MYBLDDS allocates an empty loadlib data set for the Model 204 load modules, an empty local source library for the customized source files, and an empty local object library for the customized local object modules, with the following names: MYBUILD.M204V75.LOADLIB, MYBUILD.M204.LOCAL.SRCLIB and MYBUILD.M204V75.LOCAL.OBJLIB.

Assemble and link

Copy the RACFPARM source to the MYBUILD.M204.LOCAL.SRCLIB and make any necessary modifications.
Create the member JASMSECJ in my TSO library by copying the job stream from JASMJ, using the following at the end of the job stream:
//ASM EXEC JASMP,HLQ=MYBUILD, // MEM=RACFPARM
Run JASMSECJ from my TSO library; this assembles the RACFPARM source file in the MYBUILD.M204.LOCAL.SRCLIB and stores the object in MYBUILD.M204V75.LOCAL.OBJLIB.
Copy the member LKONLNJ from MYBUILD.M204V75.RKOBJLIB to my TSO library, and customize LKONLN as follows:
- Make these changes at the top of the job stream:
  // JCLLIB ORDER=(MYBUILD.M204V75.RKOBJLIB) //LKONLN EXEC LKM204P, // HLQ=MYBUILD, // MQ=MQSERIES.SCSQLOAD
- Uncomment the INCLUDE line for LKNOSONL (that is, without RSQL).
- Uncomment the INCLUDE line for MQ.
- Uncomment the INCLUDE line for my external authorizer module (such as RACFOS and RACFPARM).
- Submit the LKONLNJ job from my TSO library, this creates ONLINE (and BATCH204 alias) in MYBUILD.M204V75.LOADLIB.
Perform a simple smoke test: run BATCH204 with 'DISPLAY ZAPS' and 'ROCKET' commands.
To link the utilities, copy member LKALLUTJ from MYBUILD.M204V75.RKOBJLIB to my TSO library, and see all << lines to customize for my site; submit the LKALLUTJ job.
Ensure that any JCL that performs deferred index sorting for Model 204 version 7.5 (typically, FLOD jobs) uses the new MYBUILD.M204V75.LOADLIB for the E15 (OI15OS) and E35 (OI35OS) sort exits.

Additional information

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