IBM Support

PI82819: ISSUE WITH ALLOCATING JOB NUMBERS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • [6/6/17 18:49:51:056 EDT] 000000f2 SchedulerSing I job number
    255956
    has been used. Will try to purge to reuse job number
                     [6/6/17 18:49:54:335 EDT] 000000f2
    RemoteExcepti E
    CNTR0020E: EJB threw an unexpected (non-declared) exception
    during
    invocation of method "submitJobFromRepository" on bean
    "BeanId(LongRunningScheduler#LongRunningJobSchedulerEJBs.jar#Job
    Schedule
    r, null)". Exception data:
    
                     java.lang.NullPointerException
    

Local fix

  • Change the sequence to start at a new value that's higher than
    any (the MAX) value that's ever been used, so that it bypass
    any issues reclaiming existing job numbers, and be off on the
    way allocating new job numbers from a clear range of unused
    numbers.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Java Batch                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using a sequence to generate       *
    *                      job numbers, and the runtime has        *
    *                      identified a jobid whose number         *
    *                      needs to be reclaimed, the reclaim      *
    *                      operation fails.  This results in       *
    *                      orphaned job numbers.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The job scheduler logic which attempts to purge old job numbers
    to reuse them can encounter the following exception:
    [6/6/17 23:06:44:973 EDT] 000000c0 SchedulerSing I   job
    number xxxxxx
    has been used. Will try to purge to reuse job number
    [6/6/17 23:06:48:788 EDT] 000000c0 RemoteExcepti E
    CNTR0020E: EJB
    threw an unexpected (non-declared) exception during invocation
    of
    method "submitJobFromRepository" on bean
    "BeanId(LongRunningScheduler#LongRunningJobSchedulerEJBs.jar#Job
    Schedule
    r, null)". Exception data: java.lang.NullPointerException
    at
    com.ibm.ws.batch.SchedulerSingleton.getJobNumberSequence(Schedul
    erSingle
    ton.java:2240)
    at
    com.ibm.ws.batch.SchedulerSingleton.syncedJobID(SchedulerSinglet
    on.java:
    2504)
    at
    com.ibm.ws.batch.SchedulerSingleton.getJobID(SchedulerSingleton.
    java:212
    At this point, the old job number is never reclaimed. This can
    prevent a valid sequence value from being obtained in order to
    use within a job id for a newly-submitted job.
    

Problem conclusion

  • A code update has been made such that a NullPointerException
    will not longer be issued when a job id could not be obtained
    from the sequence.
    
    The sample template DDL for all platforms has been updated to
    set the maximum value for the job number sequence to
    999999999.  Sequences that have already been defined would
    require manual update.  The MAXVALUE JOBIDCONTROL.CONTROLVALUE
    must also be set to this same value if and when the sequence
    maximum value is updated.  The sample DDL has been updated with
    instructions on this.
    
    Note this update of the job number sequence maximum value is
    not especially tied to this particular problem and
    NullPointerException.   Rather, it is intended to provide a
    more useful value more broadly for avoiding the impact of any
    other job number-related values that could be encountered.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.0.0.7.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI82819

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-08

  • Closed date

    2017-12-15

  • Last modified date

    2017-12-15

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

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

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021