Menu Design & Implementation w/ Graphical DDS: #1

  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Brief: The new Graphical DDS keywords make it very easy to add menu bars and pulldown menus to your AS/400 programs. But when using these keywords to describe a menu, you have many design choices to make. This two-part article presents a working example which teaches you how to use the new keywords. It also discusses the design choices that you have and guidelines for deciding when to use the various options.

In the July 1993 issue of Midrange Computing, "Pull-down Menus and More" introduced the new Graphical DDS (GDDS) keywords available in V2R2 with PTF SF11703 and officially included in V2R3. As described in the article, the keywords include support for menu bars and pulldown menus, check boxes and radio buttons, cursor control, edit masks and other enhancements-in other words, functions that let you create a graphical look with display files.

These new capabilities work with all types of display devices attached to the AS/400, from the earliest 5250 terminals to PCs running RUMBA in Windows or OS/2 and everything in between (including the new mouse-capable InfoWindow II terminals). As you use a more capable device, the graphical look is enhanced. The greater capabilities are handled by OS/400 and the workstation controller that attaches the device. This extremely valuable feature enables you to take full advantage of device capabilities without having to create different versions of a display file.

As with other software capabilities, there are design and implementation issues that you must understand and address. It is actually quite easy to use the new GDDS keywords to create menu bars and pulldown menus. But within just those two features are many options that you can use. To understand these options, we will use the new GDDS keywords to create a sample display file over the course of two articles. We'll also build an RPG program to drive the display file.

This first installment looks at defining and displaying menu bars and addresses the associated design considerations, with partial DDS and RPG examples to illustrate our progress. In next month's installment, we'll expand the same display file and code fragments into full, operational code. Part 2 will include further discussion of single-choice menus and will introduce multiple- choice and no-choice menus.

With this month's DDS and RPG fragments, we can explore these features:

o Using a variable number of items on the menu bar. o Defining a menu-bar separator. o Using a single-choice, pulldown menu.

As you'll see by working through the example, simply using GDDS does not guarantee an effective user interface. If anything, you need to be even more aware of how you present the interface to your users, since many of them have become familiar with menu bars and pulldowns from PC software. The advances promised by GDDS are not just that we can use the capabilities, but that we can also make use of a great deal of experience developed over the past several years as graphical user interfaces (GUIs) have become widely used.

Creating the Example

The figures contained within this article are actually excerpts from a complete display file and RPG program which will be published next month, in Part 2 of this series. For spatial reasons, I have included only those fragments that illustrate the specific topics covered this month. But you don't have to wait until next month to download the code in its entirety-it's available now on MC-BBS.

Before attempting to incorporate the GDDS keywords in a display file, first make sure that your system is operating at the correct release level. If your machine is running V2R3, you do not have to do anything special to use the GDDS keywords explained here. If you use V2R2, you need to order and apply PTF SF11703 if next month's display file and RPG program (and the excerpts published this month) are to work as presented.

What the Example Does

The display-file excerpt in 1 includes a menu bar, a menu-bar separator and partial definitions for pulldown menus associated with items in the menu bar. When the menu bar appears on-screen, it is displayed over the current display. The current display is not erased by the menu bar. This typical use of a menu bar display shows how you can add a menu bar to existing programs.

The display-file excerpt in Figure 1 includes a menu bar, a menu-bar separator and partial definitions for pulldown menus associated with items in the menu bar. When the menu bar appears on-screen, it is displayed over the current display. The current display is not erased by the menu bar. This typical use of a menu bar display shows how you can add a menu bar to existing programs.

In order to display the menu bar and pulldown menus without erasing the current display, the ASSUME and OVERLAY keywords are used in the DDS. Record format ASSUME contains the ASSUME keyword. The ASSUME keyword requires at least one displayable field defined in this record format (the example uses a single blank space). It is not necessary to actually use the record format in the RPG program. We satisfy the requirement of the display file by simply including this record format in the DDS for the display file.

The OVERLAY keyword is used in the MENUBAR record format. It is required in this format because we are writing the record format to the display and we do not want to replace the entire panel.

The first time it is displayed, the menu bar contains just two items: Menu and Exit. Other items are defined, but they are controlled by indicators which will remain off in this example. Selecting a menu item to display its associated pulldown menu is done differently, depending on the display device you are using. For the examples, I am assuming that the display device is a mouseless, nonprogrammable, non-Enhanced User Interface (EUI) type of device-in other words, your plain-vanilla dumb terminal. To select a menu item, you position the cursor to the immediate left of the item and press Enter.

Defining the Menu Bar

Record format MENUBAR defines the content of the menu bar and the options used. The MNUBAR keyword indicates that this record format is a GDDS menu bar. It is displayed starting on line 1 of the display. The menu-bar items are displayed horizontally across that top line. The MNUBAR record format also includes a menu-bar separator.

In addition to the MNUBAR keyword, the MNUBARDSP keyword is used. This tells DDS that the menu bar is to be displayed when the record format is written. This seems redundant, since the MNUBAR keyword previously defined the record as a menu-bar record. The reason you need MNUBARDSP has to do with how the system processes menu-bars and pulldown-menus.

The MNUBARDSP keyword has two uses; one for records which do not contain the MNUBAR keyword and one for records that do. In the first usage, you specify the keyword on a record that is not a menu-bar record. In this case, there are two required parameters (menu-bar-record and menu-bar choice-field) and one optional parameter (pulldown-menu-selection-field). This format is used if the MNUBARDSP keyword is in a record format that does not include the MNUBAR keyword. For example, you can define your application display and include the MNUBARDSP keyword to associate a menu-bar record with the application display. This concept is similar to the WINDOW keyword, where you can use the keyword either to define the window or to refer to another record format that defines the window.

