Re: UPDSRVPGM does not update file record format level

Hi, Jeff:

The problem is, DSPPGMREF will show the "wrong" (old) record format level ID for the file, after an UPDPGM or UPDSRVPGM.

The underlying cause is that the OIR records are stored in the library *OIR object, indexed by object name / type, so there is no way to tell which ones came from what *MODULE, once a module is bound into an ILE *PGM or *SRVPGM created by CRTPGM or CRTSRVPGM or updated by UPDPGM or UPDSRVPGM. So, the UPDPGM and UPDSRVPGM commands have no way to know which OIR records belong to what modules in any given bound *PGM or *SRVPGM.

Hence, the only way to ensure this information is "correct" is to keep your *MODULEs available for re-binding and then re-create any bound *PGMs and *SRVPGMs that are composed of more than one *MODULE by using CRTPGM or CRTSRVPGM, at least whenever file changes are involved.

This re-creation from the component modules can be "automated" using Alan Campin's COMPILE tool -- see

http://www.think400.dk/downloads.htm

(page down about 1/3 of the page).

Or using any other similar "pre-processor" tool or utility.

Hope that helps,

Mark S. Waterbury

> On 4/3/2013 9:31 AM, Jeff Crosby wrote:

All,

I just stumbled onto something today. Apparently an UPDSRVPGM does not
update the file record format level ID within the service program object on
any files used.

I changed the format of a file (added a field) and recompiled all programs
using it. For the service program using this file I recompiled the module,
then did UPDSRVPGM. The service program record format ID does not match
the file record format ID.

So I looked around at other service programs and found, in many cases, the
record format ID does not match the file record format ID. But I'm not
getting level checks . . .

I took a couple of service programs whose record format ID did not match
and recreated the service program via CRTSRVPGM and now the record format
level ID matches the file format ID.

If I do a DSPPGMREF of a service program to an outfile, any file used is
listed twice. Presumably one of them is for the service program itself at
creation time, and the other is for the module as last updated via
UPDSRVPGM, which explains why no level checks.

Does this make sense? Just seems eerie to me.