A fix is available
APAR status
Closed as program error.
Error description
PM70710 handled the issue of twin segments extracted from one database and loaded into another not being in the same sequence in the loaded database as they were in the extracted database. The behavior was changed of the Load (ILB) because users of FM/IMS objected that when they used the Extract (IXB) and Load (ILB) to extract data from one database and load it into another, twin segments in the loaded database were not in the same sequence as they were in the extracted database. FM/IMS was modified with the fix for APAR PM70710 to maintain the sequence of twin segments when they are extracted from one database and loaded into another. This has been found to be a problem for some users who depend on the pre-PM70710 behavior.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All FM/IMS Load (ILB) users. * **************************************************************** * PROBLEM DESCRIPTION: The fix for APAR PM75413 changed the * * behaviour of the Load (ILB) function. * * Some customers were relying on the * * pre-PM75413 behaviour. * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** Without the fix for APAR PM75413, segments with no key or a non unique key, are inserted according to the insert rule for the segment type. With the fix for APAR PM75413, segments with no key or a non unique key are inserted as the last occurrence - this is irrespective of the insert rule for the segment type. The modification was made so that twin segments extracted from one database and loaded into another are in the same sequence in the loaded database as they were in the extracted database. Pre-PM75413, the Extract (IXB) and Load (ILB) did not maintain the sequence of twin segments when the insert rule for these segments was FIRST or HERE. Nevertheless, some customers were relying on the pre-PM75413 behaviour.
Problem conclusion
The FM/IMS Load (ILB) has been modified to support a new parameter - USELCMD. When the USELCMD parameter is set to N, segments with no key or a non unique key are inserted according to the insert rule for the segment type - that is the pre-PM75413 behaviour. When the USELCMD parameter is set to Y or is not specified, segments with no key or a non unique key are inserted as the last occurrence - that is the post-PM75413 behaviour. The FM/IMS Load dialog has been modified to include the 'Do not override insert rules' option. When this option is selected and there is a segment with an insert rule of FIRST or HERE in the primary database or a logically related database, the JCL generated by the dialog includes the card: $$FILEM USELCMD=N, When this option is not selected and there is a segment with an insert rule of FIRST or HERE in the primary database or a logically related database, the JCL generated by the dialog includes the card: $$FILEM USELCMD=Y, Otherwise, the dialog does not generate a USELCMD= card. Publication Closing Code: DEVCHNG For the documentation changes associated with this APAR, please refer to: ftp://public.dhe.ibm.com/software/websphere/awdtools/ filemanager/fmv12apar.pdf The changes are to the following publications: PUB ID PUB NAME ------------ ---------------------------------------- SC19-3674-00 File Manager for z/OS V12R1 User's Guide and Reference The latest published manuals can be found at: http://www.ibm.com/software/awdtools/filemanager/library/ index.html.
Temporary fix
Comments
APAR Information
APAR number
PM94819
Reported component name
FILE MANAGER Z/
Reported component ID
5655W6800
Reported release
C14
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-09
Closed date
2013-09-10
Last modified date
2013-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FMN1LVL FMN1LVLJ FMN1LVLK
SC19367400 |
Fix information
Fixed component name
FILE MANAGER Z/
Fixed component ID
5655W6800
Applicable component levels
RC1C PSY UK97433
UP13/09/13 P F309
RC14 PSY UK97436
UP13/09/13 P F309
RC15 PSY UK97437
UP13/09/13 P F309
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":"C14","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C14","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
03 October 2013