A fix is available
APAR status
Closed as program error.
Error description
When generating JCL to create an Image Copy from SLB, the following messages may be encountered: ARYS423E - The following object was selected but does not exist in the Backup: ARYS324I - Tablespace SAMACIC1.CICSNTF partition 001 ARYS355W - Build of object profile has resulted in no selected TS/IX objects. ...... If the JCL has already been generated, the following messages may appear during execution: ARYS288E - Dataset for Tablespace ARYD320.ARYES1 partition ALL did not exist at the time of system backup. ARYS840E - It may have been created with the DEFINE NO parameter.
Local fix
The customer may restart the backup process multiple times until the backup SSID displayed on the Restore System Display panel (ARY$REST) matches the Subsystem value in the object report header. Alternatively, the repository record can be manually corrected to ensure that the backup member matches the Subsystem value in the object report. To perform this correction: # Open the _System backups SSIDs VSAM repository file_ (DD name ARYSBSSD in JCL) in edit mode. # The record structure is as follows: profile name + creator + backup time (packed format) + backup member + additional metadata + all other detected data-sharing members + ... # Identify the correct record using HEX display mode (HEX ON) and locate the backup timestamp (e.g., 20260730010203 if backup time is 07-30-2026 01:02:03). # Update the member name immediately following the timestamp to match the Subsystem value in the object report. # Adjust the list of data-sharing members accordingly to maintain consistency. After saving the dataset: # Open the Restore System Display panel (ARY$REST) # Verify that the backup SSID reflects the corrected member # Retry the Image Copy creation
Problem summary
**************************************************************** * PROBLEM DESCRIPTION: * * Errors ARYS423E or ARYS288E may occur * * during Image Copy creation from SLB. * **************************************************************** * RECOMMENDATION: * * As a workaround, the customer may restart the * * backup process multiple times until the * * backup SSID displayed on the Restore System * * Display panel (ARY$REST) matches the * * Subsystem value in the object report header. * * * * Alternatively, the repository record can be * * manually corrected to ensure that the backup * * member matches the Subsystem value in the * * object report. * * * * To perform this correction: * * - Open the System backups SSIDs VSAM * * repository file (DD name ARYSBSSD in JCL) in * * edit mode. * * - The record structure is as follows: * * profile name + creator + backup time * * (packed format) + backup member + additional * * metadata + all other detected data-sharing * * members + ... * * - Identify the correct record using HEX * * display mode (HEX ON) and locate the backup * * timestamp (e.g., 20260730010203 if backup * * time is 07-30-2026 01:02:03). * * - Update the member name immediately * * following the timestamp to match the * * Subsystem value in the object report. * * - Adjust the list of data-sharing members * * accordingly to maintain consistency. * * * * After saving the dataset: * * - Open the Restore System Display panel * * (ARY$REST) * * - Verify that the backup SSID reflects the * * corrected member * * - Retry the Image Copy creation * * * **************************************************************** When generating JCL to create an Image Copy from SLB, the following messages may be encountered: ARYS423E - The following object was selected but does not exist in the Backup: ARYS324I - Tablespace <dbname>.<tsname> partition 001 ARYS355W - Build of object profile has resulted in no selected TS/IX objects. If the JCL has already been generated, the following messages may appear during execution: ARYS288E - Dataset for Tablespace ARYD320.ARYES1 partition ALL did not exist at the time of system backup. ARYS840E - It may have been created with the DEFINE NO parameter.
Problem conclusion
Apply the PTF.
Temporary fix
Comments
APAR Information
APAR number
PH72156
Reported component name
DB2 REC EXPERT
Reported component ID
5697H7400
Reported release
320
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2026-07-08
Closed date
2026-08-31
Last modified date
2026-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO09198
Modules/Macros
ARY#AAPI ARY#BUPD ARY#IDIO ARY#MGRT ARY#PIO ARY#QS10 ARY#RIO ARY#SMS ARY#VOLS ARY#VPRO ARY$APMN ARY$BACD ARY$BBLD ARY$BJOB ARY$BLDJ ARY$BPRC ARY$BPRD ARY$BPRU ARY$BPRV ARY$BSAU ARY$BUTD ARY$CG00 ARY$CGUP ARY$CRMD ARY$CRMU ARY$DGRP ARY$DOF1 ARY$DPRU ARY$ERBA ARY$IMGO ARY$MAIN ARY$OBJD ARY$OBJR ARY$OFF1 ARY$OPRC ARY$OPRD ARY$PARM ARY$PRCL ARY$PRFD ARY$PRFN ARY$RBAD ARY$RESO ARY$RPTD ARY$SSID ARY$SYMN ARY$VAL ARY@APRN ARY@BACK ARY@BAKE ARY@BAKO ARY@BAKS ARY@BAKV ARY@BCHK ARY@BDB2 ARY@BLDB ARY@BULD ARY@CGBK ARY@CGOF ARY@CGOR ARY@CGRS ARY@CGRV ARY@DISP ARY@MJCR ARY@MSGS ARY@OCPE ARY@OCPY ARY@OFLD ARY@OFLE ARY@ORCT ARY@ORPT ARY@ORSE ARY@ORST ARY@REST ARY@RSTE ARY@RVCP ARY@SCAT ARY@SCMD ARY@SDFG ARY@SIMG ARY@SOFF ARY@SOFR ARY@SOIC ARY@SQUE ARY@SRPT ARY@YDRM
Fix information
Fixed component name
DB2 REC EXPERT
Fixed component ID
5697H7400
Applicable component levels
R320 PSY UO09198
UP26/09/01 P F608
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 September 2026