Sidebar

The API Corner: Diagnosing Decimal Data Errors

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

Consider the advantages of the Convert Hex to Character (cvthc) API.

 

In developing a general-purpose utility to detect decimal data errors, we have made use of a few APIs. In the article "In Search of Decimal Data Errors," we saw how the List Fields (QUSLFLD) API can be used to find all numeric fields, within a user-specified file record format, that are defined as either zoned decimal or packed decimal. In addition to discovering the data type of each field, we were also able to determine the name of the field, the number of decimal positions, the number of digits to the right of the decimal point, the number of bytes used to store the field value, and the starting location of the field within the record format.

In the article "Detecting Decimal Data Errors," we saw how the Copy Numeric Value (CPYNV) API can be used, in conjunction with the information obtained with the QUSLFLD API, to determine which field(s) in a record would cause a MCH1202 Decimal data error due to the encoding of the data found in a given zoned or packed numeric field.

This month, I will introduce another API, one that allows us to "see" the field value causing the MCH1202. While implementing this API, we'll also enhance the FNDDDE program in another way. This additional enhancement is to replace our previous use of the RPG dsply operation code with a printer file. When the file being examined for decimal data errors might contain millions of records, a report listing the errors could be a whole lot more useful than a series of dsplys.

The Find Decimal Data Errors Printer File

Here's the source for our new printer file, FNDDDEPRTF.

A         R HEADING                   SKIPB(2)                

A                                     5'FNDDDE'                

A                                   13'USER:'                

A           CURUSR       10A O   19                        

A                                   114                        

A                                     'PAGE:'                

A                                  120PAGNBR                  

A                                     EDTCDE(Z)              

*                                                            

A                                   13'FILE:'                

A                                    SPACEB(1)              

A           FILE_IN       10A O   19                        

A                                   60'FNDDDE ANALYSIS REPORT'

A                                   114'DATE:'                

A                                  120DATE(*JOB)          

A                                     EDTCDE(Y)              

*                                                            

A                                   114'TIME:'                

A                                    SPACEB(001)            

A                                   120TIME                    

***************************************************************

A         R RRN_VAL                   SPACEB(1)              

A                                    1'RRN:'                  

A           RELNO_C       10A       6SPACEA(1)              

***************************************************************

A         R FLD_VALS_C               SPACEB(1)              

A                                    5'FIELD:'                

A           FLDNAME       10       15                        

A           FLD_DATA     100A       30                        

***************************************************************

A         R FLD_VALS_H               SPACEB(1)              

A                                   28'X'''                  

A           FLD_DATA     100A       30                        

***************************************************************

A         R NBRSUM                                            

A                                     3'SUMMARY OF NUMERIC +    

A                                     DATA ANALYSIS'          

A                                     SPACEB(2)                

A                                     6'VALID NUMERIC VALUES:'  

A                                     SPACEB(1)                

A           GOODNBR       20 0     30EDTCDE(1)                

A                                    6'BLANK VALUES FOUND:'    

A                                     SPACEB(1)                

A           BLNKNBR       20 0     30EDTCDE(1)                

A                                     6'NON-BLANK VALUES FOUND:'

A                                      SPACEB(1)                

A           NONBLNKNBR   20 0     30EDTCDE(1)                

***************************************************************

A         R THEEND                                            

A           FLD_DATA     100A       1                        

A                                     SPACEB(2)                

A                                   53                        

A                                     '***** E N D O F R E +

A                                    P O R T *****'          

A                                     SPACEB(2)                

There are six record formats defined within FNDDDEPRTF:

  • HEADING provides a heading for each page of the report. This heading includes the name of the file being analyzed.
  • RRN_VAL provides the relative record number of a record within the file containing one or more decimal data problems.
  • FLD_VALS_C provides two pieces of information about each field found to have a decimal data problem: the name of the field and either the text 'BLANKS FOUND' or, if the field contains values other than all blanks, a character view of the data associated with the field.
  • FLD_VALS_H provides a hex view of the data causing the problem when the decimal data error is not due to all blanks being found in the field.
  • NBRSUM provides a summary of the data that was found in the file. This summary includes the number of numeric fields with valid encodings ("good" field values if you will), the number of numeric fields with invalid encodings due to all blanks being found in the field, and the number of numeric fields with invalid encodings due to at least one non-blank value being found in the field.
  • THEEND provides status information about the report in addition to identifying the end of the report.

