Reflection transfers in Quick

[Terrence Burke]

Up until a few years ago we used HP/3000 equipment, Image Database, 
Powerhouse and WRQ Reflections.   We also had to deal with the 
problem of enabling users to transfer files from the HP to their PC

We found a solution as follows (I think  --  we have changed to 
Powerhouse on VAX equipment, and threw out a lot code, etc, and I 
cannot remember the details exactly.

One Quick screen initiated a process to generate a file of data to be 
transferred to the PC, and TOLD the user the name of the file being 
created  --  but there are many variations on this theme to enable 
the user to know which file is to be transferred.
(We actually maintained a file of filenames & owners, in order to 
control what was transferred & by whom.)

 A second screen enabled the user to specify :-
	  --	the name of the file to be transferred,
	  --	the name of the target file on the PC (just a name if the file 
		was to be deposited in the current PC directory, which was usually
		the case, or include the full path).
 The screen code then performed the following :-
	  --	create a string value comprised of the escape character, the 
		characters "&oCSend ", then the name of the file to send, then the 
		string " to " and then the name of the file to be created on the PC
	  --	DISPLAY the string value (so that it has to be a field of the 
		screen) to automatically invoke Reflection's file transfer process,
	  --	ACCEPT the host startup sequence (such as Run PCLink.....) in 
		another field,
	  --	issue a Run Command operation to start the process running, and
	  --	ACCEPT the response from the PC, provided automatically once 
		the transferred has completed.   The response is one character code 
		value S, F or U  --  successful, failure or unknown.

To send a file from the PC to the HP, replace 'Send' by 'Receive' in 
the above.

This information is on page UM-126 of the WRQ Reflections manual 
(version 2.4, I think), which, for some reason, we held on to.

I hope I have remembered this correctly.   Since then, we have used 
Powerhouse on VAX equipment, and have managed to solve the same 
problem, but in a necessarily very different way  --  although the 
user interface still only requires the user to specify source & 
target files, and we have enabled transfers either way.

				Regards
				   Terry Burke

> 
> The samples directory for reflection contains an example cobol program
> COBDEMO.COB this shows how to issue commands to Reflection from within a Cobol
> program running on the HP3000 under Reflection.
> 
> You can either use the same process from within a Quick program (when you issue
> a SEND command the reflection will send back the command "RUN PCLINK......."
> this you must intercept in the Quick program and issue a RUN COMMAND "RUN PCLINK
> ........").
> 
>  You could also adapt the cobol program to your requirements and execute it from
> within quick as an external process.
> 
> 
> 
> Tom Cahill
> 
> 
> 
> 
> 
> I am trying allow a user to use WRQ's REFLECTION to do a file transfer from
> within a QUICK screen, i.e. via point and click. Upon transfer an error
> message appears: Host does not respond. When not in QUICK screen the
> transfer is successful.
> I am using version 6 of Reflections, 8.09 of PowerHouse and MPE 5.5 pp2.
> Can anyone help me solve this problem?
> TIA
> Joseph Rosenblatt
> System Administrator
> Integrated Industrial Systems
> Yalesville, CT

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Terry Burke
Admin Information Systems           EMail T.E.Burke@Dundee.ac.uk
University of Dundee
Nethergate                          Phone 01382 344022
Dundee     DD1 4HN                    Fax 01382 201604
Scotland   UK.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.