1) Windows Client Icons Object’s don’t have, and will not have an unique icons assigned in Windows Client. There is no plan to create an Windows Client patch soon. Sometimes Windows Client automatically assigns following icons, “All Data Sets Info – CSI” object has always default icon.
2) Creating Logging Script in Windows Client Creating a logging script for any of new CSI object works in Windows Client, there is no indication of problem, but the log scripts does not work, following message is presented in JESMSGLG part of the joblog: “VKG0400I VAN1526I Enter Search Argument(s) using The Input List”. This is happening because the Windows Client wizard for log script creation misses a panel for specifying the object input list. We don’t have a plan to fix this in Windows Client soon.
Circumvention is to use new Web Client which will be GA soon to create an object logging script. Or, create a logging script in Windows Client, than edit it in ISPF (or WC client browse PDS – Edit member), and insert the following script statement INPUT_LIST_SET=your.input.list.value. You can obtain this statement when you will create a GOA script for the above objects.
GOA licensed customers can create GOA script with “Log the selected records” also.
3) Compaction of INDEX part of the CLUSTER Object (OBJ02014) All Data Sets Info – CSI can display an information about the compaction attributes of dataset if the compaction is used on the dataset – columns “Comp, UserDataSz, CompUserDataSz, ByteSav”, it works for supported data set types, but for INDEX part of VSAM cluster we are not displaying this information because the IBM CSI service is not returning those information’s for INDEX component, we didn’t put this information into the help on object because we don’t know when and if IBM will fix it.
4) Dataset Encryption Attributes Object (OBJ02014) All Data Sets Info – CSI can display an information can display information about the encryption attributes of data set if the encryption is applied. This works 100% on z/OS 2.3, again because of level IBM CSI functions.
We included this information in the help : WARNING! This field contains valid data only on z/OS V2R3 and higher. If you run z/OS prior V2R3, the value -None is presented whether the entry is encrypted or not.
5) Weird Data Displayed in the Objects It is possible that customer will see in the object some weird data, which will not correspond to data displayed in ISPF 3.4 DSLIST, even it’s possible that customer will see in in new objects data sets he cannot locate in ISPF 3.4. This is because of corrupted catalog, it means that new objects can be also used to identify the problems in catalogs, prior to opening a case for this scenario, it is necessary to verify “weird” entries in customer workshop against related catalog using the VSAM LISTCAT, DIAGNOSE, EXAMINE (Note: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.e0zk100/catalog_damaged.htm )
Beside the fact that new CSI objects provide more information than original (CATALOGF) BCS Data Set Entries object, they are more memory efficient, but still, requesting information about 10 000 000 records – data sets require approx 600MB of storage, they are more CPU efficient (some workload is shifted to catalog service ‘CATALOG ‘jobname running on related LPAR), they collects data several time/hundreds time faster than original object, but time of collection is directly infuenced by current I/O workload etc. on CATALOG jobname – CSI service.