WDT/400 Code Editor Library Lists

[Guest.Visitor]

In CODE/400 I can go in and maintain my library list for in the communication properties, but my library list is fairly long and it is a pain to change it every time I need to compile in a different version of our software (ie we are always changing our library list on the as/400 automatically we we start our software package) Does anyone know of a quicker way to maintain the library list ie setup a number of custom lists and pick the appropriate one that you need to compile the program you are changing in code/400. Thanks! Dean

[Guest.Visitor]

Dean, The change management product that we develop and sell, TurnOver, has an interface to Code/400. When you take an option to edit a source member from within our product, we open the member in Code/400, and we also set the libary list based on the application you are working in. You could probably do something similar with editor macros. The easiest thing would probably just be to load up the editor's menu within Code to contain a bunch of different options, each of which launches a macro that changes the library list to some different value. The macros that we use are located in your ../Extras directory. You can use them as an example to get you started. turnmenu.lx would show you how to add menu options that will execute a macro. You can add these to your profile.lxu to have them always show up automatically. turnmake.lx builds an AS/400 command string and executes it. You would change it to build up a string for the CHGLIBL command. Here is a tip, make a CL program that does your CHGLIBL, and just have the macro call the program. Code has trouble on Win95/98/Me executing a long command string. So the command is just to CALL LIB/PGM 'PARM' you will not have any problems. Of course, copy and rename our macros, do not edit them directly. Hope this gives you some ideas. Mark Phippard Director of Development SoftLanding Systems

[Guest.Visitor]

Wow, that's really cool, I managed to write a script that dynamically builds libraries by passing the software version and company code when invoking the CL... I even put a new menu with an option to change library list (by running the macro). I put the command to add to the menu in the profile.lx and it shows up when you start code editor. Thanks for your help, I really appreciate it. BTW... IBM's Inge Weiss and the AS/400 team from the Toronto lab have released a good .PDF talking about Advanced topics in CODE/400. The PDF can be found here. http://www-3.ibm.com/software/ad/wdt...ourse_37LF.pdf

[Guest.Visitor]

Dean, Great news. I have not programmed any macros in a while so double-check this and don't just take my word for it. Somewhere in the docs it talks about the special macros that exist, like profile.lx I think that they recommend you use one named profile.lxu to store any customizations. Both are executed in the same way, the .lxu macro is just expecially for user modifications, and therefore you do not have to worry (as much) about losing your changes when applying fixes/upgrades to Code/400. Glad I could help, Mark Phippard SoftLanding Systems