The result of using MNUBARDSP in an application record format is that when a program displays the application format, the menu bar is also displayed, without the program having to explicitly write the menu-bar record format.

I do not choose to use that form of the MNUBARDSP keyword for the simple reason that I want to keep a separation between the application display and the menu- bar display. The degree of separation goes beyond just keeping the menu-bar and application record formats separate. I prefer to perform the menu-bar processing and to define the application record formats in two different programs.

The primary motivation for this design is that the processing associated with each task is done in its own program. As you will see in next month's installment, the processing for the menu-bar and pulldown options can become complicated. Rather than include that additional level of complexity in the application program, I find it advantageous to process the menu bar independently of the application using it. Instead of including code to process options from the pulldown menus, all I have to do is put a value into a parameter that is passed back to the application program. The application program then chooses the required processing, based upon the parameter value.

This separation simplifies the menu bar and the application program tremendously. It also enables you to test the menu-bar program independently of the application program, since you can plug in the parameter value using either a Change Program Variable (CHGPGMVAR) command in debug mode or a simple screen- input field where you type in the value.

In order to implement my design, I use the second format of the MNUBARDSP keyword. As shown in the excerpted DDS, the keyword is specified in the same record format as the MNUBAR keyword. In this case, you can specify one optional parameter, a numeric field that will contain the value of an item selected from a pulldown menu.

You might wonder why you actually need to specify MNUBARDSP in the same format with MNUBAR. The reason is that the system controls display input/output (I/O) whenever the menu-bar format is displayed. The MNUBAR keyword simply identifies a record format that describes the content of the menu bar. Once you display the menu bar, the system takes care of displaying and removing any pulldown menus that you select. In RPG terms, you never EXFMT a pulldown menu. The system writes and reads a pulldown menu when it is selected from the menu bar. You indicate to the system when you are giving it control by writing a record that contains the MNUBARDSP keyword.

The first field defined in the menu bar record is MNUFLD. Although this field must be defined as shown in the example, it does not appear on the display as a two-byte numeric field on line 1. Instead, the field is used to return a value to a program that indicates the menu-bar item selected. This will be explained in a moment.

The next keyword, MNUBARSEP, is defined as a field-level keyword, although it defines the menu-bar separator that applies to the menu-bar record format. The menu-bar separator is used to delimit the menu-bar items from the rest of your application display.

In the example, I have defined the separator to be a solid underline across the screen. On an 80-column display, the separator (underline) appears in columns 2-79. If you do not specify your own MNUBARSEP, the system displays a default of dash characters as the separator.

This keyword seems to be mistakenly placed at the field level and not the record level. I hope that in future releases IBM will make it a record-level keyword also, since that is where it would logically be specified.

The next several MNUBARCHC keywords define the menu-bar choices or items that you want included in the menu bar. The keyword has four parameters, the first three of which are required.

The first parameter is the choice identifier. This is a value from 1 to 99. Menu items are displayed in ascending numeric order, regardless of their order in the DDS.

The second parameter of MNUBARCHC is the name of the record format in the same display file that defines the pulldown menu associated with the selection. This can be any valid record-format name. The record format must contain the PULLDOWN keyword. Although it is unlikely that you would do so, you can use the same record format on more than one MNUBARCHC keyword.

The third parameter is used to define the text that is displayed in the menu bar. This can be defined as either a text constant, as shown in the example, or as a program-to-system field. A program-to-system field lets you dynamically alter the text of a menu-bar item. This is useful if you are creating an application to be used for different national languages. Using the program-to- system field, you can obtain the required text from a message file and display it in the menu bar.

The example also shows how to specify the optional mnemonic character used for the menu-bar item. You designate the mnemonic by placing the greater than (>) character to the immediate left of the character to be used. On workstations that support it, the mnemonic is displayed as a single-character underline within the menu item. For example, the >Menu item displays as the word Menu on low-function workstations and as Menu on higher-function workstations. Using the mnemonic allows users on higher-function terminals to select the menu-bar choice by simply entering the underlined character anywhere in the menu-bar record. On terminals that do not support the use of mnemonics, the user must tab to the menu bar item, and press Enter.

The rules for mnemonics are simple. The primary rule is that, within a set of mnemonics (for example, in this set of MNUBARCHC keywords), the mnemonics must be unique among all of the selections. The character selected as the mnemonic cannot be a blank. Another rule is that, to use the greater-than sign (>) within the text of an item, you must specify two greater-than signs together.

The optional fourth parameter of the MNUBARCHC keyword is the return field, defined as a hidden numeric field. This parameter indicates that the system should not display the associated pulldown menu, but instead should return to the program that processes the menu-bar choices. Upon returning to this program, the value in the return field is the menu-item identifier.

In the example, when the Exit! menu-bar item is selected, the EXIT pulldown menu format is not displayed. Instead, the program gets control immediately. (The program is excerpted in 2). The value in EXITRF is 99, which is the identifier of the Exit! item. (The exclamation mark in Exit! is used to indicate to the user that the action happens immediately with no pulldown menu. The system does not require that we give any special indication, but you might want to consider using such an option.)

In the example, when the Exit! menu-bar item is selected, the EXIT pulldown menu format is not displayed. Instead, the program gets control immediately. (The program is excerpted in Figure 2). The value in EXITRF is 99, which is the identifier of the Exit! item. (The exclamation mark in Exit! is used to indicate to the user that the action happens immediately with no pulldown menu. The system does not require that we give any special indication, but you might want to consider using such an option.)

