A fix is available
APAR status
Closed as program error.
Error description
IMU 4.10 PMR 57468,999,000 which is related to PMR 50609,999,000 (DLI SC04 in FSYGDBD0). ================================================================ Date reported: 05/07/2015 This APAR Supersedes APARs PI41397 and PI41786. Severity: High Users Affected: All IMU users of IMU V4.10 Problem Description: IMS/DLI programs are ABENDing for SC04. This occurs when there are no fields defined within segments in the DBD definitions. Problem Summation The program FSYGDBD0 walks thru the DBD definitions in attempt to build an SSA string. The SSA string is defined of the segment name and the key for that segment. The key is the 1st defined field in the DBD for the specified segment. The problem is that when there are no fields available, the field displacement generated in the DBD is x'ffffffff' (i.e -1). The logic in FSYGDBD0 does not check for 'no fields', therefore it ABENDs due to x'ffffffff' in the displacement field. Note: A qualified SSA is built for all Parent Segments used in the RETRIEVE statement. The key must be defined as IMU uses it to build the qualified SSA string. Problem Conclusion: The FSYGDBD0 logic was changed to ABEND with a message indicating a missing key situation. A new RETRIEV2 macro was written that must be used in the place of the RETRIEVE statement to sweep database in sequential mode. Impact on existing programs: There is no impact on existing programs that work properly. IMS/DLI programs that are using keyless segments must change RETRIEVE statement in EZT Program to use %RETRIEV2 macro instead. The macro syntax is compatible with the RETRIEVE statement as described in the IMU Reference Manual. The RETRIEVE is replaced by the %RETRIEV2 macro name. The program must be compiled and linked to run with AMODE(24), RMODE(24). Example: JOB INPUT DBDFILE %RETRIEV2 DBDFILE + SELECT (SEGMENT1 . . + . + . + SEGMENT-n ) Changed modules: FSOFT01.V4R1M0.SFSYLOAD FSYGDBD0 - existing module FSOFT01.V4R1M0.SFSYFJCC RETRIEV2 - new CCL1 macro (please assign a FSY* name) ================================================================
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All IMU V4.1 users. * **************************************************************** * PROBLEM DESCRIPTION: IMS/DLI programs are ABENDing for SC04. * * This occurs when there are no fields * * defined within segments in the DBD * * definitions. * **************************************************************** * RECOMMENDATION: Apply the PTF. * **************************************************************** The program FSYGDBD0 walks thru the DBD definitions in attempt to build an SSA string. The SSA string is defined of the segment name and the key for that segment. The key is the 1st defined field in the DBD for the specified segment. The problem is that when there are no fields available, the field displacement generated in the DBD is x'ffffffff' (i.e -1). The logic in FSYGDBD0 does not check for 'no fields', therefore it ABENDs due to x'ffffffff' in the displacement field. Note: A qualified SSA is built for all Parent Segments used in the RETRIEVE statement. The key must be defined as IMU uses it to build the qualified SSA string.
Problem conclusion
The FSYGDBD0 logic was changed to ABEND with a message indicating a missing key situation. A new RETRIEV2 macro was written that must be used in the place of the RETRIEVE statement to sweep database in sequential mode. Impact on existing programs: There is no impact on existing programs that work properly. IMS/DLI programs that are using keyless segments must change RETRIEVE statement in EZT Program to use %RETRIEV2 macro instead. The macro syntax is compatible with the RETRIEVE statement as described in the IMU Reference Manual. The RETRIEVE is replaced by the %RETRIEV2 macro name. The program must be compiled and linked to run with AMODE(24), RMODE(24). Example: JOB INPUT DBDFILE %RETRIEV2 DBDFILE + SELECT (SEGMENT1 . . + . + . + SEGMENT-n )
Temporary fix
Comments
APAR Information
APAR number
PI46029
Reported component name
MIGRATION UTILI
Reported component ID
5697N4400
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-07-30
Closed date
2015-08-14
Last modified date
2015-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FSYGDBD0 FSYRTRV2
Fix information
Fixed component name
MIGRATION UTILI
Fixed component ID
5697N4400
Applicable component levels
R410 PSY UI30225
UP15/08/19 P F508
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":"SSY4B9","label":"IBM Migration Utility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
27 October 2020