Work faster and more efficiently, keeps projects on time.

This is invaluable to help map out how an application works. You start by Downloading a system's files and programs into a model. Through the model enquire on all calls made by a program, all programs that call a specific program, file usage (by program and file), file descriptions and where fields are used in files, etc.  The model has two main enquiry points of access: one by program, and the other by file. Both allow cross over enquiry to the other. There is no recursive call problems, so you could continue enquiring about the system.

For example :

   Display a list of files.
   Take the option to see all logicals over a physical.
   Take the option to see the programs that use a logical.
   Take the option to see all the files that the program uses.
   Take the option to see all the logicals over a physical used.

Once the model has been built you can use a function to produce a report to see what programs and files are dependent on a file you wish to change, this function can optionally copy source and recompile dependent options.

Various documentation tools and cross reference reports as well as an RPG source documentation tool that can be used to (a) Link IF, DO, END, etc. within an RPG source so it is more readable when looking at it (b) print an indented RPG source listing (c) print a structure of an RPG program (d) insert colour or display attributes to user-defined places so the source is more readable.

Source debug tool for RPG and CL programs. Special features include

a) Function keys to find the corresponding or encompassing IF, ELSE, END.

b) General scan to add/remove breakpoints.

c) Work with a list of breakpoints.

d) Allow debug to be ended for a program and the breakpoints saved so when re-starting debug the break points can be applied.

e) Allow source debug to be started for batch jobs.

f) During debug mode allow source  lines to be indicated with changes and if required update the changes to the actual source member.

g) Allow up to 10 programs at once to be debugged, allowing programs to be added or removed as required.

h) Allow variables to be linked to a display key, so when the key is pressed, the variables will be displayed.

i) Allow step through to be switched on or off.

 System Help

Create fast and effective Help Text

The System help module allows you to define your own help for menus, menu options, modeler and for use in your own programs.

Help is attached at system level, allowing different systems their own or the same help.

Help is defined as a module, identified by a combination of a help name and help type. This combination is unique to each help library.

Special features are available in the definition and display of your user defined help, including :

Attributes :  Portions of help text can be displayed in various colours and attributes, to highlight headings and important pieces of text.

Hypertext :  Words and phrases in the help text can be linked to other help modules, allowing the display of related help modules by simply positioning the cursor and pressing enter.

Hypercommand : Similar to hypertext, but instead of displaying related help, a command can be     prompted or executed. (Help can use both hypertext and commands simultaneously).

 Extended Help : Numerous related helps can be attached to a single help module e.g. file fields for a file, by pressing a function key these helps are displayed in the same window consecutively.

Variable Formats : Select your standard display format from one of four window sizes. A function     key will allow you to enlarge the window to full screen size.

Some uses of this function are :

a) Send database file via TCP/IP.
b) Send a spool file to a data base file via TCP/IP.
c) Receive a file via TCP/IP.
d) Execute commands on a remote AS/400 machine by TCP/IP.
e) Send or receive an AS/400 save file via TCP/IP.

Some benefits that are already built in are :

a) Encrypt the user password if used in a CL program, to prevent disclosure of passwords through examination of the source or by dumping the  object.

b) The command can send an escape message if the file fails to be sent/received by analysing the output log of the transfer. This function can also be used in batch mode.

c) Prompt from the command to select from the configure table a host machine.

d) Allow the command to be scheduled in batch mode.

The Application implementation tool is designed to implement changes in objects and source from one environment to another. A number of features to ensure a smooth implementation including:-

A pre-check is available to make sure logicals being implemented have the required physicals in the to environment or are also being implemented, etc.

Authority can be specified for the objects being implemented.

Archiving of existing objects and source can be specified so if the change has to be backed out, the  last version still exists.

Data can be kept when implementing physicals or replaced by existing data if the physical already exists.

We also have a full change management system called RIO.

An object list is a file that contains records with object information on them (e.g. object name, type, attribute, library and text, etc.).

The main reasons for creating an object list, these are :

 i) An object list can be used in various R/Utility commands where objects have to be specified (e.g. the implement change utility). This  allows a list to be prepared beforehand and used within the utility  command.

 ii) When a group of objects have to have the same command executed  over them, (e.g. CHGOBJOWN or STRJRNPF).

 iii) When the object is being used to drive a command over another  object (e.g. CHKOBJ) to see if the object exists in another library.

An object list can have multiple commands executed over it, the records being indicated as errored or completed correctly. The indication can be used by  another command to be executed over the same list. For example :

 a) Run a CHKOBJ command over the list to check if the object exists in  another library. The records that did not would be indicated as an  ` error.

 b) Run a CRTDUPOBJ command over the list, but only selecting  errored records, to create the object in the library in which it was not  found.