A fix is available
APAR status
Closed as new function.
Error description
This APAR provides the following enhancements to Optim processing: 1.The reporting of the amount of data processed by Optim and contained in ARCHIVE and EXTRACT files (Data Byte Count) will be enhanced to provide utility to request such value for existing files as well as an improved means of presentation. 2.There are many scenarios when a System Error is being raised in Optim to issue an error message and terminate processing. The System Error use is not very user friendly. It aborts the processing without the user being able to address the reason for an error. The length of the message is limited to 72 characters. In many cases the messages are cryptic and do not provide enough information. This APAR attempts to address some of the more common System Errors as well as to introduce a rudimentary supplemental message framework with the goal of improving the overall message processing capabilities.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Optim for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: This APAR provides the following * * enhancements to Optim processing: * * * * 1. There are many scenarios when a * * System Error is being raised in Optim * * to issue an error message and terminate * * processing. * * The System Error use is not very user * * friendly. It aborts the processing * * without the user being able to address * * the reason for an error. The length of * * the message is limited to 72 * * characters. * * In many cases the messages are cryptic * * and do not provide enough information. * * This APAR attempts to address some of * * the more common System * * Errors as well as to introduce a * * rudimentary supplemental message * * framework with the goal of improving * * the overall message processing * * capabilities. * * * * 2. The reporting of the amount of data * * processed by Optim and contained in * * ARCHIVE and EXTRACT files (Data Byte * * Count) will be enhanced to provide * * utility to request such value for * * existing files as well as an improved * * means of presentation. * **************************************************************** * RECOMMENDATION: Apply the provided fix. * **************************************************************** Provide enhancements requested by customers, see problem description.
Problem conclusion
Optim processing will be enhanced to provide the following enhancements: 1. Certain System Errors have been replaced with a more robust error handling and reporting. These scenarios include: o Optim directory entry mismatch, o Optim directory entry missing when required, o ARCHIVE or EXTRACT files having invalid BLKSIZE after being copied, o File validation errors. 2. The ARCHIVE and EXTRACT file Data Byte Count values will be now available in additional scenarios and by the following means: o ISPF ARCHIVE Browse (9.B, Summary) or ISPF EXTRACT Browse (7.B, Summary) will provide the cumulative Data Byte Count for all tables within the file. Same value can be obtained by the using the REPORT utility in BATCH and specifying RPTTYPE SUM. o Optim will now collect the Data Byte Count information for newly created and newly imported ARCHIVE and EXTRACT files in its Object Directory (when the file has been cataloged). The information will be available under ISPF by using 9.4 (I)nfo on an entry or in BATCH using the DIRECTORY utility. Per table values, when available, can be obtained with the DETAIL YES parameter. o The DIRECTORY batch utility will now provide a Total Data Byte Count for all files selected for processing using the specified selection criteria, as well as per file values when available for newly created or imported ARCHIVE or EXTRACT files. For older files, new keywords of DATACOUNT and DATACOUNTTAPE can be specified to get the Data Byte Count values. See below for details. o To allow for programmatic collection of the Data Byte Count values Optim will introduce two ARCHIVE ACTION variables of: O FOP_TBL_DATA_BYTECOUNT, most useful for "After Extract of Last Row From a Table" or "After Delete of the Last Row From a Table" or "After Restore of the Last Row From a Table" and providing data byte count for the table being processed. Note that the values for a RESTORE process will reflect the count for the entire file as presented for processing and are not being adjusted for any selection criteria used. O FOP_TOTAL_DATA_BYTECOUNT, a running total of byte counts for all tables processed so far for similar events as above. These variables can be used in ARCHIVE ACTIONS and the defined SQL or calls to stored procedures. See below for details. The following Optim for z/OS publications are being updated by this APAR: o Common Elements, Chapter 2, Access Definitions, Archive Actions, Substitution Variables, add to the list of General Variables available to all action statements: o FOP_TBL_DATA_BYTECOUNT, Data Byte Count for all rows processed so far for the current table (for ARCHIVE), or the total count for all rows at the time of the archive file creation (for DELETE and RESTORE), Return Value Type: bigint. o FOP_TOTAL_DATA_BYTECOUNT, Data Byte Count for all rows processed so far for all tables (for ARCHIVE), or total count for all rows at the time of the archive file creation (for DELETE and RESTORE), Return Value Type: bigint. o Common Elements, Chapter 7, Table Maps, Archive Actions, Action Variables, add to the list of General Variables available to all action statements: o FOP_TBL_DATA_BYTECOUNT, Data Byte Count for all rows processed so far for the current table (for ARCHIVE), or the total count for all rows at the time of the archive file creation (for DELETE and RESTORE), Return Value Type: bigint. o FOP_TOTAL_DATA_BYTECOUNT, Data Byte Count for all rows processed so far for all tables (for ARCHIVE), or total count for all rows at the time of the archive file creation (for DELETE and RESTORE), Return Value Type: bigint. o Batch Utilities, Chapter 3, Maintenance Utilities, Archive Entry and File Management, DIRECTORY, the following new control keywords will be accepted: o DATACOUNT NO | YES The DIRECTORY request TYPE ARC or EXT will now provide detailed and total Data Byte Counts, when available in the Optim directory for files created or imported after application of APAR PH04646/PH04647. For older files, such counts may be obtained by processing the actual data files associated with a specific directory entry. NO Default, do not process physical ARCHIVE or EXTRACT files when Data Byte Count is not available in the Optim directory. YES Process physical ARCHIVE or EXTRACT files when Data Byte Count is not available in the Optim directory. This includes files on DISK. Files located on TAPE and Tivoli or Centera devices will not be processed. o DATACOUNTTAPE NO | YES The DIRECTORY request TYPE ARC or EXT will now provide detailed and total Data Byte Counts, when available in the Optim directory for files created or imported after application of APAR PH04646/PH04647. For older files, such counts may be obtained by processing the actual data files associated with a specific directory entry. NO Default, do not process physical ARCHIVE or EXTRACT files when Data Byte Count is not available in the Optim directory. YES Process physical ARCHIVE or EXTRACT files when Data Byte Count is not available in the Optim directory. This includes files on DISK and TAPE. Files located on Tivoli or Centera devices will not be processed.
Temporary fix
Comments
APAR Information
APAR number
PH04154
Reported component name
OPTIM MOVE FOR
Reported component ID
5655V0700
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2018-10-16
Closed date
2018-12-20
Last modified date
2019-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI60408
Modules/Macros
FOP00003 FOP00103 FOP00203 FOP00303 FOP00B FOP01B FOP05B FOP07B FOP08B FOP09B FOP0AB FOP0BB FOP0ITKA FOP1ODRV FOP1OSFN FOP3DTPR FOP4IPMN FOP4PEMN FOP4PMMN FOP4TRCE FOP9APIM FOP9GINF FOPCFPMN FOPCXLIB FOPD2V85 FOPD2V91 FOPD2VA5 FOPD2VNN FOPHSTM FOPIO FOPK03 FOPK05 FOPK10 FOPLUAH FOPMADDE FOPMAFCN FOPMAIN FOPMAMAI FOPMARCN FOPMCBMN FOPMCDRT FOPMCENU FOPMCMAI FOPMCMMN FOPMCOFN FOPMCOLA FOPMCOLP FOPMDBMN FOPMDDDL FOPMDMAI FOPMDPRC FOPMDXTR FOPMECMN FOPMEMAI FOPMIXMM FOPMMCMN FOPMMCMR FOPMMJBS FOPMMUNU FOPMMUTL FOPMSELM FOPMTMDB FOPMUXIM FOPODPP FOPOMN FOPRS10 FOPRS8 FOPRS9 FOPUMCBT FOPUUNLD FOPVOU FOPZFBMN FOPZFMMN FOPZMAIN FOPZSUB
Fix information
Fixed component name
OPTIM MOVE FOR
Fixed component ID
5655V0700
Applicable component levels
RB70 PSY UI60408
UP18/12/22 P F812
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2019