XML-SCHEMA clause
The XML-SCHEMA clause provides the means of relating xml-schema-name-1 to an external file identifier: a ddname or environment variable that identifies the actual external file that contains the optimized XML schema.
The external file identifier can be specified as a user-defined word external-fileid-1 or as an alphanumeric literal literal-8, and identifies an existing external z/OS®UNIX file or MVS™ data set that contains the optimized XML schema.
The external file identifier must be either the name specified in the DD statement for the file or the name of an environment variable that contains the file identification information.
For details on specifying an environment variable, see Environment variable contents for an XML schema file.
- XML-SCHEMA xml-schema-name-1 IS
- xml-schema-name-1 can be referenced only in
an XML PARSE statement.
The xml-schema-name in the XML SCHEMA clause can be a DBCS user-defined word.
- external-fileid-1
- Specifies a user-defined word that must conform to the following
rules:
- The user-defined word can contain one to eight characters.
- The user-defined word can contain the characters, A-Z, a-z, 0-9.
- The leading character must be alphabetic.
- literal-8
- Specifies
an alphanumeric literal that must conform to the following
rules:
- The literal can contain one to eight characters.
- The literal can contain the characters, A-Z, a-z, 0-9, @, #, and $.
- The leading character must be alphabetic, @, #, and $.
The compiler folds external-fileid-1 or literal-8 to uppercase to form the ddname or environment variable name for the file.
Environment variable contents for an XML schema file
The environment variable name must be defined using only uppercase because the COBOL compiler automatically folds the external file identifier to uppercase.
For an XML schema in an MVS data set, the environment variable must contain a DSN option in the format shown below.
data-set-name must be fully qualified. You must not code blanks within the parentheses.
For an XML schema in a z/OS UNIX file, the environment variable must contain a PATH option in the format shown below.
path-name must be an absolute path name; that is, it must begin with a slash. Special characters in the path name must be "escaped" by preceding them with a backslash. For example, to include a backslash in the path name, code two backslashes in sequence.
For more information about specifying path-name, see the description of the PATH parameter in the z/OS MVS JCL Reference.
For both formats, blanks at the beginning and end of the environment variable contents are ignored. You must not code blanks between a keyword and the left parenthesis that immediately follows the keyword.