Jim Moling

Responsibilities include managing and maintaining multiple z/VM systems and SSI clusters across multiple mainframes and locations. These z/VM systems host multiple z/TPF & Linux on Z guests. Also provide support for multiple z/OS systems running across multiple LPARs and mainframes. Also providing mainframe networking and hardware support.

Main responsibilities include working with clients to recover their mainframe systems during disaster recovery tests and/or declarations, and maintaining the DR processes, hardware and software in the hot site area.

Note: FMS & BPD merged to become Fiscal Service. Main responsibilities continue to be the installation, customization, maintenance and support of the mainframe operating systems, which includes MVS, VM and Linux as well as supporting software.

Note: FMS IT Services merged with BPD. Main responsibilities continue to be the installation, customization, maintenance and support of the mainframe operating systems, which includes MVS, VM and Linux as well as supporting software. A few examples are: • Resolved a VM system abend that caused VM to restart by analyzing the system dump that was produced (I/O recovery failure) and sent it to IBM – they created a PTF to resolve it. • Utility – Wrote a Rexx exec for VM called zFCP for determining available FCP addresses for Linux Servers • Cloned a SLES11 virtual Linux server and configured it as a central logging server for all z/Linux servers. • For all z/VM systems: Defined a new command called VMLOGOFF and made the LOGOFF command synonymous with the DISCONNECT command in order to circumvent the tendency to use the LOGOFF command instead of the DISCONNECT command, which could potentially kill a production z/OS system that is being hosted by z/VM. • Designed, developed and tested a methodology for copying the DASD volumes for a virtual Linux server from one data center to another using tape replication through an IBM Virtual Tape Subsystem (VTS) grid. Wrote Rexx execs for z/VM that dynamically obtains the current server configuration from the directory blocks, then generates JCL to backup all of the DASD volumes and submits it to run in a z/OS environment where it uses the DFDSS backup/restore utility. Also wrote Rexx execs for z/OS that are executed from the backup job in order to collect information from the volume backups and generate JCL that is submitted to execute at the remote site to properly catalog the VTS tapes that are replicated so they can be easily restored via the backup data set name.

Main responsibility is for the installation, customization, maintenance and support of the mainframe operating systems, which includes MVS, VM and Linux as well as supporting software. A few examples are: • Installed SLES11 SP1 and established a golden image. Created and configured a cloning server for the SLES11 image. • Created platforms under z/VM for disaster recovery at a new data center for recovering z/OS production systems. • Installed and setup two LPARs to run z/VM at a new data center – one for virtual Linux servers and the other for hosting z/OS guests. • Utility – Wrote Rexx execs and setup XRC DASD menus to assist in moving DASD from one data center to two other data centers (Production to one data center and non-production to the other data center). • Performed the planning, installation, customization and roll-out of an upgrade to the MVS operating system from z/OS 1.9 to z/OS 1.11. • Performed the planning, installation and customization of an upgrade to the VM operating system from z/VM 5.2.0 to z/VM 6.1.0. • Connected virtual Linux servers to a local lab environment by implementing a z/VM virtual switch (VSwitch) configured in trunk mode for access to multiple network segments. The VSwitch was configured to handle the VLAN tags so that each network segment was connected to a server in access mode, thus making the VLAN tags transparent to the servers. • Installed and configured a prototype SLES10 SP2 virtual Linux server that was configured to allow for a read-only root file system. • Designed, developed, tested and implemented a virtual environment under z/VM in preparation for moving the mainframe environment from one data center to another. This virtual environment was setup on a new DS8100 DASD unit and configured with virtual switches under z/VM with IP addresses for the new data center. This process was presented at the SHARE conference in Boston, entitled “Using Virtualization to Help Move a Data Center” on Tuesday, August 3, 2010.

