Sidebar

The API Corner: Determining How Many and What Jobs Are Currently Active

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

 

Today, we'll extend our API suite using the List Jobs System API.

 

In the last API Corner article, "Determining Whether Jobs Are Currently Active," we created the service program (*SRVPGM) JOBCHKS. The *SRVPGM exported the function JobActive, which defined one input parameter and returned an indicator. The input parameter could be a simple job name such as DAYEND, a generic job name such as DAYEND*, or a special value such as *CURRENT. If one or more jobs with the specified job name was active, JobActive returned an indicator value of '1'; otherwise, it returned a value of '0'. In this article, we will extend JOBCHKS with another API of our own creation. This API, named JobsActive, will return the number of active jobs with the specified job name and optionally return one or more of the fully qualified job names matching the specified job name.

As we did for JobActive, we'll provide the prototype for JobsActive in source member JobChksPR of QRPGLESRC. The updated source for JobChksPR is this:

/if not defined(JobChks_Prototypes)                    

                                               

d JobActive       pr              n                    

d  JobName                      10a   const                  

                                     

d JobsActive      pr            10i 0                   

d  JobName                      10a   const                  

d  JobLst                        1a   options(*nopass :*varsize)

d  SizJobLst                    10i 0 const options(*nopass)    

                                              

 /define JobChks_Prototypes                          

 /endif               

JobsActive defines one required parameter, JobName; two optional parameters, JobLst and SizJobLst, respectively; and a signed integer return value representing the number of active jobs matching the value of JobName. The JobName parameter, as with the JobName parameter of the JobActive function, can be a simple job name, a generic job name, or one of three special values (*, *CURRENT, or *ALL). JobLst is an optional parameter that is defined as being variable length and can be used to have JobsActive return a list of jobs that are active and match the JobName parameter criteria. SizJobLst is also an optional parameter and represents the size of the JobLst parameter passed to JobsActive. If the SizJobLst parameter is not provided when calling JobsActive, then the JobLst parameter will not be used even if passed.

The JobLst parameter is defined as a data structure of variable length. The first element of the data structure is a 4-byte integer representing the number of qualified job names actually returned in the JobLst parameter. Immediately following this 4-byte integer is an array of qualified job names with each qualified job name being defined as a 10-byte simple job name, a 10-byte user name, and a 6-byte job number. The allocated size of the array, as opposed to the dimensions of the array, is determined by the SizJobLst parameter value less four bytes for the number of qualified job names being returned. The caller of JobsActive can, for instance, allocate the following JobInfo data structure and pass this data structure as the JobLst parameter (along with %size(JobInfo) as the SizJobLst parameter) if they want up to 10 active job names to be returned.

d JobInfo         ds                                        

d  JobsRtnd                     10i 0                       

d  Job                          26a   dim(10)              

d   JobNam                      10a   overlay(Job :1)       

d   JobUsr                      10a   overlay(Job :11)      

d   JobNbr                       6a   overlay(Job :21)      

If the caller wants up to 100 active job names, then they can simply change the dim(10) specification for subfield Job to dim(100) and recompile the calling application program. Using %size(JobInfo) for the SizJobLst parameter when calling JobsActive will then inform the JobsActive function that there is sufficient room in JobLst for up to 100 job entries.

With that introduction to JobsActive out of the way, let's see what needs to be changed relative to the JOBCHKS *SRVPGM. First, we need to define JobsActive as an export of JOBCHKS, so here is the updated source member JOBCHKS of source file QSRVSRC.

StrPgmExp  PgmLvl(*Current) Signature('JOBCHKS')    

  Export     Symbol("JOBACTIVE")                    

  Export     Symbol("JOBSACTIVE")                    

EndPgmExp           

Second, we need to actually implement JobsActive, so here is the updated QRPGLESRC source for JOBCHKS itself.

h nomain                                                                  

                                                                           

d GetJobList      pr                                                      

d  JobName                      10a   const                               

