VALIDMEMNAME= System Option: z/OS

Syntax Description

COMPATIBLE

specifies that a SAS data set name, a view name, or an item store must follow these rules:

• The length of the names can be up to 32 characters.
• Names must begin with a letter of the Latin alphabet (A-Z, a-z) or the underscore. Subsequent characters can be letters of the Latin alphabet, numerals, or underscores.
• Names cannot contain blanks or special characters except for the underscore.
• Names can contain mixed-case letters. SAS internally converts the member name to uppercase. You cannot, therefore, use the same member name with a different combination of uppercase and lowercase letters to represent different variables. For example, customer, Customer, and CUSTOMER all represent the same member name. How the name is saved on disk is determined by the operating environment.

This is the default.

Alias:COMPAT

EXTEND

specifies that a SAS data set name, a SAS view name, or an item store must follow these rules:

• Names can include national characters.
• The name can include special characters, except for the characters / \ * ? " < > |: -.

  Note: The SPD engine does not allow ‘.’ (the period) anywhere in the member name.
• The name must contain at least one character.
• The length of the name can be up to 32 bytes.
• Null bytes are not allowed.
• Names cannot begin with a blank or a ‘.’ (the period).

  Note: The SPD engine does not allow ‘$’ as the first character of the member name.
• Leading and trailing blanks are deleted when the member is created.
• Names can contain mixed-case letters. SAS internally converts the member name to uppercase. You cannot, therefore, use the same member name with a different combination of uppercase and lowercase letters to represent different variables. For example, customer, Customer, and CUSTOMER all represent the same member name. How the name appears is determined by the operating environment.

Restriction:The windowing environment supports the extended rules in the Editor, Log, and Output windows when VALIDMEMNAME=EXTEND is set. In most SAS windows, these extended rules are not supported. For example, these rules are not supported in SAS Explorer, the VIEWTABLE window, and windows that you open using the Solutions menu.

Requirement:When VALIDMEMNAME=EXTEND, SAS data set names, view names, and item store names must be written as a SAS name literal. If you use either the percent sign (%) or the ampersand (&), then you must use single quotation marks in the name literal in order to avoid interaction with the SAS Macro Facility.For more information, see SAS Name Literals in SAS Language Reference: Concepts.

Tip:The name displays in uppercase letters.

See:How Many Characters Can I Use When I Measure SAS Name Lengths in Bytes? in SAS Language Reference: Concepts

Examples:data “August Purchases”n;

data ‘Años de empleo’n.;

CAUTION:

Throughout SAS, using the name literal syntax with SAS member names that exceed the 32-byte limit or have excessive embedded quotation marks might cause unexpected results.

The intent of the VALIDMEMNAME=EXTEND system option is to enable compatibility with other DBMS member naming conventions, such as allowing embedded blanks and national characters.

CAUTION:

Using the special character # when VALIDMEMNAME=EXTEND could cause a SAS data set to be overwritten by a generation data set.

When VALIDMEMNAME= is set to EXTEND, it is possible to name a SAS data set name that uses the naming conventions for generation data sets, which append the special character # and a three-digit number to its member name. To avoid conflict, do not name SAS data sets similar to archived SAS data sets. For example, for a data set named A, generation data sets would automatically be named A#001, A#002, and so on. If you name a SAS data set A#003, the SAS data set could be deleted by SAS in the process of adding to a generation group.

CAUTION:

In the z/OS operating environment, if the session encoding is not the default EBCDIC 1047 (U.S. English), the representation of the special character # can cause incompatibility between releases.

For SAS 9.3, the special character # is represented by the specified session encoding. For SAS Releases before SAS 9.3, the # special character is represented in EBCDIC 1047.