The API Corner: What Was the Change in This Record?

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

Let's discuss some things you should know about flexibly tracking field values.


Last month, in So Just What Changed in This Record?, we saw how a program could identify by name each field that was changed by an update operation on a record. We accomplished this using the database trigger support of the IBM i along with the List Record Formats (QUSLRCD) and List Fields (QUSLFLD) APIs. This month, we'll extend that program to display not only the names of the fields changed, but also the original and new values of the field.

When accessing the before and after values of a field, some data types (alphanumeric, date, time, timestamp) are relatively easy to handle. For example, the value of a fixed-length alphanumeric field can be accessed using an approach similar to how we determined if the value had changed. Last month, the procedure FindChgs() used the following to determine if a field (that either did not support null values or had both before and after values set to non-null values) changed:

         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');                

To access the before and after values for display purposes would just be displaying the results of the %subst operations (with the additional consideration that if using the DSPLY operation code you would also need to check that the field length in bytes (FldEntry.QUSFLB) did not exceed the maximum length supported by DSPLY52 bytes). Accessing the before and after values of a variable-length alphanumeric field is slightly more effort (and shown later in this article) but still along the same lines.

Numeric fields, however, pose more of a challenge when trying to display before and after values, and they'll be the focus of this article. Most language functions, like ILE RPG's %CHAR built-in function, want to know at compile time the characteristics of the variables being operated on. For instance, in the following assignment of Value, the compiler wants to know at compile time if SomeNbr is defined as packed decimal 9.2, packed decimal 10.2, zoned decimal 11.0, a 2-byte integer, or something else.

Value = %char(SomeNbr);

Fortunately, though not used in last month's article, the QUSLFLD API returns a lot more than just the name of each field within a record (FldEntry.QUSFN02), the offset to the field within a record (FldEntry.QUSOBP), and the length of the field in bytes (FldEntry.QUSFLB). Also provided is the data type (FldEntry.QUSDT) and, for fields of a numeric data type, the number of digits (FldEntry.QUSigits) along with the number of decimal positions (FldEntry.QUSDP).

Using this additional information, we have a variety of ways that we could use to convert a given numeric value to a displayable format.

