Previous Topic: IDADRBNP13 - PGM pgm-name VER version in MODULE format does not access DB SQLNext Topic: IDADRBNP15 - Rebind for PGM pgm-name VER version was done. Load module was used.

Administrative Services (AD) Messages › › IDADRBNP14 - PGM pgm-name VER version was rebound. Load module versus vls discrepancy

IDADRBNP14 - PGM pgm-name VER version was rebound. Load module versus vls discrepancy

Reason:

Rebind was done for pgm-name version version using load module format. The load module object code was different than the VLS object code. ALTER PGM ENV was probably issued after load module was created. ALTER PGM ENV cannot change CA Ideal object code in load module format.

Action:

Investigate the situation. If VLS format is wanted, recreate the load module object using batch CREATE MODULE. Otherwise, ignore the message.