02
Sat, Nov
2 New Articles

The API Corner: Retrieving Information, Continued

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

What would be required to reverse the order of displayed call stack entries? In this article, we'll look at one way to accomplish this.

 

When we left off in the previous article, "The API Corner: Retrieving Information, Part II," we were successfully displaying the call stack of the current thread, with the current procedure being shown at the top of the listing. But various system functions, such as the Display Job (DSPJOB) command, show the call stack with the initial program or procedure first and the current procedure last. To mimic this behavior, what would be required?

 

One immediate problem is that while format CSTK0100 of the Retrieve Call Stack (QWVRCSTK) API gives great information when moving forward through the call stack entries (the length of this call stack entry field QWVEL providing a displacement value to move from one entry to the next), there isn't anything related to moving backward through the list of variable-length entries. We could maintain an array of the pertinent information (perhaps the offsets to each entry or the program and procedure names themselves) as we move through the call stack entries and then display this information processing the array in reverse sequence. But surely there's a better way.

 

And of course there is. This is not so much a "tip" about APIs, but rather a technique based on ILE RPG capabilities that can be applied to many situations, this being one of them. Rather than maintain an array or stack of values within our program, let's instead recursively dive to the appropriate call stack entry and then display the information associated with each call stack entry as we come back up.

 

A program demonstrating this approach is shown below:

 

h dftactgrp(*no)                                                   

                                                                    

dCallStack2       pr                  extpgm('CALLSTACK2')         

d NbrEntInput                   15p 5 const                        

                                                                   

dCallStack2       pi                                                

d NbrEntInput                   15p 5 const                        

                                                                   

dGetCallStack     pr                  extpgm('QWVRCSTK')           

d RcvVar                         1    options(*varsize)            

d LenRcvVar                     10i 0 const                        

d FmtRcvVar                      8    const                        

d JobID                      65535    const options(*varsize)      

d FmtJobID                       8    const                        

d ErrCde                              likeds(QUSEC)                

                                                                   

dDisplayCSE       pr                                                

d EntInfPtr                       *   value                      

                                                                 

 /copy qsysinc/qrpglesrc,qwvrcstk                                

 /copy qsysinc/qrpglesrc,qwcattr                                 

 /copy qsysinc/qrpglesrc,qusec                                   

                                                                 

dRcvVar           ds                  likeds(QWVK0100)           

d                                     based(RcvVarPtr)           

                                                                 

dProcName         s            256    based(ProcNamePtr)         

dNbrEnt           s             10i 0                            

dCurProcName      s             52                               

dPrvPgmName       s             10                               

dWait             s              1                               

                                                                  

 /free                                                           

  // Check for parameter, default to all                         

  if %parms = 0;                                                      

     NbrEnt = *hival;                                                  

  else;                                                               

     NbrEnt = NbrEntInput;                                            

  endif;                                                              

                                                                       

  // API is to return escape messages if an error is found            

  QUSBPRV = 0;                                                        

                                                                       

  // Initialize Job identification format JIDF0100                    

  QWCF0100 = *loval;                        // Set structure to x'00's

    QWCJN02 = '*';                          //   Job name: * = this job

    QWCUN = *blanks;                        //   User name            

    QWCJNBR00 = *blanks;                    //   Job number           

    QWCIJID = *blanks;                      //   Internal job ID      

    QWCTI00 = 1;                            //   Thread = this thread 

                                                                      

  // Call API to find out how much storage is needed                 

  GetCallStack(QWVK0100 :%size(QWVK0100) :'CSTK0100'                 

               :QWCF0100 :'JIDF0100' :QUSEC);                        

                                                                     

  // Check information status                                        

  select;                                                            

     when QWVIS = ' ';                      // Info OK               

     when QWVIS = 'I';                      // Info partial, still OK

     when QWVIS = 'N';                      // Info not available    

          dsply 'Information is not available.' ' ' Wait;            

          *inlr = *on;                                               

          return;                                                    

     other;                                                          

          dsply ('Unexpected status value of ' + QWVIS) ' ' Wait;    

          *inlr = *on;                                               

          return;                                                    

  endsl;                                                              

                                                                      

  RcvVarPtr = %alloc(QWVBAVL);              // Get the storage        

  GetCallStack(RcvVar :QWVBAVL :'CSTK0100'  // Call API again to get  

               :QWCF0100 :'JIDF0100' :QUSEC);  // all of the data     

                                                                      

  // Check information status in case anything has changed            

  select;                                                              

     when RcvVar.QWVIS = ' ';               // Info OK                

     when RcvVar.QWVIS = 'I';               // Info partial, still OK 

     when RcvVar.QWVIS = 'N';               // Info not available     

          dsply 'Information is not available.' ' ' Wait;             

          *inlr = *on;                                                

          return;                                                     

     other;                                                           

          dsply ('Unexpected status value of ' + RcvVar.QWVIS) ' 'Wait;

          *inlr = *on;                                                

          return;                                                     

  endsl;                                                               

                                                                      

  // If call stack isn't as large as user requested, then tell them   

  if NbrEnt > RcvVar.QWVERTN;                                         

     NbrEnt = RcvVar.QWVERTN;                                         

     dsply ('Showing ' + %char(NbrEnt) + ' call stack entries.');     

  endif;                                                              

                                                                       

  DisplayCSE(RcvVarPtr + RcvVar.QWVEO);     // Process all entries    

                                            //   that were requested  

                                                                      

  dealloc RcvVarPtr;                        // Free the storage       

  dsply 'End of call stack list.' ' ' Wait; // Wait for the operator  

                                            //   to indicate list read

                                                                       

  *inlr = *on;                                                        

  return;                                                             

                                                             

 /end-free                                                    

                                                             

pDisplayCSE       b                                          

                                                             

dDisplayCSE       pi                                          

d EntInfPtr                       *   value                  

                                                             

dEntryInfo        ds                  likeds(QWVCSTKE)       

d                                     based(EntInfPtr)       

                                                             

 /free                                                       

                                                             

  NbrEnt -= 1;                                                

  if NbrEnt > 0;                                             

     DisplayCSE(EntInfPtr + EntryInfo.QWVEL);                

  endif;                                                     

                                                                     

  // Display Pgm/Srvpgm name when it changes                        

  if EntryInfo.QWVPGMN <> PrvPgmName;                               

     PrvPgmName = EntryInfo.QWVPGMN;                                

     dsply ' ';                                                      

     dsply ('Program name: ' + EntryInfo.QWVPGMN);                  

  endif;                                                            

                                                                    

  // If procedure name was returned, display it up to the max       

  // byte limitation of the dsply opcode (currently 52)             

  if EntryInfo.QWVPD > 0;                                           

     ProcNamePtr = EntInfPtr + EntryInfo.QWVPD;                      

     if EntryInfo.QWVPL > %size(CurProcName);                       

        CurProcName = %subst(ProcName :1 :%size(CurProcName));      

     else;                                                          

        CurProcName = *blanks;                                      

        CurProcName = %subst(ProcName :1 :EntryInfo.QWVPL);         

     endif;                                                    

     dsply CurProcName;                                        

  else;                                                         

     dsply 'Cannot determine procedure name. OPM perhaps?';    

  endif;                                                       

                                                               

  return;                                                      

                                                               

 /end-free                                                     

                                                               

pDisplayCSE       e                                                             

The actual changes to the original program are minimal.

 

First, we remove the declares for variables EntInfPtr and EntryInfo from the main procedure as we will be moving these variables into a new procedure, Display Call Stack Entry (DisplayCSE). We also remove the DoFor loop and associated control field Count found in the original program. Instead, we will use the NbrEnt field to control how deeply we recursively dive into the returned list of call stack entries. Where we previously entered into the DoFor loop, we now simply call DisplayCSE, passing a pointer to the first call stack entry. This is done with the statement 'DisplayCSE(RcvVarPtr + RcvVar.QWVEO);'.

 

Next, we define the procedure DisplayCSE. This procedure accepts one parameter: a pointer to the current call stack entry. DisplayCSE first decrements the global variable NbrEnt, which reflects how many entries remain to be processed. If NbrEnt is greater than 0, DisplayCSE recursively calls DisplayCSE , passing a pointer to the next call stack entry to be processed ('DisplayCSE(EntInfPtr + EntryInfo.QWVEL);'). When NbrEnt becomes 0, the program has read through the appropriate number of call stack entries, and DisplayCSE then continues processing the current entry. This display processing is the same as that used in the original program. The one difference is that instead of calculating the address of the next call stack entry, DisplayCSE simply returns to the previous instance of DisplayCSE at the bottom of the DoFor loop.  That instance processes its current call stack entry and again returns to its caller. This continues until all call stack entries have been processed and displayed. The program then ends in the same way as the original program: de-allocating the storage associated with RcvVarPtr and indicating that the list is finished.

 

If you have never used recursion in your applications, this capability of ILE RPG is a powerful tool that can greatly simplify the development of certain types of applications. If the call stack entries had been of fixed length, I would have used other techniques, but when working "backward" through variable-length entries, recursion can certainly simplify the application program.

 

If you have other 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 This email address is being protected from spambots. You need JavaScript enabled to view it.. 


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

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 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. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY 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. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) 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:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. 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:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot 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:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

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

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? 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: