Sidebar

The API Corner: So Just What Changed in This Record?

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

 

Learn about flexibly tracking field changes.

 

On the IT Knowledge Exchange, Luissimon recently posted, "I need to get which field changed in a file, instead of writing multiple (IF this field changed THEN DO…) for each field in each file. I was wondering if I could use some tool in RPG for doing that?" While I can't say that I'm familiar with an RPG built-in to accomplish this, I can see how using a few system APIs within an RPG application program can meet this need.

In this column, we'll look at how we can register a trigger program to be called whenever an update operation is performed on a file and how that trigger program can then determine, using the List Fields (QUSLFLD) API, which fields have been changedand without the program having to know in advance what file or fields are being tracked.

Now before we start, I do want to point out one major item. This article shows how to provide this auditing function using one program. I'm using one program solely for the purpose of being able to demonstrate everything in one article. In a production environment, I would never use this implementation, though I would use the database triggers and system APIs being discussed in this article. Rather than one large program, I would use three distinct programs. After we've looked at the sample program, I'll overview how I would implement the various functions of the program in three different programs.

Here is the source for our example program AUDDTACHG (Audit Data Change).

h dftactgrp(*no)                                                    
                                                                    
d AudDtaChg       pr                                                
d  TrgBfr                             likeds(QDBTB)                 
d  LenTrgBfr                    10i 0 const                         
                                                                    
d AudDtaChg       pi                                                
d  TrgBfr                             likeds(QDBTB)                 
d  LenTrgBfr                    10i 0 const                         
                                                                    
 ****************************************************************   
                                                                    
d CrtUsrSpc       pr                  extpgm('QUSCRTUS')            
d  QualUsrSpcN                  20a   const                         
d  XAttr                        10a   const                         
d  IntSize                      10i 0 const                         
d  IntValue                      1a   const                         
d  PubAut                       10a   const                         
d  TxtDesc                      50a   const                         
d  ReplaceOpt                   10a   const options(*nopass)        
d  ErrCde                             likeds(QUSEC) options(*nopass)
d  Domain                       10a   const options(*nopass)        
d  TfrSize                      10i 0 const options(*nopass)        
d  OptSpcAlgn                    1a   const options(*nopass)        
                                                                    
d FindChgs        pr                                                
                                                                    
d LstFlds         pr                  extpgm('QUSLFLD')             
d  UsrSpcName                   20a   const                         
d  Format                        8a   const                         
d  QualFilNam                   20a   const                         
d  RcdFmt                       10a   const                         
d  OvrPrc                        1a   const                         
d  ErrCde                             likeds(QUSEC) options(*nopass)
                                                                    
d LstRcdFmts      pr                  extpgm('QUSLRCD')             
d  UsrSpcName                   20a   const                         
d  Format                        8a   const                         
d  QualFilNam                   20a   const                         
d  OvrPrc                        1a   const                         
d  ErrCde                             likeds(QUSEC) options(*nopass)
                                                                    
d RtvUsrSpcPtr    pr                  extpgm('QUSPTRUS')            
d  QualUsrSpcN                  20a   const                         
d  UsrSpcPtr                      *                                 
d  ErrCde                             likeds(QUSEC) options(*nopass)
                                                                    
 ****************************************************************   
                                                                    
d SpcPtr          s               *                                 
d ListHdr         ds                  likeds(QUSH0100)              
d                                     based(SpcPtr)                 
                                                                    
d FldEntryPtr     s               *                                 
d FldEntry        ds                  likeds(QUSL0100)              
d                                     based(FldEntryPtr)            
                                                                    
d RcdEntryPtr     s               *                                 
d RcdEntry        ds                  likeds(QUSL010001)            
d                                     based(RcdEntryPtr)           
                                                                   
d ErrCde          ds                  qualified                    
d  Hdr                                likeds(QUSEC)                
d  MsgDta                      256a                                
                                                                   
 ****************************************************************  
                                                                   
d AftImagePtr     s               *                                
d AftImage        s          32766a   based(AftImagePtr)           
d AftNullPtr      s               *                                
d AftNullValue    s           8000a   based(AftNullPtr)            
d B4ImagePtr      s               *                                
d B4Image         s          32766a   based(B4ImagePtr)            
d B4NullPtr       s               *                                
d B4NullValue     s           8000a   based(B4NullPtr)             
d GetOut          s               n                                
d RcdFmt          s             10a                                
d SpcName         s             20a   inz('AUDDTACHG QTEMP')       
                                                                   
