IBM OS manual Builder input syntax

9. If a line comment contains the characters HEADER anywhere in it, it is not

			treated as a comment and is parsed like any ordinary line in case it is a
			HEADER statement. Otherwise comment lines are thrown away.
		10.	The only valid values for AFFINITY are GLOBAL, LUNAME, USERID, and
			BAPPL. NONE is not allowed.
		11. Keywords and values (including surrounding brackets) must not be split across
			input lines.
		12. Nested brackets are not allowed within values.
		13. The Builder is case sensitive. This applies to both keywords and their values
			(keywords must be in upper case).
		Any syntax error causes an error message to be issued. Logic errors are also
		possible; for example, CREATE DTRINGRP before CREATE TRANGRP can cause
		error messages to be issued.
		Any such errors do not cause the Builder to terminate immediately, but normally
		cause a skip to either the next keyword or the next statement, depending on the
		error. The Builder terminates with return code of 8 when EOF is ®nally reached. An
		error report lists all errors encountered. For each error, the line containing the error
		is output, plus up to four preceding lines for the same statement to put the error in
		context, plus the error message.
input_statement	=	{create_statement
		remove_statement
		header_statement
		context_statement
		comment}
create_statement	=	CREATE
		{create_trangrp
		create_dtringrp}
		;
create_trangrp	=	TRANGRP
		NAME	(trangroup)
		AFFINITY	({GLOBALLUNAMEUSERID})
		AFFLIFE	({PERMANENTSYSTEMLOGONSIGNONPCONV})
		[DESC	(string)]
		[MATCH	({LUNAMEUSERID})]
		[STATE	({ACTIVEDORMANT})]
create_dtringrp	=	DTRINGRP
		TRANGRP (trangroup)
		TRANID	(tranid)
remove_statement =		REMOVE
		TRANGRP
		NAME	(trangroup)
		;
context_statement = CONTEXT
		[plexname]
		;
header_statement =		HEADER
		[APPLID	(applid)]
		[SAVEDATE (date)]
		[SAVETIME (time)]
		;
comment	=	©*©
		[string
		header_statement]

Figure 10. Builder input syntax

Chapter 7. Running the Builder 57