MNTCON MATCH_CASE

How to:

By default, segment names and field names in Master Files must be in uppercase. To enable mixed-case names, use MNTCON MATCH_CASE ON.

Syntax: How to Enable Mixed-Case Naming

The feature to support mixed-case and NLS characters in the Master File is enabled by the following command in the EDASPROF, user, group, or service profile:

MNTCON MATCH_CASE {ON|OFF}

where:

OFF

Is the default. Segment names and field names in Master Files still must be uppercase, and Maintain refers to them in mixed-case or lowercase without error.

ON

Means that mixed-case and NLS characters will be respected. Developers must be consistent in their references to named components in terms of the case used. Components are:

  • Case names
  • Class names
  • Function names
  • Object names
  • Stack names
  • Variable name

With the feature enabled (MNTCON MATCH_CASE ON in a profile):

  • Field names COUNTRY, Country, and CounTry all refer to different fields.
  • Developers must be consistent with casing when referring to classes, functions, objects, stacks, and variables. For example, CASE MYCASE would need any associated PERFORM statement to refer to the case name as MYCASE.
  • IWC. function names must be written exactly as follows:
    • IWC.putCgiData
    • IWC.getCgiData
  • MAINTAIN and END are still required to be in uppercase.
  • Certain keywords will be automatically translated to uppercase. For example, contains and CONTAINS will always mean the same thing.

Note: With the feature off, there should be no issues running previously developed applications.

With the feature enabled, previously written applications would need to be reviewed, then updated (to keep the case, class, and other names consistent), and finally redeployed.