MSG EQQX145E or EQQX146E received in ISPF dialogs or PIF EQQMLOGs

Answer

ISPF dialog users and PIF programs communicate with the TWSz CONTROLLER through the z/OS subsystem interface. The four main components of this process are the CONTROLLER started task, the CONTROLLER z/OS SUBSYSTEM, the code executed in the PIF job's region or the ISPF dialog user's TSO address space, and the EQMINOx subsystem communication module which is used by the PIF job or dialog user to invoke the subsystem. All four of these components must be at the same TWSz release.

If a PIF/DIALOG server is used to allow "remote" users to connect to the CONTROLLER, the server code must also be of the same release.

If the CONTROLLER started task is able to start successfully, then the level of the subsystem code matches that of the CONTROLLER. The CONTROLLER will start and immediately terminate with an explanatory message in its EQQMLOG if these two components are not compatible.

If message EQQX145E is issued, then there is a mismatch between the CONTROLLER SUBSYSTEM and the PIF/DIALOG code.

If message EQQX146E is issued, then there is a mismatch between the EQQMINOx interface module and the PIF/DIALOG code... or the EQQMINOx load module is not APF authorized. Starting in TWSz V8R5M0, the name of the EQQMINOx loadmodule is suffixed to the release, so it is no longer possible to get a release mismatch between the module and the other PIF/DIALOG code, so all instances of this message in 8.5.0 and newer releases relate to APF authorization issues.

DOC APAR PK53014 explains that LIBDEF cannot be used to allocate the library containing EQQMINOR (normally SEQQLMD0) to ISPLLIB because EQQMINOR is loaded by IKJEFTSR and must execute AUTHORIZED. EQQMINOR can be allocated to ISPLLIB or STEPLIB if these are allocated prior to ISPF being started -- for instance, by a STEPLIB in the TSO logon proc.