Tag Archives for " #ibm i "

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 […]

Continue reading

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 […]

Continue reading

AS400 Modernization starts with Modernizing RPG Applications

RPG Modernization

Modernizing RPG Programs – Learn the RPG History first I had email email from an old work colleague this morning. He was a windows programmer, with limited exposure to RPG, but works in a company that is driven by a huge, old, complex RPG3 application that has changed little over the last decade. He is […]

Continue reading

IBM i v7.3 is here and its pretty cool

You think you know IBM i? You havent met 7.3 IBM i 7.3 Announcement & Material IBM® DB2™ for i Temporal Support, enabling clients to conduct accurate analysis of data within a specific historical time period More advanced analytics capability driven by enhanced OLAP functionality, allowing clients to better forecast, define gaps and build new […]

Continue reading

Turnover 3 – Promoting RPG using Turnover Forms

Promoting RPG So, you have completed your programming! You have tested the code in your library and it’s ready to pass on to the QA testing team or the User Acceptance Test team. How are we going to do that in Turnover? The process is called promotion and you do it using a thing called […]

Continue reading

Turnover 2 – Checking out code, editing and compiling using the Programmers Work list

Checking out code – this is booking the code or reserving it for *you* to work on. This takes a copy of the high level (UAT, QA, TST or PROD) into your developer library and lets you work on it. You work and compile it in there using the Programmers Worklist (which is Turnover’s version […]

Continue reading
1 2 3