A fix is available
APAR status
Closed as new function.
Error description
HP UNLOAD API does not support a GN/GNP call with three or more SSAs and MSGFABH0481E is issued for the call: FABH0481E: INVALID PARAMETER NUMBER IN CALL This restriction will be removed depending on the combination of qualified and unqualified SSAs.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS High Performance Unload for * * OS/390 Release 1 (FMID=H1IN110) * **************************************************************** * PROBLEM DESCRIPTION: HP Unload API passes the GN call * * with 3 SSAs to IMS DL/I incorrectly. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR provides the enhancements of HP Unload API. 1. In APISET 2 and 3, a GN/GNP call with the N SSAs to retrieve the N-th level segment is supported (2<=N<=15). Here, the allowable combinations of qualified SSA and unqualified SSA are: - N unqualified SSAs - 1 qualified SSA for root and N-1 unqualified SSAs - 1 qualified SSA for root and N-2 unqualified SSAs and a qualified SSA - N-1 qualified SSAs and a unqualified SSA - N qualified SSAs For any other combinations of SSAs, the error of FABH0315E is issued. 2. In APISET 2 or 3, the trace for the call that is unsupported by HP Unload API is printed in the HSSRTRAC data set.
Problem conclusion
Temporary fix
Comments
======================== = Documentation Change = ======================== IBM IMS High Performance Unload for OS/390 User's Guide (SC27-0936-05) should be changed as follows: ================================================================ 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 High Performance Unload supports three API sets. APISET 1 is the system default. Table 12 shows the DL/I call types supported by each API set, and their effects with and without segment search arguments (SSAs): Note: For restrictions, see "Restrictions" in topic 1.6.5. Table 12. DL/I call types supported by each API set +--------+---------------------------------------------------+ |API Set | Call types supported | +--------+---------------------------------------------------+ |APISET 1| | : : : +--------+---------------------------------------------------+ |APISET 2| The following call types are supported for HIDAM, | | | HDAM, PHIDAM, and PHDAM in addition to the call | | | types supported in APISET 1: | | | - GN, GHN, GNP, and GHNP calls with an unqualified| | | SSA that contains the name of a dependent segment| | | type. | | | | | | - GN, GHN, GNP, and GHNP calls with a qualified | | | SSA that contains the name of a dependent segment| | | type at the second level. | | | | || | - GN, GHN, GNP, and GHNP calls with N SSAs | || | to retrieve the segment at the N-th level | || | (2<=N<=15). The following combinations of SSAs | || | are supported: | || | - N unqualified SSAs | || | - N qualified SSAs | || | - a qualified SSA, N-2 unqualified SSAs, and | || | a unqualified or qualified SSA | || | - N-1 qualified SSAs and a unqualified SSA | || | | || | Here, the first SSA must contain the root segment| || | name and only "equal-to" (=b,b=,or EQ) relational| || | operator is allowed for each qualified SSA. | | | | +--------+---------------------------------------------------+ |APISET 3| The fully supported call types are the same as | | | those in APISET 2. Once an unsupported call is | | | issued for HIDAM, HDAM, PHIDAM, or PHDAM, | | | the call and all the succeeding calls to | | | the HSSR PCB are passed to the IMS DL/I call | | | handler to continue the processing instead of | | | ending it abnormally. | +--------+---------------------------------------------------+ =============================================================== 1.6.5 Restrictions : The following restrictions apply to HSSR calls: - For details of call types supported in each API set, see "Call types supported by each API set" - If APISET 1 or 2 is specified, or if the target is a non-HD database, the following restrictions are applied: - An unqualified or qualified SSA is not fully supported. | - Three or more SSAs are supported restrictedly. - Command codes except for NULL('*-') command code are not supported. - Multiple qualification statements are not supported. - If APISET 3 is specified for non-HD database and the unsupported call is issued, HSSR Engine ends abnormally without passing the succeeding call to IMS DL/I. - A get-next call issued after GU calls that returned a GE status might not return the same segment as DL/I. : =============================================================== 4.4.2.1 FABH messages ( The explanation of the FABH0315E message is modified.) ---------------------------------------------------------------- FABH0315E GU/GHU/GN/GHN/GNP/GHNP CALL SSA-n IS UNSUPPORTED: reason Explanation: The application program issued a call with one |or more SSAs. The n-th SSA is not supported by the HSSR call handler. The reason is one of: SEGMENT NAME The segment name is not defined in the HSSR PCB. SEGMENT LEVEL The SSA for the segment level is not supported. COMMAND CODE The command code is not supported. NON-SEQ FIELD The field is not a sequence key. | NON-UNIQUE KEY | The key field is not unique RELATIONAL OPERATOR The relational operator is not supported. MULTI QUALIFICATION STATEMENTS The multi-qualification statement is not supported. QUALIFIED SSA The qualified SSA for root segment is not supported because the database is HDAM or PHDAM. | CALL FUNCTION | The call type is not supported. | UNKNOWN | Unknown reason The unsupported call is printed in the Trace output report in the HSSRTRAC data set. System Action: If APISET is 2, HSSR Engine ends abnormally. If APISET is 3, the call and all the succeeding calls to the HSSR PCB are passed to the IMS DL/I call handler to continue the processing instead of ending it abnormally. Programmer Response: If APISET is 2, specify 'APISET 3'. If APISET is 3, ignore this message. For details about the call types and command types supported by the HSSR call handler, see "Call types supported by each API set" or "EXEC DLI command types supported by each API set". ----------------------------------------------------------------
APAR Information
APAR number
PK55449
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
2007-10-25
Closed date
2007-11-07
Last modified date
2007-12-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK31029
Modules/Macros
FABHGDLA FABHGDL8 FABHGDL9 FABHGND FABHGSA FABHJCB FABHJCB0 FABH002
| SC27093605 |
Fix information
Fixed component name
IMS HIGHPERF UN
Fixed component ID
5655E0600
Applicable component levels
R110 PSY UK31029
UP07/11/10 P F711
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