Let me apologize in advance for asking so many questions related to VM software licensing. I don't get a clear picture sometimes of what is a non-chargeable feature and what is.
If you ever completely understand it, please let the rest of us know...8-). Of course, if you do, the guys in the black helicopters will come to get you for reeducation, citizen... I'm preparing to install the non-chargeable DFSMS/VM feature. However, the install instructions list ISPF and the C runtime library of LE as co requisites. Does anyone know if these two components are already installed as part of the base z/VM or are chargeable features that need to be ordered separately? I'm running z/VM 5.3. They are not, and (at least in the case of ISPF) be prepared to open your wallet Real Wide. ISPF/VM is not cheap; I don't think you need the PDF component unless you REALLY want it. But, you don't really need it unless you are going to use the panel interface. Most of the DFSMS commands also have a line-mode version. The panels are only really helpful if you are defining SMS policies (if you have DFSMShsm on another platform, you can generate the policies there and then move them over). What part of SMS do you want? If it's just the RMS piece necessary to share a tape library with z/OS, then there is a RMSONLY parm on the SMS install that bypasses the requirement for ISPF, and there is an embedded cut-down LE preinstalled that will probably suffice for your use. Also, are there commands that will show me everything that's installed on my system? VMSES/E appears to have all the answers but not sure where in the 800+ page manual I need to reference. If this were z/OS, I could get the answers easily from SMP/e. The section in the VM Service manual on the software catalog has examples. It'd be really neat if someday IBM ran a course or conference session on how to package user tools for SES - I think more of us would actually do it if we knew how. Responses from the community thus far have been a huge help and greatly appreciated. That's normal SOP for VM. We had to survive IBM and our management telling us VM was dead repeatedly, so we learned to stick together. 8-)
