Model 204 installation on IBM z/OS

Overview

This topic describes the steps required to upgrade to Rocket Model 204 version 7.5 or later on the IBM^® z/OS^® operating system.

The new version number is referred to as x.y, where x.y can be 7.5 or later.

For information on the new features available in each version, as well as any compatibility issues, see the Model 204 release notes.

If you are skipping any versions when upgrading (such as upgrading from 7.5 to 7.7), be sure to read the release notes for those versions as well (such as 7.6).

Before you begin

• You must have either a Rocket M204 user ID or a preexisting user ID to download the installation files.
• The object library has the authorization zap (covering your licensed processors) preapplied, so you do not need to get a new authorization zap from the Rocket website.
  (The preapplied zap will authorize Model 204 itself and any separately purchased products, such as 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 run RockZap to apply any new maintenance when it becomes available for this release.)
• These upgrade instructions anticipate a default non-SVC installation of the Model 204 load modules (ONLINE, IFAM1, and IFAM4) into an APF-authorized load library and running as non-swappable.

  If you are installing CRAM, it is also a non-SVC installation, the CRAM load library also needs APF authorization, and the address space should be non-swappable.

• To use Model 204 SNA Communications Server terminal support, you must define Model 204 as an SNA Communications Server application program. For more information, see SNA Communications Server network definition requirements.

  If you are using SNA Communications Server for Horizon or PQO, you must define any Horizon or PQO links individually to SNA Communications Server. See Defining the network to SNA Communications Server or SNA Communications Server network definition.

Overview of upgrading steps

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

Each step links to a section with detailed instructions. Note that some steps (such as assembling custom modules) might not apply to your installation. Once you have started, you can proceed directly through the steps (detail sections are consecutive) or return to this list for context.

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

1. Build the Model 204 object and macro libraries:
   1. Use your Rocket M204 user ID to download the Model 204 object library and the Model 204 macro library.
   2. Upload the downloaded components to the z/OS system on the IBM mainframe.
   3. Build the RKOBJLIB object library and RKMACLIB macro library. (Once you have built these libraries, do not modify them.)
2. Submit the job to allocate the other data sets required for installation.
3. Modify and assemble these modules if you use them:
   1. Your user $functions (FUNU) and, optionally, MSGU.
   2. An external authorizer (such as RACF) for Model 204. Set up the security module, including assembling the xxxxPARM security module (such as RACFPARM). The object file is then stored in your local object library.
   3. UL/DB2 interface: preprocess and assemble the USQL module.
   4. Other customized modules, such as CDTB. Modify them as needed and assemble them.
4. Link the ONLINE load module.
5. If you use the IFAM1 and IFAM4 load modules, link them.
6. Link the Model 204 utility load modules.
7. If you use the CICS interface, customize it, and then assemble and link the CICS modules.
8. If you use the TSO interface, assemble and link-edit the TSO source modules.
9. Link the CRAM load modules as needed.
10. Install Dictionary/204.
11. If you use SoftSpy, upgrade it for x.y.
12. Verify the installation.

Build the Model 204 object and macro libraries

To build the object and macro libraries, you must download the object library and macro library; upload each library to the mainframe; and copy, modify, and run the NEW204LB job.

Object and macro libraries

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.

Downloading

1. Using your Rocket M204 user ID and password, log in to the Model 204 object file download page.
2. Click the Download object file link beside the object library that you want to download.
3. Go to the Model 204 macro library download page.
4. Click the Download macro library link beside the macro library that you want to download.

Uploading

Once the object file and macro library are downloaded to your workstation, upload them to the z/OS system on the IBM mainframe. You can use any file transfer mechanism, including FTP and IND$FILE.

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.

Building the object and macro libraries (NEW204LB job stream)

After you upload the object and macro library input streams to the mainframe, build the object and macro libraries:

1. Access the NEW204LB job stream text file.
2. Copy the job stream file into a local TSO library for editing.
3. On the first line of the job stream, modify the JOB card according to your local job card parameters.
4. Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
5. Submit the NEW204LB job to build the object library ("RKOBJLIB") and macro library ("RKMACLIB") on your z/OS system.

