I have worked in a couple locations that are smaller than you mentioned.
3 LPARS, 10-12 CICS images, DB2. We had 4 in both locations. Following
is the general breakdown of tasks. Fortunately there was very little
turnover.
Jim
Lead Systems Programmer
Primary responsibilities
z/OS
Performance and tuning
Networking
System problems
Secondary responsibilities
CICS and DB2
Unix System Services
Hierarchical File System
Disaster Recovery
Systems Programmer
Primary responsibilities
DB2
Storage Administration
Backups
Disaster Recovery
Secondary responsibilities
CICS and z/OS
Security Administration
Performance and tuning
System problems
Systems Programmer
Primary responsibilities
Printing issues
ADSM
RMM
Security Administration
Secondary responsibilities
CICS and z/OS and DB2
Storage Administration
Backups
System problems
Systems Programmer
Primary responsibilities
CICS
IBM product installation
ISV product installations
Unix System Services
Hierarchical File System
Secondary responsibilities
z/OS and DB2
System problems
Hierarchical File System
Web Servers
Disaster Recovery
System problems
All
ISV product installations
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Staller, Allan
Sent: Monday, February 11, 2008 12:14 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: z/OS system programmer staffing
Although the relationship is not linear, there is also the issue of
complexity to be dealt with.
At one shop I worked, (10 sysplexs, 44 LPARs, 20+ CECs), the CICS person
was
Actually 5 people). The z/OS sysprog was 8 and the Oracle(DB2/IMS)
person was 6.
In my current environment, all of the below is 4.
HTH,
<snip>
CICS is generally one person.
Oracle is generally one person as well.
z/VM and Linux - one or two primary people, depending on the number of
VMs and Linux instances. The z/OS sysprogs are capable of pulling double
duty here, but that may be cutting it to close.
You do not mention performance and capacity, storage management or web
services. Shift coverage, sick time, vacations, etc. are other
considerations.
With a variety of skill levels, the number should probably be between
15-20 people if you include the skills and issues that I mentioned.
With highly experienced systems programmers in all of the above
disciplines, 10-15. Less than 10 would affect your shop's ability to
meet schedules *or* would probably lead to burnout.
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
