Don't make this common Connect:Direct for z/OS mistake – Secure+ release 5.2 will not work with mixed code.

Body

While it has never been recommended to use 'mixed' versions of Connect:Direct in your ISPF environment, before release 5.2 you could sometimes get away with using 5.0 IUI programs with 5.1 for example.

Now that 5.2 Secure+ screens have been completely redesigned, you must ensure that your IUI is running the same release as your DTF started task. If you have any older releases in your ISPF concatenation, you will experience errors working with your PARMFILE, and risk corrupting it completely.

If you try to open a converted 5.2 Secure+ PARMFILE and receive this type of error, you may have mixed code.

Error:   nodename       Hash value did not verify, record ignored¹ 

Another symptom of mixed code could be a failure when doing the initial 'Save As'.

Note – It is also important to verify that you followed proper PARMFILE conversion procedures if you are using one from a previous release. 5.2 PARMFILES cannot be interchanged with those from prior releases.

See 'Use the WHO command to help detect Connect:Direct for z/OS 5.2 mixed code.' for one way to verify your IUI release.

If you suspect that you have mixed IUI code, carefully review your ISPF environment and the Connect:Direct Configuration Guide to make sure that only 5.2 libraries are used.

¹ This message can be caused by issues other than mixed code. For example, incorrect ICSF permissions can produce this message.