Data-entry CHECKAUT parameter enhancement for RMDS lookup
Processing of the MERVA function table parameter CHECKAUT=YES is enhanced to test the WebSphere® BI for FN Relationship Management Data Store (RMDS) for a current business relationship instead of the MERVA authenticator-key file.
Resolving the problem
After SWIFTNet Phase 2 migration, the MERVA authenticator-key file will be obsolete. So the CHECKAUT=YES parameter of the DSLFNT macro, which is intended to test the authenticator-key file for a current business relationship during message data entry, will no longer work unless you decide to continue to maintain the currency of the authenticator-key file.
For those installations which do no longer use the authenticator-key file, MERVA is enhanced to test the WebSphere BI for FN RMDS instead of the authenticator-key file for a current business relationship with the correspondent institution.
The new parameter CHECKAUT in DSLPRM offers you three options to control the effect of the CHECKAUT=YES parameter in the function table DSLFNTT:
MERVA checks the WebSphere BI for FN RMDS for a current business relationship.
This option requires DB2®.
MERVA checks the MERVA authenticator-key file for a current business relationship.
This option (the default) does not require DB2.
MERVA ignores the CHECKAUT=YES specifications in DSLFNTT. That is, no check for a current business relationship is made.
This option does not require DB2.
Apply PTF UK38483 for APAR PK68166 to obtain the enhancement and a detailed description from the APAR how to set up MERVA and DB2. If you intend to specify CHECKAUT=RM, you must have applied the corresponding WebSphere BI for FN PTF UK36719 before you can apply the MERVA PTF UK38483.