One of the issues that caused me to delay implementing external procedures, programs, and functions was that there was no easy way of finding out where a given program, function, or procedure was used. Since this problem has been adequately resolved (See "TechTip: Fishing for Service Programs"), there remains only one issue: how to keep track of the source members for the different module types (i.e., functions, procedures, prototypes, etc.).
I would like to be able to say that I came up with the following naming conventions on my own, but I didn't. I am sure I saw some of them as "suggestions" in some article or other. However, I am relatively certain that I have not seen them all together in one place. So without further ado...
| Name | Type of Module/Source |
| P.xxxxxxxx | Procedure |
| PR.xxxxxxx | Prototype member for /COPY |
| F.xxxxxxxx | Function |
| S.xxxxxxxx | Service Program |
| M.xxxxxxxx | Main procedure (*ENTRY/pep) |
I know it's simple, but it is what works for me. There are certainly other ways to go. Using separate source files (QRPGPROC, QRPGFUNC, QRPGMAIN, etc.) is one of the other methods I have seen. Whether you use these naming conventions or not, if you are going to be developing using ILE, you are going to need to use some sort of naming conventions. Remember, the best naming convention is the one you will actually use and stick to.
--Jeff Olen
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online