Upgrade to V7R4 also requires object compilation in v7R3 for compatibility

Products

• CA 2E

Issue/Introduction

Our host/development system is in V7R3, also the client system is in this same OS version.

When we upgrade the host/development system to V7R4, are there any parameters or compilation considerations now that the development system will be in V7R4 but the client will remain in V7R3 for some time?

Please advise.

Environment

Release : 8.7.3

Resolution

Upgrade your version 8.5 to 8.7 first and then upgrade to 8.7.3. 

As you upgraded the system to V7R4 by default the objects are generated w.r.t to V7R4 compatible. As the client is in V7R3 we need to compile objects in development systems also to V7R3. 

For that w.r.t model changes, we need to do the below changes:

1) Zoom into the *Messages file in "EDIT DATABASE RELATIONS" screen.

2) And then Zoom into the *CRT messages (for example *CRTBNDRPG) in "EDIT MESSAGE FUNCTIONS" screen.

3) and then take F7 on the "EDIT MESSAGE FUNCTION DETAILS" scren.

4) Then in the "EDIT SECOND LEVEL MESSAGE TEXT" screen  append the TGTRLS(V7R3M0) to the existing command to compile the objects to the client compatible version in this case it is V7R3.

The above settings should solve the reported problem that is create the objects in the development machine to compatible with V7R3 client machine.

In addition to the above settings, As you upgraded the OS in the development system the earlier configured routing entries(before upgrade) might loss in subsystem description of QBATCH. Could you also check the YBRTPRC routing entry was defined in the QBATCH subsystem, if not configure that routing entry so that pre compiler overrides defined in the model are applied to the objects at the time of compilation by Routing entry configured 2E tool kit program YBRTPRC.
Note: We are setting Routing entries in QBATCH subsystem because we presume your model value YCRTJBD is QBATCH. If not, then configure the routing entries in the  subsystem corresponding to your JOBD's JOBQ'.