RE: Client Access macro running on startup...

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

Go to the edit menu and click on preferences.  On the submenu choose
macro/script.  You may have inadvertently set up an auto start macro.  I
know I have before. <g>

> -----Original Message-----
> From: Richard B Baird [mailto:rbaird@esourceconsulting.com]
> Sent: Wednesday, May 29, 2002 8:14 AM
> To: midrange-l@midrange.com
> Subject: Client Access macro running on startup...
>
>
> hey all,
>
> Just recently, something wierd started happening with CAE 4.3
>
> I have a set macros recorded that type in often used text and commands
> (such as outq(xxxx) or strsrvjob(xxxx/xxxx/xxxx) etc.) -
> stuff I type all
> day and set up with shortcut keys so I don't have to.
>
> I recently went into the macro editor and removed these lines from the
> vbscript:
>
>    autECLSession.autECLOIA.WaitForAppAvailable
>    autECLSession.autECLOIA.WaitForInputReady
>
> because I only use the macros when I'm on a part of the
> screen that can
> except typing.
>
> Now, whenever I start a new 5250 session, it runs the first
> macro in my
> list, ( 'outq(xxxxxxx)' ) in the userID and password fields
> on the signon
> screen.
>
> I've looked through all the menu options, and the help, but I
> can't find
> where I might have specified a start-up macro script.
>
> It's not a big deal, but it is a little annoying.
>
> Any ideas?   TIA,
>
> Rick
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>