Category Archives for "IBM i"

0 From AS400 DLS to IBM i IFS – an Integrated File System

Over recent years, I’ve been playing with the IBM i Integrated File System a lot more than usual. The IFS allows us to use and easily share IBM i Data with Windows/Linux/Apple or just about any other computer on the network. It basically shares native IBM i (AS400) data with the windows world so that […]

0 Softlanding Turnover Scribbled Notes, User Guide and Programmer Reference

Earlier, I was explaining how to use TURNOVER Change Management to some RPG Developers who have spent years using Turnover but who had never used the Programmer Worklist Function. I was mildly surprised at the manual technique that was being used to check out each object, adding to a form source member by source member […]

0 Send IBM i Email including SQL Table Data automatically

Have you ever wanted to extract some data out of an IBMi/AS400 file using SQL and then email that data to someone as an Excel Spreadsheet? Now you can… all from one IBMi command without having to write any CL code to do it. Projex4i: DSTDTA command now handles SQL STRINGS for selecting data I […]

0 I remember the IBM AS400

Discussing a data interchange process with a software vendor today (who shall remain nameless), they told me that their product could talk to an AS400 but had no experience of iSeries or IBM i…. *sigh* I am not telling you the company name because I don’t wan to  to embarrass them in public… butif you […]

0 How to ZIP AS400 library and Email it

Now, before you get all bent out of shape and point your grubby little index finger at me cackling “you called it an AS400 na-na-nu-na-naaah“, I do have a legitimate reason. It’s a shallow SEO based one (the grey haired brigade keep searching for “zip AS400 library”) but it’s legitimate. I only used the wrong […]

0 Update an IBM i file with SQL cursor using SQLRPGLE WHERE CURRENT OF

Using SQL in RPGLE programs is easier than you think. Making the move from RPG native file IO to SQL database IO is really quite straightforward.  Changing from good old READE loops to SQL FOR Loops simply means using the SQL CURSOR function. SQL has a groovy way of referring to what the stuff that […]

0 Green Screen to Web Application in 5 minutes (aka how the AS400 got on the World Wide Web with IBM i)

Twenty years ago… I was typing on a dumb terminal, connected to a great big beige computer called IBM AS/400 with a thick grey Twinax cable. Screens were green on black, text only — or sometimes orange on black if you were posh. The internet was this thing we used to send emails (if you knew […]

0 How to Debug HTTPAPI RPG Programs – dsplnk ‘/tmp/httpapi_debug.txt’

If you are using the IBM i HTTPAPI (LIBHTTP) opensource utilities, you already realize how easy it is to talk to an internet webservice from within your IBM i RPG programs. But sometimes even the best laid plans go wrong and thats when you need to learn how about the “debug HTTPAPI webservices” function. Assuming […]

0 RPG Program Source Code – Clever or Clear?

I’ve been working on an interesting project focused on taking some old RPG code and re-factoring it to make it more efficient. Fascinating work for a client that is focused on doubling its IBM i throughput and reducing the CPU load of all its old programs. This has frequently made me choose between writing a […]

0 GETSPLF and PUTSPLF – read and write spools to physical files including all Advanced Function Printing Data Stream (AFPDS)

wow – that has got to be the longest url yet   😉

QSPGETF AND QSPPUTF APIs AND COMMANDS

IBM Knowledgebase item 8011926 describes two APIs that are undocumented in the AS/400 manuals. The two APIs, Get Spooled File (QSPGETF) and Put Spooled File (QSPPUTF), copy spool files to and restore them from physical files, respectively. The advantage of QSPGETF and QSPPUTF over the well-documented Copy Spooled File command (CPYSPLF) is that the APIs are able to copy Advanced Function Printing Data Stream (AFPDS) and Intelligent Printer Data Stream (IPDS) spool files, whereas CPYSPLF cannot.

You can call the QSPGETF and QSPPUTF APIs directly, or you can call them using command wrappers over the APIs.

• Calling the APIs Directly

The QSPGETF API call below saves spool file QPRINT to database file SPOOLDB in USER1LIB library, member MBR1, where the spool file number is 1 and the spool file job is 010160/user1/dsp03:

CALL PGM(QSYS/QSPGETF) PARM(‘QPRINT ‘ ‘SPOOLDB USER1LIB ‘ ‘DSP03 USER1 010160′ X’0001’ ‘MBR1 ‘)