Q: I've configured my ODBC data source, and I am trying to use it to retrieve data. However, when I try to run an SQL statement, I receive an error saying "column *N not found." I'm not requesting this *N column. What's going on?
A: You need to make sure there's a *LOCAL relational database entry on the system you want to connect to. Do this by running the Work with Relational Database Directory Entries (WRKRDBDIRE) command. If there is no entry with *LOCAL, select option 1 to add a new entry. Make an entry that is the same name as your AS/400 system name. Then, for the remote location, enter *LOCAL. You may also have to restart the server support job to make sure it picks up the new entry. End the job by issuing the following command:
ENDPJ QSERVER QIWS/QZDAINIT
Start it again by entering this command:
STRPJ QSERVER QIWS/QZDAINIT
This should pick up the new database entry.
- Brian Singleton


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