A fix is available
APAR status
Closed as unreproducible in next release.
Error description
IMS V9 RUNUNDER SUPPORT FOR HP UNLOAD V1.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS High Performance Unload for * * OS/390 Version 1 Release 1 (FMID=H1IN110). * **************************************************************** * PROBLEM DESCRIPTION: By the maintenance provided by this * * APAR, IMS High Performance Unload for * * OS/390 Version 1 Release 1 is enabled * * to run on IMS Version 9 (Program Number * * 5655-J38). * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** IMS High Performance Unload for OS/390 has been modified so that it can run on IMS Version 9.
Problem conclusion
Temporary fix
Comments
======================== = DOCUMENTATION CHANGE = ======================== IMS High Performance Unload for OS/390 User's Guide ( SC27093602 ) should be changed as follows: * PREFACE.5 References to IMS Products and Releases To make the text in this book easier to read, the version and release level of IMS has been abbreviated. The following abbreviation is used: >>Delete IMS Version 5 refers to IMS/ESA Version 5 Release 1 >>End of delete IMS Version 6 refers to IMS/ESA Version 6 Release 1 IMS Version 7 refers to IMS Version 7 Release 1 IMS Version 8 refers to IMS Version 8 Release 1 | IMS Version 9 refers to IMS Version 9 Release 1 Also, those versions of IMS are simply referred to as IMS, except where distinctions need to be made between the various versions. * 1.1 Introduction 1.1.3 Processing Environment 1.1.3.1 Software Requirements | High Performance Unload operates in an operating system environment. Its operating system requirements are the same as those for IMS supported by High Performance Unload. : 1.1.3.3 Restrictions High Performance Unload is subject to the following restrictions with respect to processing environment: o It cannot be run under IMS Utility Control Facility (UCF). o It does not support the checkpoint and restart capability. Restrictions related with each utility program are described in the chapters for each utility. | High Performance Unload does not supports the HALDB, if one or | more partition is following condition: | | o HALDB OLR is currently running. | o Active data sets is M-through-V. | o Two active data sets (A-through-J and M-through-V) exist. * 1.6 Application Programming Interface 1.6.2 Preparing and Running Application Program 1.6.2.3 Coding DL/I Calls or EXEC DLI command for HSSR PCB 1.6.2.3.1 Call Types Supported by Each API Set >>Delete Note: APISET 2, APISET 3, and GNP calls in APISET 1 are supported by IMS Version 6 or later. >>End of delete 1.6.2.3.2 EXEC DLI Command Types Supported by Each API Set : | Note: An HSSR call gives the same results as a DL/I call or an EXEC DLI command, with some minor differences. For details, see "PCB Feedback Information" in topic 1.6.4. * 1.8 Specifying Options for HSSR Engine 1.8.2 HSSROPT Data Set 1.8.2.2 Description of Control Statements 1.8.2.2.1 APISET Control Statement Notes: 1. If you specify APISET 3, you cannot specify any of the following control statements can be specified: BYINDEX, DBSTATS, KEYCHECK, or SKERROR. : >>Delete 4. APISET 2, APISET 3, and GNP calls in APISET 1 are supported by IMS Version 6 or later. >>End of delete 1.8.2.2.21 PCBLIST Control Statement : Notes: 1. If your application program issues a DL/I system call that gets access to the IMS PCB list, it is recommended that you specify PCBLIST IMS. One such call is the INQY call with the FIND subfunction, which returns the PCB address of the requested PCB name. | 2. If your application program issues an HSSR call as an EXEC DLI command, you must specify PCBLIST IMS. * 2.4 System Programming Interfaces 2.4.4 Writing User Record-Formatting Routine 2.4.4.3 Call Parameters 2.4.4.3.7 Parameter 7: RBA of Segment Prefix ---------- Product-Sensitive Programming Interface ----------- 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 should never modify this field. | If your IMS environment supports an OSAM database larger than 4 gigabytes, pay attention to 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: : 2.4.4.5 Get-by-RBA Calls 2.4.4.5.2 Finding the RBA Required by the Get-by-RBA Call : The control blocks should never be modified by user routines (except the field HJCBUSER of the HJCB and the field HSDBUSER of the HSDB, which can be freely used). | Note: If you plan to use the Get-by-RBA call on the IMS | environment that support an OSAM database larger than 4 gigabytes, pay attention to the RBA that you get from HSSR Engine. You must check the flag byte HDMBAMDA in the HDMB for the database data set that you are processing when you treat an RBA. The flag HDMBOS8G in this flag byte is on if and only if all of the following conditions are satisfied: : * 3.2 Generation of Sequential Subset Randomizer 3.2.1 Job Steps The assembly requires the following macro libraries: o SYS1.MACLIB o HPS.SHPSMAC0 o IMSVS.MACLIB (or IMS.SDFSMAC for IMS Version 7 or later) | o IMSVS.GENLIBB (for IMS Version 6) : * 4.0 Messages and Codes 4.4 Messages 4.4.2 Message Variables 4.4.2.1 FABH Messages >> The following new message is added: | FABH0634E DBDS=A-J FOR DBD=xxxxxxxx NOT ACTIVE | | Explanation: HP unload cannot process the DBD (xxxxxxxx), if | one or more partitions are one of following condition: | o The M-V DBDS datasets are active. | o Processing of the INITIATE OLREORG command is not | completed. | | System Action: HSSR Engine ends abnormally. | | Programmer Response: If the M-V database data sets are active, | reset the active database data sets to A-J. If processing of | the INITIATE OLREORG command is not completed, the command is | made to completed.
APAR Information
APAR number
PQ80191
Reported component name
IMS HIGHPERF UN
Reported component ID
5655E0600
Reported release
110
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2003-10-29
Closed date
2003-12-12
Last modified date
2004-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UQ83063
Modules/Macros
FABHB159 FABHB20 FABHB30 FABHDATE FABHFPH9 FABHFSU FABHFSU9 FABHGDL9 FABHHSSR FABHHSS9 FABHHTBL FABHLINK FABHPLI9 FABHPSFM FABHPSL9 FABHRPTH FABHRTI0 FABHTCB FABHTCBU FABHTEST FABHTES9 FABHURG1 FABHURG9 FABHX034 FABH002 FABH0039 FABH0109 FABH011 FABH015 FABH015A FABH0209 FABH021 FABH022 FABH0309 FABH031 FABH040 FABH041 FABH0429 FABH050 FABH060 FABH070 FABH080 FABH081 FABH082 FABH083 FABH090 FABH091 FABH092 FABH093 FABH100 FABH105 FABH110 FABH111 FABH1209 FABH130 FABH140 FABH150 FABH160 FABH190 FABH2009 FABH201 FABH2509 FABH500 FABH510 FABH511 FABH512 FABH513 FABH5159 FABH5169 FABH520 FABH530 FABH535 FABH5409 FABH550 FABH560 FABH620 FABH6309 FABH650 FABH660 FABH661 FABH662 FABH663 FABH665 FABH680 FABH681 FABIHTBL FABIUNLS FABIUNL9 HPSSHDRH HPSSMSGT HPSSSCAN HPSSSCA9 HPSSSEH9 HPSUGVT0 HPSUHPTI HPSUHTBL HPSUMSGS HPSURPTH HPSUURG1 HPSUURG9 H1IN110J
| SC27093602 |
Fix information
Fixed component name
IMS HIGHPERF UN
Fixed component ID
5655E0600
Applicable component levels
R110 PSY UQ83063
UP03/12/17 P F312
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":"110"}]
Document Information
Modified date:
20 October 2020