Lead Mainframe Storage Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to extract content:
- Intro paragraph about division, role description: "In the Technology division, we leverage innovation..." This is about the role and firm. Could be "About the role" or "About Morgan Stanley". Probably "About the role" fits.
- Responsibilities: "What You’ll Do In The Role" bullet list: Infrastructure Management, Data & Space Management, Backup & Disaster Recovery, Capacity Planning, Automation & Scripting, Incident Response. Each with details.
- Requirements/Qualifications: "What You’ll Bring To The Role" includes Operating Systems, Software & Utilities, Connectivity, Analytical Thinking. Also "Must have Skills" list: Replication and PPRC protocols, Metro Mirror, Global Mirror, Global Copy, Cyber - Safe Guarded Copy, Experience with Copy Services Manager, ESSNI etc., Resiliency - Hyperswap & Hyperwrite, Performance - Hyperlinks. Also "Nice To Have": Certificate deployment and management for network connections, Python or Perl Scripting, GDPS, Secure Vault (Cyber) - Physical and Virtual isolation, Cloud Storage for tape archival.
- Benefits: paragraph about Morgan Stanley benefits: "Morgan Stanley offers a full spectrum of benefits, including Medical, Prescription Drug, Dental, Vision, Health Savings Account, Dependent Day Care Savings Account, Life Insurance, Disability and Other Insurance Plans, Paid Time Off (including Sick Leave consistent with state and local law, Parental Leave and 20 Vacation Days annually), 10 Paid Holidays, 401(k), and Short/Long Term Disability, in addition to other special perks reserved for our employees." Also mention "At Morgan Stanley, you’ll find an opportunity to work alongside the best and the brightest..." but that's more culture; could be part of About the role.
- Pay: Salary ranges per state: multiple statements: For Cleveland, Ohio Expected base pay rates for the role will be between $110,000 and $165,000 per year... For Colorado Salary range for the position: $125,000 and $175,000 per year. For Illinois Salary range for the position: $135,000 and $195,000 per year. For Maine Expected base pay rates for the role will be between $125,000 and $175,000 per year... For Maryland Salary range for the position: $140,000 and $195,000 per year. For Massachusetts Expected base pay rates for the role will be between $135,000 and $195,000 per year... For Minnesota Salary range for the position: $125,000 and $175,000 per year... For Vermont Expected base pay rates for the role will be between $125,000 and $175,000 per year... For Virginia Expected base pay rates for the role will be between $135,000 and $195,000 per year... For Washington Salary range for the position: $155,000 and $215,000 per year.
We need to include Pay section only if posting actually states them. Yes, we have multiple ranges. We should present them perhaps as a list.
- Schedule: Not mentioned. So omit Schedule section.
- Also we should not include boilerplate like EEO, application instructions, cookie/navigation, etc. Remove duplicated lines.
We need to preserve all substantive information. So we need to include the intro paragraphs about division, role, Enterprise Z description, etc. That is substantive.
We need to format with headings and - for lists,
for prose.
We must not repeat job title as heading. The job title is "Lead Mainframe Storage Engineer". Not to be used as heading.
We need to decide sections: About the role (intro + Enterprise Z description?), Responsibilities, Requirements (maybe split into Qualifications and Skills?), Benefits, Pay.
We could have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
But we must not create thin sections; prefer few substantive sections. Could combine Qualifications and Skills into one "Requirements" section. But the instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide.
Given the content, we have "What You’ll Bring To The Role" (Operating Systems, Software & Utilities, Connectivity, Analytical Thinking) which are qualifications. Then "Must have Skills" and "Nice To Have". Could combine into Requirements and Skills sections.
We could have:
About the role
with paragraphs about division, Enterprise Z, etc.
Responsibilities
with ul list.
Qualifications
with ul list for Operating Systems, Software & Utilities, Connectivity, Analytical Thinking.
Skills
with ul list for Must have Skills and Nice To Have (maybe separate sublists? Could just list all).
Benefits
with p.
Pay
with ul list of state ranges.
We must not include placeholder text like "commensurate with experience". Not present.
We must not include duplicated lines. Ensure we don't repeat benefit description multiple times (it appears multiple times for each state). We should include it once.
We need to remove application instructions like "Please visit mybenefits.morganstanley.com to learn more about our benefit offerings." That's part of benefits but it's a link; we can keep as part of benefits prose? It's not boilerplate? It's a referral to benefits page; could be considered part of benefits. The instruction says remove application instructions. That link is not exactly application instruction but it's a reference to benefits page. Might be okay to keep. However, the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not application instruction; it's informational. I'd keep it.
We also need to remove duplicated benefit paragraphs that appear after each state salary range. We'll include only once.
Now craft HTML.
We need to be careful to escape any HTML special characters? Not needed.
Let's draft.
About the role paragraph(s):
First paragraph: "In the Technology division, we leverage innovation to build the connections and capabilities that power our Firm, enabling our clients and colleagues to redefine markets and shape the future of our communities. This is a Lead Cloud & Infrastructure Engineering position at Vice President Level, which is part of the job family responsible for managing and optimizing technical infrastructure and ensuring the seamless operation of IT systems to support business needs effectively. Morgan Stanley is an industry leader in financial services, known for mobilizing capital to help governments, corporations, institutions, and individuals around the world achieve their financial goals. Interested in joining a team that’s eager to create, innovate and make an impact on the world? Read on."
Second paragraph about Enterprise Z: "Enterprise Z is dedicated to bolstering organizational stability, security and efficiency by leveraging IBM Z technology in alignment with Morgan Stanley’s tech goals. Through advanced observability, automation and modern architectural strategies, we deliver scalable, reliable and high-performing technology solutions. These solutions ensure seamless integration while providing exceptional value. Our unwavering commitment to innovation, collaboration and continuous improvement nurtures a resilient, forward-thinking organization capable of meeting the demanding needs of our clients and adhering to global standards."
Third paragraph about role: "We are searching for a Lead Mainframe Storage Engineer to join the Z Infrastructure team responsible for providing a highly available Z Compute and Storage platform, resilient against infra failures, regional disasters and cyber events."
We can combine into About the role.
Now Responsibilities: list items:
- Infrastructure Management: Configure and maintain hardware including IBM DS8000 series DASD, TS7700 Virtual Tape Servers (VTS), that requires experience with the TS7700 MI and DS8K HMCs
- Data & Space Management: Utilize the DFSMS suite of products to design SMS configurations, manage data class, storage class, and management class rules.
- Backup & Disaster Recovery: Oversee data replication, disaster recovery planning, and routine backups, leveraging tools like DFHSM and DFDSS.
- Capacity Planning: Monitor storage utilization, forecast future space requirements, and plan infrastructure upgrades to prevent storage shortages.
- Automation & Scripting: Write and maintain automation scripts using REXX to streamline routine storage operations and alerts. For e.g. adding volumes to a storage group that is short on capacity.
- Incident Response: Troubleshoot storage-related outages, perform root cause analysis (RCA), and resolve dataset access issues.
Now Qualifications: list:
- Operating Systems: Deep knowledge of the IBM z/OS environment.
- Software & Utilities: Proficiency with system utilities (ICKDSF, IDCAMS, IEBCOPY), and tape management systems (TLMS, RMM). Tivoli Advance catalog management (catalog management tool) and IBM Tivoli Advance allocation management for z/OS (allocation optimizer tool)
- Connectivity: Understanding of FICON connectivity and z/OS access methods (VSAM, QSAM).
- Analytical Thinking: Strong problem-solving abilities to execute complex storage migrations with minimal impact to production workloads
Now Skills: Must have Skills list:
- Replication and PPRC protocols.
- Metro Mirror, Global Mirror, Global Copy
- Cyber - Safe Guarded Copy
- Experience with Copy Services Manager, ESSNI etc.
- Resiliency - Hyperswap & Hyperwrite
- Performance - Hyperlinks
Nice To Have list:
- Certificate deployment and management for network connections
- Python or Perl Scripting
- GDPS
- Secure Vault (Cyber) - Physical and Virtual isolation.
- Cloud Storage for tape archival
We could combine into one Skills section with two subheadings? But we cannot add extra headings beyond allowed? We can just list all items, maybe mark with (Nice to have) in parentheses. But better to keep as two lists: Must have Skills and Nice to have. However we only have headings for Skills; we could have a single Skills section with two lists, each preceded by a indicating category. That's acceptable.
Now Benefits: paragraph:
"At Morgan Stanley, we raise, manage and allocate capital for our clients – helping them reach their goals. We do it in a way that’s differentiated – and we’ve done that for 90 years. Our values - putting clients first, doing the right thing, leading with exceptional ideas, committing to diversity and inclusion, and giving back - aren’t just beliefs, they guide the decisions we make every day to do what's best for our clients, communities and more than 80,000 employees in 1,200 offices across 42 countries. At Morgan Stanley, you’ll find an opportunity to work alongside the best and the brightest, in an environment where you are supported and empowered. Our teams are relentless collaborators and creative thinkers, fueled by their diverse backgrounds and experiences. We are proud to support our employees and their families at every point along their work-life journey, offering some of the most attractive and comprehensive employee benefits and perks in the industry. There’s also ample opportunity to move about the business for those who show passion and grit in their work. To learn more about our offices across the globe, please copy and paste https://www.morganstanley.com/about-us/global-offices into your browser."
Then benefits specifics: "Morgan Stanley offers a full spectrum of benefits, including Medical, Prescription Drug, Dental, Vision, Health Savings Account, Dependent Day
- for lists,
for prose. We must not repeat job title as heading. The job title is "Lead Mainframe Storage Engineer". Not to be used as heading. We need to decide sections: About the role (intro + Enterprise Z description?), Responsibilities, Requirements (maybe split into Qualifications and Skills?), Benefits, Pay. We could have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. But we must not create thin sections; prefer few substantive sections. Could combine Qualifications and Skills into one "Requirements" section. But the instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide. Given the content, we have "What You’ll Bring To The Role" (Operating Systems, Software & Utilities, Connectivity, Analytical Thinking) which are qualifications. Then "Must have Skills" and "Nice To Have". Could combine into Requirements and Skills sections. We could have:
About the role
with paragraphs about division, Enterprise Z, etc.Responsibilities
with ul list.Qualifications
with ul list for Operating Systems, Software & Utilities, Connectivity, Analytical Thinking.Skills
with ul list for Must have Skills and Nice To Have (maybe separate sublists? Could just list all).Benefits
with p.Pay
with ul list of state ranges. We must not include placeholder text like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we don't repeat benefit description multiple times (it appears multiple times for each state). We should include it once. We need to remove application instructions like "Please visit mybenefits.morganstanley.com to learn more about our benefit offerings." That's part of benefits but it's a link; we can keep as part of benefits prose? It's not boilerplate? It's a referral to benefits page; could be considered part of benefits. The instruction says remove application instructions. That link is not exactly application instruction but it's a reference to benefits page. Might be okay to keep. However, the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not application instruction; it's informational. I'd keep it. We also need to remove duplicated benefit paragraphs that appear after each state salary range. We'll include only once. Now craft HTML. We need to be careful to escape any HTML special characters? Not needed. Let's draft. About the role paragraph(s): First paragraph: "In the Technology division, we leverage innovation to build the connections and capabilities that power our Firm, enabling our clients and colleagues to redefine markets and shape the future of our communities. This is a Lead Cloud & Infrastructure Engineering position at Vice President Level, which is part of the job family responsible for managing and optimizing technical infrastructure and ensuring the seamless operation of IT systems to support business needs effectively. Morgan Stanley is an industry leader in financial services, known for mobilizing capital to help governments, corporations, institutions, and individuals around the world achieve their financial goals. Interested in joining a team that’s eager to create, innovate and make an impact on the world? Read on." Second paragraph about Enterprise Z: "Enterprise Z is dedicated to bolstering organizational stability, security and efficiency by leveraging IBM Z technology in alignment with Morgan Stanley’s tech goals. Through advanced observability, automation and modern architectural strategies, we deliver scalable, reliable and high-performing technology solutions. These solutions ensure seamless integration while providing exceptional value. Our unwavering commitment to innovation, collaboration and continuous improvement nurtures a resilient, forward-thinking organization capable of meeting the demanding needs of our clients and adhering to global standards." Third paragraph about role: "We are searching for a Lead Mainframe Storage Engineer to join the Z Infrastructure team responsible for providing a highly available Z Compute and Storage platform, resilient against infra failures, regional disasters and cyber events." We can combine into About the role. Now Responsibilities: list items: - Infrastructure Management: Configure and maintain hardware including IBM DS8000 series DASD, TS7700 Virtual Tape Servers (VTS), that requires experience with the TS7700 MI and DS8K HMCs - Data & Space Management: Utilize the DFSMS suite of products to design SMS configurations, manage data class, storage class, and management class rules. - Backup & Disaster Recovery: Oversee data replication, disaster recovery planning, and routine backups, leveraging tools like DFHSM and DFDSS. - Capacity Planning: Monitor storage utilization, forecast future space requirements, and plan infrastructure upgrades to prevent storage shortages. - Automation & Scripting: Write and maintain automation scripts using REXX to streamline routine storage operations and alerts. For e.g. adding volumes to a storage group that is short on capacity. - Incident Response: Troubleshoot storage-related outages, perform root cause analysis (RCA), and resolve dataset access issues. Now Qualifications: list: - Operating Systems: Deep knowledge of the IBM z/OS environment. - Software & Utilities: Proficiency with system utilities (ICKDSF, IDCAMS, IEBCOPY), and tape management systems (TLMS, RMM). Tivoli Advance catalog management (catalog management tool) and IBM Tivoli Advance allocation management for z/OS (allocation optimizer tool) - Connectivity: Understanding of FICON connectivity and z/OS access methods (VSAM, QSAM). - Analytical Thinking: Strong problem-solving abilities to execute complex storage migrations with minimal impact to production workloads Now Skills: Must have Skills list: - Replication and PPRC protocols. - Metro Mirror, Global Mirror, Global Copy - Cyber - Safe Guarded Copy - Experience with Copy Services Manager, ESSNI etc. - Resiliency - Hyperswap & Hyperwrite - Performance - Hyperlinks Nice To Have list: - Certificate deployment and management for network connections - Python or Perl Scripting - GDPS - Secure Vault (Cyber) - Physical and Virtual isolation. - Cloud Storage for tape archival We could combine into one Skills section with two subheadings? But we cannot add extra headings beyond allowed? We can just list all items, maybe mark with (Nice to have) in parentheses. But better to keep as two lists: Must have Skills and Nice to have. However we only have headings for Skills; we could have a single Skills section with two- lists, each preceded by a
indicating category. That's acceptable. Now Benefits: paragraph: "At Morgan Stanley, we raise, manage and allocate capital for our clients – helping them reach their goals. We do it in a way that’s differentiated – and we’ve done that for 90 years. Our values - putting clients first, doing the right thing, leading with exceptional ideas, committing to diversity and inclusion, and giving back - aren’t just beliefs, they guide the decisions we make every day to do what's best for our clients, communities and more than 80,000 employees in 1,200 offices across 42 countries. At Morgan Stanley, you’ll find an opportunity to work alongside the best and the brightest, in an environment where you are supported and empowered. Our teams are relentless collaborators and creative thinkers, fueled by their diverse backgrounds and experiences. We are proud to support our employees and their families at every point along their work-life journey, offering some of the most attractive and comprehensive employee benefits and perks in the industry. There’s also ample opportunity to move about the business for those who show passion and grit in their work. To learn more about our offices across the globe, please copy and paste https://www.morganstanley.com/about-us/global-offices into your browser." Then benefits specifics: "Morgan Stanley offers a full spectrum of benefits, including Medical, Prescription Drug, Dental, Vision, Health Savings Account, Dependent Day