Future changes for programs

["Paul Godtland" <plg@xxxxxxxxxx>]

Here is some material about a future OS/400 function, provided before the
full release announcement to facilitate planning of any program handling
changes you may wish to make. This function was first discussed in a
product preview included in the iSeries announcement last October.

Starting with the next release of OS/400, program creation data will be
retained even when observable information is removed, for programs created
for that release. If observable information is removed, the creation data
cannot be retrieved by any supported interface, but the system Licensed
Internal Code will be able to use it to re-create the program. This new
function gives customers more control over the programs they choose to put
on their systems, because they can cause programs to be re-created as part
of the restore process. This program re-creation choice is expressed by
specifying the FRCOBJCVN(*YES *ALL) parameter on the RSTOBJ or RSTLIB
commands. Re-creating a program takes advantage of hardware changes and
enhancements in optimizing translator technology. Re-creating a program may
also enhance its integrity because re-creation removes any alterations that
may have been made to its executable instructions.

Programs that include creation data and are found to have been altered in
certain ways are automatically re-created when they are restored onto a
system, to further reduce the potential for security or integrity
exposures. This action also occurred on previous releases of OS/400, but
its effectiveness will be improved now that more programs will include
creation data.

Programs that have observable information removed on the next OS/400
release will be larger than the same program would have been if observable
information were removed on a previous release, but smaller than the
program was before observable information was removed.

No computer system is immune from attack. However, retaining program
creation data is an important aspect of providing OS/400 customers with
even better tools for protecting their systems. Investment protection for
customers is also enhanced, by ensuring that all programs created on the
next OS/400 release are able to more fully utilize future improvements.

Paul Godtland
Teraspace & Optimizing Translator Development; Rochester, MN

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---