IBM Support

PH06305: IMS HP IMAGE COPY ALLOWS WILDCARD SPECIFICATION IN DBD AND PART KEYWORDS OF IMAGE COPY FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • By this APAR, wildcard specification is enabled in Image Copy
    function.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS High Performance Image Copy for z/OS *
    *                 Version 4 Release 2 users ( FMID=H1J0420 ).  *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR provides that wildcard        *
    *                      specification is allowed in DBD and     *
    *                      PART keyword of Image Copy function.    *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR provides that wildcard specification is allowed in DBD
    and PART keyword of Image Copy function. By this APAR, the
    wildcard specification is enabled in DBD and PART keyword in the
    image copy function. The wildcard specification is allowed in
    with image copy function only. If you use wildcard specification
    of DBD and PART, following considerations are applied:
     - Run the process with DBRC=Y
     - Do not use DD= or AREA= keyword with DBD/PART which uses
       wildcard specification
    
    Example:
    //ICEIN DD *
     GLOBAL DBRC=Y,ICOUT=*
     IC DBD=DB* <--- (1)
     IC DBD=PHDAM,PART=PHDAM1* <--- (2)
    
    By this specification,
    (1) DBs whose names are started with DB are scheduled
    (2) Partition in DB: PHDAM whose names are started with PHDAM1
        are scheduled.
    
    ========================
    = DOCUMENTATION CHANGE =
    ========================
    The IBM IMS High Performance Image Copy for z/OS Version 4
    Release 2 User's Guide (SC19-2756-02) should be changed as
    follows:
    
    Running IMS HP Image Copy > Control statements and keywords
    > ICEIN control statement keywords
        DBD keyword
          Format
            >>-DBD=dbdname-------------------------------<
            dbdname
              The name of the DBD that includes the data set
              process.
              To process a HALDB, specify the master DBD name.
    |         dbdbname can be specified with wildcards when you run
    |         Image Copy function. Wildcards are the asterisk (*)
    |         and the percent (%) symbol. The wildcard symbol can
    |         not be used the top character of the dbdname. An
    |         asterisk (*) represents 0 - 7 characters, whereas
    |         a percent (%) symbol represents a single character.
    |         For example, DBD=dbd* matches dbd, dbd1, dbd12345,
    |         and so on. If two or more asterisks (*) are specified
    |         in sequence, only the first asterisk is recognized. In
    |         you use the wildcards in DBD keyword, you should
    |         consider followings:
    |         - Can not be used for the CRC and RCV control
    |           statements.
    |         - Use the wildcards, DBRC=Y is required.
    |         - Do not use DDN or AREA keyword with the wildcard.
    
    
        PART keyword
          Format
           >>-PART=partition_name-----------------------><
            partition_name
              The partition name that is registered in DBRC for
              each partition data set. This keyword is effective
              for HALDBs.
    |         partition_name can be specified with wildcards when
    |         you run Image Copy function. Wildcards are the
    |         asterisk (*) and the percent (%)
    |         symbol. An asterisk (*) represents 0 - 7 characters,
    |         whereas a percent (%) symbol represents a single
    |         character. For example, PART=part* matches partA,
    |         part1A, part12A, and so on. If two or more asterisks
    |         (*) are specified in sequence, only the first
    |         asterisk is recognized. In you use the wildcards in
    |         PART keyword, you should consider followings:
    |         - Can not be used for the CRC and RCV control
    |           statements.
    |         - Use the wildcards, DBRC=Y is required.
    |         - DBD= keyword for HALDB master DBD name is required.
    |         - Do not use DDN keyword with the wildcard.
    
    Troubleshooting > Message and codes > Messages
    
    |  FABJ0253E WILDCARD SYMBOL * OR % IS SPECIFIED AS THE FIRST
    |  CHARACTER OF DBD KEYWORD
    |   Explanation: The wildcard symbols asterisk (*) and the
    |   percent (%) are not allowed to use as the first character of
    |   the DBD keyword.
    |   System action: Program FABJMAIN stops processing with a
    |   return code of 16.
    |   User response: Correct the error and rerun the job.
    
    |   FABJ0254E DBRC=Y IS REQUIRED WHEN USING WILDCARD
    |   SPECIFICATION IN DBD/PART KEYWORD
    |   Explanation: When the wildcard specification is applied to
    |   DBD or PART keyword, DBRC=Y is required.
    |   System action: Program FABJMAIN stops processing with a
    |   return code of 16.
    |   User response: Correct the error and rerun the job
    
    |   FABJ0294E NO MATCHING DBD FOR DBD=xxxxxxxx IS FOUND IN RECON
    |   Explanation: There is no DB information in DBRC RECON that
    |   responds to DBD=xxxxxxxx specification.
    |   System action: Program FABJMAIN stops processing with a
    |   return code of 16.
    |   User response: Check the DB record in the RECON data set and
    |   rerun the job.
    
    |   FABJ0295E NO MATCHING DBD [OR PARTITION] FOR DBD=xxxxxxxx
    |   [PART=ppppppp] IS FOUND
    |   Explanation: There is no DBD or PART information in DBRC
    |   RECON that responds to DBD=xxxxxxxx[,PART=ppppppp]
    |   specification.
    |   System action: Program FABJMAIN stops processing with a
    |   return code of 16.
    |   User response: Check the DB or PART record in the RECON data
    |   set and rerun the job.
    
    |   FABJ0296E NO PROCESSED DB IS FOUND
    |   Explanation:  Any image copy are not  processed, because any
    |   of found DBDs from DBRC RECON does not exist in DBD library.
    |   System action: Program FABJMAIN stops processing with a
    |   return code of 16.
    |   User response: Check the RECON dataset and IMS DD.
    |   After that, rerun the job.
    
    |  FABJ4095E RECON ACCESS FAILED.
        Explanation: An error was detected in the RECON access
        processing. description provides additional information
        about the error:
       - DBRC LIST COMMAND IS NOT COMPLETED. RC=xxxxxxxx
       - SYSPRINT DD FOR DBRC LIST COMMAND IS SPECIFIED AS DUMMY
       - INTERNAL ERROR OCCURRED
       - FUNC=fffffffff RETURN CODE=xxxxxxxx REASON CODE=xxxxxxxx
         KEYS: DBD=dbdname DDN=ddname KEYTYPE=xxxxxxxxxxxx
    |  - FUNC=fffffffff RETURN CODE=xxxxxxxx REASON CODE=xxxxxxxx
    |  - FUNC=fffffffff TYPE=tttttttt DBD=xxxxxxxx
    |    RETURN CODE=xxxxxxxx REASON CODE=xxxxxxxx
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH06305

  • Reported component name

    IMS HP IMAGE CO

  • Reported component ID

    5655K9600

  • Reported release

    420

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2018-12-11

  • Closed date

    2018-12-27

  • Last modified date

    2019-01-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI60448

