Updates to IMS High Performance Unload V1.2 User's Guide

Product documentation


Abstract

Updates that apply to IMS High Performance Unload V1.2 User's Guide (SC27-0936-07)

Content

The most recent updates appear at the top of the list.



Update 3
Date of change: June 2014
Change description: Documentation changes by APAR PI10157. This APAR adds IMS database versioning support.
Topics: Changes apply to multiple topics.

---------------
Topic:
> 2.0 Unloading IMS databases
>> 2.1 Introduction to the unload utilities
>>> 2.1.2 Restrictions for IMS High Performance Unload

Restriction items have been added as follows:

Restrictions common to all HSSR applications

The following restrictions apply to all HSSR application programs including the FABHURG1 utility and the FABHFSU utility:
  • ...
  • ...
  • Start of changeIf IMS database versioning is enabled and any database version other than the current version is specified, HSSR Engine passes the DL/I calls to the DL/I call handler of IMS. Certain HSSROPT control statements are ignored. For more information, see the explanation of message FABH0638W. For the FABHURG1 utility and the FABHFSU utility, any database version other than the current version is not supported.End of change
  • The following restrictions apply to HSSR calls:
    • ...
    • ...

Restrictions common to FABHURG1 and FABHFSU

The following restrictions are common to FABHURG1 and FABHFSU:
  • The DBD that specifies the input database must be a physical DBD.
  • Start of changeIf IMS database versioning is enabled, only the current version of the database can be used. Any other versions of the database are not supported.End of change
  • ...

---------------
Topic:
> 2.0 Unloading IMS databases
>> 2.1 Introduction to the unload utilities
>>> 2.1.3 Considerations for using the unload utilities
>>>> 2.1.3.4 Considerations for HALDB Online Reorganization capable partitions

New report has been added to the following list:
...

Because the DBSTATS control statement is ignored, the following reports are not printed:
  • Start of change DB Call Statistics report DB Statistics reportEnd of change
  • Randomizing Statistics report
  • DB Record Length Distribution report

---------------
Topic:
> 2.0 Unloading IMS databases
>> 2.2 Basic job control language
>>> 2.2.1 Preparing the basic JCL

Step 3, which is shown below, has been deleted from this topic:

...

Start of change3. Modify the cataloged procedures for IMS DBRC SCI registration.
    If the IMS DBRC SCI registration requires the IMSplex name and the DBRC group identification, you must add the appropriate parameters (IMSPLEX= or PARM1=) to the FABHULU, FABHDLI, and FABHDBB catalog procedures as shown in the following figure.


    //FABHULU PROC IMSDSN=IMSVS,DBTLMD='HPS.SHPSLMD0',SOUT='*',
    //             MBR=TEMPNAME,CTRL=DFSRRC00,DBD=,BUF=7,
    //             SPIE=0,TEST=0,EXCPVR=0,RST=0,PRLD=,SRCH=0,
    //             CKPTID=,MON=N,LOGA=0,FMTO=T,IMSID=,SWAP=,DBRC=,
    //             IRLM=,IRLMNM=,IMSPLEX=,PARM1=
    //*
    //G EXEC PGM=FABHX034,PARM=('&CTRL/ULU',&MBR,&DBD,&BUF,
    //             &SPIE&TEST&EXCPVR&RST,&PRLD,&SRCH,&CKPTID,&MON,
    //             &LOGA,&FMTO,&IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM,
    //             ,,,,,,,,&IMSPLEX,,'&PARM1')
    Figure. Adding IMSPLEX and PARM1 parameters to the FABHULU procedure

    In the JCL that uses the FABHULU procedure, you can specify the parameter values as shown in the following figure.


    //UNLOAD EXEC FABHULU,
    //          MBR=FABHFSU,DBD=PHDV0100,DBRC=Y,
    //          IRLM=Y,IMSPLEX=PLEX1,PARM1='DBRCGRP=001'
    Figure. Example of the parameter specification for the FABHULU procedure
End of change

---------------
Topic:
> 7.0 Troubleshooting
>> 7.2 Messages and codes
>>> 7.2.4 Messages
>>>> 7.2.4.1 FABH messages

The following new messages have been added:

Start of change
FABH0638W SPECIFIED DBVER IS NOT SUPPORTED. HSSR CALLS FALL BACK TO DL/I

Explanation: IMS database versioning is enabled, but the specified database is not the current version of the database. HSSR Engine supports only the current version of the database when IMS database versioning is enabled. HSSR Engine passes subsequent DL/I calls to the DL/I call handler of IMS.
System action: HSSR Engine ignores BYINDEX, CO, DBSTATS, KEYCHECK, and SKERROR control statements specified in the HSSROPT data set, and activates the BLDLPCK option. HSSR Engine continues processing, however, the performance decreases.
User Response: Specify the current version of the database.
End of change
--------
Start of change
FABH0286E SPECIFIED DBVER IS NOT SUPPORTED

