Upgrading RLX from Version 9.1.5 to Version 20.1.
Using remote DB2 access with RLX.
1) Is it possible to do a remote access from an LPAR running V9.1.5 to an LPAR running V20.1 and vice versa,
or do all LPARs have to be updated concurrently?
2) If using the old PLAN name RLX915CS, is a new BIND required or is the old PLAN fine to be used with the new version ?
3) In the V9.1.5 customization the only jobs required to be run were RLXJTI and RDXJTSD, are these the jobs for V20.1 ?
4) In V9.1.5 these modules USQMAIN,SBL$TGR,RDXH were loaded into the dynamic LPA. Is this also necessary for V20.1 ?
Release : 20.1
Is it possible to do a remote access from LPAR running V9.1.5 to an LPAR running V20.1 and vice versa, or do all LPARs need updating concurrently?
And can the same PLAN name be used?
Multiple concurrent releases of the RLX products are supported. New plan names for R20.1 should be bound, for example, RLX201CS,RLX201RR, RLX201UR etc.
Is it possible to use the old PLAN name RLX915CS?
A new bind for new plans is required for R20.1 using CRAIJCL(RLXJTI) with PARM=(BIND....
In V9.1.5 customization only the jobs RLXJTI and RDXJTSD were required. Is this also sufficient for V20.1 ?
Follow the documented installation process for R20.1
Executing RLXJTI and RLXTSD are only part of the entire installation process
In V9.1.5 the load modules USQMAIN,SBL$TGR,RDXH were loaded into the dynamic LPA, Is this also necessary for V20.1 ?
It is not specifically required for the Product.