Copying EZTPOPT has different format - how to ensure installation has been successful

Products

• Easytrieve Report Generator

Issue/Introduction

Noticing that the EZPTOPT from 6.4 is different than the resulting 11.6 version after being copied,

is this ok due to the differing dataset attributes for the 6.4 CAILIB versus 11.6 CBAALOAD?

How can the installation be validated as a successful installation?

Environment

Easytrieve Report Generator Release 11.6

Resolution

This is ok - no problem with this at all.

Easytrieve Report Generator release 11.6 delivers the JOB08DEM job as an IVP job which can be run after the installation, after the EZOPTBL option file has been created via JOB06OP1, NEWFUNC set to N in JOB06OP2, etc.

JOB08DEM has multiple steps, it executes EZTPA00, creates  a load module, places that in TESTLLIB, and then executes the load module and does create/populate the sample file.

This JCL creates a load module to then be executed.  So, please have a load library where this load module may reside to then be executed.  It does not need to be populated with any other members.  This is a load library separate from the CBAALOAD, which is for the Easytrieve product itself.

This PDS can be created under 3.2 under TSO ISPF.  There is nothing special about Easytrieve here at this time.  It is simply a load library to hold the created load module.

Mine is defined with these attributes:
  Organization  . . . : PO              
  Record format . . . : U
  Record length . . . : 0
  Block size  . . . . : 19069
  Maximum dir. blocks : 2