Sidebar

AS/400 Subfile Programming Part II: Basic Coding

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

Part 1: Subfile Foundations: (July 1992) Complete understanding of any subject begins with a starting point to build upon. Laying the foundation for subfile usage requires familiarization with underlying concepts and basic definitions. As a prelude to the specific code used to implement a subfile, this article lays out a basic understanding of what a subfile is, how one is implemented and why subfiles exist in the first place.

Part 2: Basic Subfile Coding: (August 1992) We begin examining the coding of the display file and HLL program along with the logic and structure of typical subfile programs. The article uses an example of a subfile with "Position to" capability and presents the techniques and logic changes required to code a Modified Load-All, Expanding or Page-at-a-Time subfile.

Part 3: Increased Functionality: (Sept. 1992) In this article, you learn to hone your coding skills for effective use of subfiles. The specific subfile techniques and keywords discussed will allow you to put expanded control and capability into the subfiles introduced in the previous article. Additionally, the article examines the difference between input and output subfiles and the special logic requirements for coding them.

Part 4: Fine-Tuning Your Subfiles: (Oct. 1992) You'll learn to customize subfiles for peak performance. This article examines the coding required to write effective subfiles and present them on-screen without clearing the lines behind the subfile. It further discusses cursor control, determination of cursor position and the coding of a point-and-shoot type of interface to AS/400 programs.

