IBM Support

IT38410: THE EXISTING JOB ID IS PLACED IN A HELD STATE IF ANY SLA ASSOCIATIONS ARE CHANGED RESULTING IN AN EMPTY JOB

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If any SLA associations are changed which result in an empty
    job, like all the VMs or datastores are removed from one SLA
    manually or they are moved to another folder on VMware side, the
    existing Job ID is placed in a held status. Even when all the
    VMs or datastores are re-assigned back to the SLA, a new Job ID
    is created and IBM Spectrum Protect Plus performs full backup.
    
    
    Versions affected: IBM Spectrum Protect Plus 10.1.*
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus levels 10.1.x.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in IBM Spectrum Protect Plus level     *
    * 10.1.9.  Note that this is subject to change at the          *
    * discretion of IBM.                                           *
    ****************************************************************
    

Problem conclusion

  • IBM Spectrum Protect Plus has been modified to handle job
    deletion in a different manner.   When the last resource is
    unassociated from an SLA, the original behavior was to delete
    the underlying job.   This results in a new job ID being
    generated when other resources are later associated to the SLA.
    The behavior has been modified to automatically suspend a job
    when the last resource is unassociated from an SLA.  This will
    prevent empty jobs from being scheduled while maintaining the
    original job ID for future resource associations to the SLA.
    If the user chooses to delete a job, they can explicitly delete
    the job using the Schedule tab of the Jobs and Operations
    screen.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT38410

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A18

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-16

  • Closed date

    2021-09-30

  • Last modified date

    2021-11-15

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

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

Modules/Macros

  • Platform Other
    

Fix information

  • Fixed component name

    SP PLUS

  • Fixed component ID

    5737SPLUS

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A18","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
31 January 2024