|
midrange.com
You could build the pc ftp.txt file using input from the user by putting the
ftp -n -i -s:etx... into a .bat file. With the example below you can put a bat
file on a user's desktop and have it call the shared bat file. The user can
then then just click the icon and run the job.
@echo off
rem - this command builds an ftp script file and then runs it.
rem - the ftp script file updates the exchange, email file on the as400
rem - and then runs an update command
rem - Bill Meecham 8/10/2001 - THIS IS PRODUCTION CODE
rem _____________________________________________________________
rem - Required Parameters: USERPROFILE PASSWORD FILENAME
rem _____________________________________________________________
rem - clear the screen to remove the user name and password as soon as possible
& handle errors
rem _____________________________________________________________
cls
if "%1" == "" goto cmdHelp
if "%1" == "-" goto cmdHelp
if "%1" == "?" goto cmdHelp
if "%2" == "" goto cmdHelp
if "%3" == "" goto cmdHelp
rem - start building the ftp script file
rem _____________________________________________________________
@echo prompt >> ftpexchange.ftp
@echo verbose >> ftpexchange.ftp
@echo open 10.1.254.25 >> ftpexchange.ftp
@echo user %1 >> ftpexchange.ftp
@echo %2 >> ftpexchange.ftp
@echo put %3 /qsys.lib/qgpl.lib/exchange.file/exchange.mbr >> ftpexchange.ftp
@echo quote rcmd "SBMJOB CMD(EXCHANGE COPY(YES) TO(FILE) FIND(YES) DO(YES))
JOB(EXCH_EMAIL)" >> ftpexchange.ftp
@echo quote rcmd "SNDMSG MSG('Exchange email update was submitted!')
TOUSR(PROGRAMMER)" >> ftpexchange.ftp
@echo quit >> ftpexchange.ftp
rem _____________________________________________________________
rem - run the ftp script file
ftp -n -s:ftpexchange.ftp
rem _____________________________________________________________
rem - remove the script file!
del ftpexchange.ftp
goto exit
rem _____________________________________________________________
:cmdHelp
echo --------------------------------------------------------------
echo ftpExchange command:
echo This command is used to transfer the exchange email
echo data from the PC to the AS400. It will also submit a
echo procedure on the AS400 to update the associate email
echo addresses based on the file information that is sent to it
echo in the first step of this command.
echo --------------------------------------------------------------
echo Command syntax:
echo ftpExchange USERNAME PASSWORD FILENAME
echo --------------------------------------------------------------
echo USERNAME - The AS400 user name.
echo PASSWORD - The AS400 password for the user name.
echo FILENAME - The name of the CSV file that you have
echo created on the PC. Enter the full file name
echo including the extension.
echo Ex. c:\myDirectory\assoc.csv
echo Additional help - Contact MIS department.
echo Bill Meecham
echo --------------------------------------------------------------
rem _____________________________________________________________
:exit
----- Original Message -----
From: "Pete Helgren" <pete@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, October 10, 2003 3:39 PM
Subject: RE: Automating Client Access Express using Windows Scripts?
> And, just to elucidate:
>
> Build a pc cmd file with something like this in it:
>
> ftp -n -i -s:ftpcmds.txt
>
> Then in the ftpcmds.txt file put something like:
>
> open myAS400
> user myuserid
> mypassword
> quote rcmd mylib/myrptcmd (pass whatever parameters here...)
> quit
>
>
> It tends to work pretty slick although the password ends up being "in the
> clear".
>
> Pete Helgren
> Timp Tech/Ed Tech Labs
> 801-269-0220 x202
>
>
>
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of pnelson@xxxxxxxxxx
> > Sent: Friday, October 10, 2003 1:29 PM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: Automating Client Access Express using Windows Scripts?
> >
> >
> > Agreed. This is a lot simpler.
> >
> >
> > Paul Nelson
> > Arbor Solutions, Inc.
> > 708-670-6978 Cell
> > pnelson@xxxxxxxxxx
> >
> > "Always do right. This will gratify some people and astonish the rest."
> > Samuel L. Clemens (Mark Twain)
> >
> >
> >
> >
> > "Pete Helgren" <pete@xxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 10/10/2003 02:16 PM
> > Please respond to Midrange Systems Technical Discussion
> >
> >
> > To: "Midrange Systems Technical Discussion"
> > <midrange-l@xxxxxxxxxxxx>
> > cc:
> > Subject: RE: Automating Client Access Express
> > using Windows Scripts?
> >
> >
> > Probably easier to run FTP RUNRMTCMD and be done with it.
> >
> > Pete Helgren
> > Timp Tech/Ed Tech Labs
> > 801-269-0220 x202
> >
> >
> >
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx
> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of David Wright
> > > Sent: Friday, October 10, 2003 12:54 PM
> > > To: midrange-l@xxxxxxxxxxxx
> > > Subject: Automating Client Access Express using Windows Scripts?
> > >
> > >
> > > Hi All,
> > >
> > > Has anyone had any luck using Windows Scripting to control Client
> > > Access sessions?
> > >
> > > I would like to get a script to open CA, login, run a report, and
> > > signoff...
> > >
> > > I have done some scripting with MS Apps, but cannot seem to make
> > > any progress with CA.
> > >
> > > Any help, direction, or samples would be appreciated,
> > > Thanks,
> > > David
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > > mailing list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