There are two uses of the return field. The first use, shown here, is to process a menu-bar item that does not have any items on its associated pulldown menu. A further look into the partial display file shows that you do, in fact, have to define an EXIT record format with the PULLDOWN keyword. That record format does not include any menu items. To process the Exit! selection immediately, we include the return field so that the processing program gets control when the item is selected. When the return field is used, the value of the menu item is not put into the menu-choice field but into the return field itself. When you select the Exit! item, the value of MNUFLD is zero and the value of EXITRF is 99. The program can base its processing upon those values. Looking into the program excerpt in 2, you can see the section where EXITRF is tested. When it has the value 99, meaning that the Exit! option was selected, the program ends.

There are two uses of the return field. The first use, shown here, is to process a menu-bar item that does not have any items on its associated pulldown menu. A further look into the partial display file shows that you do, in fact, have to define an EXIT record format with the PULLDOWN keyword. That record format does not include any menu items. To process the Exit! selection immediately, we include the return field so that the processing program gets control when the item is selected. When the return field is used, the value of the menu item is not put into the menu-choice field but into the return field itself. When you select the Exit! item, the value of MNUFLD is zero and the value of EXITRF is 99. The program can base its processing upon those values. Looking into the program excerpt in Figure 2, you can see the section where EXITRF is tested. When it has the value 99, meaning that the Exit! option was selected, the program ends.

The second use of a return-field option on a menu-bar item is when you want to update pulldown menu selections before the menu is displayed.

This dynamic update capability of pulldown menu selections is useful in situations where you cannot predict when the updates must occur or what the text will be. For example, you can use this to dynamically add pulldown menu items to review your most recently submitted batch jobs, including the qualified job name as part of the selection text. Because you cannot predict ahead of time what the qualified job name will be, you cannot update the pulldown menu before it is requested. Later, we will explore other ways to dynamically format selections.

The final feature to note about menu-bar definition is the use of conditioning indicators on the MNUBARCHC keywords. As with any other DDS keyword, the value is selected if the indicator is on when the record format is displayed. In this example, the User and Options menu-bar items are conditioned. The program controls whether these items are displayed when the menu bar is shown by setting the conditioning indicators on or off.

Displaying the Menu Bar

There are no special considerations for displaying the menu-bar record. The RPG fragment shows the never-ending loop used to process the menu bar. The EXFMT statement displays and reads the record format. Because we have not enabled the conditioning indicators prior to the first EXFMT of the menu bar, only two menu-bar items are initially displayed: "Menu" and "Exit!"

When control returns to the program after the user has selected a pulldown menu and entered a choice from that menu, we have values in the three fields. For MNUBARCHC options that do not include the optional return field, the menu-bar item identifier is in the MNUFLD field-this tells us which pulldown menu the user selected. Looking at the partial RPG program, you can see that each pulldown menu is processed within the SELEC group.

The OPTION field's purpose is to determine which option has been selected from a pulldown menu that only allows a single-choice selection field, as we're assuming here. (We will discuss single-choice selection fields next month.) You would generally set up a SELEC group for the options of a pulldown menu within the SELEC group for the menu-bar item. Once you determine which option has been selected, you can do any processing required for the option. At this point, I usually format a return parameter to indicate which menu option was selected and return to my calling program. We will cover this in more detail next month, along with the discussion of multiple-choice menu options.

The final field, EXITRF, is used only in the event that the EXIT item is selected. You will use this field only if you need to update pulldown menus or if you are working with no-menu items. In the sample program, this field is also processed within the SELEC group that chooses which pulldown menu to process.

Menu-bar Design Considerations

If you use more menu-bar items than the first line of the display can accommodate, the additional items are placed on the second line. This can continue for up to 12 lines of menu-bar items. However, you should design the selections so that your menu bar never exceeds one line. If the selections wrap to another line, you have too many menu-bar items or the text for each item is too lengthy.

When designing a menu bar, you should keep in mind some of the ergonomic factors that cause people to associate GUI with "ease of use." One factor is that people can generally deal with only five to seven different tasks at once. Translated to menu-bar usage, that means you can expect your users to start reaching the limits of their abilities when you have that many menu-bar items. I find this true in my own experience. Even when working with what I consider to be well-designed Windows applications, I frequently have to hunt through several pulldown menus when there are "too many" of them. Unless your menu-bar items are extremely distinctive, you should try to stay within the range of five to seven items.

In terms of text for menu-bar items, the generally accepted practice is to use one word. Although the GDDS implementation will let you use any number of words, that would constitute poor design. On most terminals, apart from the three blank spaces between menu-bar items, nothing indicates to your users that the separate words make up one menu-bar item or represent additional items. A menu bar is not the place to be overly descriptive.

You should also try to follow conventions in terms of the placement of items on the menu bar. In Windows applications, the first items (from left to right) are usually File, Edit and View. A Help item is almost always included as the last (rightmost) item.

This brings up a problem for AS/400 menu design. Based on my experience of implementing a pulldown menu system, picking the menu-bar items is one of the most difficult aspects of creating the menu bar. The typical Windows File-Edit selections do not usually seem to apply. I settled on associating the first item with the underlying screen. For example, in an Order Entry application, if the underlying display is the Order Header, I would probably use either Order or Header as the first menu-bar item. When the user changes to the Customer Master lookup display, I would change the first item to Customer. Under those menu-bar item headers, the pulldown menu would have selections that apply to orders or customers.

