star_pream.b09

Create the star preamble file for the esvd programs.

Enter:

star_pream.b09 <map = map_name> <tpid = test_identifier> <ci_specs = ci_file> <star_output = star_file> <run_no = number> <esvd_specs = esvd_file> <step = step_num> <cycle = cycle_name> <autorun = ‘yes/no’>

Where:

map	Specify the map name.
tpid	Specify a unique test identifier.
ci_specs	Specify the pathname of the ci spec file.
star_output	Specify the pathname of the star1 output file.
run_no	Specify the run number.
esvd_specs	Specify the pathname of the esvd spec file.
step	Specify the step to use.
cycle	Specify the cycle name.
autorun	Specify: yes to use autorun no to disable autorun. An option must be specified.

Example:

star_pream.b09 map=TorqueCurve320
tpid=CTH_EUL
ci_specs=/esvd_data/CTH_EUL/cvs_specs.dat
star_output=/esvd_data/CTH_EUL/TorqueCurve320/star1.dat
run_no=476363
esvd_specs=esvd_filename=/esvd_data/specs/esvd_specs.dat
step=1
cycle=SimColdFTP
autorun=yes

Notes:

– /e/< s >/ ‘esvdSpecs’
– /e/< t >/ ‘cvs_specs.dat’
– /e/< t >/< m >/ ‘star1.dat’.< c >

where:

e	esvd_data
t	test plan id
st	step number of the test
r	run number of the test
c	name of the cycle that was run
s	specifications that apply to all tests
‘ ‘	quoted string is a generic filename, later replaced by the actual filename when the script, ‘cvs_file_naming.10c’ is run.

This is normally run from a script and uses a script called cvs_file_naming in /specs/cmds/ which generates the the correct pathnames and files for this task.

See Also: