Last Updated on 31 October 2019 by Roberto De Pedrini
The operating system provides us with the QSPRILSP API: just one single line of code to have all the spoolfile informations. Then combining the two techniques (find the spool and process it with SQL) it is possible to transform / improve the output of our programs with a few simple steps.
Below an example of how to call up the API with variables that contain the spool data highlighted
* API declaration dgetLastSpoolId pr extpgm('QSPRILSP') d ReceiverVariable… d 1 options(*varsize) d ReceiverVariableLength… d 10i 0 const d FormatName 8 const d errorCode likeds(QUSEC) * local variables d wait s 1 * /copy declarations for spoolfile info ds and errors handling /copy qsysinc/qrpglesrc,qsprilsp /copy qsysinc/qrpglesrc,qusec * errors initialization QUSBPrv = 0; monitor; * search for last spoolfile getLastSpoolId(QSPL0100 :%size(QSPL0100) :'SPRL0100' :QUSEC); on-error;
clear QSPSNBR03;endmon; * display last spoolfile data dsply ('Job ' + %trimr(QSPJN00) + '/' + %trimr(QSPUN00) + '/' + QSPJNBR00); dsply ('Last spoolfile name ' + QSPSN03); dsply ('Last spoolfile number ' + %char(QSPSNBR03)) ' ' Wait; *inlr = *on; return;
The monitor instruction has been inserted to be able to manage the eventuality that the job has not generated spool.
If instead of displaying (dsply) the search result we pass it to a module or service program that reads the spool and transforms it, it’s done. Furthermore, if the code of this example is transformed into a component with I/O parameters, it can be reused many times.
For more information, the official IBM documentation is available (https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/apis/QSPRILSP.htm)