IBM Support

IJ45634: LAUNCH IN CONTEXT URL IS ENCODING INCORRECTLY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • LAUNCH IN CONTEXT URL IS ENCODING INCORRECTLY
    
    STEPS TO REPRODUCE:
    
    1.Create a Launch in Context Record
    2.Go to> System Configuration> Platform Configuration> Launch in
    Context
    3.Created a New One
    4.Name: REMOVESITE
    5.Add a New Row in the Launch Contexts Section-----> JOBPLAN and
    Save
    6. Go to Application Designer
    7. Go to> System Configuration> Platform Configuration>
    Application Designer
    8 Bring up a JOBPLAN
    9. Go to the Action Me nu and select Add/Modify signature option
    and Create a New One Called JPTEST
    10. In the Advanced Signature Options Select " Associate to
    Launch entry to enable Launch in context and select the Launch
    in context you creatd above
    (REMOVESITE) and click on OK
    11. From the Job Plan Tab
    12. Open the Control Palette and Drag the Hyperlink Icon
    13.Right click on it and Select Properties
    14. Fill in the Label and Enter the signature Option you created
    above in step 9 in the event type Field
    15. Go to the Advanced Tab and enter the Signature Option there
    as well and SAVE
    16. Go to the Security Groups Application and bring up the
    MAXADMIN group
    17. Go to the Application Tab and bring up JOBPLAN
    18. Search for the Sig Option you created above an Grant Access
    and save
    19. Go to the Job Plan Application and create 2 Job Plan Records
    a.DRUM,BARREL
    b.DRUM, BARREL ( Make sure there is a space after the comma)
    20. Logout and log back in as a user that is part of the
    MAXADMIN Group
    21. Go to the Job Plan Application and bring up the JP with no
    space but with a Comma--> DRUM,BARREL
    22. Then click on the Hyperlink we created, it will bring up
    your URL ;
    Example:
    https://HostnameHere/app/jobplan/REMOVEORGSITEID.aspx?JPNUM=DRUM
    BARREL
    This Removes the Comma
    Now select the JP with the Space ---> DRUM, BARREL
    https:/HostnameHere/app/jobplan/REMOVEORGSITEID.aspx?JPNUM=DRUM%
    20BARREL
    This removes the comma and replaces the space with a unicode %20
    
    CURRENT ERRONEOUS RESULTS:
    
    Launch in context is not encoded properly
    
    EXPECTED RESULTS:
    
    Launch in Context to keep the URL intact
    
    PERFORMANCE ISSUE: No
    
    ENVIRONMENT:
    
    TPAE 7.6.1.0 Build 20180718-1141
    
    Also seen in TPAE 7613
    

Local fix

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * LAUNCH IN CONTEXT URL IS ENCODING INCORRECTLY                *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IJ45634

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-02-28

  • Closed date

    2023-04-04

  • Last modified date

    2023-04-04

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
04 April 2023