Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Visual Designer validates user inputs for Library, Object, Member, Format, and Field names. If the name is invalid, then some warning is displayed to the user.

By default, Visual Designer understands that any Library, Object, Member, Format, or Field (LOMFF) name may begin with the characters A-Z, a-z, #, @, or $. Any Library, Object, or Member (LOM) may use as subsequent characters: A-Z, a-z, 0-9, #, @, $, and the period (.). Any fields may use as subsequent characters: A-Z, a-z, 0-9, #, @, and $.

To change the list of valid characters, four configuration options are available

  • pui["valid LOMFF name 1st chars"] - A list of valid first characters for Library, Object, Member, Format, and Field names. (A-Z and a-z are always considered valid.)
  • pui["valid LOM name next chars"] - A list of valid subsequent characters for Library, Object, and Member names. (A-Z, a-z, and 0-9 are always considered valid.)
  • pui["valid FF name next chars"] - A list of valid subsequent characters for Format and Field names. (A-Z, a-z, and 0-9 are always considered valid.)
  • pui["LOMFF chars to not uppercase"] - A list of characters that Designer should not make upper-case before writing or compiling the source member. (By default, all characters are made upper-case).

Example

The following code sets the default characters, which are for EBCDIC CCSID 37. If your system uses different characters, then these options can be modified.

userdata/custom/js/settings.js
pui["valid LOMFF name 1st chars"]   = ["#","@","$"];          //Library, Object, Member, Format, Field.
pui["valid LOM name next chars"]    = ["#","@","$","_","."];  //Library, Object, Member.
pui["valid FF name next chars"]     = ["#","@","$","_"];      //Format, Field.
pui["LOMFF chars to not uppercase"] = ["à"];      //Designer should not uppercase these characters in names when writing the DSPF.

Where do you save this configuration option?  Here

Example Italian CCSID 1144

pui["valid LOMFF name 1st chars"]   = ["£","§","$"];
pui["valid LOM name next chars"]    = ["£","§","$","_","."];  //Library, Object, Member.
pui["valid FF name next chars"]     = ["£","§","$","_"];      //Format, Field.

 

Note that in EBCDIC CCSID 37, @ character is 0x7C. In CCSID 1144, § character is 0x7C. So, the valid characters can be determined by checking the CCSID code page for 0x7B, 0x7C, and 0x5B.

 

  • No labels