Summary of changes

Edit online

This topic identifies the significant improvements and enhancements that have been made to IBM Tivoli Tape Optimizer on z/OS versions 1.1, 1.2, 2.1, and 2.2 BETA. The changes are listed for each edition of this guide, from most recent to oldest.

IBM® Tivoli Tape Optimizer for z/OS® 2.2

SC23–9735–00 ( BETA edition) - September 2009
  • Deepens integration into Tivoli Enterprise Portal (TEP) by delivering take-action commands through the common user interface
  • Consolidates DFSMSrmm copy calls to help reduce the total number of DFSMSrmm calls
  • Optimizes request database close calls to help reduce the number of open and close calls per tape
  • Supports tape drive-based encryption features with an option that allows allocation of a tape drive using a user specified DATACLASS
  • Allows users to pass special expiration dates, such as 99000, to system managed storage (SMS) automatic class selection (ACS) routines to help drive management class and vital record processing

IBM Tivoli Tape Optimizer for z/OS 2.1

SC23–9735–00 (tenth edition) - July 2008
  • Support for Tivoli Enterprise Portal (TEP)
  • Improved rename masks
  • New filter allows selection of tapes pending replacement
In addition, Tape Optimizer on z/OS, V2.1:
  • Can copy individual tape data sets by name, expiration date, catalog status, and many other filter criteria
  • Has options for renaming tape data sets during copy operations
  • Includes support for 3592 tape drives and high-capacity tape media
  • Includes options that continue copy processing after certain types of failures or errors, such as tape I/O errors
  • Supports relative generation data group (GDG) catalog entries to help identify generation data sets for a copy request
  • Can edit some copy options for copy requests that have a status of pending restart
  • Includes expiration date processing of input tapes
  • Delivers copy processing of dump files that were created by the ADRDSSU utility, including the ability to create stacked tapes for these files based on byte-threshold levels and to copy files that were created when the ADRDSSU utility was run from within another program
  • Helps prevent enqueue copy tasks when you run multiple, concurrent copy tasks for a copy request
  • Delivers INCLUDE filter processing for multi-file and multi-volume tape chains
  • Maintains the product log and status files
  • Includes report processing and reporting for stacked tapes

IBM Tivoli Tape Optimizer for z/OS 1.2

SC18-9560-08 (ninth edition) - October 2007
  • The Test files for ADR Dump when LRECL is 0 field has been removed from the General Parameters panel (GTOP01A) and the Copy Options panel (GTOP02D). Tape Optimizer now automatically tests certain tape data sets to determine if they are ADRDSSU dump files, which should be copied with the ADRDSSU utility. Also, the corresponding parameter REQU_TEST_LRECL_FORADR has been deprecated. If specified, this parameter will be ignored.
  • The General Parameters panel (GTOP01A) and the Copy Options panel (GTOP02D) now include a new field named Call ADRDSSU when RECFM=U test fails. In this field, you can indicate whether Tape Optimizer should use the ADRDSSU utility or IEBGENER to copy a tape that has RECFM=U when the normal Tape Optimizer testing of the tape cannot determine whether the tape is to be copied by ADRDSSU or not. The corresponding new parameter for manually coded copy jobs is REQU_CALL_ADRDSSU_TSTF. For more information, see Setting defaults for general copy parameters; Specifying copy options for a copy request; and Other copy parameters.
  • Two new ISPF panels (GTOP01H and GTOP02U), both named "RECFM=U Specifications," have been added. On these panels, you can optionally identify the copy utility to use for any specific RECFM=U data sets for which you expect Tape Optimizer will be unable to select the copy utility automatically based on its normal testing. You specify default settings on the GTOP01H panel, and specify settings for a particular copy request on the GTOP02U panel. The utility that you specify for the data sets on these panels will override the utility that is selected by the Call ADRDSSU when RECFM=U test fails field. The corresponding new parameters for manually coded copy jobs are REQU_FILT_ADRD_nnnn, REQU_FILT_ADRF_nnnn, and REQU_FILT_ADRV_nnnn. For more information, see Setting the copy utility to use for specific RECFM=U data sets by default; Setting the copy utility to use for specific RECFM=U data sets; and RECFM=U data set parameters.
