×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I think you're making some bad assumptions here.
One, will the job users always be 8 characters? FLA*
Two, will the device names always be 10 characters? QPADEV*
Three, will IBM never change the layout of this printout at a release,
ptf, etc, level?
I believe the standard clause of the MTU applies.
<snip>
Output(*PRINT) changes
Release to release Output(*PRINT) considerations
Applications specifying OUTPUT(*PRINT) to generate spooled output from
commands must be able to
tolerate changes to the record layout in the spooled file. From release to
release, commands that support
that option can add, change, or remove records from the output. Any
application that has a dependency
on the record layout for a specific command might have to change.
</snip>
I have been burned by this before. And, it's a real hoot when you support
multiple versions of the OS.
If you must code this at 7.1, prior to QSYS2.HISTORY_LOG_INFO(), then you
might be best to use the APIs.
Birgitta gives a sample of coding an API to make a UDTF out of it.
https://www.ibm.com/developerworks/ibmi/library/i-power-of-udtf/
Rob Berendt
midrange.com
