IBM Support

PM77812: LINE BREAK HANDLING WHEN EDITING A MESSAGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WBIFN MER interface, when user fills a multiple
    line field (like the
    79 of n99), he/she has to manually enter a CRLF (Enter) at end
    of each
    line.
    
    Solution:
    Automatically insert CRLF at the end of 50th
    character in message
    

Local fix

  • fix will be provided with the APAR / PTF
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: LINE BREAK HANDLING WHEN EDITING        *
    *                      A MESSAGE                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Formerly, the browser display would not provide an indication
    when a line in a text area got too long. Furthermore, automatic
    line wrapping made it impossible to visually distinguish line
    breaks in the input data. Long lines would only be detected
    when the message was validated on the server.
    

Problem conclusion

  • Now, the browser checks for line lengths when the cursor
    leaves a text area, or when F1 is pressed. An error description
    with a text snippet indicates where a line has to be split.
    Where possible, the data entered in text areas is also checked
    for invalid characters. Error descriptions can be hidden by
    pressing Shift-F1 or the Escape key in the text area for which
    an error is indicated. On Internet Explorer, however, pressing
    the Escape key will also clear all input data from the text
    area. Automatic line wrapping is now disabled, except for
    field 77F in FIN MT 105 (EDIFACT Envelope). The latter is an
    exceedingly long single-line field. As before, it will be
    shown in the browser as a multi-line text area with automatic
    line wrapping.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM77812

  • Reported component name

    MESSAGE MANAGEM

  • Reported component ID

    5655FIN03

  • Reported release

    11M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-27

  • Closed date

    2013-04-08

  • Last modified date

    2013-05-06

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

    PM77601

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

    UK93205

Modules/Macros

  • DNQ00000 DNQ00004 DNQ00010 DNQ00041 DNQ00044
    DNQ00084 DNQ00091 DNQ00107 DNQ00110 DNQ00117 DNQ00118 DNQ00119
    DNQ00120 DNQ00130 DNQ00131 DNQ00132 DNQ00134 DNQ00140 DNQ00141
    DNQ00142 DNQ00144 DNQ00223 DNQ00224 DNQ00225 DNQ00227 DNQ00232
    

Publications Referenced
SH12693614SH12693914SH12693714SH12693814SH12694014

Fix information

  • Fixed component name

    MESSAGE MANAGEM

  • Fixed component ID

    5655FIN03

Applicable component levels

  • R11M PSY UK93205

       UP13/04/10 P F304

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11M","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 May 2013