On Saturday, August 26, 2023 at 11:17:39 AM PDT, Phil Smith III <li...@akphs.com> wrote:
> I'm not really going to tell a customer, "I'm sorry, you're clearly not up to > the job > of installing this product. Who else there knows more than you do?" so I'm > not > sure what your real-world point is-IOW, what different action you're > suggesting. The customer isn't being rude and they deserve to be educated in a polite way. You get them to come to the realization on their own by asking them questions about planning, recovery and other system critical information. More often than not, these people are trying to learn, be independent and prove themselves but they don't know what they don't know. Your questions will open the door for them to ask intelligent questions from their lead. A good lead will recognize they did not educate this person on their policies and strategies. > PSWI? Pharmacy Society of Wisconsin? PSWI (Portable Software Instance) that has been mentioned a few times in this thread. It's the first time I heard about it too and I don't know anything about it. If I understand it correctly, it's IBM's new alternative product installer that guides a user thru the complete install, setup and configuration process. I suspect that it includes SMP/e steps. I would need to see it but I'm leery that it will cause people to ignore recovery that needs to be planned during installation of products. >>You say EDIT CHANGE ALL instances is causing customers grief. Do you > Again, don't disagree that they don't understand, but?? If a customer is complaining about changing the JCL, then they are complaining that it's tedious. While they are right, we also know that they are ignoring the planning and company policies. They can easily create an edit exec with all the change commands. > But if I make the changes (via automation) and it screws up, it's my fault. > If I gave them something that won't run as provided, and > they make changes and it screws up, it's their fault. This matters. What makes you think you screwed up? This is z/OS with all it's nuances. Automation can only get the customer in the ball park but their company policies dictate what they must change by hand. Do certain files require SYS1? How about impact of recovery? What about disaster recovery? How do they manage SMP/e CSIs so that libraries remain consistent. This isn't VM or Linux where everything is consistent. As a z/OS product developer, you can't ask questions to cover every situation. VM and Linux are limited to 1 system z where as z/OS sysplex can encompass 32 system z. > When they do get it wrong, SMP/E errors are usually incomprehensible. > I've said this repeatedly; are some of my posts not getting through? I see > them. I stopped watching the list for a while so I probably missed them. If by SMP/e errors, you mean SMP/e messages, then is the SMP/e message manual not helpful? Are the actions you need to take unclear in the message manual? Is the terminology a problem? Is it a problem finding utility output in the job? Are the errors reported by the customer to you or are they problems with SMP/e statements? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
