Z/OS systems programmers

Indra Ver Empresa

Não especificado
9º Ano

Horário

40 horas por semana

Língua(s)

PT, ES, INGLÊS

Referência Interna

EPO

1.   z/Admin

1) Design and build of system software procedures deployment and maintenance:

a. System software design oriented to support application solution and security architecture.

b. Determine the base software instances structure required to meet application demands.

c. Implement the strategy to routine patches and upgrades delivery, according to the policy dictated by the vendor or Release Management and having into account the requirements from the business.

2) System software engineering:

a. Define and apply standards to create or modify software infrastructure objects.

b. Implement the strategy to provide the operational areas with procedures to perform deployments between different product versions or migrate to alternative solutions.

3) Network engineering:

a. Designing and implementing the mainframe networks, based mainly on Transmission Control Protocol / Internet Protocol (TCP/IP) and on IBM Systems Network Architecture (SNA), taking the form of the communications package Virtual telecommunications access method (VTAM).

b. Maintaining network performance.

c. Troubleshooting network problems.

d. Researching and integrating new technologies into the network lifecycle under the guidance of Directorate 4103 Security, Architecture & Innovation.

e. Interfacing with network administrators from Department 4142 Network & Data Center Management to manage or assist problems.

f. Maintain network integrity and resilience.

g. Staying abreast of necessary network updates.

4) Ensure delivery of support to developers:

a. In coordination with technical staff and contractors from PD Service Creation, ensure delivery of the necessary level of support in order to enable the development teams to build operational system software.

5) System tuning strategy:

a. Definition of system monitoring of performance through the existing tools to proactively prevent any potential SLA infringement and, upon identification of improvement opportunities, suggest and implement changes.

6) Capacity planning:

a. Related to the overall system and associated subsystems, performing installation-specific customization tasks, including integration-testing of associated products with base software, existing applications and user procedures.

b. This capacity planning must be embedded within system-wide performance tuning to meet the required levels of service.

7) Debugging problems with system software:

a. Determine where system and/or application components failed through inspection of copies of the computer’s memory contents generated in dumps and specialized debugging tools.

b. Escalate unresolved issues to the software vendor’s support representatives to discover whether the problem’s cause is known and whether a patch is available or find a workaround.

c. This Service Group is expected to be skilled on REXX and z/OS assembler language programming.

8) License Compliance Management:

a. Installation of software products on z/OS systems, and tracking software modifications to those products, through IBM System Modification Program/Extended (SMP/E) or Z/OS Management Facility (MF).

b. Produce z/OS deployment details from Resource Management Facility (RMF) ad-hoc reports.

c. Install and maintenance of the Sub-Capacity Reporting Tool (SCRT), showing software quantities consumed. Own the responsibility of SCRT reports submission to IBM each month in order to qualify for sub-capacity charges for any of the price metrics defined by IBM.

d. SMP/E or z/OS MF completeness assurance, to detect IBM customer Agreement (ICA) and International Product License Agreement (IPLA) which are not reported in SCRT, even when they are not used.

e. SCRT completeness assurance to ensure reports are provided on all LPARs and z/VM guests using 95% of the System Management Facility (SMF) records.

f. Determine non SCRT product license deployments according to the current version of EPO IBM License Management Plan 2016 – 2019 and future updates.

g. Maintenance of the z Series software roadmap.

2 Prod Merge:

1) Maintain and support customization made around these products, which mainly consist on REXX procedures 3rd party software engineering.

a. Customization on SCLM.

2) Maintenance of the batch delivery procedures.

3) Ensure delivery of support to application software deployment procedures users.

a. User community integrated by:

b. Developers in non-protected environments (Development, Test/Integration).

c. ProdMergeOper in protected environments (Development, Test/Integration/OSA/UAT/Maintenance, Production and Disaster Recovery).

4) Debugging problems with system software:

a. Determine where system and/or application components failed through inspection of copies of the computer’s memory contents generated in dumps and specialized debugging tools.

b. Escalate unresolved issues to the software vendor’s support representatives to discover whether the problem’s cause is known and whether a patch is available or find a workaround.

c. This Service Group is expected to be skilled on REXX and z/OS assembler language programming.

Você tem que entrar na sua conta para poder candidatar-se a esta oferta.

Nós ajudamos a encontrar
o emprego certo para si.

Nós ajudamos a encontrar os
candidatos certos para a sua empresa.