3-12:Subroutine Process Additional Attributes Option

Chapter 3-12: Subroutine Processes

Subroutine Process Additional Attributes Option

The additional attributes option accesses the Subroutine Process Additional Attributes overlay from which you can alter the standard EM attributes. The Additional Attributes overlay for Subroutine processes is shown in Figure 3-12-4:

Figure 3-12-4. Subroutine Process Additional Attributes Overlay

The Additional Attributes overlay for Subroutine processes contains the following fields:

· Executable Module displays the name of the executable module (EM) that is automatically generated by APPX. APPX derives the file name from the date and time the currently selected subroutine process was added. The name consists of a unique string of eight alphanumeric characters and cannot be changed. If APPX finds it necessary to recreate the EM, the new EM retains the same file name. This field is common to the Additional Attributes overlay for all types of processes.

· Cache Priority establishes the likelihood that the process will remain in memory after execution, relative to other processes that the user has also completed executing. A process with a cache priority of 99 is most likely to remain in memory. A process with a cache priority of 1 is least likely to remain in memory. A cache priority of 0 indicates that the process is never cached. The default is 50. This field is common to the Additional Attributes overlay for all types of processes.

· User Cancel OK? contains either “yes” or “no” and determines whether or not a user can select the cancel option key to stop the execution of this process. The default is “yes”. You can conditionally control the user’s ability to select the cancel option with statements and the predefined field CANCEL OK. This field is common to the Additional Attributes overlay for all types of processes.

· Description is incorporated in the message that displays on the screen when the subroutine process is compiling. It is used to communicate with users since it provides a more descriptive and easily understood alternative to Process Name, which is the default if this field is left blank.

· Commit Mode controls the commit mode for a process and can be selected from a drop-down list of available options. Commit Mode determines those points in time when APPX will commit changes made to the tables stored within an RDBMS. It is only applicable in conjunction with an RDBMS; it has no effect with APPXIO. Also, not all File Managers support this feature. Although initially set here for the process, it can be added or overridden by use of predefined field COMMIT MODE. The following options are available:

COMPATIBLE. Changes are committed as soon as all locks are freed. This provides maximum compatibility between APPXIO files and RDBMS tables.

AUTOCOMMIT*. APPX will commit each modification as it is made.
*This value will be implemented in a future release.

PCF CYCLE. APPX will commit modifications as each PCF record is processed.

END. APPX will only commit modifications at the end of the process family.

MANUAL. APPX will not automatically commit changes. You must use the COMMIT statement to do so.

APPX Application Design Manual (01/13/03)