The first example program (SEU003) defines line commands for highlighting and coloring source lines--either a single line or a block of lines. They can also be used to highlight text within a line by positioning the cursor immediately to the left of the target string (there must be a blank space available to write the hex code to). There is also a command to clear all highlighting.
The second example program (SEU004) is designed for use with display file DDS source. It enables the F7 key, which when pressed with the cursor on a line containing a MSGID or MSGCON, will retrieve the message text and send it to line 24 (as a regular message). This sure beats hunting around message files to find text strings! Just be sure that the required message file is in the library list for the option to work (unless the message file name is qualified with the library name).
There are two methods of implementing SEU exit programs. The first is for a single program. Start an SEU edit session and press F13 (Change session defaults). Page down and enter the required program and library name against the "User exit program" prompt.
The second method is to use the Work with Registration Information (WRKREGINF) command to register one or more exit programs. The exit point for SEU user-defined options is QIBM_QSU_LCMD. Option 8 allows you to work with the exit programs for that exit point. Exit programs can then be added/removed as required (check out the Help text for more details).
The default setting in SEU is to use the registration facility. The session defaults will only need to be changed if you defined a filter string. The latter can be used to tailor exit programs to individual users or groups of users.
Phil Hope has been an iSeries developer for the last decade, starting with Patient Administration systems in the UK Health Service, through Electronic Data Interchange for a leading UK food manufacturer, to Sales and Warehousing systems for major UK retailers. You can reach Phil at
Tips = $$
Earn money for the techniques you use every day!
Send your tips to
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