Variations on a roll (isn't that a pita!)

As discussed in July's "Subfile Foundations," subfiles enable programmers to present a panel of columnar data with minimal programming. They take advantage of special capabilities built into display file definitions and extensions to the HLLs supported by OS/400. The net result is that subfiles make presenting columns of information easier with their own syntax and structure that you must understand to use subfiles effectively. This article focuses on the typical logic flow of a subfile program, along with the coding of both the display file and the RPG/400 program to control it.

The goal for this article is to write a typical application which displays a list of customers on the screen in alphabetical sequence as illustrated in 1. The user can enter the name, or partial name, of a customer he is searching for; the program loads one or more screens of customers and the user locates the customer he needs. The user can then branch to an inquiry program for customer details by selecting a customer from the list.

The goal for this article is to write a typical application which displays a list of customers on the screen in alphabetical sequence as illustrated in Figure 1. The user can enter the name, or partial name, of a customer he is searching for; the program loads one or more screens of customers and the user locates the customer he needs. The user can then branch to an inquiry program for customer details by selecting a customer from the list.

Last month, we covered three methods for processing subfiles: load-all, expanding, and page-at-a-time. The first program executed in this article uses the load-all method. Modifications to the program are also presented to demonstrate the other two methods.

In order to code this application, we must:

1. Create a display file that has the subfile DDS built into it.

2. Determine the logic flow of the program to control the screen.

3. Code the HLL program to implement the logic.

Screen Definition

For clear and easy definition, we break the screen into three record formats. The first format (named HEADER) includes the title, date and time, the selection fields and the headings for the subfile. This format also works as the subfile control format which contains the keywords that control the subfile. The second format is the subfile format itself (named DETAIL) which describes the information about each customer to list in the subfile. The third format, TRAILER, displays output constants that describe the available function keys. Since there are no overlay or windowing keywords on the TRAILER format, it will clear the screen whenever it is written.

The header format has an OVERLAY keyword associated with it (and the related subfile) so that it can coexist with the TRAILER, rather than clearing the screen whenever it is written. The display file (2) is defined either by directly coding the DDS with SEU or by using SDA to select the required keywords and visually lay out each format. The order in which the record formats are specified in the DDS source member is important. The display file compiler expects to process the subfile record format prior to the control record format that controls it. If we use SDA when defining a subfile, it prompts for the control format name and places the records in the right order in the DDS source.

The header format has an OVERLAY keyword associated with it (and the related subfile) so that it can coexist with the TRAILER, rather than clearing the screen whenever it is written. The display file (Figure 2) is defined either by directly coding the DDS with SEU or by using SDA to select the required keywords and visually lay out each format. The order in which the record formats are specified in the DDS source member is important. The display file compiler expects to process the subfile record format prior to the control record format that controls it. If we use SDA when defining a subfile, it prompts for the control format name and places the records in the right order in the DDS source.

The DETAIL record has the SFL keyword identifying it as a subfile, and the HEADER record has the SFLCTL keyword which identifies the DETAIL format as the subfile it controls. All user interaction (data entry, function keys, selections and so forth) is performed through the HEADER format. The HEADER format accepts the customer name the user keys to position the subfile, while the DETAIL format is used to load up the records and to read back records the user has selected. The point to remember is that the subfile control record and the subfile record both pass data back to the program when the control record is read.

The HEADER record contains what we will call the Basic Six subfile keywords:

SFLSIZ (subfile size): The initial size of the subfile when the display file is opened.

SFLPAG (subfile page): The number of records that should appear on the screen at a time.

SFLDSP (subfile display): Controls the display of the subfile information.

SFLDSPCTL (subfile display control): Controls the display of the control format.

SFLCLR (subfile clear): Controls clearing the records currently in the subfile.

SFLEND (subfile end): Controls the "+" (or More...) indicating more records exist.

In our sample, the first two keywords define the subfile with five pages of 10 records per page. The last four keywords have conditioning indicators associated with them. Through deft manipulation of these indicators in our HLL program, we control which of these DDS keywords is active. In so doing, we control whether a write to our control record (HEADER) will:

1. Display the header format only. We accomplish this by turning on the indicator that conditions the SFL-DSPCTL keyword, and turning off the indicator that conditions the SFLDSP keyword.

2. Display the header along with the contents of the subfile. To do this, we turn on the indicators that condition SFLDSP and SFLDSPCTL.

3. Purge the contents of the subfile. This is carried out by turning on the indicator that conditions the SFLCLR keyword.

4. Indicate that the display file should control the last page indicator based upon what is currently loaded into the subfile.

In our example, we have chosen four consecutive indicators for these switches. To quote the knight in Indiana Jones' The Last Crusade, we have chosen wisely-by making them consecutive, we can set all the indicators with a single MOVE operation.

The balance of the DDS source should not hold any mysteries. We have a series of output constants and referenced database fields, your standard collection of command keys, PRINT, BLINK, and other straightforward source code elements. The screen field names (with the exception of the @NAME field) are straight references to the database file, eliminating the need for move operations in our code.

Subfile Program Logic

In Lewis Carroll's Alice in Wonderland, upon first meeting the Cheshire Cat, Alice asks, "Cheshire Cat, can you tell me which way to go?" "Where are you going?" the cat replies. Alice says, "I really don't know." The cat answers, "Then it really doesn't matter which way you go." The same thing applies to programming. If you don't know where you are going in the first place, it doesn't matter where you begin (and your code reflects that when you are done).

Every subfile program has a certain number of standard sections. Before we start coding anything, let's make sure we understand the steps to be performed. Applying the structured concepts of sequence-condition-iteration, we can design the structure and flow before we code it. For our first program, we shall assume a load-all form of subfile, i.e., that we intend to load all the eligible records into the subfile at once and only reload if the search name changes. Load-all does not necessarily mean that we will load the entire file into the subfile. We will load a number of pages when we perform the load routine and let the user scroll through that fixed set of pages. If he wants to go beyond that range, he must provide a new starting name to reposition the search, and the program then reloads the subfile. For this program to function, the following things must happen (order of function execution is not a concern at this point):

Display a list of hits back to the user.

Display detail for any records the user selects.

Load the records from the database into the subfile.

Position our file based on the name the user is requesting.

Ask the user for a name to start.

Clear the current set of records from the subfile.

If we can assume that this is a reasonable statement of the processes that must occur, let's determine the logic of the program.

Sequence

First, we organize the steps into a reasonable order. The reasonable order varies significantly from one programmer to the next and is largely determined by the programmer's age, sex, socio-economic background, sexual preference, biorhythm schedule, horoscope and, of course, number of cups of coffee consumed. We will choose the following as our reasonable order:

1. Request the name to start with.

2. Clear the subfile.

3. Position the database file based upon the search name.

4. Load the records into the subfile.

5. Display the header/detail to the user.

6. Process any selections.

Iteration or Looping

Once we have determined the sequence of the steps, we need to decide which ones should happen repetitively. The way we want this hummer to work is to display the HEADER first time through, get the name to start with, and then keep displaying the header and detail to the user until he walks away from his terminal and the job times out, turns off the tube and goes home, or presses F3 or F12. This program is harmless enough that we don't need to worry about the first two, but we should code the function keys to exit. So let's introduce some iteration.

Request the name to start with

Until F3 or F12 is pressed

Clear the subfile

Position the file based upon the search name

Load the records into the subfile

Display the header/detail to the user

Process any selections

Conditional Processing

Next, we examine the structure we have and decide which things have to happen all the time and which should be done only under certain conditions. If F3 is pressed on the very first screen, we really don't want to do anything else. We only want to clear, position and load if the starting name changed. We want to process selections only if there were detail records shown in the first place (the search could have yielded no results). So we might wind up with program logic something like this:

Request the name to start with

While F3 and F12 are not pressed

If the search name changed

Clear the subfile.

Position the file based upon the search name

Load the records into the subfile

Display the header/detail to the user

If detail records were displayed

Process any selections

HLL Program Code

Now we can translate this program logic to HLL code and write the program (see 5, page 34). We are using RPG/400 to code the examples in this article, although we could just as easily choose COBOL or PL/I or C/400 (well, some of us might just as easily write in these languages). We must first identify to the RPG program the fact that there is a subfile in this display file. This is done in the file specifications with a file (K)ontinuation line. This line identifies a subfile record format and associates an internal RPG variable to act as its relative record number pointer. Once this is established, we can write to any record within the subfile by loading the record number into the pointer (RRN in our example) and writing to the subfile. Remember, subfiles work like direct files-we access a particular subfile record via its relative position in the subfile.

Now we can translate this program logic to HLL code and write the program (see Figure 5, page 34). We are using RPG/400 to code the examples in this article, although we could just as easily choose COBOL or PL/I or C/400 (well, some of us might just as easily write in these languages). We must first identify to the RPG program the fact that there is a subfile in this display file. This is done in the file specifications with a file (K)ontinuation line. This line identifies a subfile record format and associates an internal RPG variable to act as its relative record number pointer. Once this is established, we can write to any record within the subfile by loading the record number into the pointer (RRN in our example) and writing to the subfile. Remember, subfiles work like direct files-we access a particular subfile record via its relative position in the subfile.

We now get into the working portion of the code-the Calculation specifications. The mainline of the program is written to follow the logic we determined in the previous section. As you can see, the structure chart maps almost line-for-line to the mainline. We could write this program entirely in- line, but the subroutines allow us to focus on each section of code a bit more easily.

The first step, according to our logic model, is to get the initial name to start the search. This is accomplished in the *INZSR subroutine (*INZSR runs automatically at program initialization so we do not have to call it with EXSR) by setting our four switches (indicators 31-34) to show just the HEADER format to the user and inviting his response. Indicator 32 controls when to show the subfile control format which, in our case, is the HEADER. By setting it on and the other indicators off, only HEADER is shown when we EXFMT the HEADER.

The next process (subroutine CLEAR) clears the subfile contents. This is done by setting our four switches. We set the clear indicator on and set off the indicators for both the subfile and the subfile control format. Next, we write the HEADER format and initialize the RRN field. As a general practice, we should also reset the controlling switches to turn off the clear switch and set the control format display switch on after writing the format.

In subroutine POSIT, we take the customer name entered by the user and position the file to the first record in the file that matches or comes closest to the selection using SETLL.

The LOAD subroutine then reads records from the CUSTMST file and loads them into the subfile. The RRN variable is incremented before each write, which places the data from the database into successive records of the subfile. Loading ends when either the end of the database file is reached, or the subfile size is reached. Indicator 34 will turn on if the database file reaches EOF controlling the + (or More...) at the bottom of the screen. Specifying indicator 95 in columns 58-59 of the WRITE statement to the subfile is a special use of the WRITE operation code for subfile record formats. This technique allows us to put a scrollable window over even a very large file with minimal coding. The user will be able to scroll only through the number of pages that we load.

Once we have loaded the subfile, we want to display it to the user (subroutine DISPLY). This is done by setting the four conditioning indicators and running an EXFMT operation of the control record HEADER. If, after coming out of the load routine, our RRN field is still zero, we know that there were no records loaded into the subfile and therefore we should not try to display it. (If you do try to display an empty subfile, the world ends as we know it, and so does your program!) We have chosen to redisplay the HEADER to get a new name if no records were found, and not bother with a "No records found" message.

When the user presses the Enter key, the program runs the PROCES subroutine. This routine searches the subfile for records that the user has selected using the READC operation code. READC functions just like any other READ operation- the indicator in columns 58-59 comes on only when no record is read. For each subfile record in which the user entered an option of 5, we call a subprogram to handle the inquiry display. After processing the selections, the program blanks the SELECT field and posts it back to the subfile, since we only reload when a new name is entered.

From this example, you begin to get a feel for the basic routines needed in a typical subfile program. This load-all style can be quite appropriate for a production environment, depending on the application. It does have some drawbacks, however, in that we set aside space in the PAG for the entire size of the subfile and load the entire size, even if we don't normally use all the records.

Expanding Subfile

Let's take a look at the changes that would be involved if instead we wrote an expanding subfile. The expanding version of this subfile will lessen our PAG space at the expense of a possible performance overhead. If the user requests more records than we have allocated for the subfile size, the subfile will expand dynamically. Naturally, this creates a performance hit just like any noncontiguous file.

Our program performs the same basic routines; but because we're now operating in an expanding subfile context, we should add a ROLLUP (PAGEDOWN) key to the display file and change some of the conditions when certain things are done.

First, the differences in the screen. 3 (page 32) shows the changes necessary to make the DDS in 2 work as an expanding subfile-replace the entire highlighted section. The only statements that actually change are the two new statements highlighted in 3. We are adding a ROLLUP keyword to the display file on the HEADER record. The keyword is conditioned on indicator 34, the same indicator that controls the subfile end keyword. If indicator 34 is on, it means the last pass of the load routine has read to the end of the file, so it does not make sense to allow the user to attempt to roll again.

First, the differences in the screen. Figure 3 (page 32) shows the changes necessary to make the DDS in Figure 2 work as an expanding subfile-replace the entire highlighted section. The only statements that actually change are the two new statements highlighted in Figure 3. We are adding a ROLLUP keyword to the display file on the HEADER record. The keyword is conditioned on indicator 34, the same indicator that controls the subfile end keyword. If indicator 34 is on, it means the last pass of the load routine has read to the end of the file, so it does not make sense to allow the user to attempt to roll again.

The SFLRCDNBR keyword provides control over which page of the subfile is displayed when the subfile is presented. It uses a hidden field associated with this keyword to set the subfile record number. This contains the number of a record whose page you want presented-i.e., if the page size is 10, any value between 1 and 10 would show page one, 11-20 would show page two, and so on. We did not require this keyword on the first program since we always loaded the whole enchilada up front and always started from page one. I have chosen to use the RRN field to control the page displayed. This ensures that the page last loaded (or processed) is redisplayed.

The RPG program requires only a little modification as well. Add the lines of code in 6a to the mainline, replacing the highlighted EXSR DISPLY statement to execute the load routine if the ROLLUP indicator is on. There are a few ways this can be done, but this particular method is clear and easy to follow. The rest of the changes take place in the LOAD routine. Replace the entire LOAD subroutine with the code in 6b. The loop is modified to do just one page worth rather than continuing until the subfile is full.

The RPG program requires only a little modification as well. Add the lines of code in Figure 6a to the mainline, replacing the highlighted EXSR DISPLY statement to execute the load routine if the ROLLUP indicator is on. There are a few ways this can be done, but this particular method is clear and easy to follow. The rest of the changes take place in the LOAD routine. Replace the entire LOAD subroutine with the code in Figure 6b. The loop is modified to do just one page worth rather than continuing until the subfile is full.

Remember that the subfile automatically expands as long as you define the subfile size as larger than the subfile page. The subfile as it exists after the statements were added from 6a contains no code to limit the number of pages a user can load. Without some exception code to put a "reasonable" cap on this, the user could load 100 pages before the program bombs when it exceeds the maximum number of records allowed (subfiles can never have more than 9999 records).

Remember that the subfile automatically expands as long as you define the subfile size as larger than the subfile page. The subfile as it exists after the statements were added from Figure 6a contains no code to limit the number of pages a user can load. Without some exception code to put a "reasonable" cap on this, the user could load 100 pages before the program bombs when it exceeds the maximum number of records allowed (subfiles can never have more than 9999 records).

Page-at-a-Time

The last example is a page-at-a-time subfile. It stores only the records currently shown on the screen in the subfile. Both the ROLLUP and ROLLDOWN keywords are coded in the display file's DDS, and the subfile contents are cleared each time one of these keys is pressed.

We must modify the screen to make the subfile page equal to the subfile size by replacing the highlighted section of 2 with the code in 4 (page 32). This adds a ROLLDOWN key to the HEADER record. At this point, we want to code a conditioning indicator so that the ROLLDOWN is processed only when it is appropriate (i.e., there are records available to be shown). We also want to remove the SFLRCDNBR we added for the expanding subfile example, since a page-at-a-time subfile by definition loads only one page.

We must modify the screen to make the subfile page equal to the subfile size by replacing the highlighted section of Figure 2 with the code in Figure 4 (page 32). This adds a ROLLDOWN key to the HEADER record. At this point, we want to code a conditioning indicator so that the ROLLDOWN is processed only when it is appropriate (i.e., there are records available to be shown). We also want to remove the SFLRCDNBR we added for the expanding subfile example, since a page-at-a-time subfile by definition loads only one page.

The program logic needs to be modified so that we clear the subfile on each roll key and the logic to handle the ROLLDOWN key is added. To accomplish this, insert the code shown in 7a into the mainline routine shown in 5, replacing the highlighted EXSR DISPLY statement. The basic program logic remains the same.

The program logic needs to be modified so that we clear the subfile on each roll key and the logic to handle the ROLLDOWN key is added. To accomplish this, insert the code shown in Figure 7a into the mainline routine shown in Figure 5, replacing the highlighted EXSR DISPLY statement. The basic program logic remains the same.

The largest change is the introduction of a ROLLBACK routine, which can be achieved through a number of varying techniques and styles. We could read back two pages worth and then run the regular load routine; or read back to the top of the page and then load the last page in reverse; or keep track of the top of each page and use that to go to prior pages. There is no perfect ROLLBACK routine! Different techniques work better in different situations-are the search keys unique? Is the data dynamic? Is performance the most critical factor? For simplicity, we are holding the first key on each page in an array and using that for navigation. Insert the statement in 7b after the F- specs.

The largest change is the introduction of a ROLLBACK routine, which can be achieved through a number of varying techniques and styles. We could read back two pages worth and then run the regular load routine; or read back to the top of the page and then load the last page in reverse; or keep track of the top of each page and use that to go to prior pages. There is no perfect ROLLBACK routine! Different techniques work better in different situations-are the search keys unique? Is the data dynamic? Is performance the most critical factor? For simplicity, we are holding the first key on each page in an array and using that for navigation. Insert the statement in Figure 7b after the F- specs.

The load routine is modified to increment the TOPS array index "T" each pass. This index gets initialized each time we reposition the search. Within the load loop, we capture the key of the first record on the page, as shown in 7c. Replace the entire LOAD subroutine with the code in 7c.

The load routine is modified to increment the TOPS array index "T" each pass. This index gets initialized each time we reposition the search. Within the load loop, we capture the key of the first record on the page, as shown in Figure 7c. Replace the entire LOAD subroutine with the code in Figure 7c.

The ROLLBACK routine BACKUP (7d) uses the keys stored in the array TOPS to reposition to the top of the last page. The load routine is then called to refill the subfile. This technique limits the ROLLBACK so that it does not go beyond the first page of the search. This is handled by controlling when the ROLLDOWN key can be pressed. Add the BACKUP subroutine in 7d to the end of program.

The ROLLBACK routine BACKUP (Figure 7d) uses the keys stored in the array TOPS to reposition to the top of the last page. The load routine is then called to refill the subfile. This technique limits the ROLLBACK so that it does not go beyond the first page of the search. This is handled by controlling when the ROLLDOWN key can be pressed. Add the BACKUP subroutine in Figure 7d to the end of program.

Add Method to Your Madness

The HLL program logic really changes very little from one method of subfile processing to the next. The amount of time you want to put into the code should vary based upon the importance of a particular program to the application. Each of these subfile techniques has its merits, and each can be implemented from one basic shell. The key is not to get into a rut of coding all subfiles one way. Match the method to the application.

Our next article examines more of the subtleties of subfile processing, as well as some of the more exotic keywords and techniques. Until then, enjoy!


AS/400 Subfile Programming Part II: Basic Coding

Figure 1 Screen for sample application

 
  Figure 1:  Screen for Sample Application 
 
                           Work With Customers                   Date   6/16/92 
                                                                 Time  21:42:26 
     Position to name... A 
 
    Type options, press Enter. 
 
      5=Display 
 
      Opt  Customer    Customer                            Credit 
              No.      Name                                 Limit 
       _      150      Alliance Gas Co.                     60000.00 
       _      950      Anaconda Supplies Inc.              300000.00 
       _      550      Autocut Distributors Inc.            54000.00 
       _      900      Boxcar Supplies Inc.                300000.00 
       _      500      Distrends Inc.                       54000.00 
       _      100      Duplo Products Inc.                  60000.00 
       _      200      Dynopipe Inc.                        50000.00 
       _      250      Ever Ready Pipes Inc.                50000.00 
       _      300      Fabricators Unlimited Inc.           75000.00 
       _     1000      Integrated Dynamics Inc.            275000.00      + 
 
      F3=Exit   F12=Cancel 

AS/400 Subfile Programming Part II: Basic Coding

Figure 2 Display file XRD002DF

 
       A                                      DSPSIZ(24 80 *DS3) 
       A                                      REF(CUSTMST) 
       A                                      PRINT 
       A                                      CA03(03) 
       A                                      CA12(12) 
       A          R DETAIL                    SFL 
       A            SELECT         1A  I 12  6 
       A            CSNUM     R        O 12 11 
       A            CSNAME    R        O 12 23 
       A            CSCRLT    R        O 12 56EDTCDE(1) 
       A          R HEADER                    SFLCTL(DETAIL) 
       A                                      OVERLAY 
       A                                      SFLSIZ(0050) 
       A                                      SFLPAG(0010) 
       A  31                                  SFLDSP 
       A  32                                  SFLDSPCTL 
       A  33                                  SFLCLR 
       A  34                                  SFLEND 
       A                                  1 31'Work with Customers' 
       A                                      DSPATR(HI) 
       A                                  1 68'Date' 
       A                                  1 73DATE EDTCDE(Y) 
       A                                  2 68'Time' 
       A                                  2 73TIME 
       A                                  4  2'Position to name:' 
       A            @CNAME    R        B  4 21REFFLD(CSNAME CUSTMST) 
       A                                  6  2'Type options, press Enter' 
       A                                      COLOR(BLU) 
       A                                  7  5'5=Display' COLOR(BLU) 
       A                                 10 10'Customer' DSPATR(HI) 
       A                                 10 23'Customer' DSPATR(HI) 
       A                                 10 59'Credit' DSPATR(HI) 
       A                                 11  5'Opt' DSPATR(HI) 
       A                                 11 12'No.' DSPATR(HI) 
       A                                 11 23'Name' DSPATR(HI) 
       A                                 11 60'Limit' DSPATR(HI) 
       A          R TRAILER 
       A                                 23  2'F3=Exit   F12=Cancel' 
       A                                      COLOR(BLU) 

AS/400 Subfile Programming Part II: Basic Coding

Figure 3 DDS modication for expanding subfile

 
       A          R HEADER                    SFLCTL(DETAIL) 
       A                                      OVERLAY 
       A N34                                  ROLLUP(25) 
       A                                      SFLSIZ(0050) 
       A                                      SFLPAG(0010) 
       A  31                                  SFLDSP 
       A  32                                  SFLDSPCTL 
       A  33                                  SFLCLR 
       A  34                                  SFLEND 
       A            RRN            3  0H      SFLRCDNBR 

AS/400 Subfile Programming Part II: Basic Coding

Figure 4 DDS modificaiton for page-at-a-time subfile

 
       A          R HEADER                    SFLCTL(DETAIL) 
       A                                      OVERLAY 
       A                                      SFLSIZ(0010) 
       A                                      SFLPAG(0010) 
       A N34                                  ROLLUP(25) 
       A N35                                  ROLLDOWN(26) 
       A  31                                  SFLDSP 
       A  32                                  SFLDSPCTL 
       A  33                                  SFLCLR 
       A  34                                  SFLEND 

AS/400 Subfile Programming Part II: Basic Coding

Figure 5 RPG program code

 
        * Indicator usage:  03 - F3 response indicator 
        *                   12 - F12 response indicator 
        *                   31 - Display subfile contents 
        *                   32 - Display subfile control record 
        *                   33 - Clear the subfile 
        *                   34 - Control display of "+" 
        * 
        **************************************************************** 
       FCUSTMST IF  E           K        DISK 
       FXRD002DFCF  E                    WORKSTN 
       F                                        RRN   KSFILE DETAIL 
        * 
        * This is a no-cycle program 
       C                     MOVE *ON       *INLR 
        * 
        * Mainline:  Do until user presses F3 or F12 
       C           *IN03     DOWEQ*OFF 
       C           *IN12     ANDEQ*OFF 
        * 
        * Only reload if the search name changes 
       C           HLDNAM    IFNE @CNAME 
       C                     EXSR CLEAR 
       C                     EXSR POSIT 
       C                     EXSR LOAD 
       C                     MOVEL@CNAME    HLDNAM 
       C                     ENDIF 
        * 
       C                     EXSR DISPLY 
        * 
        * Process the selections if the user is still game 
       C           *IN03     IFEQ *OFF 
       C           *IN12     ANDEQ*OFF 
       C           RRN       ANDNE*ZERO 
       C                     EXSR PROCES 
       C                     ENDIF 
       C                     ENDDO 
        **************************************************************** 
        * Subroutine name:  *INZSR 
        ** Purpose:  First pass logic 
        **************************************************************** 
       C           *INZSR    BEGSR 
        * Set up a hold name and initialize it to all 9's 
       C           *LIKE     DEFN CSNAME    HLDNAM 
       C                     MOVE *ALL'9'   HLDNAM 
        * 
        * Get the starting name 
       C                     MOVEA'0100'    *IN,31 
       C                     WRITETRAILER 
       C                     EXFMTHEADER 
       C                     ENDSR 
        **************************************************************** 
        * Subroutine name:  CLEAR 
        * Purpose:  Clear the subfile and RRN 
        **************************************************************** 
       C           CLEAR     BEGSR 
       C                     MOVEA'001'     *IN,31 
       C                     WRITEHEADER 
       C                     Z-ADD*ZERO     RRN     30 
       C                     WRITETRAILER 
        * 
        * Reset for the next process 
       C                     MOVEA'010'     *IN,31 
       C                     ENDSR 
        **************************************************************** 
        * Subroutine name:  POSIT 
        * Purpose:  Position the file based upon the name 
        **************************************************************** 
       C           POSIT     BEGSR 
       C           @CNAME    SETLLCUSTMST 
       C                     ENDSR 
        **************************************************************** 
        * Subroutine name:  LOAD 
        * Purpose:  Load the subfile 
        **************************************************************** 
       C           LOAD      BEGSR 
       C           *IN34     DOUEQ*ON 
       C           *IN95     OREQ *ON 
       C                     READ CUSTREC                  34 
       C           *IN34     IFEQ *OFF 
       C                     ADD  1         RRN 
       C                     WRITEDETAIL 
       C                     ENDIF 
       C                     ENDDO 
       C                     ENDSR 
        **************************************************************** 
        * Subroutine name:  DISPLY 
        * Purpose:  Display the HEADER/DETAIL 
        **************************************************************** 
       C           DISPLY    BEGSR 
        * 
        * Set the subfile display indicator if records are loaded 
       C           RRN       IFNE *ZERO 
       C                     MOVE *ON       *IN31 
       C                     ENDIF 
       C                     EXFMTHEADER 
       C                     ENDSR 
        **************************************************************** 
        * Subroutine name:  PROCES 
        * Purpose:  Process the user's selections 
        **************************************************************** 
       C           PROCES    BEGSR 
        * 
        * Locate all the selected records 
       C           *IN95     DOUEQ*ON 
       C                     READCDETAIL                   95 
       C           *IN95     IFEQ *OFF 
        * 
       C           SELECT    IFEQ '5' 
       C                     CALL 'CUSTDSP' 
       C                     PARM           CSNUM 
       C                     ENDIF 
        * 
        * Insure the SELECT field is reset 
       C                     CLEARSELECT 
       C                     UPDATDETAIL 
       C                     ENDIF 
       C                     ENDDO 
       C                     ENDSR 

AS/400 Subfile Programming Part II: Basic Coding

Figure 6A Mainline modificaiton for expanding subfile

 
       C                     EXSR DISPLY 
       C           *IN25     IFEQ *ON 
       C                     EXSR LOAD 
       C                     ENDIF 

AS/400 Subfile Programming Part II: Basic Coding

Figure 6B LOAD subroutine for expanding subfile

 
       C           LOAD      BEGSR 
       C           1         DO   10        X       30 
       C                     READ CUSTREC                  34 
        * 
       C           *IN34     IFEQ *ON 
       C                     LEAVE 
       C                     ENDIF 
        * 
       C                     ADD  1         RRN 
       C                     WRITEDETAIL 
       C                     ENDDO 
       C                     ENDSR 

AS/400 Subfile Programming Part II: Basic Coding

Figure 7A Mainline modification for page-at-a-time subfile

 
       C                     EXSR DISPLY 
        * Reposition to the prior page - ROLLDOWN key 
       C           *IN26     IFEQ *ON 
       C                     EXSR CLEAR 
       C                     EXSR BACKUP 
       C                     EXSR LOAD 
       C                     ENDIF 
        * Load another page on a ROLLUP key 
       C           *IN25     IFEQ *ON 
       C                     EXSR CLEAR 
       C                     EXSR LOAD 
       C                     MOVE *OFF      *IN35 
       C                     ENDIF 

AS/400 Subfile Programming Part II: Basic Coding

Figure 7B E-spec for page-at-a-time subfile

 
       E                    TOPS      100 30 

AS/400 Subfile Programming Part II: Basic Coding

Figure 7C LOAD subroutine for page-at-a-time subfile

 
       C           LOAD      BEGSR 
       C                     ADD  1         T       30 
        * 
       C           1         DO   10        X       30 
       C                     READ CUSTREC                  34 
        * 
       C           *IN34     IFEQ *ON 
       C                     LEAVE 
       C                     ENDIF 
        * 
       C           X         IFEQ 1 
       C                     MOVELCSNAME    TOPS,T 
       C                     ENDIF 
        * 
       C                     ADD  1         RRN 
       C                     WRITEDETAIL 
       C                     ENDDO 
       C                     ENDSR 

AS/400 Subfile Programming Part II: Basic Coding

Figure 7D Rollback subroutine for page-at-a-time subfile

 
       C           BACKUP    BEGSR 
        * Backup to the first record on the prior page 
       C           T         IFGE 2 
       C                     SUB  1         T 
       C           TOPS,T    SETLLCUSTNAME 
       C                     SUB  1         T 
       C                     ENDIF 
        * Set the ROLLBACK control indicator 
       C           T         IFEQ *ZERO 
       C                     MOVE *ON       *IN35 
       C                     ELSE 
       C                     MOVE *OFF      *IN35 
       C                     ENDIF 
       C                     ENDSR 
BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • 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!

    SB Maxava PPL 5476PRACTICAL TOOLS TO IMPLEMENT DISASTER RECOVERY IN YOUR IBM i ENVIRONMENT

    CLOUD VS. ON-PREMISE?
    - COMPREHENSIVE CHECKLISTS
    - RISK COST CALCULATIONS
    - BUSINESS CASE FRAMEWORK
    - DR SOLUTIONS OVERVIEW
    - RFP BUILDER
    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

    HelpSystems

    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

    SB_HelpSystems_WC_Generic

    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

    SB_HelpSystems_WC_Generic

    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 NodeRun.com 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.

     

     

  • 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.