Use the chkds command to check the syntax in a dataset file. The command generates no output when there are no syntax errors; otherwise, it issues an error. Empty files generate a warning.
See Also:
"Dataset Commands" for related commandsYou must have the display administrative domain's configuration right to run the chkds command.
chkds dataset-file-name ...
Specifies the name of a dataset file. Refer to "dataset-file-name" for a descriptions of the dataset-file-name placeholder.
Example 2-22 creates a dataset file with bad syntax and then checks it.
Example 2-22 Checking a File for Syntax
ob> mkds --nq --input badsyntax.ds Input the new dataset contents. Terminate with an EOF or a line containing just a dot ("."). icnlude host brhost2 . Error: the following problems were detected in dataset badsyntax.ds: 1: icnlude host brhost2 Error: "icnlude" - unknown keyword ob> chkds badsyntax.ds Error: the following problems were detected in dataset badsyntax.ds: 1: icnlude host brhost2 Error: "icnlude" - unknown keyword
Example 2-23 creates two dataset files and then checks them.
Example 2-23 Checking Files for Syntax
ob> mkds --nq --input empty.ds Input the new dataset contents. Terminate with an EOF or a line containing just a dot ("."). . ob> mkds --nq --input goodsyntax.ds Input the new dataset contents. Terminate with an EOF or a line containing just a dot ("."). include host brhost2 include path /home . ob> chkds empty.ds goodsyntax.ds Warning: dataset empty.ds is empty