SC18-9560-07 (eighth edition) - June 2007
  • The General Parameters panel (GTOP01A) and the Copy Options panel (GTOP02D) include the new field Use Volume Expiration Date When no Data set Expiration Date. In this field, you can indicate whether Tape Optimizer should use the expiration date of the input tape volume as the expiration date for a data set on the output tape when that data set had no data-set expiration date on the input tape. The corresponding new parameter for manually coded copy jobs is REQU_USE_VOLEXP_IF_NODSNE. For more information, see Setting defaults for general copy parameters; Specifying copy options for a copy request; and Other copy parameters.
SC18-9569-06 (seventh edition) - May 2007
  • The General Parameters panel (GTOP01A) and the Copy Options panel (GTOP02D) include the new field Test files for ADR Dump when LRECL is 0. In this field, you indicate whether Tape Optimizer should test tape data sets to determine if they are ADRDSSU dump files when the data sets have 1) a LRECL of zero or a RECFM of U and 2) a create program name other than ADRDSSU. If the test indicates that a data set is an ADR dump file, Tape Optimizer calls the ADRDSSU utility to copy the data set. It is highly recommended that you enable this test to run. The corresponding new parameter for manually coded copy jobs is REQU_TEST_LRECL_FORADR.
  • Optional customization step: If you use a TVTOC to protect tape data sets, you will probably need to define a RACF® tape-data-set profile for the high-level-qualifier "TCMEND" for Tape Optimizer to be able to generate a TCMEND control file after each tape volume that is copied to a stacked tape.
  • Documentation clarification: For the Number of Days to Retain Input Tapes and Apply New Expiration Date to Input Volume When Copy by Data Sets fields now notes that Tape Optimizer does not calculate a new expiration date and apply it to input tapes if you also specify data-set renaming criteria for the copy request.
SC18-9569-05 (sixth edition) - April 2007
  • The Stacked Tape Parameters panels (GTOP01D for copy request defaults and GTOP02E for a specific copy request) contain the new field Specify Default Stacked Tape End Dataset Name Template. In this field, you define a template for generating the dummy data set name that Tape Optimizer records on a stacked tape when either a tape media threshold or the maximum file count is reached and a new tape needs to be loaded. This data set name marks the end of a tape in a series of stacked tapes. The following new messages are related to this field: GTO480E and GTO481E. For more information, see Setting defaults for stacked tape parameters and Specifying stacked tape parameters for a copy request.
