A fix is available
APAR status
Closed as program error.
Error description
Customer is performing ARCHIVE with DELETE after ARCHIVE. The ARCHIVE step produces an ARCHIVE file with no rows in it. The DELETE step reports that there are no rows to be deleted and terminates as expected. An attempt to process the CONTROL file from the DELETE step yields the following error: *** ERROR *** CANNOT OPEN THE DATA FILE REFERENCED BY THE CONTROL FILE
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Optim users. * **************************************************************** * PROBLEM DESCRIPTION: Optim issues the error message where * * there is no actual error condition. * **************************************************************** Optim issues the error message where there is no actual error condition. The DELETE process completes without error but leaves the CONTROL file in an "invalid" state due to certain DELETE optimization measures. The subsequent REPORT function is then unable to process such CONTROL file.
Problem conclusion
Optim DELETE processing logic will be enhanced to issue the following new message (following the *** WARNING ***) when none of the tables in the AF had any rows hence none have been delete from the tables: *** WARNING *** THERE WERE NO ROWS TO BE DELETED No errors. Due to successful completion, CONTROL file has been invalidated. An attempt to process the CONTROL file In such scenario will result, as before, in the error message of: *** ERROR *** CANNOT OPEN THE DATA FILE REFERENCED BY THE CONTROL FILE Note that this will only occur when the user did not specify the EMPTY_TABLE_FOUND_RC4 YES keyword. With EMPTY_TABLE_FOUND_RC4 YES, the DELETE optimization for empty delete set of rows is disabled and the CONTROL file will be valid and can be processed.
Temporary fix
Comments
APAR Information
APAR number
PH38306
Reported component name
OPTIM MOVE FOR
Reported component ID
5655V0700
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-06-21
Closed date
2021-07-19
Last modified date
2021-08-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FOP1OSFN FOP9APIM FOPCFPMN FOPCRDB FOPCXLIB FOPHSTM FOPIBDPK FOPIBIND FOPIDBNM FOPIDMTB FOPIGRNT FOPIIXNM FOPINS2 FOPISGNM FOPITABL FOPITSNM FOPITSPC FOPIX000 FOPIX001 FOPK04 FOPMAIN FOPMARCN FOPMCBMN FOPMCENU FOPMCMAI FOPMCMMN FOPMCOLA FOPMCOLP FOPMDBMN FOPMDPRC FOPMECMN FOPMMCMR FOPMMJBS FOPMMUNU FOPMMUTL FOPODPP FOPOMN FOPRS10 FOPRS3 FOPRS9 FOPTBIPK FOPTDBN1 FOPTDMTX FOPTGRNT FOPTIX00 FOPTIXNM FOPTSGNM FOPTTABL FOPTTSPC FOPTX001 FOPTXBND FOPTXBPK FOPTXSNM FOPZFMMN FOPZMAIN
Fix information
Fixed component name
OPTIM MOVE FOR
Fixed component ID
5655V0700
Applicable component levels
RB70 PSY UI76359
UP21/07/22 P F107
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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"B70"}]
Document Information
Modified date:
10 August 2021