Attention: Once you have built RKOBJLIB and 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.

Allocate the data sets for Model 204 upgrading

Three basic data sets are used for the upgrade to Model 204 7.x:

• 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, TSFS, and ACF2PARM, RACFPARM, or TOPSPARM.

• If you have a customized module, copy it from your existing library to your local source library.
• If you want to add one of the modules, copy it from RKMACLIB to your local source library and customize it.

As described below, JALINSJ allocates the source library if it does not already exist.

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, which is a job stream to allocate data sets for the installation. JALINSJ contains information about naming conventions for the data sets.

Allocating data sets (JALINSJ job stream)

1. Copy JALINSJ into a local TSO library.
2. Edit your copy of JALINSJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. Submit the JALINSJ job to allocate the basic installation datasets:
   • hlq.M204V77.LOADLIB - the library for linking most load modules
   • hlq.M204V77.LOCAL.OBJLIB - the library for assembling optional object files: RACFPARM, FUNU, etc.
   • hlq.M204.LOCAL.SRCLIB - the library in which you store source for assembling modules such as FUNU and xxxPARM. Note that this DSN does not have a version identifier (such as V75, V76, and so on). This library is only allocated if it does not already exist. It is used for installing all versions of Model 204.

   Note: hlq.M204V77.LOADLIB and hlq.M204V77.LOCAL.OBJLIB are deleted and then allocated whenever you submit JALINSJ. If your local source lib (hlq.M204.LOCAL.SRCLIB) exists, it is retained.

Assemble FUNU and optional MSGU

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

Note: If you have your own FUNU or MSGU module, you must assemble it before linking the ONLINE/IFAM1/IFAM4 load modules.

Assemble your FUNU and/or optional MSGU modules with the following steps:

1. Modify FUNU for 64-bit addressing considerations and store the modified source in the local source library you allocated.

   FUNU changes for 7.x are:

   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.
2. If you have any user-defined messages (MSGU), store them in your local source library.
3. Assemble FUNU (and MSGU, if applicable), with the output object file stored in your local object library.
   1. Run JASMJ to assemble FUNU into your local object library.
   2. If applicable, run JASMJ to assemble MSGU.

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

Set up the security module

This section describes how to install a security interface such as CA-ACF2, RACF, or CA-Top Secret.

1. Review the Model 204 installation section for your interface and complete all of the steps:
   • CA-ACF2 (MVS)
   • CA-ACF2 (VM)
   • RACF
   • CA-Top Secret
2. Assemble the security module: ACF2PARM, RACFPARM, or TOPSPARM.
3. Optional. Link the security module as described below if you want it to be dynamically loaded.

Linking the security module (LKSECRJ job stream)

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.

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.

One of the members of the RKOBJLIB object library is LKSECRJ, a job stream to link-edit the security parameter module.

1. Copy LKSECRJ into a local TSO library.
2. Edit your copy of LKSECRJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
   • In the Security interfaces section, uncomment the appropriate two lines for your interface.
3. Submit the LKSECRJ job to link-edit the security parameter module (ACF2PARM, RACFPARM, or TOPSPARM).

Install the UL/DB2 interface (JAUSQLJ job stream)

To support the UL/DB2 interface, USQL code is delivered in source for you to preprocess for your version of DB2. If you use the UL/DB2 interface, assemble the source as described below before linking the ONLINE/IFAM1/IFAM4 load modules.

1. Copy JAUSQLJ into a local TSO library.
2. Edit your copy of JAUSQLJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. 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. This step produces two data sets: the DBRM and the expanded USQL source. The DBRM is saved as USQLDBRM in the local object library. The expanded USQL source is passed to step two for assembly.
   • Assemble expanded USQL source into local object library.
4. Bind the DBRM as the plan with a site-specific plan name.

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

Copy the customized source module (such as, PRECCAIN, FUNU, MSGU, ACF2PARM, RACFPARM, TOPSPARM, CDTB, or UL/DB2) from your current release 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.

One of the members of the RKOBJLIB object library is JASMJ, a job stream to assemble a member from your Model 204 local source library into your local object library (LOCAL.OBJLIB).