SC18-9569-04 (fifth edition) - September 2006
  • The logic that Tape Optimizer uses to select a copy utility for a copy operation changed. Tape Optimizer will always use the ADRDSSU backup utility to copy a tape data set if the DFSMSrmm create program name is ADRDSSU, regardless of how you set the Call ADRDSSU when Blocksize is 0 option on the General Parameters panel or the Copy Options panel.
  • The General Parameters panel and the Copy Options panel include the new option Enable Job Restart. If you select this option, Tape Optimizer locks the Request Database when a copy job terminates abnormally so that you can restart the job later from the point at which it abended. If you clear this option, Tape Optimizer will not lock the Request Database. As a result, you will not be able to restart the copy job. However, the Request Database will be available for use by another copy job. The corresponding new parameter for manually coded copy jobs is REQU_JOB_RESTARTABLE. For more information, see Setting defaults for general copy parameters; Specifying copy options for a copy request; and Other copy parameters.
  • The General Parameters panel includes the new field Number of Seconds to Retry Allocation. In this field, you can specify the maximum number of seconds that Tape Optimizer should retry allocating input tape units for a copy request when the initial allocation attempt fails. Valid values are from 0 through 9999. The default value is 0, which causes Tape Optimizer to make no retry attempts. The corresponding new parameter for manually coded copy jobs is REQU_ALLOC_WAIT_SECS. For more information, see Setting defaults for general copy parameters and Other copy parameters.
  • If you use generation data groups (GDGs), you can now specify a generation data set name with a relative generation number when you create a copy request based on data set names or when you define a data-set-name filter. For more information, see Defining a basic copy request based on data set names and Creating a data-set-name filter.
  • You can now include a special percent sign (%) wildcard in criteria for renaming tape data sets as they are copied. This wildcard enables you to append a value to existing data set names to generate new data set names. For more information, see Criteria for renaming tape data sets.
  • If you select the Perform unit name validity check option on the General Parameters panel, Tape Optimizer will display the new Invalid Unit Name window whenever you specify an invalid input or output unit name on the General Parameters panel or the Create/Edit Request panel. From this window, you can direct Tape Optimizer to accept an invalid name if your SMS routines can interpret the name or if you intend to run the copy request on a processor where the name is valid. For more information, see Setting defaults for general copy parameters and Defining a basic copy request based on volsers.
  • A new report, called the Tape Selection Summary, lists the tapes and data sets that Tape Optimizer selects for copying based on the selection criteria that you specify in the basic copy request and any filters that you define. This report is generated when you perform a trial run or the actual run of a copy job. If the report is generated during a trial run, you can use it to check that the correct tapes and data sets will be copied when you actually run the copy job. For more information, see Tape Selection Summary report.
  • The following additional messages are documented: GTO004I, GTO216I, GTO250E, GTO363I, GTO435E, GTO437I, GTO438E, GTO439E, GTO440E, GTO441E, GTO442E, GTO443E, GTO444E, GTO445E, GTO446E, GTO447E, GTO448E, GTO449E, GTO450I, GTO451I, GTO452I, GTO453E, GTO454E, GTO455I, GTO456I, GTO457W, GTO458E, GTO459E, GTO460I, and GTO470E.

IBM Tivoli Tape Optimizer for z/OS 1.1

SC18-9569-03 (fourth edition) - March 2006
  • Tape Optimizer provides improved support for IBM 3592 tape drives and high-capacity tape media, such as Write Once Read Many (WORM) media. You can now use tapes that have the enterprise recording format EFMT1 or EFMT2 and a type of MEDIA5. The following new options and parameters are provided:
    • The General Parameters panel and the Copy Options panel include the new option Use Exact Data Set Name for Tape Unit Allocation. If you select this option, Tape Optimizer uses the exact name of the first data set that is selected for copying when allocating an output tape drive. If you specified data-set renaming criteria, Tape Optimizer uses the name that is generated for the first output data set. For SMS-managed data sets, this feature enables your ACS routines to determine that a 3592 tape drive with high-capacity media is needed. The corresponding parameter for manually coded copy jobs is REQU_USE_EXACT_TDSN. For more information, see Setting defaults for general copy parameters; Specifying copy options for a copy request; and Other copy parameters.
    • The Stacked Tape Parameters panels (for defaults and for a specific copy request) provide two new options, EFMT1 and EFMT2, for setting the maximum threshold utilization levels (in MBs) for tapes that have the EFMT1 or EFMT1 format. The corresponding parameters for manually coded copy jobs are REQU_EFMT1_THRESHOLD and REQU_EFMT2_THRESHOLD. For more information, see Setting defaults for stacked tape parameters and Specifying stacked tape parameters for a copy request.
  • Documentation clarification: Tape Optimizer does not support copying data from tapes that are managed by hierarchical storage management (HSM).
  • Documentation clarification: If you select the Copy Tape without Recatalog option, Tape Optimizer ignores the following catalog-related options if selected: Continue When Invalid Catalog Entries Found and Use FSEQ for Catalog Matches when DSSEQ Match Fails. Similarly, if you set the REQU_NO_RECATALOG parameter to Y in a manually created copy job, Tape Optimizer ignores the REQU_CONT_WHEN_INV_CATENT and REQU_USE_FSEQ_FOR_CAT parameters if specified.
  • Documentation clarification: The REQU_TLIB_TYPE parameter must be included in manually created tape-copy jobs. For more information, see Tape library parameter.
