Re: Client Access - Disable transfer option on workstation pr...

Andre P TOCHE wrote:

> Subject:
> Client Access - Disable transfer option on workstation program
> ---------------------------------
> We have now started to implement CA win 3.1.3 on our new NT4 stations.
> In the past, our users had PCS on WFW 3.11
>
> Our users are allowed to use the workstation program, and some  file transfer
> that have been prepared by the programmers.
> For each file transfer, they just have to click an a nice icon.
>
> The problems with CA are :
>
> 1. autorun
>  when they start a file transfer with PCS, the autorun parameter allows an
> automatic execution.
> (the parameters are in the RTO file)
> the same definition, executed with CA does not execute automatically : it 
>shows
> the data transfer screen, and the user has to click on "data transfer to
> AS/400".
> BUT that means, he will be able to change the definitions and execute 
>something
> completely different ...
>
> Is the a possibility to change that ?

  We have automated some of our transfers using the dos batch program supplied  
with Client Access.  For Example...

C:\PROGRA~1\IBM\CLIENT~1\rtopcb c:\dwnload.tto | Find "Receive completed 
successfully."
IF ERRORLEVEL 1 GOTO WARNTF
GOTO TRNFROK
:WARNTF
CLS
ECHO Download of Transactions from AS400 Failed!!
ECHO If failure is due to connection problems,
ECHO reboot the PC to re-established the
PAUSE connection and try again.
GOTO END
:TRNFROK


>
>
> 2. Transfer on the menu
> on the workstation program, there is now a "transfer" menu, and a "Send" and
> Recv" icons on the toolbar.
> This means that our users have now the possibility to define new file 
>transfers,
> and even upload data on the as/400.
> Even if we secure our libraries, a user which was allowed to access a file, 
>will
> now be allowed to destroy that file with an upload.
>
> How can I suppress this option from the menu (and the transfer icons) ?

  One new problem with Client Access which may or may not apply to you  and is 
different than Rumba, is that an upload will get an sql error unless
you
  have defined a Field Reference File for the target physical file.  Some people
  may use these all the time and thus already have them for their files, but in
  our case we had to define them for any upload to work. This being the case,
  a user can't upload to any file they choose unless there is a FRF.

Terry

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---