After the first item, you can have selections that become more generic as you go across the menu bar. Most AS/400 applications involve more than one display. For example, to process an order, your application may have three or four unique displays, depending upon how far the user has progressed in entering the order. You can create a generic "View" menu item that can be used to select which panel to view. I call this a "generic" item because it will be used on all of the displays within an application. The selections within the View pulldown menu are updated when going to another display. For example, when you are on the Order Header panel, the View menu might include an option to "view order details." When you go to the Order Details panel, you would update the View menu to remove the "view order details" selection.

The most important aspect of menu-bar item selection, as far as your users are concerned, is that you be consistent with your choices and their placement. Consistent choices mean that your users can form an expectation of what selections will appear on the pulldown-menu formats. Consistent placement means that the items are in the same relative order on each display. The actual position of the items is not as important as the ordering. The menu-bar items expand and contract as you show more or fewer items. The position is not constant, but the order is. For more information on menu bars and pull-downs, see the SAA CUA panel design manual listed at the end of this article.

Coming Next Month

IBM provided an excellent upgrade to DDS with the new GDDS keywords. With just a few lines of code in a display file, you can include a fully functional, pulldown-menu interface. But as I've tried to show in this first article, there are many design considerations that apply to the menu bar itself. It makes little sense to implement this type of interface if you ignore the common-sense and customary practices that have evolved over the past several years. Although AS/400 applications contain almost no examples of menu bars and pulldown menus, you can experiment with any Windows or Macintosh application to get a feel for how menu bars are used and study the design factors involved. With GDDS, IBM has made the technical implementation easy. It is up to you to supply an intelligent design.

Next month, we will look at what goes on "under" the menu bar. There are two types of pulldown menus: single-choice and multiple-choice. Practically all implementations of pulldown menus are the single-choice type, but we will review the multiple choice type so that you will understand why it is not the preferred technique. Also included is the full DDS and RPG source code to complete the example

Craig Pelkie can be reached through Midrange Computing.

REFERENCES DDS Reference (SC41-9620, CD-ROM QBKA7402) SAA Common User Access Panel Design and User Interaction (SC26-4351).

Menu Design & Implementation w/ Graphical DDS: #1

Figure 1 DDS for Menu Bar Support

       A* To compile: 
       A                                      CA11 
       A                                      WDWBORDER((*CHAR '   ||---')) 
       A                                      VLDCMDKEY(91 'VLDCMDKEY') 
       A*  Record format ASSUME - define ASSUME keyword for file 
       A          R ASSUME                    TEXT('ASSUME record') 
       A                                      ASSUME 
       A                                  1  2' ' 
       A*  Record format MENUBAR - Menu bar definition 
       A          R MENUBAR                   TEXT('Menu Bar record') 
       A                                      INDTXT(22 'Enable USER format') 
       A                                      INDTXT(23 'Enable OPTN format') 
       A                                      OVERLAY 
       A                                      MNUBAR 
       A                                      MNUBARDSP(&OPTION) 
       A            MNUFLD         2Y 0B  1  2TEXT('Menu choice field') 
       A                                      MNUBARSEP((*DSPATR UL)   + 
       A                                                (*CHAR  ' ')) 
       A  22                                  MNUBARCHC( 2 USER '>User') 
       A  23                                  MNUBARCHC( 3 OPTN '>Options') 
       A                                      MNUBARCHC(99 EXIT 'E>xit!' &EXITRF) 
       A                                      MNUBARCHC( 1 MENU '>Menu') 
       A            OPTION         2S 0H      TEXT('Selection in PULLDOWN') 
       A            EXITRF         2Y 0H      TEXT('Return field from Exit') 
       A*  Record format MENU - Menu pulldown 
       A          R MENU                      TEXT('MENU pulldown') 
       A                                      PULLDOWN 
       A            MSEL           2Y 0B  1  1TEXT('MENU selection field') 
       A                                      MLTCHCFLD 
       A                                      CHOICE( 1 '>User tasks') 
       A                                      CHOICE( 2 'Set >Options') 
       A                                      CHOICE(91 '>Enable all') 
       A                                      CHOICE(92 '>Reset all') 
       A                                      CHOICE(99 'E>xit') 
       A                                      CHCCTL( 1 &CTL01) 
       A                                      CHCCTL( 2 &CTL02) 
       A                                      CHCCTL(91 &CTL91) 
       A                                      CHCCTL(92 &CTL92) 
       A                                      CHCCTL(99 &CTL99) 
       A            CTL01          1Y 0H      TEXT('CHCCTL for User tasks') 
       A            CTL02          1Y 0H      TEXT('CHCCTL for Options') 
       A            CTL91          1Y 0H      TEXT('CHCCTL for Enable all') 
       A            CTL92          1Y 0H      TEXT('CHCCTL for Reset all') 
       A            CTL99          1Y 0H      TEXT('CHCCTL for Exit') 
       A*  Record format USER - User pulldown 
       A          R USER                      TEXT('USER pulldown') 
       A                                      PULLDOWN 
       A                                      INDTXT(31 'Condition WRKACTJOB') 
       A            USESEL         2Y 0B  1  1TEXT('USER menu selection') 
       A                                      SNGCHCFLD 
       A                                      CHOICE(1 'Work with >Job queues') 
       A                                      CHOICE(2 'Work with >Output queues') 
       A  31                                  CHOICE(3 'WRK>ACTJOB') 
       A                                      CHOICE(4 'WRK>SYSSTS' *SPACEB) 
       A                                      CHCCTL(4 &CTL04) 
       A            CTL04          1Y 0H      TEXT('CHCCTL for WRKSYSSTS') 
       A*  Record format OPTN - Set Options pulldown 
       A          R OPTN                      TEXT('OPTN pulldown') 
       A                                      PULLDOWN 
       A            OPTSEL         2Y 0B  1  1TEXT('OPTN menu selection') 
       A                                      SNGCHCFLD 
       A                                      CHOICE(1 &OPTNTX) 
       A                                      CHCACCEL(1 'F11') 
       A            OPTNTX        35   P      TEXT('Option text field') 
       A*  Record format EXIT - Exit menu pulldown 
       A          R EXIT                      TEXT('EXIT') 
       A                                      PULLDOWN 

