Do you know how to recompile your service programs without having to recompile all programs using the service program?
Written by Tom Snyder
I have to admit that the binding language was a late discovery for me, and I've struggled for quite awhile working around it. But I've found the binding language to solve the problem of having to recompile your service programs without having to recompile all the programs that are using it. Without the binding language, service programs are very similar to modules due to the need to recompile the programs every time they change. This article will show you how to overcome this problem with the use of the binding language.
IBM i programmers give web enabling with Presto two thumbs up. Presto is the most flexible IBM i Web GUI for green screens. Use it to web enable your green screen apps to different levels: • Instant modern Web GUI for all your IBM i green screen programs, O/S screens & 3rd party apps • Enhanced Web GUI with new UI elements & styling (date pickers, links, drop downs, etc) • Extended Web GUI with new functionality (additional fields and validation, Web Services…) Read the reviews or watch a video
Process the data returned by the QjoRetrieveJournalEntries API.
Written by Bruce Vining
Last month, in "The Case of the Missing Stream Files," we saw how to call the QjoRetrieveJournalEntries API, documented here, in order to access all journal entries associated with the removal of an IFS link from a directory. The links removed might be *STMFs, *SYMLNKs, *DIRs, etc. As the goal of the project is to determine who removed the links, today we'll look at how to process the results of calling the QjoRetrieveJournalEntries API.