You can start the debugger from CODE/400 without prompting by pressing Ctrl-D. The debugger will be invoked right away. Unfortunately, if you press Ctrl-D by accident, you cannot cancel it until everything is loaded. Fortunately, you can make sure the debugger always prompts you.
The subdirectory c:codemacros has *.LXL files that are loaded according to the type of source code you want to edit. For example, if you want to edit an RPG/400 program, look in the file RPG400.LXL that is loaded before the source member. In this file, you'll find information such as which macro is assigned to which key.
To make the debugger always prompt you when you press Ctrl-D, find the following line and remove the /N:
SET ACTION.C-D START CODEDT /EACCMDLE /N /P "%FILENAME%"
You can do the same for other files, such as CLP400.LXL, RPGLE400.LXL, and RPG4SQL.LXL.
? Jan Jorgensen
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