IBM Support

OA48006: PROVIDE CAPABILITY TO COORDINATE GKB AND CODE MODIFICATIONS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Some GKB updates need to be synchronmized with the code change
    as they are both shipped separately. Some users missed the code
    change update after they apply the GKB updates.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IBM Tivoli Asset Discovery for z/OS      *
    *                 V 8.1 users.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: This fix addresses various              *
    *                      problems, particularly in the           *
    *                      working of the code with the GKB.       *
    *                                                              *
    *                      1. The code does not check that         *
    *                      the Repository and GKB are at           *
    *                      compatible maintenance levels.          *
    *                                                              *
    *                      2. The code does not                    *
    *                      diagnose the use of an old GKB.         *
    *                                                              *
    *                      3. The code does not                    *
    *                      diagnose common errors in loading       *
    *                      the GKB.                                *
    *                                                              *
    *                      4. AUTOCOMMIT is turned off             *
    *                      during Usage Import COUNTUSAGE          *
    *                      processing.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. SMP/E usually takes care of issues of code coordinated
    maintenance levels, but the GKB and database updates are
    performed outside of SMP/E. Some significant updates need
    to be applied uniformly for continued safe operation, but the
    current mechanism is purely manual relying on update
    instructions being correctly followed.
    
    2. Use of an old GKB means that latest identification changes
    and corrections are being missed, but the code currently only
    displays the GKB date, and does not issue a warning against
    the use of an old GKB.
    
    3. It is unfortunately common for the GKB load job to
    be missed in a new setup, and the code that needs to
    access the GKB does not expect this type of error, and
    may issue some cryptic error messages.
    
    4. The AUTOCOMMIT value may be left inadvertently off during
    Usage Import COUNTUSAGE processing. This may lead to delays
    and an increased number of Database locks in some
    setups.
    

