A fix is available
APAR status
Closed as program error.
Error description
Copying an image copy using IMS V10, ABENDU3835 occurs because HPIC notifies DBRC of a recovery time with embedded blanks. This is a bug of CRC, when IMS V10 is used with UTC timestamp. The timestamp length has been expanded by IMS V10. KEYWORDS: IMSV10TGT/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS High Performance Image Copy for z/OS * * Version 4 Release 1 users ( FMID=H1J0410 ) * **************************************************************** * PROBLEM DESCRIPTION: HPIC Create Image Copy function * * terminates with ABEND U3835 * * ( ABENDU3835 ) and message FABJ3835E * * ( MSGFABJ3835E ) when all of the * * following conditions are satisfied: * * - IMS V10 is used. * * - UTC timestamp offset ( +00:00 ) is * * used. * * - Created image copy data set is * * notified to DBRC as either the * * primary or the secondary image copy. * * * * Also, this APAR fixes the problem, HPIC * * Create Image Copy function and Recovery * * function always use current time zone * * as offset value, when all of the * * following conditions are satisfied: * * - IMS V10 is used. * * - TIMESTMP= keyword with offset value * * different from current time zone is * * specified in ICEIN control statement. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** HPIC Create Image Copy function terminates with ABEND U3835 ( ABENDU3835 ) and message FABJ3835E ( MSGFABJ3835E ) when all of the following conditions are satisfied: - IMS V10 is used. - UTC timestamp offset ( +00:00 ) is used. - Created image copy data set is notified to DBRC as either the primary or the secondary image copy. The cause of this problem is that HPIC Create Image Copy process sets the incorrect UTC timestamp offset to the CHANGE.IC command. Also, this APAR fixes the problem, HPIC Create Image Copy function and Recovery function always use current time zone as offset value, when all of the following conditions are satisfied: - IMS V10 is used. - TIMESTMP= keyword with offset value different from current time zone is specified in ICEIN control statement. The cause of this problem is that HPIC always uses the current time zone that is obtained from CVT ( Communications Vector Table ) instead of the offset value specified by TIMESTMP= keyword.
Problem conclusion
FABJRCHK has been modified to handle the timestamp offset correctly. The following modules have been reassembled. FABJRCH7 FABJRCH8 FABJRCH9 FABJRCHA
Temporary fix
Comments
APAR Information
APAR number
PK67873
Reported component name
IMS HP IMAGE CO
Reported component ID
5655K9600
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-06-19
Closed date
2008-06-24
Last modified date
2010-08-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK37643
Modules/Macros
FABJRCHA FABJRCHK FABJRCH7 FABJRCH8 FABJRCH9
Fix information
Fixed component name
IMS HP IMAGE CO
Fixed component ID
5655K9600
Applicable component levels
R410 PSY UK37643
UP08/06/26 P F806
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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"4.1.0","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020