Modules/Macros

  • FABJACQG FABJAPIM FABJASPM FABJATRC FABJCMDB FABJCRC0 FABJCRC1
    FABJCRC3 FABJCTCV FABJCZCV FABJDALC FABJDALO FABJDALS FABJDAPI
    FABJDBAL FABJDBC1 FABJDBCM FABJDBD2 FABJDBD3 FABJDBD4 FABJDBD5
    FABJDBD9 FABJDBDA FABJDBDB FABJDBF0 FABJDBLK FABJDBR2 FABJDBR3
    FABJDBR4 FABJDBR5 FABJDBR9 FABJDBRA FABJDBRB FABJDCTL FABJDDIM
    FABJDEMP FABJDFC2 FABJDFC3 FABJDFC4 FABJDFC5 FABJDFC9 FABJDFCA
    FABJDFCB FABJDMP0 FABJDMP2 FABJDMP3 FABJDMP4 FABJDMP5 FABJDMP9
    FABJDMPA FABJDMPB FABJDOPN FABJDPS2 FABJDPS3 FABJDPS4 FABJDPS5
    FABJDPS9 FABJDPSA FABJDPSB FABJDPUT FABJDREQ FABJDRQS FABJDRSN
    FABJFCAI FABJFCC2 FABJFCC3 FABJFCC4 FABJFCC5 FABJFCC9 FABJFCCA
    FABJFCCB FABJFCCM FABJFCD2 FABJFCD3 FABJFCD4 FABJFCD5 FABJFCD9
    FABJFCDA FABJFCDB FABJFDMP FABJGDGB FABJGLRP FABJICDD FABJIDX2
    FABJIDX3 FABJIDX4 FABJIDX5 FABJIDX9 FABJIDXA FABJIDXB FABJINT1
    FABJINT2 FABJINT3 FABJIPRC FABJISDD FABJLINK FABJMAIN FABJMAS1
    FABJMDP2 FABJMDP3 FABJMDP4 FABJMDP5 FABJMDP9 FABJMDPA FABJMDPB
    FABJMRGE FABJMSGC FABJMSUL FABJNTFC FABJNTFI FABJNTFS FABJOFDD
    FABJOFL0 FABJOFL1 FABJORC2 FABJORC3 FABJORC4 FABJORC5 FABJORC9
    FABJORCA FABJORCB FABJPARM FABJPRM2 FABJPRM3 FABJRCH2 FABJRCH3
    FABJRCH4 FABJRCH5 FABJRCH9 FABJRCHA FABJRCHB FABJRDB2 FABJRDB3
    FABJRDB4 FABJRDB5 FABJRDB9 FABJRDBA FABJRDBB FABJRETC FABJRETM
    FABJRFC2 FABJRFC3 FABJRFC4 FABJRFC5 FABJRFC9 FABJRFCA FABJRFCB
    FABJRPT0 FABJRPT1 FABJSAS1 FABJSAS2 FABJSDBK FABJSTA  FABJTERM
    FABJTFSI FABJTGEN FABJTGET FABJTOI  FABJTOI2 FABJUIC1 FABJWCRD
    FABJXCR  FABJXHPC FABJXLIM
    

Publications Referenced
SC19275602    

Fix information

  • Fixed component name

    IMS HP IMAGE CO

  • Fixed component ID

    5655K9600

Applicable component levels

  • R420 PSY UI60448

       UP18/12/29 P F812

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.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89E","label":"IMS Tools"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0"}]

Document Information

Modified date:
10 April 2023