d X               s             10i 0                            
                                                                 
 ****************************************************************
                                                                 
 /copy qsysinc/qrpglesrc,trgbuf                                  
 /copy qsysinc/qrpglesrc,qusec                                   
 /copy qsysinc/qrpglesrc,qusgen                                  
 /copy qsysinc/qrpglesrc,quslfld                                 
 /copy qsysinc/qrpglesrc,quslrcd                                 
                                                                 
 ****************************************************************
                                                                 
 /free                                                           
                                                                 
  if (GetOut);                                                   
     *inlr = *on;                                                
     return;                                                     
  endif;                                                         
                                                                 
  select;                                                        
     when TrgBfr.QDBTE = '1';                                  
          // Insert operation -- not a concern today           
                                                               
     when TrgBfr.QDBTE = '2';                                  
          // Delete operation -- not a concern today           
                                                               
     when TrgBfr.QDBTE = '3';                                  
          // Update operations have before and after images    
                                                               
          B4ImagePtr = %addr(TrgBfr) + TrgBfr.QDBORO;          
          B4NullPtr = %addr(TrgBfr) + TrgBfr.QDBORNBM;         
                                                               
          AftImagePtr = %addr(TrgBfr) + TrgBfr.QDBNRO;         
          AftNullPtr = %addr(TrgBfr) + TrgBfr.QDBNRNBM;        
                                                               
          FindChgs();                                          
                                                               
     other;                                                    
          // Basically Read operations which should never      
          // trigger this program...                           
                                                                    
  endsl;                                                            
                                                                    
  *inlr = *on;                                                      
  return;                                                           
                                                                    
  // *************************************************************  
                                                                    
  begsr *inzsr;                                                     
                                                                    
    QUSBPrv = 0;                                                    
    ErrCde.Hdr.QUSBPrv = %size(ErrCde);                             
                                                                    
    RtvUsrSpcPtr(SpcName :SpcPtr :ErrCde);                          
                                                                    
    select;                                                         
       when ErrCde.Hdr.QUSBAvl = 0;                                 
            // User space previously created                        
                                                                    
       when ErrCde.Hdr.QUSEI = 'CPF9801';                           
            // UsrSpc not found, so create it                  
                                                               
            CrtUsrSpc(SpcName :' ' :4096 :x'00' :'*ALL' :' '   
                      :'*YES' :ErrCde :'*DEFAULT' :0 :'1');    
                                                               
            if ErrCde.Hdr.QUSBAvl <> 0;                        
               dsply ('Unable to create *USRSPC: ' +           
                      ErrCde.Hdr.QUSEI);                       
               GetOut = *on;                                   
            else;                                              
               // Get accessibility to user space              
                                                               
               RtvUsrSpcPtr(SpcName :SpcPtr :ErrCde);          
               if ErrCde.Hdr.QUSBAvl <> 0;                     
                  dsply ('Unable to access *USRSPC: ' +        
                      ErrCde.Hdr.QUSEI);                       
                  GetOut = *on;                                
               endif;                                          
            endif;                                             
       other;                                                  
            // Something seriously wrong.                       
                                                                
            dsply ('Serious Error found: ' +                    
                  ErrCde.Hdr.QUSEI);                            
            GetOut = *on;                                       
    endsl;                                                      
                                                                
    if (not GetOut);                                            
       LstRcdFmts(SpcName :'RCDL0100'                           
                  :(TrgBfr.QDBFILN02 + TrgBfr.QDBLIBN02)        
                  :'0' :ErrCde);                                
                                                                
       select;                                                  
          when ErrCde.Hdr.QUSBAvl <> 0;                         
               dsply ('Unable to access record formats: ' +     
                      ErrCde.Hdr.QUSEI);                        
               GetOut = *on;                                    
                                                                
          when ListHdr.QUSIS <> 'C';                            
               dsply ('Unable to access all record formats: ' + 
                      ErrCde.Hdr.QUSEI);                     
               GetOut = *on;                                 
                                                             
          when ListHdr.QUSNbrLE <> 1;                        
               dsply ('More than one record format found');  
               GetOut = *on;                                 
                                                             
          other;                                             
               RcdEntryPtr = SpcPtr + ListHdr.QUSOLD;        
               RcdFmt = RcdEntry.QUSFN05;                    
       endsl;                                                
    endif;                                                   
                                                             
    if (not GetOut);                                         
       LstFlds(SpcName :'FLDL0100'                           
               :(TrgBfr.QDBFILN02 + TrgBfr.QDBLIBN02)        
               :RcdFmt :'0' :ErrCde);                        
                                                             
       select;                                               
          when ErrCde.Hdr.QUSBAvl <> 0;                      
               dsply ('Unable to access field info: ' +            
                      ErrCde.Hdr.QUSEI);                           
               GetOut = *on;                                       
                                                                   
          when ListHdr.QUSIS <> 'C';                               
               dsply ('Unable to access all fields');              
               GetOut = *on;                                       
                                                                   
          other;                                                   
               // Continue on                                      
       endsl;                                                      
    endif;                                                         
                                                                   
  endsr;                                                           
                                                                   
 /end-free                                                         
                                                                   
 ***************************************************************** 
                                                                   
