Easytrieve Installation Overview

Installing CA Easytrieve Report Generator is a systems programming task—not something application developers perform daily. Broadcom ships Easytrieve 11.6 for z/OS through SMP/E (or z/OSMF workflows), allocates libraries such as CBAALOAD and sample JCL in CBAAJCL, and requires post-install configuration of the options table before developers can compile with PGM=EZTPA00. This page orients beginners to what installation means and how the pieces connect.

Progress0 of 0 lessons

Who Installs Easytrieve and Why It Matters to Developers

Systems programmers acquire the product pax from Broadcom Support, run SMP/E receive and apply jobs, allocate datasets, and configure global options. Application developers consume the result: STEPLIB to CBAALOAD, procs in CBAAJCL, and an options table file. When your compile fails with missing EZTPA00 or EZOPTBL errors, the root cause is often installation or configuration—not your source code.

Understanding installation at a high level helps you request the right library names in change tickets, read shop standards documents, and distinguish compile errors from environment misconfiguration.

Installation Methods

Broadcom z/OS installation paths
MethodTypical userSummary
SMP/E JCLSystems programmerClassic batch jobs: mount USS pax, receive, apply, accept, install into target libraries
z/OSMFSystems programmerWorkflow-driven install through z/OS Management Facility UI
Distributed installPlatform adminSeparate media/process for UNIX, Linux, Windows Easytrieve Plus

SMP/E JCL Install Flow (High Level)

Broadcom documents these major phases for pax-based SMP/E installation:

  1. Allocate and mount a USS file system for the product pax files.
  2. Acquire product pax files and maintenance from Broadcom Support.
  3. Create a product directory from the pax file on USS.
  4. Copy sample installation JCL to a z/OS partitioned dataset.
  5. Prepare the SMP/E environment (zones, DDDEF entries pointing to new libraries).
  6. Run installation jobs: receive, apply, accept, install.
  7. Clean up the USS work directory.
  8. Complete configuration: options table, EZTINI, license key, verification.

Each site names libraries with a high-level qualifier (for example PROD.EZT.R116.CBAALOAD). Your JCL must use your site names—not generic Broadcom examples copied literally.

Key Libraries After Installation

Common z/OS library suffixes (prefix varies by site)
Library suffixPurpose
CBAALOADLoad modules: EZTPA00 compiler/runtime, EZTINI, runtime support
CBAAJCLSample installation and configuration JCL (JOB06OP1, JOB06OP2, etc.)
CBAASRC or similarSource samples and macros (site-dependent naming)
EZOPTBL fileOptions table file—not always a PDS; file DSN configured at install
Application load libraryWhere your compiled programs (load modules) are stored

Concurrent Releases and Migration

Broadcom explicitly allows running an older release in one SMP/E environment while 11.6 runs in another. Installing 11.6 into an existing SMP/E environment can remove previous release libraries in that environment—plan separate zones. Migration from 6.4 to 11.6 includes options table conversion, compatibility mode testing (PARM COMPAT), and eventual new-function mode validation.

Developers upgrading programs should read Broadcom "Migrate from Release 6.4 to 11.6" and "Differences Between Releases" before mass recompile.

Post-Install Configuration Essentials

Options table (EZOPTBL)

Release 11.x uses a file-based options table. JCL can specify //EZOPTBL DD pointing to the dataset. If omitted at compile/execute time, Easytrieve reads the default DSN from the EZTINI load module in CBAALOAD—created during installation job JOB06OP1 per Broadcom configuration best practices.

Global options (JOB06OP2)

Setting global options in the options table reduces per-program PARM clutter and standardizes report behavior site-wide. Options can still be overridden locally with PARM and REPORT statements.

License / site key

Broadcom mainframe products require proper licensing. Easytrieve 11.6 documentation references site key installation—coordinate with your software asset management team.

Roles Involved in Installation

  • Systems programmer — SMP/E, procs, STEPLIB standards.
  • Storage administrator — DASD space for libraries and work files.
  • Security administrator — RACF profiles for datasets and program execution.
  • Easytrieve coordinator / senior developer — options table content, migration testing.

Verification After Install

Broadcom provides "Verify Your Installation" steps: compile and execute a sample program using CBAAJCL examples, confirm SYSPRINT listing, check return codes, and validate EZTPA00 resolves from STEPLIB. Developers should not proceed with production migration until this baseline succeeds.

Explain It Like I'm Five

Installing Easytrieve is like setting up a printing shop in the basement of a big building. The systems programmer brings the machines (libraries), connects power (SMP/E), and sets the default settings (options table). You, the report writer, just need to know which button to press (JCL proc) when you want to print your homework—after the shop is built.

Exercises

  1. List three Broadcom installation phases in order.
  2. Ask your shop documentation for your site CBAALOAD dataset name.
  3. Explain why 11.6 and 6.4 might use different SMP/E environments.
  4. Describe what EZTINI eliminates from JCL when configured.
  5. Name two roles besides developers involved in Easytrieve install.

Quiz

Test Your Knowledge

1. Who typically installs Easytrieve on z/OS?

  • Application developer only
  • Systems programmer
  • End user on laptop
  • Db2 DBA only

2. Broadcom recommends installing release 11.6:

  • Into the same SMP/E zone as 6.4 without planning
  • Into a separate SMP/E environment from older releases
  • Only on Windows
  • Without any libraries

3. The main runtime load library for Easytrieve 11.6 on z/OS is often named:

  • SYS1.LINKLIB
  • CBAALOAD (site prefix varies)
  • CEE.SCEERUN only
  • SYS1.PARMLIB

4. The options table on 11.x z/OS is:

  • Only in PARMLIB
  • A file identified by EZOPTBL DD or defaults in EZTINI
  • Not used
  • Compiled into every program automatically

5. Installation methods documented by Broadcom include:

  • SMP/E JCL and z/OSMF
  • npm install only
  • Docker pull only
  • ISPF option 0 only
Published
Read time11 min
AuthorMainframeMaster
Reviewed by MainframeMaster teamVerified: Broadcom Install Easytrieve for z/OS 11.6 TechDocsSources: Broadcom SMP/E install guide, Configuration Best Practices, Prepare for InstallationApplies to: CA Easytrieve Report Generator 11.6 z/OS installation