1 / 13

ACSPAC Operating Systems Deployment Assessment Overview

This overview outlines the standards and practices used in the corporate deployment of mainframe operating systems by ACS. It aids in determining changes required for successful deployment of ACSPAC operating systems models.

josephwells
Download Presentation

ACSPAC Operating Systems Deployment Assessment Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ACSPAC Operating Systems Deployment Assessment Overview SES-PBCT Team – Spring 2004 Slide 1

  2. Introduction • This outline is intended for those that are responsible for the support and deployment of OS/390 and z/OS Mainframe operating systems in the ACS corporate environment. It outlines standards and practices used in the corporate deployment of mainframe operating systems by ACS. • The material presented during this overview is used to aid in determination of changes that are required for the successful deployment of ACSPAC operating systems models. Slide 2

  3. Systems Upgrade Assessment • Current System Maintenance requirements • Security Product Considerations • Product support Review • System Catalog Structure Analysis • Workload Analysis and Definitions • System Exit and parameter research and diligence • JES Subsystem Considerations • System Procedure Library Research • TSO/ISPF Procedure Research Slide 3

  4. Systems Upgrade Assessment • Sample System - Wabash Cannonball Rail Systems • Medium Workload System • DB2/CICS Online Predominant • Upgraded 2.5 years ago • Server PAC install Slide 4

  5. Systems Upgrade Assessment Toleration Maintenance • SES-CMOS team determines the current maintenance level. • SES-CMOS team determines proper toleration maintenance level for “target” operating systems environment. • SES-CMOS team applies any necessary toleration maintenance to the ‘existing’ system. • SES-CMOS team determines if the toleration maintenance is co-existence, or fallback. • The two levels of operating system cannot operate in tandem, if only fallback is available. Slide 5

  6. Systems Upgrade Assessment Security Packages • The most current level of the RACF Security Server is installed in the delivered ACS OS-Base by default. • SES-CMOS team will ensure that the correct level of CA-ACF2, or CA-TSS (Top Secret) is installed prior to the upgrade, or research to determine impact of pairing the update of the product with the upgrade. Slide 6

  7. Systems Upgrade Assessment Program Products • Each product that requires update will be done prior to the upgrade, where applicable. In certain situations, a product upgrade may be required to be ‘paired’ with the upgrade, or another product, because of interdependency. • Consult the Software inventory for the client, and the recommended product list for the Operating system upgrade level. Slide 7

  8. Systems Upgrade Assessment System Catalog Analysis • Certain rules are in place for the operating system master catalog. With the ACS operating systems model, a new master catalog is delivered the first time the model is deployed for any LPAR. • All data sets with the exception of high-level qualifiers SYS1, SYS2, and PAGE, must be catalogued in User Catalogs, and accessed via Aliases in the master catalog. • Generation Data Groups(GDG’s) and other data sets that are not part of the “delivered operating system will be relocated. • If the SYS2 high level data set qualifier is an alias on the target system, a procedure exists to substitute the qualifier SYSACS. • Generate work requests to relocate entries from the master catalog to user catalogs, security adjustments, SMS adjustments (if required). The catalog structure, and any deviations must be documented in the “Systems Information Document” for this customer Slide 8

  9. Systems Upgrade Assessment System Exit Analysis • The system exits that are in use must be identified, and the correct source must be located, inventoried, and documented, if not already done; • Document any Security package Exits • Document any SMF exits • Document any DADSM (DFP) Exits • Document JES2 Exits • Document any SMS/HSM/TMS/TLMS Exits • Document any PSF Exits • Document any ISPF/PDF Exits • Document any TSO Exits • Document any Rexx Option Modules • Document SDSF parameters • Document Cobol Option parameters • Document HLA Option parameters • Document LE/370 Option parameters Document the exits in the “System Information Document” for this customer; Have Source for exits placed in SYS2.SOURCE.&SYSNAME Have Application JCL placed in SYS2.STAGELIB.&SYSNAME Slide 9

  10. Systems Upgrade Assessment JES2 Subsystem Analysis • The parameters, and resources in use by the target systems JES2 subsystem must be documented, and converted to meet the model requirements • Determine where JES* parameters are located. • Request that SES-CMOS team review the JES2 parameters for necessary conversion. • Verify Exits used are accounted for in “System Exit Analysis”. • Document the JES2 information in the “System Information Document” in the “JES2 Information” section for this customer. • Place Source for exits in SYS2.SOURCE.&SYSNAME. • Place Application JCL in SYS2.STAGELIB.&SYSNAME. • Optionally, request segregation of the JES2 parameters into the standard ACS member names; • COMMONxx - Basic JOB/STC/OUTCLASS/EXIT definitions • COMSYSxx - System(SpoolDef/Checkptdef/MASDEF/Inits) • COMNETxx - Network Definitions • COMPRTxx - Printer Definitions Slide 10

  11. Systems Upgrade Assessment System Procedure Library Research • Research System Procedure Library concatenation for local procedures in non-standard libraries; • Analyze contents of system procedure library concatenations. • Identify Non IBM procedures contained in SYS1.PROCLIB. • Verify no IBM procedures are duplicated in concatenation. • Document any exceptions, or customer requirements for customer modified IBM procedures. • Document the System Procedure concatenation findings, or exceptions in the “System Information Document”(SID) for this customer. Slide 11

  12. Systems Upgrade Assessment - TSO Logon Procedure Research • Research system TSO/ISPF logon procedures for non-standard content; • Determine/Document location of target system TSO/ISPF Logon Procedures. • Identify any procedures with STEPCAT or STEPLIB statements. • Identify any Procedures with hard coded volume references. • Identify any ISPF invocation CLIST's that allocate ISPF environment. • Work Request to populate SYS2.TSO.PROCLIB.&SYSNAME with TSO/ISPF logon procedures for target system. • Document the System Procedure concatenation findings, or exceptions in the “System Information Document” for this customer. Slide 12

  13. Systems Upgrade Assessment Miscellaneous Assessment Tasks • Developing A System Upgrade Testing Plan; • Timeline 2 ACS Only, and 3 Customer Tests • Operating System Base testing • Tape/Silo Operations (CA1/Rmm/Mim/HSC/VTS) • Program Product IVP’s • Database System Testing (DB2/IDMS/ADABASE) • Online Systems (CICS/IMS-DBDC) • Communications Software (Multisess/TPX/VPS/NDM/NET/TCPIP/FTP) • Print Subsystems Software (PSF/XPAF) • Print Archival Systems (View/Express/Dispatch/Xporter) • Customer Specific Dependencies; • Mission Critical Online Testing • Mission Critical Batch Testing • Mission Critical Network Requirements Slide 13

More Related