d  Status                       10a   const                                

                                                                           

 /copy qrpglesrc,JobChksPR                                                

                                                                           

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

                                                                           

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 LstJobs         pr                  extpgm('QUSLJOB')                

d  QualUsrSpcN                  20a   const                            

d  Format                        8a   const                            

d  QualJobName                  26a   const                            

d  Status                       10a   const                            

d  ErrCde                             likeds(QUSEC) options(*nopass)   

d  JobType                       1a   const options(*nopass)           

d  NbrFldsRtn                   10i 0 const options(*nopass)           

d  FldKeys                      10i 0 const options(*nopass)           

d  CntHandle                    48a   const options(*nopass)           

                                                                        

d RtvUsrSpcPtr    pr                  extpgm('QUSPTRUS')               

d  QualUsrSpcN                  20a   const                            

d  UsrSpcPtr                      *                                    

d  ErrCde                             likeds(QUSEC) options(*nopass)   

                                                                        

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

                                                                   

d JobHdrPtr       s               *                               

d LJobHdr         ds                  likeds(QUSH0100)            

d                                     based(JobHdrPtr)            

                                                                   

d JobDtaPtr       s               *                               

d LJobDta         ds                  likeds(QUSL010002)          

d                                     based(JobDtaPtr)            

                                                                   

d                sds                                               

d curJobName            244    269                                

                                                                   

d ErrCde          ds                  qualified                   

d  Hdr                                likeds(QUSEC)               

d  MsgDta                      256a                               

                                                                   

 /copy qsysinc/qrpglesrc,qusec                                    

 /copy qsysinc/qrpglesrc,qusgen                                   

 /copy qsysinc/qrpglesrc,qusljob                                  

                                                                   

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

                                                                   

p JobActive       b                   export                      

d JobActive       pi              n                               

d  JobName                      10a   const                       

                                                                   

 /free                                                            

                                                                   

  QUSBPrv = 0;                                                     

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

                                                                   

  if %subst(JobName :1 :1) = '*';                                 

     return *on;                                                  

  endif;                                                          

                                                                   

  GetJobList(JobName :'*ACTIVE');                                  

                                                                   

  return (LJobHdr.QUSNbrLE <> 0);                                 

                                                                   

 /end-free                                                           

                                                                     

p JobActive       e                                                 

                                                                     

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

                                                                     

p JobsActive      b                   export                        

d JobsActive      pi            10i 0                               

d  JobName                      10a   const                         

d  JobInfo                       1a   options(*nopass :*varsize)    

d  SizJobInfo                   10i 0 const options(*nopass)        

                                                                     

d JobInfHdrPtr    s               *                                 

d JobsRtnd        s             10i 0 based(JobInfHdrPtr)           

                                                                     

d JobInfDtaPtr    s               *                                 

d JobInf          ds                  based(JobInfDtaPtr)           

d  JobNam                       10a                                  

d  JobUsr                       10a                                 

d  JobNbr                        6a                                 

                                                      

