IBM Support

JR33167: DOCUMENTATION AND AN ERROR MESSAGE ABOUT THE RULE OF COLUMN NAME SHOULD BE UPDATED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Refer to CRM 17742,999,760 & 18512,999,760
    
    Designer Client Guide (P.35) incorrectly states that $ can be
    used as the start chacracter for a column name. The error
    message that is produced by the Designer is also incorrect. It
    should state that the leading character can be an alphabetic,
    or underscore. On NLS systems it can also contain extended
    characters (i.e. > ASCII 127 and double byte characters such as
    Japanese characters). Subsequent characters can also include $
    and extended characters for NLS enabled systems.
    Designer Client Guide also has incorrect rules for Job Name,
    Link name, Shared Contained name and Stage name.
    Planning, Installation and configuration Guide has incorrect
    rules for project names
    DataStage error messages for these need modifying
    DataStage evil character handling should be consistent with
    these rules
    
    In an environment where NLS is enabled (i.e. presumably the case
    in a japanese environment):
    
    Column name:
            First character can be:
              Any character from the extended
    character set  (i.e. > ASCII 127)
              Any alphabetic character (i.e.
    A-Z, a-z)
              Underscore (i.e. _)
            Subsequent characters can be:
              Any character from the extended
    character set  (i.e. > ASCII 127)
              Any alphabetic character (i.e.
    A-Z, a-z)
              Any numeric
              Underscore, dollar or period
    (i.e. _,$ or .)
    
    Table name:
            First two parts of a table name (i.e. "Data
    source type" and "Data source name"):
              Any character except control
    characters (i.e. < ASCII 32) and vertical bar (i.e. | )
              Any extended character (i.e. >
    ASCII 127)
            Table name:
              Any character from the extended
    character set  (i.e. > ASCII 127)
              Any alphabetic character (i.e.
    A-Z, a-z)
              Any numeric
              Underscore, dollar or period
    (i.e. _,$ or .)
    
    
    Shared Container
      First Character can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
      Subsequent characters can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
        Any numeric
    
    
    Job name
      First Character can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
      Subsequent characters can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
        Any numeric
        Underscore (i.e. _)
    
    Link Name
      First Character can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
      Subsequent characters can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
        Any numeric
        Underscore (i.e. _)
    
    
    Stage Name
      First Character can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
      Subsequent characters can be:
        Any character from the extended
    character set  (i.e. > ASCII 127)
        Any alphabetic character (i.e.
    A-Z, a-z)
        Any numeric
        Underscore (i.e. _)
    
    
    Project Name
      Can consist of any characters except:
       <> *?"|,'!^&;+/\:.
       unicode characters whose encoding is 9
    or 12288
       and has no trailing underscores
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Japanese user wishing to know which characters can be used in
    DataStage artifact names in Designer and Administrator client.
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Question from the customer relating to errors in documentation
    of naming rules in "Designer Client Guide" and "Planning,
    Installation and configuration Guide"
    
    These rules are also exposed in DataStage's end-user eror
    messages.
    
    From customer's PMRs:
    
    17742,999,760
    
    "Designer Client Guide" shows that column name should start
    with alphabet or $ and it can include alphabet, underscore,
    period and $.
    But actually we can use Japanese character for 1st character of
    column name in Japanese environment but it is not allowed to
    start with $. When trying to enter $ as the 1st character of a
    column name, the following error message is displayed and it is
    not allowed:
    
    
    Error: name should start with alphabet or Japanese character and
    it is not allowed to use except Japanese character, alphabet,
    underscore and period.
    
    18512,999,760:
    
    "Designer Client Guide" shows the following information about
    the rules of names:
    
    
       1. job name :  starts with alphabet, can include alphabet,
    numeric and underscore.
       2. link name :  starts with alphabet, can include alphabet,
    numeric and underscore.
       3. shared container name :  starts with alphabet, can
    include alphabet and numeric.
       4. stage tyep name :  starts with alphabet, can include
    alphabet, numeric, period and underscore.
    
    
    And "Planning, Installation and configuration Guide" shows:
    
    
    
       5. project name: can include alphabet, numeric and
    underscore
    
    
    But for all the above cases (from 1. to 5.), we can use
    Japanese characters in Japanese environment.
    
    ****************************************************************
    RECOMMENDATION:
    Fix in next release: Code changes + documentation
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR33167

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-29

  • Closed date

    2009-06-11

  • Last modified date

    2009-06-11

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

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

Fix information

Applicable component levels

  • R810 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
11 June 2009