Assuming that you store the preceding source in member FNDDDEPRTF of QDDSSRC, you can create the printer file using this command:

CRTPRTF FILE(FNDDDEPRTF) SRCFILE(QDDSSRC)

Using the printer file, as opposed to the previous RPG DSPLY operations, allows us to output a character view of the data in error using FNDDDEPRTF record format FLD_VALS_C. To try and display the character values using the DSPLY operation would be a bit dangerous as fully one fourth of all possible EBCDIC encodings are below x'40' and represent control codes (such as 5250 display attributes) which, if sent directly to a display, can cause all kinds of problems. As a significant percentage of encoded values could be below x'40', and not represent displayable characters, FNDDDE also uses the FLD_VALS_H record format to output the hexadecimal values associated with fields in error in a displayable form.

The Convert Hex to Character (cvthc) API

To output the hexadecimal values, FNDDDE uses the Convert Hex to Character (cvthc) API, which is documented in the ILE C/C++ MI Library Reference manual.

The cvthc API takes 4-bit values (nibbles) of a field and formats each nibble as a displayable character. If a given field, for instance, is defined as being two bytes in length and has a value of x'2611', then cvthc would return the 4-byte character string '2611'.

The cvthc API defines three parameters: the first parameter is the receiver variable where cvthc returns the character string representation of various nibbles, the second parameter is the source variable that is to be converted from nibbles to characters, and the third parameter, which is passed by value, is a 4-byte integer set to the number of nibbles in the source variable to be converted.

Note that there is no parameter where you tell the API how large the receiver variable is. It is the API caller's responsibility to ensure that the receiver variable is large enough to hold the resulting character stringbasically, that the allocated size of the receiver variable, in bytes, is at least twice the number of nibbles (the value passed in the third parameter) to be converted.

Changes to the FNDDDE Program

With that introduction to the cvthc API, here is the latest version of the FNDDDE program with changes from last month shown in bold. In the program, the cvthc API is prototyped using the name CvtFrmNibbles.

h DftActGrp(*No) BndDir('QC2LE')                                      

                                                                      

fFileX     if   f32766       disk   extfile(FileXVar) usropn        

f                                     infds(FileXDS)                  

fFndDDEPrtFo   e             printer infds(PrtFDS)                  

                                                                      

*********************************************************************

                                                                      

dFndDDE           pr                 extpgm('FNDDDE')                

d File_In                       10a   const                          

d Lib_In                       10a   const                          

                                                                      

dFndDDE           pi                                                  

d File_In                       10a   const                          

d Lib_In                       10a   const                          

                                                                      

*********************************************************************

                                                                    

d CpyN           pr                 extproc('_LBCPYNV')            

d Rcv                               like(Target)                  

d RcvAttr                       7a   const                          

d Src                               const like(Source)            

d SrcAttr                       7a   const                          

                                                                      

d CvtFrmNibbles   pr                 extproc('cvthc')              

d Rcv                         100a                                  

d Src                         50a   const                          

d Length                       10i 0 value                          

                                                                    

d CrtUsrSpc       pr                 extpgm('QUSCRTUS')            

d QualName                    20a   const                          

d XtndSpcAttr                 10a   const                          

d IntSize                     10i 0 const                          

d IntValue                     1a   const                    

d PubAut                       10a   const                    

d Text                         50a   const                    

d Replace                     10a   const options(*nopass)  

d ErrCde                             likeds(QUSEC)            

d                                    options(*nopass)        

d Domain                       10a   const options(*nopass)  

d TfrSiz                       10i 0 const options(*nopass)  

d OptSpcAlgn                   1a   const options(*nopass)  

                                                              

d GetFDefn       pr                                          

                                                              

d LogRecIDVals   pr                                            

                                                              

d LogNbrError     pr                                          

                                                              

d LstFld         pr                 extpgm('QUSLFLD')        

d QualUsrSpc                   20a   const                  

d Format                       8a   const                  

d QualFileName                 20a   const                  

d RcdFmt                       10a   const                    

d OvrPrc                       1a   const                  

d ErrCde                             likeds(QUSEC)          

d                                     options(*nopass)        

                                                              

d RmvPM           pr                 extpgm('QMHRMVPM')      