Assembling customized modules (JASMJ job stream)

1. Copy JASMJ into a local TSO library.
2. Edit your copy of JASMJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. Submit the JASMJ job to assemble the module into your local object library.

Link the Model 204 ONLINE load module

Notes:

• 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.
• 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 INCLUDE TCPLIB(SNMPGSYS) statement for Horizon TCP/IP in the Online-link-edit job is no longer required and has been eliminated.
• A number of INLUDE LELIB(CEE*) statements have also been eliminated from the Online-link-edit job. These were required to support several mathematical $functions but those $functions have been rewritten in Assembly language and are now automatically part of the Online load module.
• The INCLUDE BLOCKPRT(IEFSD095) statement is required if block printing on separator pages is desired. Usually the BLOCKPRT DD points to DSN=SYS1.AOSB0.
• As of Model 204 version 7.7, FastUnload is linked as an alias of the ONLINE load module, not as a standalone module. The FastUnload code is fully integrated into the Model 204 nucleus.
• The Online, IFAM1, and IFAM4 load modules INCLUDE object module M204XSVC, which executes cross-memory code inline rather than as an SVC.

One of the members of the RKOBJLIB object library is LKONLNJ, which is a job stream to link the Model 204 ONLINE load module.

Linking ONLINE (LKONLNJ job stream)

1. Copy the LKONLNJ job stream from RKOBJLIB into a local TSO library.
2. Edit your copy of LKONLNJ for your configuration. Specific editing instructions are provided within the LKONLNJ file. In summary:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
   • As needed, edit the lines after SYSLIN DD * that are marked with <<. See the comments at the top of the SYSLIN sections (A-D) for instructions.
3. Submit the LKONLNJ job to link the ONLINE load module.

Link the Model 204 IFAM1 and IFAM4 load modules

Among the members of the RKOBJLIB object library are:

• LKIFAM1J, which is a job stream to link the Model 204 IFAM1 load module
• LKIFAM4J, which is a job stream to link the Model 204 IFAM4 load module.

Linking IFAM1 (LKIFAM1J job stream)

1. Copy the LKIFAM1J job stream from RKOBJLIB into a local TSO library.
2. Edit your copy of LKIFAM1J for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
   • In the Security interfaces section, uncomment the appropriate two lines for your interface, if applicable.
3. Submit the LKIFAM1J job to link the IFAM1 load module.

Linking IFAM4 (LKIFAM4J job stream)

1. Copy the LKIFAM4J job stream from RKOBJLIB into a local TSO library.
2. Edit your copy of LKIFAM4J for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
   • In the Security interfaces section, uncomment the appropriate two lines for your interface, if applicable.
3. Submit the LKIFAM4J job to link the IFAM4 load module.

Link the Model 204 utility load modules

Following are the utility load modules to be linked:

Module	Description
AUDIT204	Generate an audit trail from the CCAJRNL or CCAJLOG data sets, with report stats and analysis
BATCH2	Enable batch users to access a Model 204 Online that is running in a separate region
HASH15	Sort exit for hash file index
HASH35	Sort exit for hash file index
M204LIST	A module to support the XREF cross-reference reporting subsystem.
M204XREF	Another module to support the XREF cross-reference reporting subsystem.
MERGEJ	Media recovery journal merge utility
OI15OS	Sort exit for variable length deferred updates (Ordered Index)
OI35OS	Sort exit for variable length deferred updates (Ordered Index)
UTILC	Information from checkpoint stream
UTILJ	Journal/Audit trail debug utility
ZBLDTAB	Build prototype password table
ZCTLTAB	Convert CCASTAT for the Password Expiration feature

Linking the utility load modules (LKALLUTJ job stream)

One of the members of the RKOBJLIB object library is LKALLUTJ, a job stream to link the Model 204 utility load modules.

1. Copy LKALLUTJ into a local TSO library.
2. Edit your copy of LKALLUTJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. Submit the LKALLUTJ job to link the utility load modules.

Install the CICS interface