Worked at Financial Management Service (FMS) branch of the U.S. Treasury since point of hire. As Systems Manager for CSC (Computer Sciences Corporation) under the PACER application project, have been responsible for managing a group of up to five other MVS systems programmers. A few examples are: • Sent by CASI to customer site for 2 days at the data center for a southern tri-state bank. Assisted in troubleshooting a CICS transaction response time problem. • Sent by CASI to customer site for 1 day at a military installation in New Jersey. Resolved installation related problems with CA-Sort that was causing sort module Abend's during execution. • Analyzed PACER application program Abend’s via dump analysis on several occasions. • Created and gave a presentation on the new features of OS/390 as part of the process to migrate users from MVS/ESA (4.3.0) to OS/390 (1.1.0). • Designed, developed and implemented automated processes for PACER CM to move programs between the development, integration and production environments. Provided documentation and flow charts of the processes. • Installed and customized the Hourglass 2000 date simulator software product for Y2K testing purposes. The customization included writing a security exit in assembler and designing two authorization tables to limit the scope of jobs influenced by date overrides. The security exit calls the authorization tables, which defines users and their scope of authority for batch jobs. Also created additional panels for the ISPF product interface to support the maintenance of the security exit tables and generate reports for auditing purposes. • Designed, developed and implemented two VTAM SNA system utilities written in assembler for 3270 terminal devices. One determines if a 3270 device supports extended attributes and the other builds a 3270 data stream and displays it on the device with compatible characteristics.

Lead systems programmer with overall responsibility for installation, customization, testing and maintenance of all operating systems and system management software products, disaster recovery preparedness and performance and tuning. Guided three other systems programmers in day to day activities and projects. A few examples are: • Performed extensive performance tuning during a multiple month period prior to the acquisition of additional central processor storage. Through these efforts, impact to service levels was kept to a minimum, thus maintaining a 0.5-second or better end-to-end transaction response time for the production CICS regions. • Designed, developed and implemented a series of reports and graphs on system performance for upper management. SMF data was summarized and downloaded into a PC workstation to generate reports and graphs on system utilization levels and performance. • Implemented the PR/SM feature of the 3090 complex including the development of procedures for operating in a partitioned environment. Setup 2 LPAR’s, one for production and one for system level testing of software & maintenance. • Worked extensively with SMP/E. Designed & implemented a 3 Global Zone structure, one for IBM software, one for all CA software, and one for all other vendor software. Developed and implemented standards and procedures for installation and maintenance of software (for both SMP/E and non-SMP/E packaged software). • Project lead in charge of all disaster recovery technical preparedness. Designed, developed and tested an automated procedure for restoring the system. • Designed, developed and implemented a company wide charge back system. Involved the selection and collection of mainframe environment metrics and porting of data to a charge back system developed and run on a PC workstation that allocated and distributed mainframe costs across company cost centers based on utilization of the metrics and produced both reports and graphs.

Responsibilities included CICS, VTAM & NCP, MVS product installs and maintenance, and system performance and tuning. A few examples are: • Setup and customized VTAM with a multi session manager product (TPX) and converted users commission wide to TPX as the gateway logon to the system. • Setup and tested the first dialup lines to the mainframe with callback security and documented procedures for dialup and session control. Modems attached to AEA adapters on 3174 controllers were configured with dial-back security to insure that only authorized staff could access the system from predefined remote locations. • Setup the PR/SM feature after upgrading from a 3090 180E to a 3090-200E, which included the splitting of the production and development workloads into separate LPAR’s, as well as a third LPAR for systems testing and maintenance. • Setup a common SYSRES volume from which any of the LPAR’s could be IPLed. • To allow cross communication between the LPARS, setup VTAM with CDRM and configured TPX for logon access to each LPAR. • Software installs and maintenance using SMP/E included CA-PANVALET, FOCUS, CA 9, JES328X, TSOPLUS, and a CBIPO install of NCP. • Performed NCP configuration changes; generated & loaded NCP definitions into an IBM 3705 communications controller. • Upgraded MVS/XA 2.1.7 to MVS/XA 2.2.0. Performed various tasks, which included customization of VTAM, TSO/E and ISPF, configured IPL parameters and generating & loading MVSCP & IOCP device configuration decks. • Wrote and modified several MVS and JES2 exits. • Was heavily involved in the preparations and test load of the operating system at a disaster recovery facility following the operating system upgrade to MVS/XA 2.2.0.

