|
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. >
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.