Re: i5/OS V6R1 not converting *SRVPGMs on "first touch"?

Mark -

Are these objects that belong to a software package?

Many software vendors (such as Oracle's JDE World Software) supply objects
with observability removed.

By running the ANZOBJCVN command on the V5.4 system, we identified thousands
of objects that would not convert. In consideration of our pending V5.4 ->
V7.1 conversion, it will be necessary for us to get a new tape from Oracle
that has objects saved from their V7.1 system.

- sjl



Mark wrote:
One of our customers is in the process of converting from V5R3 to V6R1
... (side-by-side upgrade; separate box.)

For some reason, they are getting this message in some job logs:

CPI5D20 Information 10 08/17/10 08:34:07.122556 QBNBIND QSYS *STMT QBNBIND
From module . . . . . . . . : QBNBLOAD
From procedure . . . . . . : QBNBLOAD__ProgramManager__Load
Statement . . . . . . . . . : 9
To module . . . . . . . . . : QBNBLOAD
To . . . . . . . : QBNBLOAD__LoadObject
Statement . . . . . . . . . : 5
Message . . . . : Service program SRVPGM01 requires conversion.
Cause . . . . . : Service program SRVPGM01 in library *LIBL requires
conversion because it is not in the format required. Converting a
service
program to the current format may change the way it uses argument
optimization (ARGOPT). Recovery . . . : If there are problems with
ARGOPT, convert this service program, and then try the command
again. Use
the Start Object Conversion (STROBJCVN) command to convert the service
program.

For some reason, they changed QFRCCVNRST to "1" (from the IBM
recommended default of "3".) Yet, most of the objects in the library
where these *SRVPGMs reside say "Conversion required . . . *NO". But
for some reason, a few of them say "*YES" and they have *UNOBS for the
Observable information.

I thought OS/400 and i5/OS was supposed to automatically convert such
objects on "first touch" (or first use), as needed?

I told the customer to submit a batch job to run a STROBJCVN for the
library containing these objects, and that seems to have resolved this
issue. But, is this now necessary?

Is anyone else seeing this?