Question for Alpha Users - Parameter passing QUICK Screens

[Walker, Chris]

I assume that this is a VMS-specific question, rather than a feature of the
Alpha.

Suggestion 1: 
	Use job table logicals to pass parameters from Quick to Quiz or QTP
Suggestion 2: 
	Use CLI symbols (but be sure to define them using "run command",
rather than "setsystemval"
Suggestion 3: 
	Write a generalized DCL procedure that writes its parameters to a
temporary file, then invokes QTP or Quiz.  For example:

	$ tmpfile = "sys$scratch:" + f$getjpi("","pid") + ".tmp"
	$ open/write tmp 'tmpfile'
	$ if p2 .nes. "" then write tmp p1
	$ if p3 .nes. "" ... ! and so on
	$ close tmp
	$ define/user sys$input 'tmpfile'
	$ quiz auto='p1'
	$ delete 'tmpfile';

	This solution is rather unsatisfactory as the vagaries of the prompt
mechanism could cause the parameters to be misplaced, but there may be
situations where it's the only way.

Chris Walker
Tate & Lyle
London

> -----Original Message-----
> From:	Terry Pickering [SMTP:pickering@myself.com]
> Sent:	Wednesday, August 18, 1999 1:42 AM
> To:	powerh-l@lists.swau.edu
> Subject:	Question for Alpha Users - Parameter passing QUICK Screens
> 
> The following pertains to user on ALPHA machines only:
> 
> 
> I've come accross many times when I needed to have a DCL job command file
> with parameters in the file that is used by QTP or QUIZ. I don't really
> want to have to code the entire command procedure in the quick screen
> before submitting it, but I haven't figured out a way to do it otherwise.
> 
> For example, let's say you want to submit a command procedure that is like
> this:
> 
> $QTP AUTO=GLS_EXE:GLST014.QTC
> 2000
> 02
> $QUIZ AUTO=GLS_EXE:GLSZ001.QZC
> $EXIT
> 
> I've tried creating a command procedure like this and passed the
> parameters, but that doesn't work either. The substitution only works for
> DCL commands. QTP thinks you're giving "'p1" as the prompted value and it
> is not substituted correctly.
> 
> $QTP AUTO=GLS_EXE:GLST014.QTC
> 'p1
> 'p2
> $QUIZ AUTO=GLS_EXE:GLSZ001.QZC
> 
> 
> In the real life example there could be 20-30 (or more) DCL commands. I'd
> much rather have a command procedure somewhere other than embedded within
> my QUICK code. It's also much easier to test the command procedure first
> by
> writing the DCL commands in the editor.
> 
> The only way I've figured out how to do it now, is to create a temporary
> file, write out all the commands using QUICK, submit the temporary file as
> a job, then delete the file. Some of the parameters are for CHOOSE prompts
> or DEFINE prompts. In some cases you could set a logical and then use the
> GETSYSTEMVAL, but that presents problems when the programs are being run
> interactively.
> 
> Any suggestions?
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Terry Pickering        Consultant Extraordinare
> Monday and Friday        Tuesday - Thursday
> Portland                 Eugene
> (503) 245-7178           (541) 687-3416
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.