d CSE                         10a   const                  

d CSECtr                       10i 0 const                  

d MsgKey                       4a   const                    

d MsgToRmv                     10a   const                  

d ErrCde                             likeds(QUSEC)          

d LenCSE                       10i 0 const options(*nopass)  

d CSEQual                     20a   const options(*nopass)  

d RmvUnhExcp                   10a   const options(*nopass)  

d CSEType                     10a   const options(*nopass)  

d AlwDftRpyRej                 10a   const options(*nopass)  

                                                              

d RtvFD           pr                 extpgm('QDBRTVFD')      

d RcvVar                       1a   options(*varsize)      

d LenRcvVar                   10i 0 const                  

d QualNameRtn                 20a                            

d Format                       8a   const                  

d QualFileName                 20a   const                  

d RcdFmt                       10a   const                  

d OvrPrc                       1a   const                    

d System                       10a   const                  

d FmtType                     10a   const                  

d ErrCde                             likeds(QUSEC)          

                                                              

d RtvUsrSpcPtr   pr                 extpgm('QUSPTRUS')      

d QualUsrSpc                   20a   const                  

d UsrSpcPtr                     *                              

d ErrCde                             likeds(QUSEC)              

                                                                

d SndEscMsg       pr                                            

d MsgID_In                     7a   const                      

d MsgDta_In                   256a   const                      

                                                                

d SndPgmMsg       pr                 extpgm('QMHSNDPM')        

d MsgID                         7a   const                      

d MsgFile                      20a   const                      

d MsgDta                     256a   const options(*varsize)    

d LenMsgDta                   10i 0 const                      

d MsgType                     10a   const                      

d CSE                         10a   const options(*varsize )  

d CSECtr                       10i 0 const                      

d MsgKey                       4a                              

d ErrCde                             likeds(QUSEC)              

d                                     options(*varsize)              

d LenCSE                       10i 0 const options(*nopass)        

d QualCSE                     20a   const options(*nopass)        

d WaitTime                     10i 0 const options(*nopass)        

d CSEDtaType                   10a   const options(*nopass)        

d CCSID                       10i 0 const options(*nopass)        

                                                                    

d SndSysMsg       pr                                                

                                                                    

*********************************************************************

                                                                      

d CpyNFailure     c                   const(00202)                  

d MaxNbrNumFlds   c                   const(1000)                    

d Packed         c                   const(x'03')                  

d SpcSize         c                  const(1048576)                

d Zoned           c                   const(x'02')                  

                                                                    

*********************************************************************

                                                                    

* Structures related to API QDBRTVFD                                

                                                                    

d myQDBQ25_Ptr   s               *                                  

d myQDBQ25       ds                 likeds(QDBQ25)                

d                                     based(myQDBQ25_Ptr)            

                                                                    

d myQDBQ36_Ptr   s               *                                  

d myQDBQ36       ds                 likeds(QDBQ36)                

d                                     based(myQDBQ36_Ptr)            

                                                                      

* Structures related to API QUSLFLD                                

                                                                    

d LstFldHdr_Ptr   s               *                                  

d LstFldHdr       ds                  likeds(QUSH0100)              

d                                     based(LstFldHdr_Ptr)          

                                                                

d LstFld100_Ptr   s               *                              

d LstFld100       ds                 likeds(QUSL0100)          

d                                     based(LstFld100_Ptr)      

                                                                

d CurNbrNumFlds   s             5u 0                            

d NumFlds         ds                 qualified                  

d NumFldsArray                 21a   dim(MaxNbrNumFlds)        

d   FldName                     10a   overlay(NumFldsArray :1)  

d   Bytes                       5u 0 overlay(NumFldsArray :11)  

d   SrcAttr                     7a   overlay(NumFldsArray :13)  

d   Type                       1a   overlay(SrcAttr :1)        

d   Scale                       3u 0 overlay(SrcAttr :2)        

d   Digits                     3u 0 overlay(SrcAttr :3)        

d                               10i 0 overlay(SrcAttr :4)        

d                                     inz(0)                    

d   BfrStrPos                   5u 0 overlay(NumFldsArray :20)  

                                                                    

d FileXDS         ds                                                

d RelNo               397   400i 0                                

                                                                      

d PrtFDS         ds                                                

d OFLine               188   189i 0                                