p FindChgs        b                                                
d FindChgs        pi                                               
                                                                   
 /free                                                             
                                                                   
  for X = 1 to ListHdr.QUSNbrLE;                                   
      if X = 1;                                                    
         FldEntryPtr = SpcPtr + ListHdr.QUSOLD;                    
      else;                                                        
         FldEntryPtr += ListHdr.QUSSEE;                            
      endif;                                                       
                                                                   
      select;                                                      
         when ((FldEntry.QUSNVA = '0') or                          
               (%subst(B4NullValue :X :1) = '0' and                
                %subst(AftNullValue :X :1) = '0')) and             
               %subst(B4Image :FldEntry.QUSOBP :FldEntry.QUSFLB) <>
               %subst(AftImage :FldEntry.QUSOBP :FldEntry.QUSFLB); 
                                                                   
              dsply (%trimr(FldEntry.QUSFN02) +                    
                     ' value changed');                            
                                                         
         when %subst(B4NullValue :X :1) = '1' and        
              %subst(AftNullValue :X :1) = '1';          
              // Both are null, so no change             
                                                         
         when %subst(B4NullValue :X :1) = '1' and        
              %subst(AftNullValue :X :1) = '0';          
                                                         
              dsply (%trimr(FldEntry.QUSFN02) +          
                     ' changed from null to not null');  
                                                         
         when %subst(B4NullValue :X :1) = '0' and        
              %subst(AftNullValue :X :1) = '1';          
                                                         
              dsply (%trimr(FldEntry.QUSFN02) +          
                     ' changed from not null to null');  
                                                         
      endsl;                                             
                                                         
  endfor;                                                
                            
 /end-free                  
                            
p FindChgs        e         

As AUDDTACHG will be used as a database trigger program, the system will call the program passing two parameters. As documented in the IBM Knowledge Center under How trigger programs work, the first parameter will contain information about the change operation and the second parameter the length of the first parameter. Documentation for the first parameter, often referred to as a trigger buffer, can be found here with the QSYSINC include for the parameter in member TRGBUF of QSYSINC/QRPGLESRC. TRGBUF defines the static portion of the parameter with data structure QDBTB, and AUDDTACHG prototypes the first parameter passed to it (TrgBfr) as being likeds(QDBTB).

Having received the two parameters, the *INZSR subroutine of AUDDTACHG runs. The *INZSR, after setting the Bytes provided field of the QUSEC API error code structure to 0 (send exceptions) and the Bytes provided field of the ErrCde API error code structure to a non-zero value (return exceptions in ErrCde), checks to see if the user space QTEMP/AUDDTACHG exists by calling the Retrieve Pointer to User Space (QUSPTRUS) API to set the pointer variable SpcPtr to the address of the user space. If this is the first time the trigger program AUDDTACHG has been called in the current job, the user space will not exist (ErrCde.Hdr.QUSBAvl will be non-zero and ErrCde.Hdr.QUSEI will be CPF9801 – Object in library not found) and AUDDTACHG will then create the user space with the Create User Space (QUSCRTUS) API and again call the QUSPTRUS API to set SpcPtr to the address of to the user space.

The SpcPtr variable is used by the program to base the common List API generic header (data structure QUSH0100 from QSYSINC/QRPGLESRC,QUSGEN) using the name ListHdr.

Our desire is to call the List Fields (QUSLFLD) API in order to determine what fields are defined for the record change that caused AUDDTACHG to be called, which is what the API will return to our user space. The QUSLFLD API, however, requires a record format name (in addition to the name of the file) and, unfortunately, the trigger buffer passed by the system to AUDDTACHG does not include the record format name. So the program calls the List Record Formats (QUSLRCD) API to get the record format name associated with the physical file TrgBfr.QBDFilN02 (the file name passed in the trigger buffer) in library TrgBfr.QDBLibN02 (the library name passed in the trigger buffer).

