Path: utzoo!attcan!uunet!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!log-hb!markus
From: markus@log-hb.se (Markus Nikolopoulos)
Newsgroups: comp.lang.modula2
Subject: Re: Using CLI routines & Modula-2
Message-ID: <11471@log-hb.se>
Date: 14 Mar 90 15:05:57 GMT
References: <5277.25f92d46@uwovax.uwo.ca>
Reply-To: markus@log-hb.se (Markus Nikolopoulos)
Organization: TeleLOGIC AB, Stockholm, Sweden
Lines: 30

In article <5277.25f92d46@uwovax.uwo.ca> 4203_5021@uwovax.uwo.ca writes:
>I am writing some modula-2 code for a VAX-6330 and I need some assistance
>using VAX Command Language (CLI) routines with my program.
>

Your SUBCOMMAND.CLD file should look something like:

	DEFINE VERB YourProgram
	IMAGE "Complete_file_spec_for_the_executable_of_your_program"
	PARAMETER P1, LABEL=MyParameter

To install "YourProgram" do:

	$ set command subcommand.cld

From your Modula-2 program you can get the parameter value by calling:

	.....
	VAR value:ARRAY[0..30] OF CHAR; length:CARDINAL;
	CommandLanguageInterface.CLI$GET_VALUE('MyParameter',value,length);
	.....

The language used for writing CLD files allows you to define very complex
combinations of parameters, options and startup values for a program. 
Using them saves a lot of parameter checking that you have to do within
your program.
The disadvantages are that you have to learn a new language and
your programs become difficult to port outside VMS.

I hope this helps.