Q: I have started programming my interactive programs with cursor-sensitive searches. If the user presses a function key to perform a search, I calculate the location of the cursor. If it falls within a hard-coded range, I present the user with the requested search. I want to soft-code that range from the display file. I should be able to match the cursor position to the field location and present the user with the desired search. Is there a way to retrieve the location of a field within a display file (other than reading the display file source)?
A: There's an easy way to accomplish this. Use the DDS Return Cursor Location (RTNCSRLOC) record-level keyword in your display file. It returns the name of the field that the cursor is on. This method has some advantages over using hard-coded screen coordinates. It means that if you move a field in a display file from one location on the screen to another, you don't have to worry about changing the program which uses that display file.
The return cursor location has two required parameters as well as an optional third parameter. For an example of how to use this keyword look at the four lines of code in 3. The two required parameters, (cursor-record and cursor-field), must be defined as 10-character hidden fields. The cursor-record variable returns the name of the record format and the cursor-field variable returns the name of the field where the cursor is located. The third parameter (cursor-position) is optional and, if used, must be defined as a four-position, signed-numeric, hidden field. This field returns the relative position within the field where the cursor is located.
The return cursor location has two required parameters as well as an optional third parameter. For an example of how to use this keyword look at the four lines of code in Figure 3. The two required parameters, (cursor-record and cursor-field), must be defined as 10-character hidden fields. The cursor-record variable returns the name of the record format and the cursor-field variable returns the name of the field where the cursor is located. The third parameter (cursor-position) is optional and, if used, must be defined as a four-position, signed-numeric, hidden field. This field returns the relative position within the field where the cursor is located.
In your program, just test the value of the cursor-field variable. If it matches a field for which the user can perform a search, then present the search results. If it doesn't, you might want to display a message which says something like, "Search not valid for cursor location." Using this technique, you can code cursor-sensitive searches within your programs without hardcoding screen coordinates.
Cursor-sensitive Searches
Figure 3 DDS for RTNCSRLOC Keyword
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 A RTNCSRLOC(&RCD &FLD &POS) A RCD 10A H A FLD 10A H A POS 4S 0H
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