Technical Blog Post
Abstract
Use the WHO command to help check Connect:Direct for z/OS 5.2 mixed code.
Body
Mixed code in the Connect:Direct IUI can be a serious problem. It is important to keep your 5.2 ISPF environment separate from earlier releases of code.
See 'Don't make this common Connect:Direct for z/OS mistake – Secure+ release 5.2 will not work with mixed code.' for an example of how mixed code can affect you.
To assist you with detecting possible mixed code, we have added a new field to the 'WHO' command so that it displays both the IUI Version and the DTF Version. If there is a discrepancy, you may have mixed code.
This WHO output is from a correctly configured 5.2 system – no mixed code is used.
IUI VERSION ==> 05
IUI RELEASE ==> 002
IUI MODIFICATION ==> 000
IUI PUT LEVEL ==> 0000
DTF VERSION ==> 5.02.00
If you get an 'Unknown' DTF VERSION, that could indicate that the DTF is pre 5.2 running with 5.2 IUI screens:
IUI VERSION ==> 05
IUI RELEASE ==> 002
IUI MODIFICATION ==> 000
IUI PUT LEVEL ==> 0000
DTF VERSION ==> Unknown
This is an example of a C:D 5.0 linklib (ISPLLIB) mixed with 5.2 IUI. '5002' is not a valid put level for 5.2.
IUI VERSION ==> 05
IUI RELEASE ==> 000
IUI MODIFICATION ==> 000
IUI PUT LEVEL ==> 5002
DTF VERSION ==>
If you are trying to run 5.2 and don't see the DTF VERSION field, that is also an indication of possible mixed code.
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.
UID
ibm11124007