We have our first z/VM 5.4 system up and running. DIRMAINT is currently installed, but we have not learned how to really use it. We have RACF and need to configure and make security decisions regarding Linux guests. We need to install Performance Toolkit and likely another monitor on top of that to monitor from the Mainframe perspective. Processes and procedures need to be defined, and day to day automation tasks built/addressed. We have not yet defined how we are going to handle maintenance, backup and recovery of z/VM and Linux guests. I realize this is a subset of the list of tasks. We just started in November with 2 z/OS System programmers going to one "getting started" class. Now we are being asked to estimate how long it will take us to have a "production ready" z/VM system (not including the Linux guest installs) and develop a timeline. Anyone out there been through the pain of doing this who can give us some idea of timeline and people resource required??
Thanks for any suggestions. > Valerie Le Grande > Systems Engineer Senior > Sentry Insurance System Programming and Support > Email: valerie.legra...@sentry.com Phone: (715)346-7074 This e-mail is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this e-mail in error, please tell us immediately by return e-mail to email.cont...@sentry.com and delete the document. E-mails containing unprofessional, discourteous or offensive remarks violate Sentry policy. You may report employee violations by forwarding the message to email.cont...@sentry.com. No recipient may use the information in this e-mail in violation of any civil or criminal statute. Sentry disclaims all liability for any unauthorized uses of this e-mail or its contents. This e-mail constitutes neither an offer nor an acceptance of any offer. No contract may be entered into by a Sentry employee without express approval from an authorized Sentry manager. Warning: Computer viruses can be transmitted via e-mail. Sentry accepts no liability or responsibility for any damage caused by any virus transmitted with this e-mail.
