The input file used by MKTMPF to create repository files can be created with a text editor (or other method of the user's choosing). It should contain one set of default path names and a set of one or more template entries. The following is an example of an input file with a single template.
Note:
The keywords surrounded by <> are replaced by the appropriate data.
Blank lines are ignored.
Any line in which an asterisk appears before any other non-white space is ignored.
Keywords are not case-sensitive; key values are case-sensitive.
Descriptive_name and comment must be in double quotation marks.
***************************************************** *** This section appears once in the input file *** ***************************************************** Repository_pathname = xxxxxxxxxx Default_message_pathname = xxxxxxxxxx Default_causes_pathname = xxxxxxxxxx Default_actions_pathname = xxxxxxxxxx Default_details_pathname = xxxxxxxxxx Descriptive_name = "xxxxxxxxxx" ***************************************************** *** The remaining lines define a single template. *** *** Additional templates may be appended by *** *** replicating the following text. *** ***************************************************** <action> Template_number = xxxxxxxx Comment = "xxxxxxxxxxxxxxxxx" Message_number = xxxxxxxx Log_Class = x Message_pathname = xxxxxxxxxxxxx Causes_pathname = xxxxxxxxxxxxxxx Actions_pathname = xxxxxxxxxxxxx Details_pathname = xxxxxxxxxxxxxxxxxxx Fail_causes = xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx Fail_actions = xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx Install_causes = xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx Install_actions = xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx User_causes = xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx User_actions = xxxxxxxx,xxxxxxxx,xxxxxxxx,xxxxxxxx Detail_data = <length>,<offset>,<heading>,<type>
Note: Long file names, white space, and special characters are acceptable if the user's file system supports them. If a path name contains leading or trailing white space, it should be enclosed in double quotation marks. You can provide either a full path name or just the file name. If the file name is provided, it is the developer's responsibility to make sure it is in a directory specified in the DPATH of the system where the repository will be used.