d CurLine             367   368i 0                                

                                                                      

d PSDS           sds                                                

d ExcpID               40     46a                                  

d CurUsr               358   367a                                  

                                                                      

d ErrCde         ds                 qualified                      

d Hdr                               likeds(QUSEC)                  

d MsgDta                     256a                                  

                                                                    

*********************************************************************

                                                              

d BlnkNbr         s            20i 0                          

d FileXVar       s             21a                            

d GoodNbr         s             20i 0                          

d RecIDLogged     s               n                            

d MsgDta         s            256a                            

d MsgKey         s             4a                            

d NonBlnkNbr     s             20i 0                          

d NotMCH1202     s               n                            

d QualNameRtn     s            20a                            

d RcdFmt         s             10a                            

d Source         s           100a   based(Source_Ptr)        

d Source_Ptr     s               *                            

d Target        s           100a                            

                                                              

d X               s             10i 0                          

                                                              

*********************************************************************

                                                                    

/copy qsysinc/qrpglesrc,qdbrtvfd                                    

/copy qsysinc/qrpglesrc,qusec                                        

/copy qsysinc/qrpglesrc,qusgen                                      

/copy qsysinc/qrpglesrc,quslfld                                    

                                                                    

*********************************************************************

                                                                    

iFileX     ns                                                        

i                                 132766 InpBfr                    

                                                                    

*********************************************************************

                                                                    

/free                                                              

                                                                    

write Heading;                                                    

                                                                  

read FileX;                                                      

dow (not %eof(FileX));                                          

                                                                  

     for X = 1 to CurNbrNumFlds;                                  

         Source_Ptr = %addr(InpBfr) + NumFlds.BfrStrPos(X) - 1;  

                                                                  

         monitor;                                                

             CpyN(Target :NumFlds.SrcAttr(X)                        

                 :Source :NumFlds.SrcAttr(X));                    

             GoodNbr += 1;                                        

                                                                  

         on-error CpyNFailure;                                    

             if ExcpID = 'MCH1202';                                

               LogNbrError();                                    

             else;                                                

                NotMCH1202 = *on;                                  

             endif;                                            

                                                                

         on-error *all;                                        

             NotMCH1202 = *on;                                  

         endmon;                                              

     endfor;                                                  

                                                                

     read FileX;                                              

     RecIDLogged = *off;                                      

enddo;                                                        

                                                                

close FileX;                                                  

                                                                

if (CurLine + 5) >= OFLine;                                  

     write Heading;                                              

endif;                                                        

                                                                

write NbrSum;                                              

                                                              

if NotMCH1202;                                              

     Fld_Data = 'Other numeric errors also found';            

else;                                                      

     // Remove all messages UNLESS a non-MCH1202              

     // was received                                          

                                                              

     RmvPM('*' :0 :' ' :'*ALL' :ErrCde);                      

     Fld_Data = 'Data analysis was completed successfully.';  

endif;                                                      

                                                              

if (CurLine + 4) >= OFLine;                                

     write Heading;                                          

endif;                                                      

                                                              

write TheEnd;                                              

                                                                    

close FndDDEPrtF;                                                  

                                                                    

*inlr = *on;                                                        

return;                                                            

                                                                    

// *****************************************************************

                                                                      

