Attributes are the fields you define in your System i file.

You can begin by building your attribute list in Integrator by synchronizing the object with the host. This process reads the file definition from the System i and builds your list of attributes. The synchronize process will automatically run and read the definitions for the first occurrence of this file name within the library list. You can repeat this process manually multiple times if you change the file definition on the host by using the ‘Synchronize with Host’ option. However, the synchronization process will not recognize changed field names.

Non on key field attributes: The integrator requires a unique key for each object. If the host file already has a key, the synchronization process will automatically identify fields as part of the key as well as add a sequence number to multiple key parts. If the file does not have a unique key, you must either create a keyed logical file or identify the key manually. Key fields are the default sort order for all list views for an object.

By applying security to an object, you can control which users can view the object and which users can create, change, delete or copy the object.

Basic object security allows you to control who can display or maintain an object. Advanced object security allows you to control selectively who can create, change, delete, or copy an object.

In the basic model, all of the maintenance activities are permitted to those users who are authorized to maintain the object. Use the basic security model if you want a user who can change an object to also be able to create or delete the object. Use the advanced security model if you need to restrict some users to changing the object but not creating or deleting the object.

If you haven't already, you may want to start to explore your IDF programs. Currently they provide the replacement for the 300 series inquiry programs. In addition, navigation drill downs are far superior to any green screen presentation of the data.