SC18-9569-02 (third edition) - January 2006
SC18-9569-01 (second edition) - November 2005
  • Tape Optimizer can now copy individual data sets from input tapes and stack them together onto output tapes. This copy strategy is an alternative to copying the entire tape chains that contain the data sets. The Create/Edit Request panel for data sets now includes VOLSER and DSSEQ columns in support of this feature. For more information, see Defining a basic copy request based on data set names.
  • The Dates Filters panel includes a new field named Tapes/Data Sets That Expire After for including tapes or data sets in a copy request that expire after a particular date. The pre-existing exclusion option Exclude tapes that expire before was renamed Tapes/Data Sets That Expire Before. For more information, see How expiration or retention dates are used in tape filtering and Creating a date filter.
  • The Other Filters panel includes a new inclusion option named Cataloged Data Sets. You can use this option to include only the data sets that are in the system catalog in a copy request. For more information, see Creating a filter based on other tape criteria.
  • The General Parameters panel now includes the following new options for specifying default values for copy requests:
    • Number of Copy Log Entries
    • Number of Seconds to Retry Re-Allocation
    • Continue Copy Following a Copy Utility Failure
    • Continue When Invalid Catalog Entries Found
    • Use FSEQ for Catalog Matches When DSSEQ Match Fails

    Also, the pre-existing option Do Not Use Assign/Create Date for Data Set Searches was moved to this panel from the Copy Options panel. The default values for the Number of Days to Retain Input Tapes field and the Perform unit name validity check field have changed.

    For information about all of these options, see Setting defaults for general copy parameters.

  • The Copy Options panel now includes the following new options:
    • Continue Copy Following a Copy Utility Failure
    • Apply New Expiration Date to Input Volume When Copy by Data Sets
    • Print Summary Statistics Reports
    • Continue When Invalid Catalog Entries Found
    • Use FSEQ for Catalog Matches When DSSEQ Match Fails

    For more information about these options, see Specifying copy options for a copy request.

    Also, the options Do Not Use Assign/Create Date for Data Set Searches and Perform Unit Name Validity Check were removed from this panel. They now appear on the General Parameters panel only.

  • The Default DFSMSrmm Parameters panel and the DFSMSrmm Copy Request Parameters panel now include the following new options:
    • Use Volume Expiration Date When a Volume Is Retained and No Data-Set Expiration Date or Retention Date Exists
    • Use Old Data-Set Retention Date When No Data-Set Expiration Date Exists
    • Continue After RMM Variable Copy Failure

    For descriptions of these options, see Setting defaults for DFSMSrmm parameters and Specifying DFSMSrmm parameters for a copy request.

  • You can now perform limited editing of copy requests that have the status ACTIVE or PEND RSTRT if these requests have actually terminated.
  • Manually created copy jobs now include a GTOUTRPT DD statement for indicating the destination for the summary report output for the copy job. For more information, see Basic JCL for a tape-copy job.
  • You can now specify the following new parameters when manually creating the JCL for a copy job:
    • REQU_CONT_COPY_AFTER_FAIL
    • REQU_CONT_WHEN_INV_CATENT
    • REQU_COPY_ONLY_CATALOGED
    • REQU_DFRM_CONT_VARCOPYFAIL
    • REQU_EXPR_DATE_INC
    • REQU_EXPIRE_COPY_BY_DATASET
    • REQU_PRINT_STATS_REPORTS
    • REQU_TABLE_BY_DSNVOL_nnnn
    • REQU_TABLE_BY_DSNDSQ_nnnn
    • REQU_USE_DSRET_AS_DSNEXP
    • REQU_USE_EXP_WHEN_DSNOTRET
    • REQU_USE_FSEQ_FOR_CAT

    For descriptions of these parameters, see Manually creating JCL for a Tape Optimizer job.

  • The following new messages, which are related to the new copy parameters, might be issued: GTO404W through GTO433W, GTO700E through GTO704W, GTO710E, GTO750I, and GTO755I. These messages are described in Messages.
  • The runtime_HLQ.CNTL library contains two new members that contain sample JCL for removing records from the stats file: GTOSTDEL and GTOSTREO. Also, the runtime_HLQ.CNTL library member GTOUTIL was renamed GTOUTILR to distinguish it from the member by the same name in the runtime_HLQ.LOAD library. For more information, see Product run-time libraries and files.