begsr *inzsr;                                                      

                                                                    

   // Set API QUSEC parameter to send exceptions                    

                                                                      

   QUSBPrv = 0;                                                    

                                                                    

   // Set API ErrCde parameter to not send exceptions              

                                                                    

   ErrCde.Hdr.QUSBPrv = %size(ErrCde);                              

                                                                  

   GetFDefn();                                                  

                                                                  

   // Get list of File_In fields and field attributes            

                                                                  

   RtvUsrSpcPtr('QUSLFLD   QTEMP' :LstFldHdr_Ptr :ErrCde);      

                                                                  

   if ErrCde.Hdr.QUSBAvl > 0;                                    

       if ErrCde.Hdr.QUSEI = 'CPF9801';                          

         // Create user space if not found                      

                                                                  

         CrtUsrSpc('QUSLFLD   QTEMP' :' ' :SpcSize :x'00'        

                   :'*ALL' :'UsrSpc for QUSLFLD output'          

                   :'*YES' :QUSEC :'*USER' :0 :'1');            

                                                                  

         RtvUsrSpcPtr('QUSLFLD   QTEMP' :LstFldHdr_Ptr :QUSEC);  

      else;                                                      

         // Any other error is a hard failure                

                                                              

         SndSysMsg();                                        

       endif;                                                  

   endif;                                                    

                                                              

   LstFld('QUSLFLD   QTEMP' :'FLDL0100'                        

         :(File_In + Lib_In) :RcdFmt :'0' :QUSEC);            

                                                              

   for X = 1 to LstFldHdr.QUSNbrLE;                          

       if X = 1;                                              

           LstFld100_Ptr = LstFldHdr_Ptr + LstFldHdr.QUSOLD;  

       else;                                                  

           LstFld100_Ptr += LstFldHdr.QUSSEE;                  

       endif;                                                  

                                                              

       // Load up numeric fields into NumFldsArray            

                                                                    

       select;                                                      

           when LstFld100.QUSDT = 'S';                              

               CurNbrNumFlds += 1;                                

               NumFlds.FldName(CurNbrNumFlds) = LstFld100.QUSFN02;

              NumFlds.Bytes(CurNbrNumFlds) = LstFld100.QUSFLB;    

               NumFlds.Type(CurNbrNumFlds) = Zoned;                

               NumFlds.Scale(CurNbrNumFlds) = LstFld100.QUSDP;    

               NumFlds.Digits(CurNbrNumFlds) = LstFld100.QUSigits;

               NumFlds.BfrStrPos(CurNbrNumFlds) = LstFld100.QUSIBP;

                                                                    

           when LstFld100.QUSDT = 'P';                              

               CurNbrNumFlds += 1;                                

               NumFlds.FldName(CurNbrNumFlds) = LstFld100.QUSFN02;

               NumFlds.Bytes(CurNbrNumFlds) = LstFld100.QUSFLB;    

               NumFlds.Type(CurNbrNumFlds) = Packed;              

              NumFlds.Scale(CurNbrNumFlds) = LstFld100.QUSDP;    

               NumFlds.Digits(CurNbrNumFlds) = LstFld100.QUSigits;  

               NumFlds.BfrStrPos(CurNbrNumFlds) = LstFld100.QUSIBP;

                                                                    

           other;                                                    

               // Don't care about other types                      

       endsl;                                                      

   endfor;                                                          

                                                                    

   FileXVar = %trimr(Lib_In) + '/' + %trimr(File_In);              

   open FileX;                                                      

                                                                    

endsr;                                                            

                                                                    

/end-free                                                          

                                                                    

*********************************************************************

                                                                    

p LogNbrError     b                                              

d LogNbrError     pi                                              

                                                                  

/free                                                            

                                                                  

if (not RecIDLogged);                                          

     LogRecIDVals();                                              

endif;                                                          

                                                                  

FldName = NumFlds.FldName(X);                                  

                                                                  

if %subst(Source :1 :NumFlds.Bytes(X)) = *blanks;              

     if (CurLine + 1) >= OFLine;                                  

       write Heading;                                            

       LogRecIDVals();                                          

     endif;                                                      

                                                                  

     Fld_Data = 'BLANKS FOUND';                                    

     write Fld_Vals_C;                                              

                                                                    

     BlnkNbr += 1;                                                  

else;                                                            

     if (CurLine + 2) >= OFLine;                                    

       write Heading;                                              

       LogRecIDVals();                                            

     endif;                                                        

                                                                    

     Fld_Data = %subst(Source :1 :NumFlds.Bytes(X));                

     write Fld_Vals_C;                                              

                                                                    

     Fld_Data = *blanks;                                            

                                                                    

     if NumFlds.Bytes(X) < 50;                                      

       CvtFrmNibbles(Fld_Data :%subst(Source :1 :NumFlds.Bytes(X))

                     :(NumFlds.Bytes(X) * 2));                      

       %subst(Fld_Data :((NumFlds.Bytes(X) * 2) + 1) :1) = '''';  

     else;                                                          

      CvtFrmNibbles(Fld_Data :%subst(Source :1 :49) :98);        

       %subst(Fld_Data :99 :1) = '''';                          

     endif;                                                        

                                                                    

     write Fld_Vals_H;                                              

                                                                    

     NonBlnkNbr += 1;                                              

endif;                                                            

                                                                    