Menu Design & Implementation w/ Graphical DDS: #1

Figure 2 RPG Code for Menu Bar Support

        * To compile: 
        *. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 
       FGUI004DFCF  E                    WORKSTN 
       I              'Enable WRKACTJOB in -C         ENATXT 
       I              'User menu' 
       I              'Disable WRKACTJOB -  C         DISTXT 
       I              'in User menu' 
       C           *ON       DOWEQ*ON 
       C                     EXSR MNUBAR 
       C                     ENDDO 
       C*  Initialize program, set choices in menu formats 
       C           *INZSR    BEGSR 
       C                     Z-ADD2         CTL92            *Disable Reset 
       C                     WRITEMENU                       *Initialize fmt 
       C                     MOVEL*OFF      *IN31            *Disable WRKACT 
       C                     WRITEUSER                       *Initialize fmt 
       C                     MOVELENATXT    OPTNTX           *Set OPTN text 
       C                     WRITEOPTN                       *Initialize fmt 
       C                     ENDSR 
       C*  Display/process menu bar 
       C           MNUBAR    BEGSR 
       C                     EXFMTMENUBAR 
       C                     SELEC 
       C*  Process Valid Command Key - across all menus 
       C           *IN91     WHEQ *ON                        *VLDCMDKEY 
       C                     EXSR CMDKEY 
       C*  Process MENU format - must read for MLTCHCFLD 
       C           MNUFLD    WHEQ 1                          *MENU format 
       C                     READ MENU                   9999*99 - ERR/EOF 
       C           CTL99     IFEQ 1                          *EXIT 
       C                     MOVEL*ON       *INLR 
       C                     RETRN 
       C                     ENDIF 
       C                     SELEC 
       C           CTL91     WHEQ 1                          *Enable all 
       C                     Z-ADD1         CTL01            *Selected 
       C                     Z-ADD1         CTL02            *Selected 
       C                     Z-ADD2         CTL91            *Unavailable 
       C           CTL92     WHEQ 1                          *Reset all 
       C           MSEL      OREQ 0                          *No selections 
       C                     Z-ADD0         CTL01            *Available 
       C                     Z-ADD0         CTL02            *Available 
       C                     Z-ADD0         CTL91            *Available 
       C                     Z-ADD2         CTL92            *Unavailable 
       C                     ENDSL 
       C                     SETOF                     2223  *Do not display 
       C           CTL01     IFEQ 1                          *USER menu 
       C                     SETON                     22    *Display 
       C                     Z-ADD0         CTL92            *Enable Reset 
       C                     ENDIF 
       C           CTL02     IFEQ 1                          *OPTN menu 
       C                     SETON                     23    *Display 
       C                     Z-ADD0         CTL92            *Enable Reset 
       C                     ENDIF 
       C                     WRITEMENU                       *Update menu 
       C*  Process USER menu 
       C           MNUFLD    WHEQ 2                          *USER menu 
       C*  Process OPTN menu 
       C           MNUFLD    WHEQ 3                          *OPTN menu 
       C                     SELEC 
       C           OPTION    WHEQ 1                          *Selected Opt 1 
       C                     EXSR SETOPT 
       C                     ENDSL 
       C*  Process EXIT menu 
       C           EXITRF    WHEQ 99                         *EXIT menu 
       C                     MOVEL*ON       *INLR 
       C                     RETRN 
       C                     ENDSL 
       C                     ENDSR 
       C*  Process valid command keys 
       C           CMDKEY    BEGSR 
       C           *INKK     IFEQ *ON                        *CF11 
       C                     EXSR SETOPT 
       C                     ENDIF 
       C                     ENDSR 
       C*  Set options for USER and OPTN menu 
       C           SETOPT    BEGSR 
       C                     CLEAROPTNTX                     *OPTN text 
       C           *IN31     IFEQ *OFF                       *WRKACT disabld 
       C                     MOVEL*ON       *IN31            *Enable WRKACT 
       C                     MOVELDISTXT    OPTNTX           *Set text 
       C                     ELSE                            *WRKACT enabled 
       C                     MOVEL*OFF      *IN31            *Disable WRKACT 
       C                     MOVELENATXT    OPTNTX           *Set text 
       C                     ENDIF 
       C                     WRITEUSER                       *Update menu 
       C                     WRITEOPTN                       *Update menu 
       C                     ENDSR 
        *. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 