As physical files can have only one record format, and AUDDTACHG will be used only as a trigger for physical files, the program sets the variable RcdFmt to the value of the first, and only, record format name (RcdEntry.QUSFN05) returned by QUSLRCD. This "first" entry is accessed by setting the pointer variable RcdEntryPtr to the address of the user space (SpcPtr) plus the QUSLRCD List API generic header offset to list data (ListHdr.QUSOLD). The RcdEntryPtr variable is used by the program to base the QUSLRCD RCDL0100 returned record entry (data structure QUSL010001 from QSYSINC/QRPGLESRC,QUSLRCD) using the name RcdEntry.

Having obtained the necessary record format name, AUDDTACHG then calls the QUSLFLD API, reusing the same user space, as we have what we need from QUSLRCD, to access all of the field definitions associated with the file (using the same trigger buffer fields of TrgBfr.QDBFilN02 and TrgBfr.QDBLibN02 for file and library name, respectively) along with the record format name found in variable RcdFmt. The *INZSR subroutine then returns to the main line of AUDDTACHG.

In the main line of the program, a check is made to see what type of operation caused our trigger program to be called. This information can be found in TrgBfr.QDBTE (trigger event) with a value of '1' indicating a new record was written to the file, a value of '2' indicating a record was deleted from the file, a value of '3' indicating that an update of an existing record was done, and a value of '4' indicating that a record was read from the file. For today, all we care about are changes, a TrgBfr.QDBTE value of '3'. The other cases are basically a subset of a change operation in that an add adds all fields, a delete deletes all fields, and a read doesn't change anything.

Having determined that the current operation is an update, AUDDTACHG sets four pointers:

  • B4ImagePtr to where the "prior to update" record value is found in the trigger buffer. The B4ImagePtr variable is used to base the variable B4Image, which is defined as a character field with a length of 32766 bytes (the maximum database file size). The value of B4ImagePtr is set using the address of the trigger buffer plus the trigger buffer–provided original record offset within the trigger buffer (TrgBfr.QDBORO). B4Image now represents the entire "before update" record contents.
  • B4NullPtr to where the null byte map associated with the "prior to update" fields is found in the trigger buffer. The B4NullPtr variable is used to base the variable B4NullValue, which is defined as a character field with a length of 8000 bytes (the maximum number of fields in a record format). The value of B4NullPtr is set using the address of the trigger buffer plus the trigger buffer–provided original record null byte map offset (TrgBfr.QDBORNBM). B4NullValue now represents the entire "before update" null map contents.
  • AftImagePtr to where the "after update" record value is found in the trigger buffer. The AftImagePtr variable is used to base the variable AftImage which, like B4Image, is defined with a length of 32766 bytes. The value of AftImagePtr is set using the address of the trigger buffer plus the trigger buffer–provided new record offset (TrgBfr.QDBNRO). AftImage now represents the entire "after update" record contents.
  • AftNullPtr to where the null byte map associated with the "after update" fields is found in the trigger buffer. The AftNullPtr is used to base the variable AftNullValue which, like B4NullValue, is defined with a length of 8000 bytes. The value of AftNullPtr is set using the address of the trigger buffer plus the trigger buffer–provided new record null byte map offset (TrgBfr.QDBNRNBM). AftNullValue now represents the entire "after update" null map contents.

Null byte maps, if you're not familiar with them, allow you to determine if a given field is set to a NULL or non-NULL value where NULL means no value (which is different than, say, a field set to all blanks). For each field of the record, there will be a 1-byte character field in the null byte map. If the null byte map field is set to '0', then the field is not NULL. If the null byte map field is set to '1', then the field is set to NULL.

Having set the various pointers to address the before and after record values and null byte maps, AUDDTACHG calls procedure FindChgs().

FindChgs() loops thru all of the field definitions returned by the QUSLFLD API. The number of fields returned, the to value associated with the for statement, is found in the QUSLFLD List API generic header number of list entries (ListHdr.QUSNbrLE). As when we wanted to access the first RcdEntry in the *INZSR, FindChgs() sets the pointer variable FldEntryPtr when accessing the first field entry (X is equal to 1) by adding the List API header offset to list data (ListHdr.QUSOLD) to the address of the user space (SpcPtr). Subsequent field definitions (X is greater than 1) are accessed by adding the List API header size of each entry (ListHdr.QUSSEE) to the current value of FldEntryPtr. The FldEntryPtr variable is used by the program to base the QUSLFLD FLDL0100 returned field entry (data structure QUSL0100 from QSYSINC/QRPGLESRC,QUSLFLD) using the variable FldEntry.