d SizRcvVar       s             10i 0                

                                                      

 /free                                               

                                                      

  QUSBPrv = 0;                                       

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

                                                      

  if %parms() >= 3;                                  

     SizRcvVar = SizJobInfo;                         

  else;                                              

     SizRcvVar = 0;                                   

  endif;                                             

                                                      

  if JobName = '*';                                  

     if SizRcvVar >= %size(JobsRtnd);                

        JobInfHdrPtr = %addr(JobInfo);               

        SizRcvVar -= %size(JobsRtnd);                

                                                      

        if SizRcvVar >= %size(JobInf);               

           JobInfDtaPtr = %addr(JobInfo) + %size(JobsRtnd);     

           JobInf = curJobName;                                 

           JobsRtnd = 1;                                        

        else;                                                   

           JobsRtnd = 0;                                         

        endif;                                                  

     endif;                                                     

                                                                 

     return 1;                                                   

  endif;                                                        

                                                                 

  GetJobList(JobName :'*ACTIVE');                               

                                                                 

  if SizRcvVar >= %size(JobsRtnd);                              

     JobInfHdrPtr = %addr(JobInfo);                             

     JobsRtnd = 0;                                              

                                                                 

     SizRcvVar -= %size(JobsRtnd);                              

                                                                 

     dow ((SizRcvVar >= %size(JobInf)) and                       

          (JobsRtnd < LJobHdr.QUSNbrLE));                        

         if JobsRtnd = 0;                                        

            JobDtaPtr = JobHdrPtr + LJobHdr.QUSOLD;              

            JobInfDtaPtr = %addr(JobInfo) + %size(JobsRtnd);     

         else;                                                   

            JobDtaPtr += LJobHdr.QUSSEE;                         

            JobInfDtaPtr += %size(JobInf);                        

         endif;                                                  

                                                                  

         JobNam = LJobDta.QUSJNU;                                

         JobUsr = LJobDta.QUSUNU;                                 

         JobNbr = LJobDta.QUSJNbrU;                              

                                                                  

         JobsRtnd += 1;                                          

         SizRcvVar -= %size(JobInf);                             

     enddo;                                                      

  endif;                                                         

                                                                  

  return LJobHdr.QUSNbrLE;                                       

                                                                  

 /end-free                                                      

                                                                 

p JobsActive      e                                             

                                                                 

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

                                                                 

p GetJobList      b                                             

d GetJobList      pi                                            

d  JobName                      10a   const                     

