Mainframe Support Overview
Supporting Downer Grove and DCS (Omaha)
[Link]
Luis M Bonilla
2022-0404
During the Presentation…
❖ Meeting to begin 2 minutes after the scheduled time
❖ Meeting will be recorded, voice your concerns
❖ Mute your phone or teams during presentation
❖ Please hold off on questions or concerns until open for Q&A
❖Contributions to this presentation
▪ Kavita Goel
▪ Sandy Quinn
▪ Agata Gugliotta
Private and confidential 2
Where is this stuff
➢SharePoint and Notes
❖[Link]
❖OneNote
– [Link]
99d7-b51f96819ab3}&action=edit&wd=target%[Link]%7C5b1b0268-d29e-4c89-9dc2-
63e3ad0fb88a%2FShare%20and%20stay%20organized%20in%20OneNote%7C6af0c085-1810-4017-aabd-
978d3a47c4b8%2F%29
❖System Software Standards [Link]
Private and confidential 3
Presentation
➢Session one
▪Downers Grove – Primarily production for “classic” Ensono/Acxiom clients
▪Standards for
– Software (HLQs)
– Roll out protocols / procedures
➢Session two
▪Omaha – Primarily production for “classic” DCS clients
▪Standards for
– Software (HLQs)
– Roll out protocols / procedures
Private and confidential 4
Session One Agenda
➢ Ensono Datacenters Overview
▪ Hardware Team Support
➢ Downer Grove LAB1, LAB2, & T-LPARs
▪ Lab Team
▪ APARs and PTFs
➢ Software Rollout
▪ OEM Software Respository
▪ FTP GURU
▪ HLQs OEMPP, OEMDS, OEMA, OEM, & OEML
Private and confidential 5
6
Ensono Datacenter Overview
As far as data centers, our 3 primary data centers are DG, Omaha and Kings Mt.
➢ DG – primarily production for “classic” Ensono/Acxiom clients, but we do
have disaster recovery in DG for many clients that came from DCS
➢ Omaha – primarily production for “classic” DCS clients, but we are doing
disaster recovery in Omaha for our DG clients
➢ Kings Mt – starting to build out and fill KDC, we have production there for
DnB and Windstream. It will get more PROD and DR clients
➢ We also have a DC in the UK and have TESCO as a client there for PROD
➢ We use co-lo data centers and also 3rd party vendor data centers for DR for
many clients (IBM, Sungard, Equinex)
Private and confidential 7
Hardware Support Team
➢ Run team – supports day to day operations and ITSM for our clients – I call
this the daily care and feeding of our clients (manager: Mike Ludwig for HW
and Storage)
➢ Optimize team – works on projects to upgrade existing clients when there is
no revenue associated with it (manager: Sandy Quinn for HW and data
migration) – we’re working on our Data Center Migration project, processor
upgrades to get off a handful of BC12s, and Oracle to IBM tape refresh
projects for both DG and Omaha
➢ Implement team – works on new client migrations and client projects with
associated revenue (manager: Jerry Bunton for HW and data migration)
Private and confidential 8
9
10
LAB Team Support
LAB team manages the software inventories and generate the TADz reports based
on any request.
➢ Management of the SW Upgrade repository to support the SW currency
plan (LAB)
➢ Maintain SW Compatibility Matrix and EOS research (Refreshed on a
Quarterly basis for zOS, DB2, CICS etc.)
➢ SW discovery for ISV products via TADz and generate reports on need basis
➢ SW Upgrade assessment (e.g. version/maintenance upgrade, clean up,
retirement etc.)
➢ Output from assessment and compatibility research will create Initial SW
Upgrade Roadmap
➢ Communication of client specific SW Compatibility assessments for various
internal and client stakeholders
Private and confidential 11
Software Rollout Option
Private and confidential 12
Software Rollout
Private and confidential 13
FTPGURU Option
Private and confidential 14
FTPGURU
Private and confidential 15
Software Standards
Below are the Ensono OEM HLQs definitions and the purpose for its use for supporting HA Group’s environments, in
addition, added the security permissions.
OEMPP.**
➢ HLQ used for base OEM installs datasets supplied by the vendors tape(s) or downloads.
➢ HLQ is not to be used for production use.
➢ Customers must be prevented (via security) from having any access.
➢ Should be SMS Managed.
➢ Version numbers are allowed in the dataset(s)
OEM.**
➢ Used for all datasets not required to be in the master catalog, are not APF authorized, and are vendor supported
datasets. For example, macro and source libraries, ISPF message, panel, skeleton, etc.
➢ Should be SMS Managed.
➢ No version numbers in the dataset(s)are allowed
OEMA.**
➢ Used for all load libraries that are APF authorized and that are not required to be in the master catalog and or in the
LINKLIST.
➢ Intended to be used as a STEPLIB.
➢ Should be SMS Managed.
➢ No version numbers in the dataset(s) are allowed
Private and confidential 16
Software Standards
Below are the Ensono OEM HLQs definitions and the purpose for its use for supporting HA Group’s environments, in
addition, added the security permissions.
OEMDS.**
➢ Used for support datasets (LOG files, the CA-1 TMC, Journals, etc.) that are not allocated by the installation
process.
➢ Should be SMS Managed.
➢ No version numbers in the dataset(s) are allowed
OEML.**
➢ Used for any dataset that is required to be cataloged in the master catalog.
For example, LINKLIST or LPALIST files.
➢ NEVER SMS Managed.
➢ No version numbers in the dataset(s) are allowed
System Software Standards [Link]
Private and confidential 17
End of Session One
Questions and Answers
©2022 Ensono is a registered trademark of Ensono, LP. All rights reserved. [Link]