One approach might be to extend how we previously used the based variables B4Image and AftImage. Rather than just basing these two alphanumeric variables (and the basing pointers B4ImagePtr and AftImagePtr, respectively), we could also define based variables on these pointers for each possible numeric variable definitionthat is, based variables named such as Pkd15_0, Pkd15_1, and Pkd15_2 that would be used when the data type is packed decimal (FldEntry.QUSDT = 'P'), the number of digits is 15 (FldEntry.QUSigits = 15), and the number of decimal positions is 0, 1, or 2, respectively. In conjunction with IF and/or SELECT/WHEN logic, this would then allow us to provide the correct field name to the %CHAR function (as in Value = %char(Pkd15_2); when FldEntry.QUSDT = 'P', FldEntry.QUSigits = 15, and QUSDP = 2). This approach, to my way of thinking anyway, is very painful. For packed-decimal fields, you can have from 1 to 63 digits and from 0 to 63 decimal positions (as long as the decimal positions value doesn't exceed the digits value). This leaves us with, well, lots and lots of field definitions and logic checks to code if we want to handle all possible numeric definitions. Not an approach I would recommend.

Another approach might be to use the various %BIT* built-in functions provided by RPG to "de-compress" packed-decimal fields accessed by way of B4Image and AftImage. That is, work through the substringed B4Image and AftImage fields (as was done to determine if the field value had changed), determining for each nibble the appropriate character value ('0' to '9') the nibble represents and in addition, for the last byte of the data, what sign (positive or negative) should be assigned. While this approach might prove to be highly educational, it's still not one I would recommend.

My preference is to use APIs that can be told at run time, rather than compile time, what type(s) of numeric data we're working with and then have the APIs return the value in a format suitable for DSPLYing. Along these lines, here is an updated version of last month's AUDDTACHG program.

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 CpyNV           pr                  extproc('_LBCPYNV')         
d  CpyNVResult                        like(CpyNVResult)           
d  TgtDtaAttr                         const likeds(TgtDtaAttr)    
d  SourceValue                  63a   const                       
d  SrcDtaAttr                         const likeds(SrcDtaAttr)    
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 EdtNbr          pr                                                
d  SrcPtr                         *   const                         
d FindChgs        pr                                                
d GetEdtDta       pr                  extpgm('QECEDT')              
d  RcvVar                      256a                                 
d  LenRcvVar                    10i 0 const                         
d  SrcDta                      256a   const                
d  SrcClass                     10a   const                
d  Precision                    10i 0 const                
d  EdtMsk                      256a   const                
d  LenEdtMsk                    10i 0 const                
d  FillChr                       1a   const                
d  ErrCde                             likeds(QUSEC)        
d GetEdtMsk       pr                  extpgm('QECCVTEC')   
d  EdtMsk                      256a                        
d  LenEdtMsk                    10i 0                      
d  LenRcvVar                    10i 0                      
d  FillChr                       1a                        
d  EdtCde                        1a   const                
d  FillFloat                     1a   const                
d  Precision                    10i 0 const                
d  ScaleIn                      10i 0 const                
d  ErrCde                             likeds(QUSEC)        
d GetValue        pr            52a                        
d  SrcPtr                         *   const                          
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 SrcDtaAttr      ds                  qualified                      
d  Type                          1a                                  
d  Length                        5i 0                                
d  Reserved                      4a   inz(x'00000000')               
d TgtDtaAttr      ds                  qualified                  
d  Type                          1a   inz(x'02')                 
d  Length                        5i 0                            
d  FracDigits                    3i 0 overlay(Length)            
d  TotalDigits                   3i 0 overlay(Length :2)         
d  Reserved                      4a   inz(x'00000000')           
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 CpyNVResult     s             63a                                
d EdtMsk          s            256a                                
d EdtRcvVar       s            256a                                
d FillChr         s              1a                                
d GetOut          s               n                                
d LenEdtMsk       s             10i 0                              
d LenEdtRcvVar    s             10i 0                              
d MaxLen          s             10i 0                              
d RcdFmt          s             10a                                
d Scale           s             10i 0                              
d SpcName         s             20a   inz('AUDDTACHG QTEMP')       
d Value           s             52a                                
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                                 
  if (GetOut);                                                   
     *inlr = *on;                                                
     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;     
          // Basically Read operations which should never   
          // trigger this program...                        
  *inlr = *on;                                              
  // *************************************************************
  begsr *inzsr;                                                   
    QUSBPrv = 0;                                                  
    ErrCde.Hdr.QUSBPrv = %size(ErrCde);                           
    RtvUsrSpcPtr(SpcName :SpcPtr :ErrCde);                        
       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: ' +        
               GetOut = *on;                                
               // Get accessibility to user space           
               RtvUsrSpcPtr(SpcName :SpcPtr :ErrCde);       
               if ErrCde.Hdr.QUSBAvl <> 0;                  
                  dsply ('Unable to access *USRSPC: ' +     
                  GetOut = *on;                             
            // Something seriously wrong.                   
            dsply ('Serious Error found: ' +                
            GetOut = *on;                                   
    if (not GetOut);                                            
       LstRcdFmts(SpcName :'RCDL0100'                           
                  :(TrgBfr.QDBFILN02 + TrgBfr.QDBLIBN02)        
                  :'0' :ErrCde);                                
          when ErrCde.Hdr.QUSBAvl <> 0;                         
               dsply ('Unable to access record formats: ' +     
               GetOut = *on;                                    
          when ListHdr.QUSIS <> 'C';                            
               dsply ('Unable to access all record formats: ' + 
               GetOut = *on;                                    
          when ListHdr.QUSNbrLE <> 1;                           
               dsply ('More than one record format found');     
               GetOut = *on;                               
               RcdEntryPtr = SpcPtr + ListHdr.QUSOLD;      
               RcdFmt = RcdEntry.QUSFN05;                  
    if (not GetOut);                                       
       LstFlds(SpcName :'FLDL0100'                         
               :(TrgBfr.QDBFILN02 + TrgBfr.QDBLIBN02)      
               :RcdFmt :'0' :ErrCde);                      
          when ErrCde.Hdr.QUSBAvl <> 0;                    
               dsply ('Unable to access field info: ' +    
               GetOut = *on;                               
          when ListHdr.QUSIS <> 'C';                       
               dsply ('Unable to access all fields');            
               GetOut = *on;                                     
               // Continue on                                    
p FindChgs        b                                              
d FindChgs        pi                                             
  for X = 1 to ListHdr.QUSNbrLE;                                 
      if X = 1;                                                     
         FldEntryPtr = SpcPtr + ListHdr.QUSOLD;                     
         FldEntryPtr += ListHdr.QUSSEE;                             
         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 from:');                       
              dsply GetValue(B4ImagePtr);                           
              dsply ('to:');                                        
              dsply GetValue(AftImagePtr);                          
         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:');        
              dsply GetValue(AftImagePtr);             
         when %subst(B4NullValue :X :1) = '0' and      
              %subst(AftNullValue :X :1) = '1';        
              dsply (%trimr(FldEntry.QUSFN02) +        
                     ' changed to null from:');        
              dsply GetValue(B4ImagePtr);              
p FindChgs        e                                              
p GetValue        b                                              
d GetValue        pi            52a                              
d  mySrcPtr                       *   const                      
d VarLenPtr       s               *                              
d VarLen          s              5u 0 based(VarLenPtr)           
d SrcValue        s          32766a   based(mySrcPtr)            
     when ((FldEntry.QUSDT = 'A') and                            
           (FldEntry.QUSVLFI = '0'));                             
          if FldEntry.QUSFLB <= %size(Value);                     
             Value =                                              
               %subst(SrcValue :FldEntry.QUSOBP :FldEntry.QUSFLB);
             Value =                                              
               %subst(SrcValue :FldEntry.QUSOBP :%size(Value));   
     when ((FldEntry.QUSDT = 'A') and                             
           (FldEntry.QUSVLFI = '1'));                             
          VarLenPtr = mySrcPtr + FldEntry.QUSOBP;                 
             when VarLen = 0;                                     
                  Value = *blanks;                                
             when VarLen <= %size(Value);                         
                  Value =                                                 
                    %subst(SrcValue :(FldEntry.QUSOBP + 2) :VarLen);      
                  Value =                                                 
                    %subst(SrcValue :(FldEntry.QUSOBP + 2) :%size(Value));
     when FldEntry.QUSDT = 'B';                                           
          SrcDtaAttr.Type = x'00';                                        
          SrcDtaAttr.Length = FldEntry.QUSFLB;                            
          TgtDtaAttr.Length = FldEntry.QUSIGITS;                          
     when FldEntry.QUSDT = 'L';                                           
          Value =                                                         
            %subst(SrcValue :FldEntry.QUSOBP :10);                        
     when FldEntry.QUSDT = 'P';                                           
          SrcDtaAttr.Type = x'03';                                        
          SrcDtaAttr.Length = FldEntry.QUSIGITS;                          
          TgtDtaAttr.Length = FldEntry.QUSIGITS;       
     when FldEntry.QUSDT = 'S';                        
          SrcDtaAttr.Type = x'02';                     
          SrcDtaAttr.Length = FldEntry.QUSIGITS;       
          TgtDtaAttr.Length = FldEntry.QUSIGITS;       
     when FldEntry.QUSDT = 'T';                        
          Value =                                      
            %subst(SrcValue :FldEntry.QUSOBP :8);      
     when FldEntry.QUSDT = 'Z';                        
          Value =                                      
            %subst(SrcValue :FldEntry.QUSOBP :26);     
          Value = *blanks;                             
  return Value;                                                 
p GetValue        e                                             
p EdtNbr          b                                             
d EdtNbr          pi                                            
d  mySrcPtr                       *   const                     
d SrcValue        s          32766a   based(mySrcPtr)           
     CpyNV(CpyNVResult :TgtDtaAttr                              
           :%subst(SrcValue :FldEntry.QUSOBP :FldEntry.QUSFLB)  
     Value = *blanks;                                             
  if ((FldEntry.QUSIGITS <> MaxLen) or                            
      (FldEntry.QUSDP <> Scale));                                 
     // Reuse previous mask if MaxLen and Scale have not changed  
     MaxLen = FldEntry.QUSIGITS;                                  
     Scale = FldEntry.QUSDP;                                      
     GetEdtMsk(EdtMsk :LenEdtMsk :LenEdtRcvVar :FillChr           
               :'L' :' ' :MaxLen :Scale :ErrCde);                 
  GetEdtDta(EdtRcvVar :LenEdtRcvVar :CpyNVResult :'*ZONED'        
            :MaxLen :EdtMsk :LenEdtMsk :FillChr :ErrCde);         
  if ErrCde.Hdr.QUSBAvl = 0;                                      
     Value = %triml(%subst(EdtRcvVar :1 :LenEdtRcvVar));     
     Value = *blanks;                                        
p EdtNbr          e                                          

A summary of the changes being made (with the details to follow) are:

  • New prototypes named CpyNV (Copy Numeric Value), EdtNbr (Edit Number), GetEdtDta (Get Edited Data), GetEdtMsk (Get Edit Mask), and GetValue (Get Field Value)
  • New data structures named SrcDtaAttr (Source Data Attributes) and TgtDtaAttr (Target Data Attributes)
  • New standalone fields CpyNVResult (Copy Numeric Value Result), EdtMsk (Edit Mask), EdtRcvVar (Edit Receiver Variable), FillChr (Fill Character for Editing using an edit mask), LenEdtMsk (Length of Edit Mask), LenEdtRcvVar (Length of Edit Receiver Variable), MaxLen (Maximum Length), Scale, and Value
  • Minor changes to the DSPLY operations used in the procedure FindChgs()
  • New procedures named GetValue and EdtNbr

The first code change can be found in the procedure FindChgs(). Last month, FindChgs() simply displayed text indicating if a given field was changed. This month, FindChgs() displays text that includes the field before and after values related to that change. This is done by DSPLYing the return value of procedure GetValue().

The GetValue() procedure is prototyped as taking one input, the address of the record buffer (before or after image) to be processed, and providing an alphanumeric return value with a size of 52 bytes, which is the limit that the DSPLY operation can display. GetValue() also defines three local fields:

  • VarLenPtrA pointer to the first byte associated with a variable-length field
  • VarLenAn unsigned 2-byte integer based on the pointer variable VarLenPtr. This is used to determine the actual length of the variable-length field.
  • SrcValueA based alphanumeric variable with a length of 32,766 bytes. This is used to access field values in the same manner as B4Image and AftImage, but without having to be concerned with whether the value is before or after.

GetValue() processing is a SELECT group based on the data type (FldEntry.QUSDT) of the field currently being processed. Processing of the "simple" data types is quite direct. When the data type is:

  • 'A' (alphanumeric) and not variable-length (FldEntry.QUSVLFI = '0'), set the variable Value to the actual length (or truncated length if the length exceeds 52 bytes) of the field being processed
  • 'A' (alphanumeric) and variable-length (FldEntry.QUSVLFI = '1'), set VarLenPtr to the start of the field being processed, determine the actual length of the variable field using the based variable VarLen, and set the variable Value to the actual length (or truncated length if the actual length exceeds 52 bytes) of the field being processed. When accessing the field value, the starting offset of the %SUBST operation is also adjusted to bypass the 2-byte length value.
  • 'L' (date), set the variable Value to the 10-byte date value of the field being processed
  • 'T' (time), set the variable Value to the 8-byte time value of the field being processed
  • 'Z' (timestamp), set the variable Value to the 26-byte timestamp value of the field being processed

For the fields with numeric data types ('B' for binary/integer, 'P' for packed decimal, and 'S' for zoned decimal), GetValue() does some "prep" work and then calls the procedure EdtNbr. This "prep" work will be explained after an introduction to EdtNbr().

Within EdtNbr(), after setting a MONITOR to catch "bad" numeric data values, the Copy Numeric Value (CPYNV) machine instruction is run. The CPYNV instruction is rather handy in that it will:

  • Copy numeric values from one field (the source) to another (the target)
  • Allow you to dynamically define the attributes of the source and target fields in terms of data type, number of digits, and number of decimal positions
  • Automatically convert the source format to the target format if the data attributes are different

In other words, just what we need to get a variety of numeric values converted to a consistent format.

The CPYNV instruction is passed four parameters. They are the target field, the attributes of the target field, the source field, and the attributes of the source field. The attributes are passed as a 7-byte data structure defined in the documentation of the Set Data Pointer Attributes (SETDPAT) machine instruction. Within the AUDDTACHG program, there are two instances of this data structure declaredSrcDtaAttr to define the source field as it's defined in the record image and TgtDtaAttr to define the target field that we want the source value to be converted to.

The "prep" work being done in the GetValue() procedure is where the appropriate SrcDtaAttr and TgtDtaAttr data structure subfields are being set in preparation of EdtNbr() running the CPYNV instruction. Some fields, like TgtDtaAttr.Type, are static and set one time when the data structures are initialized. For example, in the case of TgtDtaAttr.Type the static value is x'02', indicating that we always want the source numeric value to be returned in the target field as a zoned-decimal format. Other fields, like SrcDtaAttr.Type, need to be set on a field-by-field basis. For example, when the source data type (FldEntry.QUSDT) is:

  • 'B' (binary), then SrcDtaAttr.Type is set to x'00', SrcDtaAttr.Length is set to the length in bytes of the source field (which will be either 2, 4, or 8), and TgtDtaAttr.Length is set to the number of digits found in the source field
  • 'P' (packed), then SrcDtaAttr.Type is set to x'03' and both SrcDtaAttr.Length and TgtDtaAttr.Length to the number of digits found in the source field
  • 'S' (signed), then SrcDtaAttr.Type is set to x'02' and both SrcDtaAttr.Length and TgtDtaAttr.Length to the number of digits found in the source field

Returning to our discussion of the EdtNbr procedure, EdtNbr() runs the CPYNV instruction using the data attribute structures set by GetValue() and has the result of the copy operation returned in variable CpyNVResult. At this point, CpyNVResult is set to the zoned-decimal representation of the field being processed. But in order to display that value in a meaningful way, we need to edit it by inserting a decimal point where appropriate, a negative sign for negative values, etc. To accomplish this, AUDDTACHG uses two additional APIsConvert Edit Code (QECCVTEC), prototyped as GetEdtMsk, and Edit (QECEDT), prototyped as GetEdtDta.

The QECCVTEC API can be used to dynamically create an edit mask appropriate for the proper editing (decimal point, sign, etc.) of a given numeric value. As a minor performance improvement, AUDDTACHG when creating an edit mask stores the number of digits and number of decimal positions in variables MaxLen and Scale, respectively. So prior to creating an edit mask, a check is made to determine if the last created edit mask happens to match the characteristics of the current field to be edited. If not, which will certainly be the case for the first numeric changed field to be processed by AUDDTACHG, then QECCVTEC is called (as GetEdtMsk). If the characteristics do match, then the previous edit mask is re-used.

The QECCVTEC API is passed the edit code to be used ('L' in the example program), the way in which zero suppression should be handled (a blank in the example program), the number of digits (MaxLen, which is set to the FldEntry.QUSigits value of the current field), and the number of decimal positions (Scale, which is set to the FldEntry.QUSDP value of the current field). The API returns four fields:

  • EdtMskThe edit mask to use based on the inputs to the API (edit code, zero suppression option, etc.)
  • LenEdtMskThe length of the edit mask returned (EdtMsk)
  • LenEdtRcvVarThe length required to return the edited value after applying the edit mask
  • FillChrThe fill character to pass subsequently pass to the QECEDT API

Having gotten an appropriate edit mask, the QECEDT API is called (as GetEdtDta) in order to access the edited value. The API defines one receiver variable where the formatted numeric value is to be returned (EdtRcvVar) and several input parameters. These inputs are the length of the EdtRcvVar variable (LenEdtRcvVar, previously returned by QECCVTEC), the numeric value to be formatted (CpyNVResult, previously returned by the CPYNV API), the data type found in CpyNVResult (the value '*ZONED' as we previously hardcoded the TgtDtaAttr structure used with the CPYNV instruction to return zoned-decimal data), the number of digits (MaxLen), the edit mask to use (EdtMsk, previously returned by QECCVTEC), the length of the edit mask (LenEdtMsk, previously returned by QECCVTEC), and the fill character to be used (FillChr, previously returned by QECCVTEC).

The returned EdtRcvVar value is then returned by EdtNbr() to GetValue() by way of assigning Value to the contents of the %TRIML value of EdtRcvVar for a length of LenEdtRcvVar. GetValue() in turn returns Value to FindChgs() for DSPLYing to the user (as either a before value or an after value).

While the formatting of numeric values is not as straightforward as that found for data types such as alphanumeric, date, time, etc., it can be accomplished using system APIs, in a quite dynamic nature, without too much work. You may find the CPYNV, QECCVTEC, and QECEDT APIs to be just what you need in other applications to stream line some code.

To compile and test AUDDTACHG, please refer to the earlier article So Just What Changed in This Record?.

Before closing a few points:

  • Some careful readers may have noticed that, while the data attributes structure used by CPYNV allows the specification of the total number of digits (TotalDigits) and the number of decimal point digits (FracDigits), AUDDTACHG only sets the Length (effectively, just the TotalDigits variable) portion of the structure. There is nothing wrong with setting TotalDigits and FracDigits to the appropriate values (and for some applications, that will be the right thing to do), but, in the case of AUDDTACHG, I "know" that the subsequent edit APIs will be the final decider in terms of decimal point location. In the case of AUDDTACHG's use of CPYNV, the important item is to get all of the digits defined for the field. Decimal location can be introduced on the field later (which it is in EdtNbr()).
  • Others may have noticed that the QECEDT API directly supports data types of binary, packed decimal, and zoned decimal and wondered why the CPYNV API was needed at all (as QECEDT could handle the various data types). AUDDTACHG uses both APIs for the following two primary reasons. First, not all applications will want to have the numeric value formatted as an edited string, so general knowledge of the CPYNV API is of value. Second, when the i introduced 8-byte integer support, for some reason (I suspect oversight), this support was not added to QECEDT. CPYNV, however, does support this length and, as this length may very well exist in some of your files, the use of CPYNV in copying the 8-byte integer value to a zoned-decimal value allows the value to be properly edited (and DSPLYed) by EdtNbr().
  • The EdtRcvVar passed to QECEDT is actually declared with a length of 256 bytes though the API call uses the value of LenEdtRcvVar returned by QECCVTEC. LenEdtRcvVar will always be 256 bytes or less, and it's the value that you must pass to QECEDT. Any other value passed to the API will result in CPF27AF – Edit mask not valid.
  • The EdtNbr() statement Value = %triml(%subst(EdtRcvVar :1 :LenEdtRcvVar)); runs the risk of a truncation error due to Value being defined as only 52 bytes in length while LenEdtRcvVar may be a larger number. In a production environment, I would anticipate that Value would really be a variabl- length field (of much greater maximum size than 52 bytes) written to an audit file and, in order to avoid adding code to handle the DSPLY limitation of 52 bytes, I simply accepted the risk of truncation (as I really don't expect any "real" application to simply DSPLY the before or after values).

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 

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







  • Mobile Computing and the IBM i

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

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

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

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

    Order your copy here.

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


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


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

    SB Profound WP 5539

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

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

    Read Node.js for Enterprise IBM i Modernization Now!


  • 2020 IBM i Marketplace Survey Results


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

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

  • AIX Security Basics eCourse

    Core Security

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

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


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

    Profound Logic Software, Inc.

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

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

  • What to Do When Your AS/400 Talent Retires

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

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

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


  • IBM i Resources Retiring?

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


  • Backup and Recovery Considerations for Security Data and Encrypted Backups

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

  • Profound.js: The Agile Approach to Legacy Modernization

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


  • Data Breaches: Is IBM i Really at Risk?

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

    Watch the webinar today!


  • Easy Mobile Development

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


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

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

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

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

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

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

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

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

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

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

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

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

    Download and watch today!


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

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

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


  • Accelerating Programmer Productivity with Sequel


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

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

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

  • Business Intelligence is Changing: Make Your Game Plan

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

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

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


  • Controlling Insider Threats on IBM i

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

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

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

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

  • How to Manage Documents the Easy Way

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

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


  • Lessons Learned from the AS/400 Breach

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

  • Overwhelmed by Operating Systems?

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

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

    This presentation includes a live demo of Network Server Suite.


  • Real-Time Disk Monitoring with Robot Monitor

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

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



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

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

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

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


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

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

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

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


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

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

    • Capture
    • Manage
    • And distribute documents digitally


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


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

    Are there still companies that use AS400? Of course!

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

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


  • Ask the RDi Experts

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

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

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


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

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

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



  • Inside the Integrated File System (IFS)

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

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

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


  • Expert Tips for IBM i Security: Beyond the Basics

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

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

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



  • 5 IBM i Security Quick Wins

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

  • How to Meet the Newest Encryption Requirements on IBM i

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

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



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

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

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

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



  • Fight Cyber Threats with IBM i Encryption

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

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




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

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

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


  • How to Transfer IBM i Data to Microsoft Excel

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

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

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



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

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

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

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



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