Within the for loop, a select is run for each defined field. The first when is checking for the following conditions:

  • Does this field even allow NULL values? This is determined by examining the QUSLFLD returned value FldEntry.QUSNVA (Null values allowed). If the value is '0', then NULL values are not allowed.
  • If NULL values are allowed, are both the "before update" and "after update" fields set to a non-NULL value? This is determined by examining the trigger buffer null byte map fields associated with the field. If the Xth byte of B4NullValue is '0', then the "before update" field was not NULL, and if the Xth byte of AftNullValue is '0', then the "after update" field is not NULL
  • If either of the two previous checks are true (the field is not NULL-capable or the field is NULL-capable and both the before and after fields are not NULL), then a check is made for the "before" field value not being equal to the "after" field value. This is done by comparing the substring of the B4Image and AftImage values. The %subst start position is determined using the QUSLFLD returned value FldEntry.QUSOBP (Output buffer position) and the length using the QUSLFLD returned value FldEntry.QUSFLB (Field length in bytes). If the B4Image field value is not equal to the AftImage field value, then a message is displayed using the dsply operation. The message provides the name of the field that was changed (using the QUSLFLD returned value FldEntry.QUSFN02 (Field name) with the text 'value changed').

The following when operations are pretty straightforward. If both "before" and "after" null byte map values are '1', indicating that both are NULL, we know there was no change.

Otherwise, there was a change, either changing from NULL to not NULL or from not NULL to NULL, and an appropriate message is displayed.

When the for loop completes and all appropriate messages related to field value changes have been displayed, FindChgs() returns to the main line of AUDDTACHG, *INLR is set on, and the program returns.

That's it. Per the original request of "…which field changed in a file…," we have identified each field that was changed and avoided any hard coding of field names with multiple if checks. I suspect, however, that a follow-on request might be "OK, I now know the fields that were changed, but I really wanted to know what the before and after values were when the field changed. Can this be done in the same manner?" The answer of course is yes, and all you have to do is patiently wait for next month's API Corner.

Assuming that you've stored the above program source in member AUDDTACHG of source file QRPGLESRC and that the library containing QRPGLESRC is in your current library list, then you can create the program with the following command:

CrtBndRPG Pgm(AUDDTACHG) 

To test AUDDTACHG, we'll create a physical file with a variety of data types, sizes, and attributes. The file will be DTACHGPF (Data change physical file) with the following DDS definition.

R RECORD                              
  TXTFLD        30A         ALWNULL   
  VARTXTFLD     50A         VARLEN    
  NBRFLD3P0      3P 0                 
  NBRFLD10P2    10P 2                 
  NBRFLD4B2      4B 2                 
  NBRFLD9B0      9B 0                 
  NBRFLD18B0    18B                   
  NBRFLD10S0    10S 0       ALWNULL   
  NBRFLD15S2    15S 2                 
  DATFLD          L         ALWNULL   
  TIMFLD          T                   
  TSFLD           Z          

Assuming you have stored the above DDS source in member DTACHGPF of source file QDDSSRC and that the library containing QDDSSRC is in your current library list, then you can create the file with this command:

CrtPF File(DTACHGPF) SrcFile(QDDSSRC)

And then you associate AUDDTACHG as an update trigger to DTACHGPF with this command:

AddPFTrg File(DTACHGPF) TrgTime(*After) TrgEvent(*Update) Pgm(AUDDTACHG)

Now add a record to DTACHGPF using whatever tool you are comfortable with (DFU, SQL, RPG program, etc.) and, after adding the record, change one or more field values again using the tool of your choice. You should then get the messages identifying only those fields that you changed.