Problem conclusion

  • 1. The code now checks that the GKB and Repository are at the
       expected level. This mechanism is added for future use.
       This update will tolerate previous Databases as per normal,
       and future maintenance that is not significant, but will
       fail once a future GKB or Database maintenance is applied
       that requires an equivalent code maintenance to be applied.
    
    2. An informational message will be displayed in the log and
       standard output if the GKB is old, as a reminder to update
       the GKB. This will not affect the job return code.
    
    3. The Inquisitor Import and Aggregator which access the GKB
       will perform some checks that the GKB has been loaded.
    
    4. AUTOCOMMIT is now turned on during Usage Import processing,
       and its value is displayed in the log.
    
    The following are documentation updates:
    
    Administration Guide and Reference SC22-5474-00
    
    
    Administration Guide and Reference SC22-5474-00
    
    Product documentation is updated as follows:
    +--- Tivoli Asset Discovery for z/OS Version 8 Release 1 -----+
    |                                                             |
    |PROGRAM NUMBER: 5698-AA4                                     |
    |                                                             |
    |TITLE: Tivoli Asset Discovery for z/OS                       |
    |       Administration Guide and Reference                    |
    |                                                             |
    |Chapter 11. Troubleshooting, messages, and support           |
    |                                                             |
    |Section: Tivoli Asset Discovery for z/OS messages -          |
    |         HSIC messages                                       |
    |                                                             |
    |Add the following messages:                                  |
    |                                                             |
    |HSIC081E Incompatible GKB level for gkb schema:schema.       |
    |Expected level:expected_level_number,received:               |
    |received_level_number.                                       |
    |                                                             |
    |Explanation:                                                 |
    |                                                             |
    |A mismatch between the GKB level and the level expected by   |
    |the program was found. This indicates that the GKB and the   |
    |code are at different maintenance levels. If the             |
    |received_level_number is greater than the                    |
    |expected_level_number, it indicates that a later level of the|
    |the GKB is used than can be handled by the current           |
    |maintenance level of the code.                               |
    |If the received_level_number is less than the expected       |
    |level_number, it indicates that an old level of the GKB that |
    |can no longer be handled by the current maintenance level    |
    |of the code is used.                                         |
    |                                                             |
    |System action:                                               |
    |                                                             |
    |The application terminates.                                  |
    |                                                             |
    |User response:                                               |
    |                                                             |
    |Apply GKB and code maintenance to the indicated GKB schema as|
    |required to ensure code and GKB are compatible. Contact IBM  |
    |support for further assistance.                              |
    |                                                             |
    |HSIC082E Incompatible repository level for repository schema:|
    |schema. Expected level:expected_level_number,received:       |
    |received_level_number.                                       |
    |                                                             |
    |Explanation:                                                 |
    |                                                             |
    |A mismatch between the Database repository level and the     |
    |level expected by the program was found. This indicates that |
    |the repository and the code are at different                 |
    |maintenance levels.                                          |
    |If the received_level_number is greater than the             |
    |expected_level_number, it indicates that a later level of    |
    |the repository is used than can be handled by the current    |
    |maintenance level of the code.                               |
    |If the received_level_number is less than the expected       |
    |level_number, it indicates that an old level of the          |
    |repository that can no longer be handled by the              |
    |current maintenance level of the code is used.               |
    |                                                             |
    |System action:                                               |
    |                                                             |
    |The application terminates.                                  |
    |                                                             |
    |User response:                                               |
    |                                                             |
    |Apply Database repository and code maintenance to the        |
    |indicated repository schema as required to ensure code and   |
    |repository are compatible.                                   |
    |Contact IBM support for further assistance.                  |
    |                                                             |
    |HSIC083I GBK schema:schema of version date:gkb_date is out of|
    |date. It is more than number_of_months old.                  |
    |                                                             |
    |Explanation:                                                 |
    |                                                             |
    |The used GKB of the given schema name is likely to be        |
    |superseded and can be replaced by a more recent GKB          |
    |containing more product updates. The GKB that is used is     |
    |older than the default value of the number_of_months         |
    |from the current date which means the latest                 |
    |identification changes may be missed.                        |
    |                                                             |
    |System action:                                               |
    |                                                             |
    |The application continues.                                   |
    |                                                             |
    |User response:                                               |
    |Apply GKB maintenance as soon as possible.                   |
    |                                                             |
    |HSIC084E GBK schema:schema is missing configuration          |
    |parameters.                                                  |
    |                                                             |
    |Explanation:                                                 |
    |                                                             |
    |The used GKB of the given schema name is missing             |
    |configuration parameters that the program needs.             |
    |This is most likely to occur if the GKB has not been         |
    |loaded successfully.                                         |
    |                                                             |
    |System action:                                               |
    |                                                             |
    |The application terminates.                                  |
    |                                                             |
    |User response:                                               |
    |                                                             |
    |Ensure GKB is loaded successfully. Contact IBM support if    |
    |problem persists.                                            |
    |                                                             |
    |HSIC085E GBK schema:schema does not have any scorecards.     |
    |                                                             |
    |Explanation:                                                 |
    |                                                             |
    |The used GKB of the given schema name does not have any      |
    |scorecards that can be used to match discovered modules.     |
    |This is most likely to occur if the GKB has not been loaded  |
    |successfully.                                                |
    |                                                             |
    |System action:                                               |
    |                                                             |
    |The application terminates.                                  |
    |                                                             |
    |User response:                                               |
    |                                                             |
    |Ensure GKB is loaded successfully. Contact IBM support if    |
    |problem persists.                                            |
    |                                                             |
    +-------------------------------------------------------------+
    |Chapter 11. Troubleshooting, messages, and support           |
    |                                                             |
    |Section: Tivoli Asset Discovery for z/OS messages -          |
    |         HSIC messages return codes                          |
    |                                                             |
    |Add the following return codes:                              |
    |                                                             |
    |6074   GKB level is unsupported.                             |
    |6075   Repository level is unsupported.                      |
    |6076   GKB is missing configuration parameters               |
    |6077   GKB is missing scorecards                             |
    |                                                             |
    +-------------------------------------------------------------+
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA48006

  • Reported component name

    TIV ASSET DISC

  • Reported component ID

    5698B39TD

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-04

  • Closed date

    2015-06-26

  • Last modified date

    2015-07-01

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

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

    UA77910

Modules/Macros

  •    HSICIQIM HSICLDEL HSICSQLT HSICTLAG HSICUDEL
    HSICUIMP HSICUSUM
    

Publications Referenced
SC22547400SC22547400   

Fix information

  • Fixed component name

    TIV ASSET DISC

  • Fixed component ID

    5698B39TD

Applicable component levels

  • R810 PSY UA77910

       UP15/06/30 P F506

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBLR8","label":"Tivoli Asset Discovery for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"810","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
18 July 2023