|
Eric, I did find a bug. If you have a parameter that expects a short value in it, such as COPIES on the OVRPRTF command (parm must be 6 characters or less); and if you use a variable name that is longer than the 6 characters (such as &COPIES), it gives the bogus error that the value is too long. It should not be testing for length constaints such as this if you use a variable name. Doug Edwards ______________________________ Reply Separator _________________________________ Subject: Prompting CL without STRCODE Author: code400-l@midrange.com at INTERNET Date: 8/17/01 8:56 AM After a few posts from users, I posted at the end of April that we were looking into being able to prompt CL using the same mechanism that OpsNav uses from the AS/400 Toolbox. This would avoid to need to have a STRCODE session to prompt your CL statements from the CODE Editor. Well, we now have something for you to try out. I have posted on the WDT400 website (exact link is below) the update. A couple of points: 1. This update is provided AS IS. 2. You have to have V5R1 of WDT400 with CODE Service Pack 1 or CODE Service Pack 2. 3. Read the instructions carefully. http://www-4.ibm.com/software/ad/wdt400/support/codesupport.html#PromptingCLwith outSTRCODE Note: Occasionally, the graphical-user-interface that displays the prompted CL statement appears behind the editor. If this happens, switch focus to the graphical-user-interface. Hope you find it useful, Eric Eric Simpson IBM Toronto Lab Phone: (416) 448-3226, T/L: 778-3226 Email and SameTime Connect: esimpson@ca.ibm.com _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com
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.