/end-free                                                          

                                                                    

p LogNbrError     e                                                

********************************************************************

                                                                    

p LogRecIDVals   b                                                

d LogRecIDVals   pi                                              

                                                                  

/free                                                            

                                                                    

if (CurLine + 5) >= OFLine;                                      

     write Heading;                                                

endif;                                                          

                                                                    

RelNo_C = %char(RelNo);                                          

write RRN_Val;                                                  

                                                                  

RecIDLogged = *on;                                              

                                                                  

/end-free                                                        

                                                                  

p LogRecIDVals   e                                                

*******************************************************************

                                                                  

p SndSysMsg      b                                                

d SndSysMsg       pi                                              

                                                                  

/free                                                              

                                                                  

if ErrCde.Hdr.QUSBAvl <= 16;                                    

     SndEscMsg(ErrCde.Hdr.QUSEI :' ');                            

else;                                                            

     SndEscMsg(ErrCde.Hdr.QUSEI                                    

               :%subst(ErrCde.MsgDta :1                            

                 :(ErrCde.Hdr.QUSBAvl - 16)));                    

endif;                                                            

                                                                  

/end-free                                                        

                                                                  

p SndSysMsg       e                                                

********************************************************************

                                                                    

p SndEscMsg       b                                                

d SndEscMsg       pi                                                

d MsgID_In                     7a   const                        

d MsgDta_In                   256a   const                        

                                                                    

/free                                                              

                                                                    

SndPgmMsg(MsgID_In :'QCPFMSG   *LIBL'                            

           :MsgDta_In :%len(%trimr(MsgDta_In))                    

           :'*ESCAPE' :'*PGMBDY' :1                                

           :MsgKey :QUSEC);                                        

                                                                    

/end-free                                                          

                                                                    

p SndEscMsg       e                                                

*******************************************************************

                                                                  

p GetFDefn       b                                                

d GetFDefn       pi                                              

                                                                  

/free                                                            

                                                                  

   // Get File_In definition and record format name              

                                                                  

   RtvUsrSpcPtr('QDBRTVFD QTEMP' :myQDBQ25_Ptr :ErrCde);        

                                                                  

   if ErrCde.Hdr.QUSBAvl > 0;                                    

       if ErrCde.Hdr.QUSEI = 'CPF9801';                            

         // Create user space if not found                        

                                                                  

          CrtUsrSpc('QDBRTVFD QTEMP' :' ' :SpcSize :x'00'        

                   :'*ALL' :'UsrSpc for QDBRTVFD output'      

                   :'*YES' :QUSEC :'*USER' :0 :'1');          

                                                                

         RtvUsrSpcPtr('QDBRTVFD QTEMP' :myQDBQ25_Ptr :QUSEC);

       else;                                                    

         // Any other error is a hard failure                  

                                                                

         SndSysMsg();                                          

       endif;                                                  

   endif;                                                      

                                                                

   RtvFD(myQDBQ25 :SpcSize :QualNameRtn :'FILD0100'            

         :(File_In + Lib_In) :'*FIRST' :'0' :'*LCL'            

         :'*EXT' :ErrCde);                                    

                                                                

   if ErrCde.Hdr.QUSBAvl > 0;                                  

       SndSysMsg();                                            

   endif;                                                        

                                                                  

   if %bitand(%subst(myQDBQ25.QDBBits27 :1 :1) :x'20') = x'20';  

       MsgDta = %trimr(Lib_In) + '/' + %trimr(File_In) +          

               ' is not a table/physical file. Command ended';  

                                                                  

       SndEscMsg('CPF9898' :MsgDta);                              

   endif;                                                        

                                                                  

   // Get record format name                                    

                                                                  

   myQDBQ36_Ptr = myQDBQ25_Ptr + myQDBQ25.QDBFOS;                

   RcdFmt = myQDBQ36.QDBFT01;                                    

                                                                  

/end-free                                                        

                                                                  

p GetFDefn       e                                              

Not counting the various changes that were made in support of using the printer file FndDDEPrtTF, the major change of interest can be found in the function LogNbrError.