d  Status                       10a   const                      

                                                                 

 /free                                                          

                                                                 

  // Get addressability to Job List *USRSPC                     

                                                                 

  RtvUsrSpcPtr('JOBLIST   QTEMP' :JobHdrPtr :ErrCde);           

                                                                 

  if ErrCde.Hdr.QUSBAvl = 0;                                    

     // All is OK                                               

                                                                 

  else;                                                               

     // Assume UsrSpc not found, so create it                        

                                                                      

     CrtUsrSpc('JOBLIST   QTEMP' :'JobList' :4096                    

               :x'00' :'*ALL' :'Used by JobChks'                     

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

                                                                      

     RtvUsrSpcPtr('JOBLIST   QTEMP' :JobHdrPtr :QUSEC);               

  endif;                                                             

                                                                      

  LstJobs('JOBLIST   QTEMP' :'JOBL0100'                              

          :(JobName + '*ALL      ' + '*ALL  ')                       

          :Status :QUSEC);                                           

                                                                      

 /end-free                                                           

                                                                      

p GetJobList      e                                                  

There are a few additions to the global definitions of the JOBCHKS module:

  1. 1.Defining the pointer variable JobDtaPtr and the data structure LJobDta, which is based on JobDtaPtr. In the previous article, we utilized the List Job (QUSLJOB) API in procedure GetJobList but never actually examined the list of jobs returned. In this article, we will (in some code paths) be using this list, and the variables JobDtaPtr and LJobDta are used to point to a list entry and define the contents of a list entry, respectively. LJobDta is defined like the QSYSINC/QRPGLESRC, QUSLJOB IBM-provided data structure QUSL010002. QUSL010002 provides the definition of QUSLJOB's format JOBL0100, which is what is requested in the GetJobList procedure
  2. 2.Inclusion of the program status data structure (PSDS) with the subfield curJobName to provide easy access to the qualified job name of the current job. The PSDS will be used when the '*' special value is passed by the caller for the JobName parameter of JobsActive.
  3. 3.Copying of the IBM-provided QSYSINC/QRPGLESRC,QUSLJOB API definitions. This is done in support of point 1 above.

The next set of changes in JOBCHKS is the exported procedure JobsActive itself.

The local definitions for JobsActive are these:

  1. 1.The pointer variable JobInfHdrPtr and the integer variable JobsRtnd, which is based on JobInfHdrPtr. When the caller of JobsActive passes a JobInfo parameter that is 4 bytes or larger in size, JobRtnd is used to return the number of qualified job names that are returned in the JobInfo parameter.
  2. 2.The pointer variable JobInfDtaPtr and the data structure JobInf, which is based on JobInfDtaPtr. When the caller of JobsActive passes a JobInfo parameter that is 30 bytes or larger in size, JobInf is used to return the qualified job names in the JobInfo parameter.
  3. 3.The integer variable SizRcvVar, which is used to track the size of available storage in the JobInfo parameter to return qualified job name information in.

Moving on to the actual processing of JobsActive, we start (as we did in the previous JobActive procedure) by setting the two instances of the API error code structure, QUSEC and ErrCde, to appropriate values for sending escapes and not sending escapes, respectively.

Following this, JobsActive checks to see if the SizJobInfo parameter was passed by the caller. If the parameter was passed, then SizRcvVar is set to the value of SizJobInfo; otherwise, SizRcvVar is set to zero.

A check is then made for a JobName special value of '*', indicating that a check for only the current job is needed. In the previous JobActive procedure, any of the supported special values resulted in JobActive returning a value of '1' to indicate that yes, at least one job is currently active on the system, and for performance reasons, we could bypass the actual calling of the QUSLJOB API. In the case of JobsActive, which returns the number of jobs active on the system for the given JobName, we can only bypass calling QUSLJOB in the case of the '*' special value. With an input value of '*', we know only one "current" job is active, while the special values '*CURRENT' and '*ALL' are quite likely (and guaranteed in the case of '*ALL') to have multiple currently active jobs on the system.

If JobName is '*', JobsActive determines if there is sufficient available storage in the JobInfo parameter to return the number of active jobs returned (that is, SizRcvVar is greater than or equal to the size of JobsRtnd). If there is not sufficient storage, then JobsActive simply ends with no additional processing, returning an active job count of 1.

If there is sufficient storage, JobsActive sets JobInfHdrPtr to the address (location) of the JobInfo parameter, decrements the amount of available storage in JobInfo by the size of the number of jobs returned, and determines if there is sufficient remaining storage in the JobInfo parameter to return the qualified job name of the current job (SizRcvVar is greater than or equal to the size of the JobInf data structure). If there is not sufficient storage, JobsActive sets the number of jobs returned (JobsRtnd) to 0 and ends, returning an active job count of 1. If there is sufficient storage, JobsActive sets JobInfDtaPtr to the address of where to return the qualified job name, sets JobInf to the current job name using the job name found in the PSDS, sets the number of jobs returned to 1, and returns an active job count of 1.

If JobName is not the special value '*', JobsActive calls the GetJobList procedure of the previous article to get a list of jobs (using the QUSLJOB API) that are currently active with the specified JobName. There are no changes this month in the processing of the GetJobList procedure, but, unlike JobActive, which simply examined the number of jobs returned by the QUSLJOB API, JobsActive may process the returned job entries.

After calling GetJobList, JobsActive determines, using the same method of how the special JobName value of '*' was handled, if there is sufficient available storage in the JobInfo parameter to return the number of active jobs returned. If there is not sufficient storage, then JobsActive ends, returning the number of active jobs returned by the QUSLJOB API (LJobHdr.QUSNbrLE). Please note that relative to this return value there is a "qualifier" at the end of the article related to the accuracy of this returned active job count.

If there is sufficient storage, JobsActive sets JobInfHdrPtr to the address (location) of the JobInfo parameter, sets the number of jobs returned to 0, decrements the amount of available storage in JobInfo by the size of the number of jobs returned, and enters into a DOW, which will return those active qualified job names that will fit in the remaining storage of the JobInfo parameter.

The DOW is run while two conditions remain true. The conditions are that there is sufficient available storage in JobInfo to return another qualified job name (SizRcvVar is greater than or equal to the size of the JobInf data structure) and that there are additional active jobs to be returned (that is, the number of jobs currently being returned in JobInfo, JobsRtnd, is less than the number of active jobs returned by the QUSLJOB API, LJobHdr.QUSNbrLE). While these two conditions are true, JobsActive sets the pointer JobDtaPtr to the address of the next QUSLJOB active job entry to be processed, sets the pointer JobInfDtaPtr to the address of where to return the next qualified job name within JobInfo, sets the qualified job name within JobInfo (JobNam, JobUsr, and JobNbr) from the QUSLJOB entry, increments the number of active jobs returned in JobInfo (JobsRtnd) by one, and decrements the amount of available storage within JobInfo (SizRcvVar) by the size of JobInf. The DOW condition for SizRcvVar being greater than or equal to the size of the JobInf data structure is what prevents JobsActive from returning partial qualified job names.

Within this DOW, there is processing conditioned by whether or not JobsActive is working with the first active job to be returned or with a subsequent active job that is to be returned. In the case of returning the first active job, the pointer variable JobDtaPtr, used to access the QUSLJOB active job entry, is set by taking the address of the start of the user space containing the QUSLJOB API list (JobHdrPtr) and adding the offset to the first API returned job entry (LJobHdr.QUSOLD) while the pointer variable JobInfDtaPtr, used to return the next qualified job name within JobInfo, is set by taking the address of the start of the JobInfo parameter and adding the size of JobsRtnd (which precedes the returned list within the JobInfo parameter). When returning an active job that is not the first job returned in JobInfo, the pointer variable JobDtaPtr is incremented by the size of each QUSLJOB API returned entry (LJobHdr.QUSSEE) while the pointer variable JobInfDtaPtr is incremented by the size of each qualified job name return in the JobInfo parameter (%size(JobInf)).

When the DOW is exited, JobsActive ends, returning the number of active jobs returned by the QUSLJOB API.

Assuming that the above source is stored in member JOBCHKS of source file QRPGLESRC, you can create the JOBCHKS *MODULE and *SRVPGM using these two commands:

CRTRPGMOD MODULE(JOBCHKS)

CRTSRVPGM SRVPGM(JOBCHKS)

We're now ready to start using the JobsActive function within our application code. The updated source for our test program UseJobChks is shown below.

h dftactgrp(*no) bnddir('SOMETOOLS')                        

                                                             

d UseJobChks      pr                                        

d  JobName                      10a   const                 

                                                             

d UseJobChks      pi                                        

d  JobName                      10a   const                 

                                                             

 /copy qrpglesrc,JobChksPR                                  

                                                             

d JobInfo         ds                                        

d  JobsRtnd                     10i 0                       

d  Job                          26a   dim(100)              

d   JobNam                      10a   overlay(Job :1)       

d   JobUsr                      10a   overlay(Job :11)      

d   JobNbr                       6a   overlay(Job :21)      

                                                             

d X               s             10i 0                       

                                                             

 /free                                                       

                                                             

  if JobActive(JobName);                                    

     dsply 'It is active';                                  

  else;                                                      

     dsply 'Not active right now';                          

  endif;                                                    

                                                             

  dsply (%char(JobsActive(JobName)) + ' active jobs');      

                                                             

  JobsActive(JobName :JobInfo :%size(JobInfo));             

  for X = 1 to JobsRtnd;                                    

      dsply (%trimr(JobNam(X)) + '/' +                      

             %trimr(JobUsr(X)) + '/' +                      

             JobNbr(X));                                    

  endfor;                                                   

                                                             

  *inlr = *on;                                              

  return;                                                   

                                                             

 /end-free    

These are the updates:

  1. 1.The definition of a JobInfo data structure. This data structure defines the subfield JobsRtnd to know how many active qualified job names are returned in JobInfo and the array Job. Job is defined as an array of 100 elements, each element representing a qualified job name.
  2. 2.The definition of a signed integer variable X. This variable will be used to index the Job array of JobInfo.
  3. 3.A dsply of the number of active jobs. This demonstrates calling JobsActive with only one parameter, the job name.
  4. 4.A dsply of the active qualified job names. This demonstrates calling JobsActive with all three parameters and then processing the returned list of active jobs.

To compile our sample program you can use this command:

CRTBNDRPG PGM(USEJOBCHKS)

To test the UseJobChks program with a job name of 'Q*', you can use this:

CALL PGM(USEJOBCHKS) PARM(Q*)  

Assuming there are jobs on the system starting with the letter 'Q', this should result in messages similar to the following:

CALL PGM(USEJOBCHKS) PARM(Q*)     

DSPLY  It is active               

DSPLY  2314 active jobs           

DSPLY  QSYSARB/QSYS/541096        

DSPLY  QSYSARB2/QSYS/541097       

DSPLY  QSYSARB3/QSYS/541098       

DSPLY  QSYSARB4/QSYS/541099       

DSPLY  QSYSARB5/QSYS/541100   

DSPLY  QLUS/QSYS/541101       

DSPLY  QDBSRV01/QSYS/541104   

DSPLY  QDBSRV02/QSYS/541105   

DSPLY  QDBSRV03/QSYS/541106    

In this article, we've seen how to access the first entry of a list of entries returned by a list API such as QUSLJOB and then how to access subsequent entries within the list. With the number of list APIs on the system, this knowledge can be quite useful.

We've also seen how to provide our own API wrapper, JobsActive, around a system API such as QUSLJOB. One benefit of this wrapper approach is that we can provide customized system-level information (such as the Job array of UseJobChks) to application developers without the application developers needing to know how to call system APIs directly.

A second benefit of the wrapper is that we might better understand a fairly common warning found in the documentation of many system APIs. This warning is related to APIs that return data in output parameters (like the JobLst parameter of JobsActive) and have a "Length of" parameter where you provide the size of the output parameter (like the SizJobLst parameter of JobsActive). The warning itself is "If the length is larger than the size of the receiver variable, the results may not be predictable," and this warning certainly applies to JobsActive.

You may or may not have noticed that while the sample program UseJobChks defines the array Job to process the returned active jobs, JobsActive has no such array. JobsActive uses based storage to return active job information to its caller and has no clue as to how its caller, UseJobChks in our case, has defined this storage. The caller may have defined the storage related to JobLst qualified job names using:

  1. 1.an array approach such as UseJobChks (with whatever array dimensions you might want10, 100, 500, etc.)
  2. 2.one big character variable that will be accessed using operators such as %subst
  3. 3.a data structure with specific subfields such as JobName1, JobUser1, JobNbr1, JobName2, JobUser2, JobNbr2, etc.
  4. 4.a variety of other approaches

 

All of these approaches will work just fine as the only thing JobsActive (and system APIs) care about is the size of the receiver variable where information is to be returned, not how you have elected to define your use of this storage. In UseJobChks, we use %size(JobInfo) to have the RPG compiler determine the correct SizJobLst value to pass to JobsActive.

A "rookie" mistake would be to hardcode the SizJobLst value. Let's say our rookie determined the size of JobLst as 2604 by multiplying the number of Job dimensions (100) by the size of one Job entry (26) plus 4 for JobsRtnd. If the developer then codes JobsActive('Q*' :JobInfo :2604); no harm is done. But if they make a typo and code the third parameter as 3604 rather than 2604, then problems could occur. If there are only 50 active jobs, then they'll get back the qualified job names of the 50 jobs. If there are 200 active jobs, then they'll get back the qualified job names of 138 jobs (what will fit in 3604 bytes). As Job is only allocated for 100 jobs, where do the other 38 qualified job names go? This is where "the results may not be predictable" warning comes into play.

We can safely say the 988 bytes associated with the 38 qualified job names will go immediately after the first 100 qualified job names that are returned. The question is, what was previously in those 988 bytes and has now been overwritten? It might have been a variable in UseJobChks that was used before calling JobsActive and isn't used after the call, it might have been a variable in UseJobChks that now has a "strange" value that will be used after the call, it might have been an RPG run-time control area so rather strange RPG errors might start showing up in the program (like files "closed" when you know they're "open"), it might have been a variable in another program (that will "blow up" much later for no apparent reason), it might have been an RPG run-time control area in another program, it might have been storage beyond the end of the current activation group, or it might have been any combination of the above (and the combination can change based on your programs being recompiled and/or different programs being called in the current job). This is not a good situation to be in, and this is why we want to make sure the specified length of the receiver variable parameter is not larger than the allocated size of the receiver variable when calling an API. Using a built-in such as %size for length parameters is definitely the way to go. A variation of this, and one that I have seen more than once, is when the user of the API correctly hardcoded the length of the receiver variable (let's say 2604 for 100 returned entries as in our UseJobChks example), but a year later the UseJobChks source was copied for another project, and it was determined that this new project only needed 10 returned entries, so the dim(100) was changed to dim(10) without changing the 2604 value. Care to guess what will happen at some point in the future? There are other reasons for using %size beyond this concern for unpredictable results, but this is the major one.

Before closing, two other points need to be discussed.

The first point is relative to the accuracy of the number of active jobs value returned by JobsActive. What is being returned is the number of list entries returned by the QUSLJOB API, and this value may or may not represent all active jobs with the specified JobName. The QUSLJOB API returns the active job list in a user space and the maximum size of a user space is roughly 16MB. This size is more than sufficient to return in excess of 250,000 job entries, but what if there are 450,000 active jobs? Note that I have no idea if anyone is running this number of active jobs in 2014, but the documented maximum of all jobs on the system (active, on a *JOBQ, or ended with spooled output) is 485,000 jobs, and this number of jobs will not fit in one user space. With the current coding of JobsActive, I've taken the simplistic approach of just returning a big number representing the number of active jobs that are returned by the first call to QUSLJOB and not caring if the actual number of active jobs might be higher.

If I did care, then the following changes could be made:

  1. 1.After processing all entries returned by the QUSLJOB API, check the value of the Information Status field in the List API Generic Header (LJobHdr.QUSIS).
  2. 2.If the information status value is 'C' (complete), then all job entries have been returned and LJobHdr.QUSNbrLE is accurate, so JobsActive can end, returning LJobHdr.QUSNbrLE.
  3. 3.If the information status value is 'P' (partial), then there are more job entries that could be returned. In this case, JobsActive could:
    1. a.Store the value of LJobHdr.QUSNbrLE.
    2. b.Call the QUSLJOB API again asking for the next set of entries following the initial set of entries (that is, another 250,000+ active jobs). To get this next set of entries, this subsequent call to QUSLJOB would utilize the Continuation handle parameter, setting the parameter to the continuation handle value provided in the API specific Header Section.
    3. c.Process the returned entries (if there's still available storage in JobInfo).
    4. d.Add the LJobHdr.QUSNbrLE value of this API call to the previously stored value of previous API calls.
    5. e.Go back to step 1 and replace the step 2 returning of LJobHdr.QUSNbrLE with the returning of the stored value of all accumulated LJobHdr.QUSNbrLE values.

Using this continuation handle approach, we can process list API output (like that of QUSLJOB) even though the number of entries exceeds the capacity of a single user space. This use of continuation handles may not apply to many of you in the case of listing jobs in an active status, as done with our calls to GetJobList where the second parameter is '*ACTIVE', but QUSLJOB does support other status values, such as '*ALL', and I've certainly been on systems where the number of all jobs on the system would exceed the number of entries that can be returned in one user spacerequiring the use of the continuation handle parameter.

The second point I would like to make is that I somewhat short-changed the reader in terms of how JobsActive implements support for the JobName special value '*'. I used the RPG PSDS to obtain the qualified job name of the current job, but, as this is The API Corner, I might have demonstrated the use of an API to access the current job's qualified job name. If you know that you're interested in a specific job (like the current job), rather than a list of jobs, then there are several system APIs available to directly return this job information through a receiver variable. As an exercise, can you find at least one API to directly return the qualified job name of the current job? I found four rather quickly, though I anticipate most readers finding one particular API first. If you are not able to find an API to retrieve the current job's qualified name, you might want to refer to the 7.1 Information Center and search on the words "Retrieve Job Information." I want to avoid providing the API name in this article, but you should find a link to this API in the result list of your search.

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.