Explanation: IMS database versioning is enabled, but the specified database is not the current version of the database. When IMS database versioning is enabled, only the current version of the database can be used.
System action: FABHURG1 or FABHFSU ends abnormally.
User Response: Specify the current version of the database.
End of change
--------
Start of change
FABH0659E SPECIFIED DBVER IS NOT SUPPORTED

Explanation: IMS database versioning is enabled in the ULU region, but the specified database is not the current version of the database. When IMS database versioning is enabled, only the current version of the database can be used.
System action: HSSR Engine ends abnormally.
User Response: Check whether DBVERSION=(YES,DBLEVEL=BASE) statement is coded in the DFSDF xxx member of the IMS.PROCLIB data set. If the statement exists, remove it or change the DBLEVEL value so that the current version of the database is used.
End of change



Update 2
Date of change: November 2013
Change description: Documentation changes by APAR PM97558. This APAR adds a new control statement, SKIPAUTH, for the HSSR Engine. You can use this control statement to bypass IMS DBRC database authorization for HALDB partitions.
Topics: Changes apply to the following multiple topics.

> 2.0 Unloading IMS databases
>> 2.9 Options for HSSR Engine
>>> 2.9.1 Overview of HSSROPT control statements

SKIPAUTH control statement has been added to the following table:

Table. List of HSSROPT control statements for HSSR Engine
(Table 28 in PDF and BookManager formats)
Used for Keyword Function
Call analyzer and call handler ... ...
Start of changeSKIPAUTH Specifies whether to bypass IMS DBRC database authorization for HALDB partitions.End of change
... ...

---------------
>> 2.9 Options for HSSR Engine

The following new topic has been added:

Start of change
SKIPAUTH control statement

The SKIPAUTH control statement specifies whether to bypass IMS DBRC database authorization to avoid DBRC authorization failure (DFS047A) for HALDB partitions.

SKIPAUTH YES is effective only when the HALDB is processed in the ULU region. Otherwise, it is ignored.

Position
    Description
1
    Code the SKIPAUTH keyword to bypass IMS DBRC database authorization.
10
    Specify one of the following operands:
    YES
      Requests HSSR Engine to bypass IMS DBRC database authorization.
    NO
      Requests HSSR Engine not to bypass IMS DBRC database authorization. NO is the default value.
End of change
===============
>7.0 Troubleshooting
>> 7.2 Messages and codes
>>> 7.2.4 Messages
>>>> 7.2.4.1 FABH messages

The following two new messages have been added:

--------
Start of change
FABH0677E INVALID SKIPAUTH CONTROL STATEMENT IS SPECIFIED

Explanation: An incorrect operand is specified on the SKIPAUTH control statement in the HSSROPT data set. The operand must be either YES or NO.
System action: The incorrect statement is ignored.
User response: Correct the SKIPAUTH statement and then rerun the job.
End of change
--------
Start of change
FABH0696I "SKIPAUTH YES" IS APPLICABLE ONLY TO HALDB

Explanation: SKIPAUTH YES is specified in the HSSROPT data set. This control statement is applicable only to HALDBs.
System action: HSSR continues processing. If the database is a HALDB, IMS DBRC database authorization request is bypassed.
User response: If you want to avoid DBRC authorization failure (DFS047A) for non-HALDBs, specify DBRC=N and then rerun the job.
End of change
--------
The following two messages have been deleted:
  • FABH0385E JCB POINTERS TO SDB'S NOT OK
  • FABH0392E SECONDARY LIST OF LP NOT FOUND



Update 1
Date of change: September 2012
Change description: User's guide correction
Topic:
> 3.0 Tuning and customizing HSSR application jobs
>> 3.7 Site default options
>>> 3.7.1 How the runtime parameters are determined

The first paragraph has been replaced with the following paragraph:

Start of changeIMS HP Unload uses the parameter values that are specified in the HSSROPT, HSSRCABP, SYSIN, and CARDIN data sets. If parameter values are not found in these data sets but in the FABHOPT option table, values in the FABHOPT option table are used. If parameter values are not found in the data sets nor in the FABHOPT option table, the system default values are used. End of change

Publication number

SC27-0936-07

Copyright date

2000, 2012

Original publication date

2012/9/5

Cross reference information
Segment Product Component Platform Version Edition
Information Management IMS Tools IMS Database Solution Pack z/OS

Rate this page:

(0 users)Average rating

Document information


More support for:

IMS Tools
IMS HP Unload

Software version:

1.2.0

Operating system(s):

z/OS

Reference #:

7036099

Modified date:

2014-06-16

Translate my page

Machine Translation

Content navigation