The first change to LogNbrError is the use of indicator RecIDLogged to keep track of whether or not record information, such as the relative record number, has already been printed when a decimal data error is encountered within a record. RecIDLogged, which is turned "off" in the mainline of FndDDE when a new record from FileX is read, is used to avoid printing redundant relative record number information when a given FileX record contains more than one decimal data error. On entry to LogNbrError, if RecIDLogged is "off," then function LogRecIDVals is called. LogRecIDVals simply prints the current relative record number, sets RecIDLogged to "on," and returns.

LogNbrError then prints the name of the field in error and either the text 'BLANKS FOUND', if the field contains all blanks, or the contents of the field, if the field contains any non-blank values. When non-blank data values are encountered, LogNbrError first prints the character representation of the data found, followed by the character representation of the data nibbles found (using the cvthc API). As the printer file field Fld_Data is defined with a length of 100 bytes, there is a check to determine the length of the field in error. If the field length, in bytes, is less than 50, then all of the nibbles are converted to character form for printing; otherwise, only the nibbles associated with the first 49 bytes are converted to character form and printed. Since the allocated size of Fld_Data is 100 bytes, and printing the first 49 bytes of data requires 98 print positions (recall that there are two nibbles per byte), this allows room in Fld_Data for a closing apostrophe to follow the data that is in error.

A second API-related change to FNDDDE is the conditional use of the Remove Program Messages (QMHRMVPM) API, prototyped as RmvPM, when exiting the program and only MCH1202s were encountered when testing the zoned decimal and packed decimal numeric data found in FileX. While the use of the operation codes of MONITOR and ON-ERROR allow the FNDDDE program to continue running in the event an exception such as MCH1202 is received, the monitored message is also retained in the job log. Rather than cluttering up the job log with a potentially large number of MCH1202 messages, messages that FNDDDE both expects and handles, FNDDDE uses the QMHRMVPM API to remove all these messages. As an alternative implementation, FNDDDE could have removed the MCH1202s as they were received, rather than when exiting the program, but I elected to remove them en masse as I do not anticipate any errors other than MCH1202 will be encountered when testing the numeric fields. If you're interested in learning more about this rather handy API, refer to the earlier "API Corner" article "Removing Error Messages from the Job Log."

Assuming that you store the preceding source in member FNDDDE of QRPGLESRC, then you can create the utility program using this command:

CRTBNDRPG PGM(FNDDDE)

Diagnosing Why a Field Has a Data Decimal Error

Last month, we loaded the test file DDEDATA with both "good" and "questionable" data. Now, we'll run our updated version of FNDDDE using this command:

CALL PGM(FNDDDE) PARM(DDEDATA *LIBL)

This should result in a printed report similar to what's shown below (the headings are left out due to margin considerations).

RRN: 2                                          

   FIELD:   ZNDFLD1       BLANKS FOUND      

   FIELD:   PKDFLD1       BLANKS FOUND      

   FIELD:   PKDFLD2       001                

                           X'F0F0F1'            

   FIELD:   ZNDFLD3       BLANKS FOUND      

RRN: 4                                          

   FIELD:   PKDFLD1       at                

                           X'81A3'              

   FIELD:   PKDFLD2       oss                

                           X'96A2A2'            

   FIELD:   ZNDFLD3       ibleHere          

                           X'89829385C8859985'  

SUMMARY OF NUMERIC DATA ANALYSIS                          

     VALID NUMERIC VALUES:                           23      

     BLANK VALUES FOUND:                             3      

     NON-BLANK VALUES FOUND:                         4      

Data analysis was completed successfully.                    

