I make frequent use of the RPG *LIKE DEFN operation, as I enjoy the increased security of defining work fields properly. There is, however, a very subtle consideration with *LIKE that caused me quite a bit of debugging time.
For a recent project, I had defined fields as shown in 3. Note that the field OFFSET is defined as a binary field, length four (which allows up to nine digits). I also wanted field PMOFST to be defined as a binary field, length four. By using *LIKE DEFN as shown in the figure, however, PMOFST is defined as a packed field, length nine.
For a recent project, I had defined fields as shown in Figure 3. Note that the field OFFSET is defined as a binary field, length four (which allows up to nine digits). I also wanted field PMOFST to be defined as a binary field, length four. By using *LIKE DEFN as shown in the figure, however, PMOFST is defined as a packed field, length nine.
In most circumstances, this probably would not cause any problems. But in my usage, I specifically needed a binary field, as I was using it as a parameter to an openness API. Many of the APIs require binary fields as parameters. In my case, the unforeseen conversion to packed is what caused erroneous processing.
Gotcha! Likewise, My Friend
Figure 3 RPG source for *LIKE DEFN
Figure 3: RPG Source for *LIKE DEFN I DS I B 1 40OFFSET C *LIKE DEFN OFFSET PMOFST
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