A fix is available
APAR status
Closed as new function.
Error description
Support for IMS V14 KEYWORDS: IMSV14TGT/K IMSV13TGT/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS High Performance Unload for * * z/OS Version 1 Release 2 (FMID=H1IN120) * **************************************************************** * PROBLEM DESCRIPTION: This APAR provides the following new * * capabilities of HP Unload: * * 1. Run under IMS Version 14 * * 2. Unload HALDB 8GB OSAM data sets * * in IMS V13 and V14 * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR enables HP Unload to support IMS Version 14. And HALDB OSAM 8GB data sets are supported as input. If a HALDB to be unloaded is registered as OSAM8G in the RECON data set, the FABH0399I WTO message is issued: FABH0399I HALDB dbdname IS DEFINED AS OSAM8G
Problem conclusion
Temporary fix
Comments
======================== = DOCUMENTATION CHANGE = ======================== The IBM IMS High Performance Unload for z/OS User's Guide Version 1 Release 2 Suffix 7 (SC27-0936-07) should be changed as follows: --------------------------------------------------------------- 3.6 System programming interfaces 3.6.4 User record-formatting routine 3.6.4.3 Call parameters Parameter 7: RBA of segment prefix This 4-byte field contains the relative byte address of the segment prefix. The content of this field has a meaning only for HD databases. The user routine must never modify this field. If your IMS environment supports an OSAM database larger than 4 gigabytes, be careful with the RBA. You must check the flag byte SPRBAFLG when you treat an RBA. The flag SPRBAX4G in this flag byte is on if and only if all of the following conditions are satisfied: | - Your IMS environment supports relative byte addressability | for up to 8 gigabytes of data in an OSAM, HDAM, HIDAM, | PHDAM, or PHIDAM database data set. - Your database is an OSAM database. - Your database has an even block size. - The RBA of the segment prefix is larger than or equal to 4 gigabytes. Thus, if your IMS environment satisfies the first condition, you must check whether the flag SPRBAX4G is on or off. If the flag is on, the value in SPRBA is not the real RBA. In this case, you must move bit 1 of SPRBA to bit position 33 to get the real 33-bit RBA. See the sample code provided in the following figure. --------------------------------------------------------------- 7.2 Messages and codes 7.2.4 Messages 7.2.4.1 FABH messages -------------------------------------------------------------- FABH0031E DDNAME=ddname; DATA REQUEST OUTSIDE OF DATA SET LIMITS Explanation: The CAB buffer handler has received a data request for an OSAM block number or ESDS CI number that is not within the extents of the data set (indicated by ddname). System Action: HSSR Engine ends abnormally. User Response: Complete the following tasks to identify the cause, and take appropriate actions: - Activate the compare and hardcopy trace options, and execute the failing call sequence with the FABHTEST utility (see "FABHTEST utility for problem determination" in topic 7.1.3). - Ensure that the database processed by HSSR Engine was not being updated at the time when the error occurred. | - If an OSAM block over 4 gigabytes is requested by an odd | RBA in the HALDB, ensure that the HALDB is defined as | OSAM8G in the RECON data sets. -------------------------------------------------------------- | FABH0399I HALDB dbdname IS DEFINED AS OSAM8G | | Explanation: The indicated HALDB is defined as OSAM8G | in the RECON data set and the maximum capacity of OSAM data | sets is 8 gigabytes of data. | System Action: HSSR Engine continues processing. | User Response: None -------------------------------------------------------------- ================= End of Documentation Change ==================
APAR Information
APAR number
PI27636
Reported component name
IMS HIGHPERF UN
Reported component ID
5655E0600
Reported release
120
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2014-10-14
Closed date
2014-12-15
Last modified date
2015-05-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI23871
Modules/Macros
FABHA01 FABHA30 FABHB20 FABHB30 FABHC00 FABHDATE FABHFCKR FABHFPH4 FABHFSU FABHFSU4 FABHGDL4 FABHHSSR FABHHTBL FABHJCB FABHJCB0 FABHKEYX FABHLINK FABHPSL4 FABHRPTH FABHRTI0 FABHTCBU FABHTEST FABHTES4 FABHURG1 FABHURG3 FABHURG4 FABHX034 FABH001 FABH002 FABH0034 FABH0104 FABH011 FABH015 FABH015A FABH0203 FABH0204 FABH021 FABH022 FABH0304 FABH031 FABH040 FABH041 FABH0424 FABH050 FABH060 FABH070 FABH080 FABH081 FABH082 FABH083 FABH090 FABH091 FABH092 FABH093 FABH100 FABH105 FABH110 FABH111 FABH120A FABH120B FABH1202 FABH1203 FABH1204 FABH1208 FABH1209 FABH130 FABH140 FABH150 FABH160 FABH190 FABH2004 FABH201 FABH2504 FABH500 FABH510 FABH511 FABH512 FABH513 FABH5154 FABH5164 FABH520 FABH530 FABH535 FABH5404 FABH550 FABH560 FABH620 FABH6304 FABH650 FABH660 FABH661 FABH662 FABH663 FABH665 FABH680 FABH681 FABIHTBL FABIUNLS FABIUNL4 HPSSHDRH HPSSMSGT HPSSSCAN HPSSSCA4 HPSSSEH4 HPSUGVT0 HPSUHPTI HPSUHTBL HPSUMSGS HPSURPTH HPSURR05 HPSURR13 HPSUURG1 HPSUURG4 HPSUUSHF H1IN120J
| SC27093607 |
Fix information
Fixed component name
IMS HIGHPERF UN
Fixed component ID
5655E0600
Applicable component levels
R120 PSY UI23871
UP14/12/17 P F412
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.
[{"Line of Business":{"code":"LOB10"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSCX89K","label":"IMS Tools"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.2.0"}]
Document Information
Modified date:
14 December 2020