Sponsored By
 ADVANCED SYSTEMS CONCEPTS
|
|
ABSTRACT DELIVERS:
- Cross-Referencing -
- Impact Analysis -
- Flowcharting -
- File Re-creation -
- Documentation -
- Field expansion -
Follow the link below to discover why you
need to replace your existing iSeries
cross-reference tool
with ABSTRACT
Read More
|
|
Sponsored By
 INFINIUM USERNET
|
|
Infinium UserNet is the user-run organization for professionals who support, manage and rely on
Infinium software applications.
Attend the 2003 Infinium UserNet Conference & Expo from June 18-20 in Oak Brook, IL. Technical education, in-depth seminars, user experiences, new product showcase and networking opportunities abound.
For the latest information and registration, visit www.infiniumusernet.org
|
|
|
Working with Varying-Length Database Fields
Hey, David:
We use a utility to replicate data files between our iSeries system and several SQL Server databases running on Windows 2000. When the original file definition comes from SQL Server, this utility creates varying-length character fields on our iSeries. This caused a problem in an RPG program when I forgot to set the length of the field when I changed its value. Do you know how much space we save when a field is varying-length? Also, what is the easiest way to determine and set the length of data in a varying-length field after changing the field's value? Our programs are ILE RPG, and we are on V5R1.
READ MORE >
|
When a 10-Digit Variable Won't Hold a 10-Digit Number
Hey, Ted:
I've noticed that you and others sometimes use the i and u data types in your RPG IV programs, so I decided to use them, too. Things were going fine until I tried to store a 10-digit stock number in a 10-digit integer field. The program canceled, with message RNQ0103. (The target for a numeric operation is too small to hold the result.) Should I just stick with good old reliable packed decimal?
READ MORE >
|