I mentioned at the start of this article that "In a production environment I would never use this implementation" and that I would tend more toward using three distinct programs. The three programs I have in mind are these:

  1. The first program would be an interactive program that maintains a control file of those files and fields within the file that are to be audited for change (or insert and delete activity). The program would be passed a file name, use the logic found in the *INZSR subroutine of AUDDTACHG to access the fields defined for the file, merge this list with any existing file/field records in the control file, and present the user with a subfile showing those fields currently audited and those not being audited. The user makes whatever changes are desired (stop auditing this field, start auditing this field), and the program then writes/updates to the control file those fields that are to be audited. For each field being audited, the control file record would contain the essential pieces of information used by the AUDDTACHG FindChgs() procedurethe name of the file (TrgBfr.QDBFilN02), the name of the field (FldEntry.QUSFN02), whether or not the field can be set to NULL (FldEntry.QUSNVA), the offset to the field within the record (FldEntry.QUSOBP), and the length of the field in bytes (FldEntry.QUSFLB).
  2. The second program would be the trigger program associated with any file that has one or more records in the control file from program 1. The trigger program would verify that the file is audited (there is at least one record in the control file for the file being changed) and, if so, maintain three (or five) transaction files. The first transaction file would be a header file most likely indexed by the current %timestamp value. Each header record would also contain (at a minimum) a unique numeric value identifying the transaction, the file name (TrgBfr.QDBFilN02), the file library name (TrgBfr.QDBLibN02), the type of trigger event (TrgBfr.QDBTE), and the qualified name of the program performing the trigger event (to find this, you can refer to an earlier API Corner article, Retrieving Information, Part I, which uses the Retrieve Call Stack (QWVRCSTK) API). This program would then write to a second file (indexed by the same unique value used in the header file) that holds "before images" (B4Image) and the "before null byte map" (B4NullValue), with the third file (again indexed by the same header file index value) holding the "after images" (AftImage) and the "after null byte map" (AftNullValue). If the combination of Image and NullValue into one record/file exceeds the maximum size of a record, then the fourth and fifth transaction files would contain the B4NullValue and AftNullValue images (again indexed by the same unique value found in the header file). To support auditing of insert operations (TrgBfr.QDBTE = '1'), this program would write the header record, the AftImage value, and the AftNullValue value. To support auditing of delete operations (TrgBfr.QDBTE = '2'), this program would write the header record, the B4Image, and the B4NullValue value.
  3. The third program would read the header file (using the timestamp index) maintained by the second program and, for update events, access the before and after transaction files using the unique key value found in the header file record. Using the control file maintained by the first program, this third program would then perform the processing being done in the FindChgs() procedure of AUDDTACHG to identify any changed data values and record those changes to a printer file, a permanent audit file, or just dsply them (though this last option is rather unlikely). Having processed a given transaction the program would then delete the header record and any Image/NullValue records associated with the transaction

This three-program approach would have many advantages over an implementation such as AUDDTACHG. Three that readily come to mind are these:

  • Most files contain at least some fields that do not need to be audited, so why process them every time?
  • Most files are not going to change very often in terms of the fields defining the record, so why re-access the field definition values (that is, use QUSLFLD) every time? Just record the essential facts about fields that are to be audited once.
  • Why do the audit analysis as part of the application transaction (basically slowing down interactive response time)? Record what's needed (the who, what, when of the header file) and do the field level analysis in a background batch program.

I will add that this three-program approach is not just theoretical. I successfully implemented this approach a few years back for a company needing to audit field-level changes involving several hundred files. They had absolutely no desire to change any of the application programs maintaining these files, and they wanted to minimize the impact to their users. I will point out, though, that my implementation included a few additional "bells and whistles"items like having the transaction file records written by the second program be in the same commitment cycle as the initiating program in order to catch rollback situations, control level values in the transaction header file to accommodate changed record-level definitions (new fields, changed field definitions, etc), and the like.

Have Some System API Questions?

As usual, if you have any API questions, send them to me at This email address is being protected from spambots. You need JavaScript enabled to view it..

Bruce Vining

Bruce Vining is president and co-founder of Bruce Vining Services, LLC, a firm providing contract programming and consulting services to the System i community. He began his career in 1979 as an IBM Systems Engineer in St. Louis, Missouri, and then transferred to Rochester, Minnesota, in 1985, where he continues to reside. From 1992 until leaving IBM in 2007, Bruce was a member of the System Design Control Group responsible for OS/400 and i5/OS areas such as System APIs, Globalization, and Software Serviceability. He is also the designer of Control Language for Files (CLF).A frequent speaker and writer, Bruce can be reached at bvining@brucevining.com. 


MC Press books written by Bruce Vining available now on the MC Press Bookstore.

IBM System i APIs at Work IBM System i APIs at Work
Leverage the power of APIs with this definitive resource.
List Price $89.95

Now On Sale

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.