For relative record number 2 of DDEDATA, FNDDDE is reporting four problems. Three of the fields (ZndFld1, PkdFld1, and ZndFld3) are found to contain all blanks, and one field (PkdFld2) is found to contain the character value '001' or, in hexadecimal form, x'F0F0F1'. The cases where all blanks are found is easy enough to understand (and one I'm sure many of you have run into before), but what's wrong with the PkdFld2 value of '001'?

If you review the DDS defining DDEDATA or use the Display File Field Description command specifying FILE(DDEDATA), you'll see that field PkdFld2 is defined as being packed decimal. The problem is that the value x'F0F0F1' does not conform to the encoding rules of packed decimal data, rules which are introduced here in the ILE RPG Language Reference manual and further expanded on in the Machine Interface Concepts discussion of Arithmetic Operations under Packed Decimal Computation.

The system requires that packed decimal data have all nibbles except the last in the range of '0' through '9', with the last nibble (representing the sign) being in the range of 'A' through 'F' (where 'B' or 'D' represents a negative sign and 'A', 'C', 'E', or 'F' a positive sign). PkdFld2's value of x'F0F0F1' fails to meet these requirements in four of the six nibbles; the first, third, and fifth nibbles are 'F' (not '0' through '9') and the last nibble is '1' (not 'A' through 'F').

The value of PkdFld2 does, however, meet the encoding requirements of zoned decimal data, documented here in the ILE RPG Language Reference, where the second nibble of each byte must be in the range of '0' through '9' (the '0', '0', and '1' of x'F0F0F1') and the first nibble of the last byte must be in the range of 'A' through 'F' (the third 'F' of x'F0F0F1'), representing the value 1+. In the case of DDEDATA, this encoding of PkdFld2 as zoned decimal is just a curiosity, but in the real world, where data might be coming from another system/company, it could also, if a pervasive cause of decimal data errors, indicate an incorrect data definition in either the originator of the data or the recipient of the data.

Let's now look at the data associated with relative record number 4. Three of the fields (PkdFld1, PkdFld2, and ZndFld3) are identified in the report as being in error. With our previous discussion of the encoding requirements for packed decimal and zoned decimal fields, and the hexadecimal values being shown for these fields, you should be able to identify what is wrong with these fields. In the case of PkdFld1, there is an invalid 'A' where a number is required and an invalid sign value of '3'; in the case of PkdFld2, two invalid 'A' values and a bad sign ('2'); and in the case of ZndFld3, an invalid '8' where the sign is expected. Note that while there are a variety of both numeric and alphabetic values ('8's, '9's, and even a 'C') in the first nibble of various bytes of ZndFld3, this is not an error as only the first nibble of the last byte (the sign nibble) is used when working with zoned decimal fields. Change the second 'e' of 'Here' in the LOADDDE program to a '5' (that is, 'ibleHer5') and you'll find that ZndFld3 now has the value of 92358595+. Change the 'e' to 'N' and ZndFld3 is now 92358595-. The reason for this is that the '5' provides a valid positive sign ('5' is x'F5') and the 'N' a valid negative sign ('N' is x'D5').

A minor item to point out, related to the byte of data providing the sign value, is that when a numeric field such as PkdFld1 of relative record number 2 is all blanks, it's really only the byte containing the sign that is causing the decimal data error. The blank character is x'40', and neither the '4' for zoned decimal fields or the '0' for packed decimal fields will yield a valid sign value (which is 'A' through 'F'). All of the other bytes, however, are quite valid in that the '0's represent a valid numeric digit for zoned decimal and both the '4's and '0's represent valid numeric digits for packed decimal fields.

Continuing to look at relative record number 4, you might notice that the fields ZndFld1 and ZndFld2 are not included in the FNDDDE report even though the loaded values are the character strings 'dD' and 'IsP', respectively. Given the previous paragraph, you can probably guess what's happening. If you write a program (using the cvthc API, of course) to display the hexadecimal values of the character strings 'dD' and 'IsP' in character form, you will find that these field values are x'84C4' and x'C9A2D7', respectively. These values do conform to the rules of zoned decimal encodings and result (as we now know) in the numeric values of 44+ and 927- (or more accurately 92.7- as ZndFld2 is defined with one digit to the right of the decimal point). Due to the context of how these values are setas part of the larger character string 'BadDataIsPossibleHere'I would consider these numeric values to be bogus (though "good" in that they do not generate decimal data errors) and not "right" for processing. The key item here is that there can be data problems above and beyond decimal data errors.

By now, you most likely know why the sixth record of DDEDATA, loaded with the rather strange character string of '()E5q?xyz1-/"s0AT0J0D', doesn't show up in the FNDDDE report at all. That odd character string happens to result in hexadecimal values that conform to the rules for zoned decimal and packed decimal encodings. Verifying this, with the help of the cvthc API, is left as an exercise for you.

Next month's article will be the last planned change to the FNDDDE program. In addition to providing the relative record number of any record containing decimal data errors (which is currently being done), FNDDDE will be enhanced to also print the key values (assuming the file is keyed, of course) associated with any records containing decimal data errors. Certainly a nice feature if you want to "fix" the data.

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.. I'll see what I can do about answering your burning questions in future columns.

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.