Upon arrival, main responsibility was the support and maintenance of VM & DOS/VSE Operating Systems. In spring of 1987, began a migration to MVS/XA. After a two-week course in MVS System Fundamentals, worked exclusively with the MVS/XA system. A few examples of work performed are: • Initially there was one DOS/VSE guest (1.3.5) under VM/SP (3.0.0). Setup and configured a 2nd DOS/VSE guest for programmer testing and development and a 3rd DOS/VSE guest for installing and testing system related software, i.e. monitors, disk & tape management, etc. • Performed hardware configuration activities, such as defining and initializing 3380 DASD. • Performed problem determination of the DOS/VSE systems via dump analysis. • Performed CICS problem resolution using CICS & partition dumps and monitor data. • Performed CICS tuning tasks. • Preparatory tasks for migrating from DOS/VSE guests under VM to an MVS/XA environment included: 1. Replaced the EPIC/VSE tape and DASD manager with CA DYNAM/D, /T, & /FI for MVS compatibility. 2. Replaced VM/SP with VM/HPO for compatibility with an AMDAHL 5890 CPU. 3. Converted from an IBM 4381 to an AMDAHL 5890 190E. 4. Installed 3380 DASD and migrated data from 3330 & 3350 DASD devices. 5. Setup a 4th DOS/VSE guest under VM for isolated testing of pilot applications in parallel with MVS. • Took a two week course in MVS System Fundamentals, since returning from class in mid July of 1987, worked exclusively in the MVS/XA environment, which included: 1. Assisted in the initial install and tailoring of MVS/XA 2.1.7 using the MVS/Express option from IBM. 2. Installed CA ACTIVATOR, CA DYNAM/TLMS & DASD, CA JARS, and CA OPTIMIZER. 3. Learned how to use OMEGAMON/MVS to analyze system performance. 4. Wrote various exits for MVS and tape management control. 5. Designed and documented a comprehensive system backup and recovery plan.

Hired as the first systems programmer for their mainframe, was initially responsible for an IBM 4331 running SSX/VSE. The system was upgraded to an IBM 4361 running VM/SP (4.0.0) with a DOS/VSE/SP (2.1.4) guest machine before leaving. A few examples of work performed are: • Initially, the system configuration consisted of an IBM 4331 running a self-maintaining small version of DOS/VSE in native mode called the Small System Executive (SSX/VSE). This system had become very unstable, resulting in CICS crashes on a daily basis. Initial task was to restore stability to CICS and the rest of the system. • To run SAS and SYSTEM 2000 required installing the VM operating system. This resulted in installing VM/SP 3.1.0 with SSX/VSE running as the preferred VM guest machine. • Configuring SSX/VSE to run under VM was a major challenge as it was not designed for this and required extensive analysis and debugging. Talked to the IBM developers of SSX/VSE in Germany at one point. • Worked with and instructed the operators on VM operating procedures. Developed and maintained menu driven interfaces under CMS to allow the operators to easily perform many routine tasks such as the IPL and shutdown of the SSX/VSE guest machine. • Planned and implemented a migration from SSX/VSE to DOS/VSE/SP 2.1.4. • Planned and implemented an upgrade from VM/SP 3.1.0 to 4.0.0. • Was involved in the planning and procurement of an IBM 4361 and various other equipment, i.e. 3422 tape drives, 3820 laser printer, and 4245 line printer. • Setup remote dial up lines via an IBM 7171 ASCII converter and established cross communications to a WANG VS100. • Assisted programmers in solving programming errors, installing software packages (general ledger, accounts payable & receivable, etc.), and setting up JCL. Also assisted in establishing JCL conventions for production jobs. • Using VTAM under DOS/VSE, defined remote lines and adjusted buffers to improve performance.