A fix is available
APAR status
Closed as new function.
Error description
HP UNLOAD API issued MSGFABH0334E or MSGFABH0674E for GN/GNP call with one or two qualified SSAs to retrieve a 2nd level dependent segment. FABH0332E: SEGMENT-NAME IN SSA IS NOT ROOT-NAME FABH0674E ERROR FOUND IN HSSR CALL STATEMENT, INVALID NUMBER OF PARAMETERS
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS High Performance Unload * * for OS/390 Release 1 (FMID=H1IN110) * **************************************************************** * PROBLEM DESCRIPTION: This APAR provides several * * enhancements of HP Unload API. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR provides the following enhancements of HP Unload API; 1. In all APISETs, GU call with an unqualified SSA for root segment is allowed. 2. In APISET 2 and 3, a qualified SSA on the sequence key field of the 2nd level segment is allowed in GN and GNP call. 3. In APISET 2 and 3, two SSAs are allowed in GN and GNP call. The first SSA must specify the root segment and the second SSA must specify the second level segment. 4. If a call unsupported by the HSSR call handler is issued by the user application, the call is printed in the "Trace Output" report in the HSSRTRAC data set even if TRHC and TRDB control statements are not specified in the HSSROPT data set. 5. When 'APISET 3' is specified, the HSSR call handler issues an error message and the FABH0695I message before passing an unsupported call to the IMS DL/I call handler: +FABH0315E GN CALL SSA-1 IS UNSUPPORTED:COMMAND CODE +FABH0695I DL/I CALLS TO HSSR PCB (PCB#=0001) ARE PASSED TO IMS DL/I User can ignore the error message.
Problem conclusion
Temporary fix
Comments
======================== = Documentation Change = ======================== IBM IMS High Performance Unload for OS/390 User's Guide (SC27-0936-04) should be changed as follows: ================================================================ 1.0 Using High Performance Unload 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 "1.6.5 Restrictions". Table 12. DL/I call types supported by each API set +--------+----------------------------------------------------+ | API set| Call types supported | +--------+----------------------------------------------------+ |APISET 1| The following call types are supported: | | | - GU and GHU calls without SSA | | | the first root segment of the database is | | | retrieved. | || | - GU and GHU calls with an unqualified SSA that | || | contains only the name of a root segment type. | | | : | +--------+----------------------------------------------------+ |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 the following | || | two SSAs; | || | - The first SSA is a qualified SSA on the root | || | sequence key with equal-to (=b,b=,or EQ) | || | relational operator. | || | For HDAM, the position at the root segment | || | must be established by the preceding call. | || | - The second SSA is an unqualified or a qualified| || | SSA that contains the name of a dependent | || | segment type at the second level. | || | Any other combination of two SSAs is not | || | supported. | +--------+----------------------------------------------------+ |APISET 3|The 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. | +--------+----------------------------------------------------+ | If a user application issues a call that is unsupported | by the HSSR call handler, the call is printed as the last call | in the 'Trace output' report in the HSSRTRAC data set | even if the TRHC and TRDB control statements are not specified | in the HSSROPT data set. ================================================================ 1.6.2.3.2 EXEC DLI command types supported by each API set High Performance Unload supports three API sets. APISET 1 is the system default. Table 13 shows the EXEC DLI Command types supported by each API set, and their effects with and without SEGMENT options: Table 13. EXEC DL/I command types supported by each API set +--------+----------------------------------------------------+ | API set| Command types supported | +--------+----------------------------------------------------+ |APISET 1| The following command types are supported: | || | - GU command without SEGMENT options | || | - GU command with a SEGMENT option that contains | || | the name of a root segment type. | | | : | +--------+----------------------------------------------------+ |APISET 2| The following command types are supported for | || | HIDAM,HDAM,PHIDAM, and PHDAM in addition to | | | the command types supported in APISET 1: | || | - GN or GNP command with a SEGMENT option | | | that contains the name of a dependent | | | segment type. | || | - GN or GNP command with a SEGMENT option and | || | a WHERE option qualified on the sequence key of | || | a second level dependent segment type. | +--------+----------------------------------------------------+ |APISET 3|The 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 an HSSR application program: : - 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" in topic 1.6.2.3.1. - 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 not supported. | Two SSAs are supported restrictedly. - Command codes except for NULL('*-') command code are not supported. - Multiple qualification statements are not supported. : ================================================================ 4.4 Messages 4.4.2 Message variables 4.4.2.1 FABH messages ---------------------------------------------------------------- | FABH0315E GU/GHU/GN/GHN/GNP/GHNP CALL SSA-n IS UNSUPPORTED: | reason | | Explanation: The application program issued a call | with one or two 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. | 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. | | 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" in topic 1.6.2.3.1 or "EXEC DLI command | types supported by each API set" in topic 1.6.2.3.2. ---------------------------------------------------------------- FABH0332E SEGMENT-NAME IN SSA IS NOT ROOT-NAME Explanation: The application program issued an HSSR GN call with an SSA; the segment name in the SSA is not the name of the root segment. System Action: HSSR Engine ends abnormally. | Programmer Response: Specify 'APISET 2' or 'APISET 3'. For details about the call types and command types that APISET supports, see "Call types supported by each API set" in topic 1.6.2.3.1 or "EXEC DLI command types supported by each API set" in topic 1.6.2.3.2. ---------------------------------------------------------------- FABH0333E SEGMENT-NAME IN SSA NOT FOLLOWED BY A BLANK Explanation: The application program issued an HSSR GN call with an SSA; the 8-byte segment name in the SSA is not followed by a blank. System Action: HSSR Engine ends abnormally. | Programmer Response: Specify 'APISET 2' or 'APISET 3'. For details about the call types and command types that APISET supports, see "Call types supported by each API set" in topic 1.6.2.3.1 or "EXEC DLI command types supported by each API set" in topic 1.6.2.3.2. ---------------------------------------------------------------- FABH0481E INVALID PARAMETER NUMBER IN CALL Explanation: The application program issued an HSSR call with an incorrect number of parameters (too few or too many). | The HSSR call handler does not support three or more SSAs. | 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' | control statement. If APISET is 3, there is no need | to take care this message. Problem Determination: The following parameters are required for Assembler and COBOL programs: - Call function - PCB - I/O AREA - SSA (optional) The following parameters are required for PL/I programs: - PARM count - Call function - PCB - I/O AREA - SSA (optional) ---------------------------------------------------------------- | FABH0489E UNSUPPORTED COMMAND CODE Explanation: The application program issued a call with a command code that is not supported by HSSR call handler. HSSR call handler supports only the "T" and "NULL" command codes. System Action: HSSR Engine ends abnormally. | Programmer Response: Specify 'APISET 3'. For details about the call types and command types that APISET supports, see "Call Types Supported by Each API Set" in topic 1.6.2.3.1 or "EXEC DLI Command Types Supported by Each API Set" in topic 1.6.2.3.2. ---------------------------------------------------------------- FABH0674E ERROR FOUND IN HSSR CALL STATEMENT, INVALID xxxxxx Explanation: The HSSR language interface detected an error in the HSSR call statement described in xxxxxx. xxxxxx is one of the following: PARAMETER COUNT: | If APISET is 1, the parameter count must be 3 or 4. | If APISET is 2, the count must be from 3 to 5. | If APISET is 3, the count must be from 3 to 18, inclusive. PCB ADDRESS: PCB address is incorrect. NUMBER OF PARAMETERS: | If APISET is 1, the number of parameters must be 3 or 4. | If APISET is 2, the number must be from 3 to 5. | If APISET is 3, the number must be from 3 to 18, inclusive. System Action: HSSR Engine ends abnormally. | Programmer Response: Specify 'APISET 2' or 'APISET 3'. ---------------------------------------------------------------- | FABH0675E ROOT SEGMENT POSITION IS NOT ESTABLISHED | | Explanation: Two or more SSAs are specified and the first | is a qualified SSA, but the root segment position has not | established yet by the preceding call. | This call is not supported by the HSSR call handler. | 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' | control statement. If APISET is 3, ignore this message. ---------------------------------------------------------------- ================= End of Documentation Change ================== ×**** PE07/08/24 FIX IN ERROR. SEE APAR PK49836 FOR DESCRIPTION
APAR Information
APAR number
PK32595
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
2006-10-06
Closed date
2006-10-19
Last modified date
2007-08-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK18960
Modules/Macros
FABHGND FABHGSA FABHHSS8 FABHHSS9 FABHJCB FABHJCB0 FABHPLI8 FABHPLI9 FABHTCB FABHTCBU FABH001 FABH002 FABH012 FABH0208 FABH0209 FABH090 FABH090C FABH092 FABH100 FABH2007 FABH2008 FABH2009 FABH310 HPSUHOUT HPSUURG8 HPSUURG9 HPSUUSHF HQ090C
| SC27093604 |
Fix information
Fixed component name
IMS HIGHPERF UN
Fixed component ID
5655E0600
Applicable component levels
R110 PSY UK18960
UP06/10/21 P F610
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