IBM Support

PM93373: PARALLEL JOB NAME SPECIAL CHARACTER ISSUE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • java.io.IOException: Server returned HTTP response code: 500
    occurs when the xJCL for a parallel job contains special
    characters in the job name.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Parallel Job Manager jobs having        *
    *                      special characters in the job name      *
    *                      have issues retrieving sub-job logs as  *
    *                      shown below:                            *
    *                      System.out: [06/27/13 11:28:35:075      *
    *                      EDT] **********  Begin                  *
    *                      XDCGIVT!_#PAR#:64994:64995 log          *
    *                      **********                              *
    *                      System.out: [06/27/13 11:28:35:075      *
    *                      EDT] Unable to retrieve sub job         *
    *                      [XDCGIVT!_#PAR#:64994:64995] logs due   *
    *                      to the following exception:             *
    *                      java.io.IOException: Server returned    *
    *                      HTTP response code: 500 for             *
    *                      URL:                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a WebSphere batch parallel job containing one or more
    special characters in the job name, is submitted, a failure
    will occur during the underlying HTTP communication that takes
    place.  The string containing the character is not encoded,
    causing the failure.
    

Problem conclusion

  • The code which handles this parameter has been updated to
    encode the string prior to making the HTTP call.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.1.  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

    PM93373

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-18

  • Closed date

    2013-10-22

  • Last modified date

    2014-01-08

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

    PM92258

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022