|
Right, except you do not need STRCODE to use CODE. The only thing STRCODE buys you is green screen CL prompting and host commands (including possible functionality from third-party plug-ins). I personally like STRCODE CL prompting better than GUI because GUI prompting is limited. Anyway, you can start CODE locally and search without any AS400 setup, but why would you when STRPDM is faster? With a little AS400 setup, you can set up commands to use CODE directly from PDM (ex: "E" = Edit with CODE instead of "2" = Edit with SEU). In fact, you can set up browse and design commands as well (ex: "D" = Design, "B" = Browse). In a simple CL example for CODE editing, your call would be as follows: call pgm(qdevtools/evfcfdbk) parm('37' 'Y' 'OS400' '<LOCAL> CODEEDIT "<>&L/&F(&N)" /M Y /N') Maybe some use library QCODE instead of QDEVTOOLS but I think QDEVTOOLS is supposed to be newer? Not sure but I always use QDEVTOOLS. Make sure your current library is added beforehand. Below is an excerpt from a CL for handling the PDM input: * For EVFCFDBK, there are 4 parms. The first 3 parms are required. + * Parm 4 (CODEPARM) values: + * Browse source = 'CODEBRWS "<>&L/&F(&N)" /N' + * Design DDS = 'CODEDSU "<>&L/&F(&N)"' + * Edit source = 'CODEEDIT "<>&L/&F(&N)" /M Y /N' + * The empty <> looks for the first server (or enter a server here). + * /M Y means to lock the member. + * /N indicates to retain sequence numbers. + CHGVAR VAR(&CODEPARM2) VALUE('<LOCAL>' *BCAT + &CODEPARM) CALL PGM(QDEVTOOLS/EVFCFDBK) PARM('37' 'Y' + 'OS400' &CODEPARM2) You could even take this further and set the current library automatically based on a list of users in a file before calling the program. You could even have another CL that executes the STRCODE with defaults and the current library added automatically beforehand. If anyone is interested in these CL's, let me know. Thanks, Craig Strong craigs@xxxxxxxxx ** Vern wrote: You're right. You need the various parts of 5722WDS - including the Workstation Tools. There are many product options here. Be sure to look into PTFs - the WDT400 webpage should have info on this. To use CODE, of course, you need to STRCODE, and to debug, you need to STRDBGSVR. Good luck Vern At 10:45 AM 7/28/2003 -0500, you wrote: >I'm curious to know if there is any configuration that needs to be done >on our 400 in order to start using WDT/400. I've read that the WAS needs >to be configured in order to use WDS, but right now I'm interested in >using CODE. Shouldn't I be able to install WDT/400 and use CODE with >little or no configuration on our 400?
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.