Re: IBM Object naming rules

On 13-Jun-2014 08:29 -0500, Mark Murphy/STAR BASE Consulting Inc. wrote:

There are valid characters, and unfriendly characters. If you plan to
SQL, the period (.) is one of those unfriendly characters as it
interferes with the standard SQL name delimiter (in *SQL naming). But
even if you are using *SYS naming, SQL cannot access stored
procedures or user defined functions in libraries containing a period
(.).

To be sure, the SQL *can access* the objects in libraries where that library name contains a period.

I haven't tried with a period in the object name itself, but I
suspect that it interferes there as well.

The same issue and resolution exist for any /object name/ as with the /library object name/; as well the other /names/ such as columns, routines, constraints, etc. can contain periods and be referenced.

The SQL provides support for any SQL identifier that includes a period. A requirement to effect the reference to such an identifier is that the SQL identifier must be delimited. The delimiter is the double-quote character. An example referencing some identifiers with embedded periods; using the new support for SQL naming within System naming to show both qualifier characters [period and slash], and a qualified column as well:

SELECT "ORD.LIB"."ORD.UDF"(T1."ORD.FIELD")
FROM "ORD.LIB"/"ORD.TABLE" AS T1

Note: the column name "ORD.FIELD" is a bit different [than the other object names] in that statement, because the "ORD.FIELD" is the actual name as stored and visually presented, whereas the other names as stored and visually presented would generally be without delimiters.