The Model 204 CICS interface allows CICS complete access to Model 204 facilities and supports CICS pseudo conversational programs.

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

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 compatible with version 7.x of Model 204.

Requirements

• CICS Transaction Server support

  Rocket M204 supports the CICS Transaction Server versions 5.4, 5.5, and 5.6 in addition to CICS Transaction Server versions 4.1, 4.2, and 5.3 .

• Supporting TPROCESS COBOL applications

  If your CICS TPROCESS application was originally linked with AMODE=24, you must relink the CICS TPROCESS application specifying AMODE=31, because AMODE=24 is not supported.

Installation steps

1. Customize the interface by editing the CICFG copy member.
2. Updating 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.
3. Allocate a CICS user library.
4. Assemble and link the CICS modules.

Customizing the CICS interface

To customize the CICS interface, copy the CICFG copy member from RKMACLIB into your local source library and edit it as needed.

For information on customizations needed for using the CICS Standard Mapping Service, see Use the CICS Standard Mapping Service.

Updating the CICS System Definition (CSD)

You can update the CSD by 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 the CEDAM204 member, then define the transactions and programs by 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 preceding example, 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 (JALCICSJ job stream)

One of the members of the RKOBJLIB object library is JALCICSJ, a job stream to allocate an empty CICS user library. You must allocate the CICS user library before assembling and linking the CICS modules.

1. Copy JALCICSJ into a local TSO library.
2. Edit your copy of JACICSJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. Submit the JALCICSJ job to allocate the CICS user library.

Assembling and linking CICS modules (LKCICSJ job stream)

One of the members of the RKOBJLIB object library is LKCICSJ, a job stream to assemble and link the Model 204 CICS modules.

1. Copy LKCICSJ into a local TSO library.
2. Edit your copy of LKCICSJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. Submit the LKCICSJ job to assemble and link the CICS module.

Install 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 compatible with version 7.x of Model 204.

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

The TSO Interface consists of two load modules, M204FS and M204TTY. The modules are completely reentrant, reusable, and refreshable.

Installation requires link-editing of the TSO source modules using the LKTSOJ job stream from the RKOBJLIB library:

1. If you are using TSO extensions, modify M204FS prior to linking:
   1. Copy the TSFS source from RKMACLIB to the local source library you allocated and continue with the following steps.
   2. 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.

   3. Run JASMJ to assemble TSFS into your local object library.
2. Edit your copy of LKTSOJ for your configuration:
   • Replace the first line with a JOB card.
   • Edit the lines in the job stream that are marked with numbers followed by <<. The numbers correspond to the numbered steps at the end of the comment section.
3. Submit the LKTSOJ job to assemble and link the TSO modules.

CRAM

Notes:

• CRAM SVC installation is deprecated in version 7.5 and later. The following instructions are for CRAM-XDM.
• This CRAM-XDM installation creates a separate CRAM load library (CRAMLIB). Since CRAM-XDM remains upwardly compatible (for supported Model 204 releases), a single CRAMLIB can be used by multiple versions of Model 204.
• It is not a necessity to immediately install the version of CRAM-XDM that corresponds to the version of Model 204 you are installing. That is, you may want to install and test your new version of Model 204 with your existing CRAM version before you install and test your new version of CRAM. However it is recommended that the latest available version of CRAM-XDM is eventually used.
• If you are using CRAM-XDM, the XDM load module, M204XDM, must run from an APF-authorized load library, because it must run non-swappable and non-cancellable.

Link the CRAM modules

To install the CRAM load modules, proceed with the following steps:

1. Before linking the CRAM load modules, familiarize yourself with CRAM: what it does, which facilities require it, and the available CRAM options.
2. Install 7.x CRAM-XDM by running LKCRAMJ, the job stream to link the CRAM load modules. LKCRAMJ is found in RKOBJLIB.

   The z/OS secondary subsystem name (SSN) you specify in LKCRAMJ (as the CRMSSN value) is typically how your 7.x Online locates CRAM-XDM. This value will be assembled into the CRAM IGCLM244 load module. Select the SSN in coordination with your systems programmers. It must be a value that is or will be defined in SYS1.PARMLIB(IEFSSNxx).

   If you want to install and test Model 204 with your existing (older) CRAM installation before bringing up your new CRAM version, you can do one of the following:

   • Specify your older CRAM's SSN as the 7.x LKCRAMJ CRMSSN value (and bring up the Online with the 7.x CRAMLIB load library as a concatenated STEPLIB).
   • Put the older CRAM's IGCLM244 load module in the 7.x load library; it will point to the CRAM SVC number or it will indicate that CRAM-XDM is in effect.
   • Only if your older CRAM is CRAM-XDM, specify its SSN as the value of the XDMSSN parameter in the Online's CCAIN.

   CICS interface users: Unlike version 7.4 CRAM-XDM, the step in the link JCL for the CRAM modules specifies the RENT value for PARM. Read the Note in Running with storage protection on for details.

Post-installation

After installation, when you are ready to test this CRAM-XDM with Model 204, you will need to bring up CRAM-XDM before you bring up the Onlines that will be using it. See Activating CRAM-XDM.

Upgrade SoftSpy

To upgrade SoftSpy for version 7.x, download, upload, and restore the SoftSpy procedure file, SPYPROC, which is distributed in a dump format.

1. Download SPYPROC, in binary form, from the SOUL files download page to a workstation file.
2. Upload the file from your workstation to your z/OS system.
3. RESTORE the file into a Model 204 SOUL file.

For detailed instructions, see Downloading and restoring SOUL files.

For details on the SoftSpy installation, including customization and System Manager considerations, see the SoftSpy installation guide.

RSQL maintenance

RKOBJLIB also contains the LKMAINTJ job stream. LKMAINTJ is used to relink the ONLINE, IFAM1, and IFAM4 load modules when a maintenance version of the RSQL (and sometimes EVCP) object files is distributed on the Model 204 maintenance page.

When and if there are any fixes for them, the most recent versions of these object files will appear as 'Model 204 .. RSQL' and 'Model 204 .. EVCP' with your desired version number.

The description of the RSQL and EVCP fixes will be contained in the entire set of Model 204 fixes, which you can download from the maintenance page by clicking a 'Download Zaps' link. RSQL and EVCP fixes are listed in the zap file with the characters '*77Lxx' at the start of their comment boxes.

Verify Model 204 x.y on your system

To perform an initial verification that your upgrade to 7.x was successful, issue the following commands from the Model 204 command line.

Command	You should see...
ROCKET	A list of authorized M204 products (including 7.x) currently on your system.
DISPLAY ZAPS	A list of Model 204 zaps (including 7.x zaps) on your system.
DICTADMIN	(if you have installed Dictionary/204) The Dictionary Administration subsystem, displaying Release 7.x on its menu screens.
SUBSYSMGMT	The management tool of the Application Subsystem facility, displaying VER 7 REL x on its menu screens.

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

1. Download the object library (M204V75.OBJ) from the downloads page.
2. Upload to the mainframe, in binary format, with settings FB/80/6400, as MYBUILD.M204V75.RKOBJLIB.DISTRIB.
3. Download the macro library (M204V75_ZOS.MAC) from the downloads page.
4. Upload to the mainframe, in binary format, with settings FB/80/6400, as MYBUILD.M204V75.RKMACLIB.DISTRIB.
5. 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

6. Run MYBLDOB from my TSO library. MYBLDOB deletes and then creates MYBUILD.M204V75.RKOBJLIB and MYBUILD.M204V75.RKMACLIB.
7. Upload to the mainframe, in binary format, with settings FB/80/6400, as MYBUILD.M204V75.RKMACLIB.DISTRIB.
8. 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

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

1. Copy the RACFPARM source to the MYBUILD.M204.LOCAL.SRCLIB and make any necessary modifications.
2. 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

3. 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.
4. 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.
5. Perform a simple smoke test: run BATCH204 with 'DISPLAY ZAPS' and 'ROCKET' commands.
6. 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.
7. 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.

Dictionary/204 installation

For details on installing Dictionary/204, see the Dictionary/204 installation guide.

See also

• Model 204 installation on IBM z/VSE