Support MC Press Online





  • Mobile Computing and the IBM i

    SB ASNA PPL 5450Mobile computing is rapidly maturing into a solid platform for delivering enterprise applications. Many IBM i shops today are realizing that integrating their IBM i with mobile applications is the fast path to improved business workflows, better customer relations, and more responsive business reporting.

    This ASNA whitepaper takes a look at mobile computing for the IBM i. It discusses the different ways mobile applications may be used within the enterprise and how ASNA products solve the challenges mobile presents. It also presents the case that you already have the mobile programming team your projects need: that team is your existing RPG development team!

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

    DDL SystemsDownload the technical whitepaper on MANAGING YOUR IBM i WIRELESSLY and (optionally) register to download an absolutely FREE software trail. This whitepaper provides an in-depth review of the native IBM i technology and ACO MONITOR's advanced two-way messaging features to remotely manage your IBM i while in or away from the office. Notify on-duty personnel of system events and remotely respond to complex problems (via your Smartphone) before they become critical-24/7. Problem solved!

    Order your copy here.

  • DR Strategy Guide from Maxava: Brand New Edition - now fully updated to include Cloud!


    Download your free copy of DR Strategy Guide for IBM i from Maxava today.


  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • 2020 IBM i Marketplace Survey Results


    This year marks the sixth edition of the popular IBM i Marketplace Survey Results. Each year, HelpSystems sets out to gather data about how businesses use the IBM i platform and the IT initiatives it supports. Year over year, the survey has begun to reveal long-term trends that give insight into the future of this trusted technology.

    More than 500 IBM i users from around the globe participated in this year’s survey, and we’re so happy to share the results with you. We hope you’ll find the information interesting and useful as you evaluate your own IT projects.

  • AIX Security Basics eCourse

    Core Security

    With so many organizations depending on AIX day to day, ensuring proper security and configuration is critical to ensure the safety of your environment. Don’t let common threats put your critical AIX servers at risk. Avoid simple mistakes and start to build a long-term plan with this AIX Security eCourse. Enroll today to get easy to follow instructions on topics like:

    • Removing extraneous files
    • Patching systems efficiently
    • Setting and validating permissions
    • Managing service considerations
    • Getting overall visibility into your networks


  • Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.

    Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    HelpSystemsIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    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:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • IBM i Resources Retiring?

    SB HelpSystems WC GenericLet’s face it: IBM i experts and RPG programmers are retiring from the workforce. Are you prepared to handle their departure?
    Our panel of IBM i experts—Chuck Losinski, Robin Tatam, Richard Schoen, and Tom Huntington—will outline strategies that allow your company to cope with IBM i skills depletion by adopting these strategies that allow you to get the job done without deep expertise on the OS:
    - Automate IBM i processes
    - Use managed services to help fill the gaps
    - Secure the system against data loss and viruses
    The strategies you discover in this webinar will help you ensure that your system of record—your IBM i—continues to deliver a powerful business advantage, even as staff retires.


  • Backup and Recovery Considerations for Security Data and Encrypted Backups

    SB PowerTech WC GenericSecurity expert Carol Woodbury is joined by Debbie Saugen. Debbie is an expert on IBM i backup and recovery, disaster recovery, and high availability, helping IBM i shops build and implement effective business continuity plans.
    In today’s business climate, business continuity is more important than ever. But 83 percent of organizations are not totally confident in their backup strategy.
    During this webinar, Carol and Debbie discuss the importance of a good backup plan, how to ensure you’re backing up your security information, and your options for encrypted back-ups.

  • Profound.js: The Agile Approach to Legacy Modernization

    SB Profound WC GenericIn this presentation, Alex Roytman and Liam Allan will unveil a completely new and unique way to modernize your legacy applications. Learn how Agile Modernization:
    - Uses the power of Node.js in place of costly system re-writes and migrations
    - Enables you to modernize legacy systems in an iterative, low-risk manner
    - Makes it easier to hire developers for your modernization efforts
    - Integrates with Profound UI (GUI modernization) for a seamless, end-to-end legacy modernization solution


  • Data Breaches: Is IBM i Really at Risk?

    SB PowerTech WC GenericIBM i is known for its security, but this OS could be more vulnerable than you think.
    Although Power Servers often live inside the safety of the perimeter firewall, the risk of suffering a data leak or data corruption remains high.
    Watch noted IBM i security expert Robin Tatam as he discusses common ways that this supposedly “secure” operating system may actually be vulnerable and who the culprits might be.

    Watch the webinar today!


  • Easy Mobile Development

    SB Profound WC GenericWatch this on-demand webinar and learn how to rapidly and easily deploy mobile apps to your organization – even when working with legacy RPG code! IBM Champion Scott Klement will demonstrate how to:
    - Develop RPG applications without mobile development experience
    - Deploy secure applications for any mobile device
    - Build one application for all platforms, including Apple and Android
    - Extend the life and reach of your IBM i (aka iSeries, AS400) platform
    You’ll see examples from customers who have used our products and services to deliver the mobile applications of their dreams, faster and easier than they ever thought possible!


  • Profound UI: Unlock True Modernization from your IBM i Enterprise

    SB Profound PPL 5491Modern, web-based applications can make your Enterprise more efficient, connected and engaged. This session will demonstrate how the Profound UI framework is the best and most native way to convert your existing RPG applications and develop new modern applications for your business. Additionally, you will learn how you can address modernization across your Enterprise, including databases and legacy source code, with Profound Logic.

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.

    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).

  • 5 New and Unique Ways to Use the IBM i Audit Journal

    SB HelpSystems ROBOT GenericYou must be asking yourself: am I doing everything I can to protect my organization’s data? Tune in as our panel of IBM i high availability experts discuss:

    - Why companies don’t test role swaps when they know they should
    - Whether high availability in the cloud makes sense for IBM i users
    - Why some organizations don’t have high availability yet
    - How to get high availability up and running at your organization
    - High availability considerations for today’s security concerns

  • Profound.js 2.0: Extend the Power of Node to your IBM i Applications

    SB Profound WC 5541In this Webinar, we'll demonstrate how Profound.js 2.0 enables you to easily adopt Node.js in your business, and to take advantage of the many benefits of Node, including access to a much larger pool of developers for IBM i and access to countless reusable open source code packages on npm (Node Package Manager).
    You will see how Profound.js 2.0 allows you to:

    • Provide RPG-like capabilities for server-side JavaScript.
    • Easily create web and mobile application interfaces for Node on IBM i.
    • Let existing RPG programs call Node.js modules directly, and vice versa.
    • Automatically generate code for Node.js.
    • Automatically converts existing RPGLE code into clean, simplified Node.js code.

    Download and watch today!


  • Make Modern Apps You'll Love with Profound UI & Profound.js

    SB Profound WC 5541Whether you have green screens or a drab GUI, your outdated apps can benefit from modern source code, modern GUIs, and modern tools.
    Profound Logic's Alex Roytman and Liam Allan are here to show you how Free-format RPG and Node.js make it possible to deliver applications your whole business will love:

    • Transform legacy RPG code to modern free-format RPG and Node.js
    • Deliver truly modern application interfaces with Profound UI
    • Extend your RPG applications to include Web Services and NPM packages with Node.js


  • Accelerating Programmer Productivity with Sequel


    Most business intelligence tools are just that: tools, a means to an end but not an accelerator. Yours could even be slowing you down. But what if your BI tool didn't just give you a platform for query-writing but also improved programmer productivity?
    Watch the recorded webinar to see how Sequel:

    • Makes creating complex results simple
    • Eliminates barriers to data sources
    • Increases flexibility with data usage and distribution

    Accelerated productivity makes everyone happy, from programmer to business user.

  • Business Intelligence is Changing: Make Your Game Plan

    SB_HelpSystems_WC_GenericIt’s time to develop a strategy that will help you meet your informational challenges head-on. Watch the webinar to learn how to set your IT department up for business intelligence success. You’ll learn how the right data access tool will help you:

    • Access IBM i data faster
    • Deliver useful information to executives and business users
    • Empower users with secure data access

    Ready to make your game plan and finally keep up with your data access requests?


  • Controlling Insider Threats on IBM i

    SB_HelpSystems_WC_GenericLet’s face facts: servers don’t hack other servers. Despite the avalanche of regulations, news headlines remain chock full of stories about data breaches, all initiated by insiders or intruders masquerading as insiders.
    User profiles are often duplicated or restored and are rarely reviewed for the appropriateness of their current configuration. This increases the risk of the profile being able to access data without the intended authority or having privileges that should be reserved for administrators.
    Watch security expert Robin Tatam as he discusses a new approach for onboarding new users on IBM i and best-practices techniques for managing and monitoring activities after they sign on.

  • Don't Just Settle for Query/400...

    SB_HelpSystems_WC_GenericWhile introducing Sequel Data Access, we’ll address common frustrations with Query/400, discuss major data access, distribution trends, and more advanced query tools. Plus, you’ll learn how a tool like Sequel lightens IT’s load by:

    - Accessing real-time data, so you can make real-time decisions
    - Providing run-time prompts, so users can help themselves
    - Delivering instant results in Microsoft Excel and PDF, without the wait
    - Automating the query process with on-demand data, dashboards, and scheduled jobs

  • How to Manage Documents the Easy Way

    SB_HelpSystems_WC_GenericWhat happens when your company depends on an outdated document management strategy?
    Everything is harder.
    You don’t need to stick with status quo anymore.
    Watch the webinar to learn how to put effective document management into practice and:

    • Capture documents faster, instead of wasting everyone’s time
    • Manage documents easily, so you can always find them
    • Distribute documents automatically, and move on to the next task


  • Lessons Learned from the AS/400 Breach

    SB_PowerTech_WC_GenericGet actionable info to avoid becoming the next cyberattack victim.
    In “Data breach digest—Scenarios from the field,” Verizon documented an AS/400 security breach. Whether you call it AS/400, iSeries, or IBM i, you now have proof that the system has been breached.
    Watch IBM i security expert Robin Tatam give an insightful discussion of the issues surrounding this specific scenario.
    Robin will also draw on his extensive cybersecurity experience to discuss policies, processes, and configuration details that you can implement to help reduce the risk of your system being the next victim of an attack.

  • Overwhelmed by Operating Systems?

    SB_HelpSystems_WC_GenericIn this 30-minute recorded webinar, our experts demonstrate how you can:

    • Manage multiple platforms from a central location
    • View monitoring results in a single pane of glass on your desktop or mobile device
    • Take advantage of best practice, plug-and-play monitoring templates
    • Create rules to automate daily checks across your entire infrastructure
    • Receive notification if something is wrong or about to go wrong

    This presentation includes a live demo of Network Server Suite.


  • Real-Time Disk Monitoring with Robot Monitor

    SB_HelpSystems_WC_GenericYou need to know when IBM i disk space starts to disappear and where it has gone before system performance and productivity start to suffer. Our experts will show you how Robot Monitor can help you pinpoint exactly when your auxiliary storage starts to disappear and why, so you can start taking a proactive approach to disk monitoring and analysis. You’ll also get insight into:

    • The main sources of disk consumption
    • How to monitor temporary storage and QTEMP objects in real time
    • How to monitor objects and libraries in real time and near-real time
    • How to track long-term disk trends



  • Stop Re-keying Data Between IBM I and Other Applications

    SB_HelpSystems_WC_GenericMany business still depend on RPG for their daily business processes and report generation.Wouldn’t it be nice if you could stop re-keying data between IBM i and other applications? Or if you could stop replicating data and start processing orders faster? Or what if you could automatically extract data from existing reports instead of re-keying? It’s all possible. Watch this webinar to learn about:

    • The data dilemma
    • 3 ways to stop re-keying data
    • Data automation in practice

    Plus, see how HelpSystems data automation software will help you stop re-keying data.


  • The Top Five RPG Open Access Myths....BUSTED!

    SB_Profound_WC_GenericWhen it comes to IBM Rational Open Access: RPG Edition, there are still many misconceptions - especially where application modernization is concerned!

    In this Webinar, we'll address some of the biggest myths about RPG Open Access, including:

    • Modernizing with RPG OA requires significant changes to the source code
    • The RPG language is outdated and impractical for modernizing applications
    • Modernizing with RPG OA is the equivalent to "screen scraping"


  • Time to Remove the Paper from Your Desk and Become More Efficient

    SB_HelpSystems_WC_GenericToo much paper is wasted. Attempts to locate documents in endless filing cabinets.And distributing documents is expensive and takes up far too much time.
    These are just three common reasons why it might be time for your company to implement a paperless document management system.
    Watch the webinar to learn more and discover how easy it can be to:

    • Capture
    • Manage
    • And distribute documents digitally


  • IBM i: It’s Not Just AS/400


    IBM’s Steve Will talks AS/400, POWER9, cognitive systems, and everything in between

    Are there still companies that use AS400? Of course!

    IBM i was built on the same foundation.
    Watch this recorded webinar with IBM i Chief Architect Steve Will and IBM Power Champion Tom Huntington to gain a unique perspective on the direction of this platform, including:

    • IBM i development strategies in progress at IBM
    • Ways that Watson will shake hands with IBM i
    • Key takeaways from the AS/400 days


  • Ask the RDi Experts

    SB_HelpSystems_WC_GenericWatch this recording where Jim Buck, Susan Gantner, and Charlie Guarino answered your questions, including:

    • What are the “hidden gems” in RDi that can make me more productive?
    • What makes RDi Debug better than the STRDBG green screen debugger?
    • How can RDi help me find out if I’ve tested all lines of a program?
    • What’s the best way to transition from PDM to RDi?
    • How do I convince my long-term developers to use RDi?

    This is a unique, online opportunity to hear how you can get more out of RDi.


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Inside the Integrated File System (IFS)

    SB_HelpSystems_WC_GenericDuring this webinar, you’ll learn basic tips, helpful tools, and integrated file system commands—including WRKLNK—for managing your IFS directories and Access Client Solutions (ACS). We’ll answer your most pressing IFS questions, including:

    • What is stored inside my IFS directories?
    • How do I monitor the IFS?
    • How do I replicate the IFS or back it up?
    • How do I secure the IFS?

    Understanding what the integrated file system is and how to work with it must be a critical part of your systems management plans for IBM i.


  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • How to Meet the Newest Encryption Requirements on IBM i

    SB PowerTech WC GenericA growing number of compliance mandates require sensitive data to be encrypted. But what kind of encryption solution will satisfy an auditor and how can you implement encryption on IBM i? Watch this on-demand webinar to find out how to meet today’s most common encryption requirements on IBM i. You’ll also learn:

    • Why disk encryption isn’t enough
    • What sets strong encryption apart from other solutions
    • Important considerations before implementing encryption



  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Fight Cyber Threats with IBM i Encryption

    SB PowerTech WC GenericCyber attacks often target mission-critical servers, and those attack strategies are constantly changing. To stay on top of these threats, your cybersecurity strategies must evolve, too. In this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access




  • 10 Practical IBM i Security Tips for Surviving Covid-19 and Working From Home

    SB PowerTech WC GenericNow that many organizations have moved to a work from home model, security concerns have risen.

    During this session Carol Woodbury will discuss the issues that the world is currently seeing such as increased malware attacks and then provide practical actions you can take to both monitor and protect your IBM i during this challenging time.


  • How to Transfer IBM i Data to Microsoft Excel

    SB_HelpSystems_WC_Generic3 easy ways to get IBM i data into Excel every time
    There’s an easy, more reliable way to import your IBM i data to Excel? It’s called Sequel. During this webinar, our data access experts demonstrate how you can simplify the process of getting data from multiple sources—including Db2 for i—into Excel. Watch to learn how to:

    • Download your IBM i data to Excel in a single step
    • Deliver data to business users in Excel via email or a scheduled job
    • Access IBM i data directly using the Excel add-in in Sequel

    Make 2020 the year you finally see your data clearly, quickly, and securely. Start by giving business users the ability to access crucial business data from IBM i the way they want it—in Microsoft Excel.



  • HA Alternatives: MIMIX Is Not Your Only Option on IBM i

    SB_HelpSystems_WC_GenericIn this recorded webinar, our experts introduce you to the new HA transition technology available with our Robot HA software. You’ll learn how to:

    • Transition your rules from MIMIX (if you’re happy with them)
    • Simplify your day-to-day activities around high availability
    • Gain back time in your work week
    • Make your CEO happy about reducing IT costs

    Don’t stick with a legacy high availability solution that makes you uncomfortable when transitioning to something better can be simple, safe, and cost-effective.



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    SB HelpSystems SC 5413Robot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    SB HelpSystems SC 5413Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.

  • ACO MONITOR Manages your IBM i 24/7 and Notifies You When Your IBM i Needs Assistance!

    SB DDL Systems 5429More than a paging system - ACO MONITOR is a complete systems management solution for your Power Systems running IBM i. ACO MONITOR manages your Power System 24/7, uses advanced technology (like two-way messaging) to notify on-duty support personnel, and responds to complex problems before they reach critical status.

    ACO MONITOR is proven technology and is capable of processing thousands of mission-critical events daily. The software is pre-configured, easy to install, scalable, and greatly improves data center efficiency.