|
Craig and Others, If we need someplace to offer these and/or other Code Macros besides an IBM site, I can offer up my personal site at www.veriteccomputing.com . I already have some VARPG stuff there. I was going to add my own Code macros to it, but never got around to it. I changed positions and got away from using CODE. Now I am back. I am not trying to promote anything on that site. I no longer have the time to run a sideline consulting service and never got around to changing the site. I just want to offer it up as a place to put stuff like the macros. -- ------------------------------------------------------ Scott P. Johnson Applications Development Team Coordinator Microcomputer Development Specialist IBM Certified Specialist - AS/400 RPG Programmer ------------------------------------------------------ craigs@dekko.com Sent by: To: code400-l@midrange.com code400-l-admin@mi cc: drange.com Subject: Useful CODE/400 Macros 01/16/2002 12:03 PM Please respond to code400-l Since we are on the subject of wish lists, I thought I would mention the macros I have and use on a regular basis. I meant to mention this earlier. Every one of them I have created in-house or modified from the website for ultimate flexibility, elimination of errors, and ease of use. Some of the macros like clipline.lx and modmark.lx on the website, had errors so I stopped using them but modified them instead. I am willing to share them with IBM if they are interested. I use CODE/400 quite a bit and I have been using the following macros for quite awhile: 1. ModBlock.lx - Used to fill in a modification mark in positions 1-5 and can also be used to update the modification date depending on what parm you pass. You can select a block in any fashion (select/mark) and the block will be modified. You can even use the select all to modify the blocks. Of course, if you don't even select anything, the line you are on automatically gets selected. Since both functions have the same type of processing, they are in one macro. Other errors like cutting off the comments in ILE RPG are now fixed. Also allows blanking out a mod mark or zeroing out a date. Written by Scott Johnson as Mod2, rewritten by Craig Strong as ModBlock. I think this is also a good example of using subroutines in REXX. 2. ClipLine.lx - Uses the mark text method for cut/copy. Now includes an identification of a block as unmarked by blocktype = 'UNSET' method to handle all selections like ModBlock.lx does. I think there are some original errors that are fixed now too. Written by David Morris, modified by Brian James for mark text, and modified by Craig Strong to fix original errors. 3. Create_Subroutine_RPG (also as RPGLE) - Create subroutine. Written by Craig Strong. Note: This macro might not want to be used as is because you would want comments different ways. It prompts for the comment and then the name of the subroutine. If anyone would like any of these macros, please e-mail me and I will send them out right away. The original authors of the first two macros did an excellent job writing them and setting a strong foundation, I just took them some steps further. Maybe other people can come up with different mods. I could still see a use for the ModBlock macro after the IBM modification in service pack 5 to include a SIGNATURE as a Mod Mark when adding a line. Thanks, Craig Strong craigs@dekko.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 Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-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.