ACS Operating Systems Deployment/Upgrade Overview

1. ACS Operating Systems Deployment/Upgrade Overview SES-PBCT Team - Summer, 2004 – Release 2.0 Slide 1

2. Introduction • This outline is intended for those that are responsible for the support and deployment of 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 can be used to aid in future operating systems upgrade planning, and upgrade activities. Slide 2

3. Overview Outline Slide 3

4. Systems Deployment Components • Systems Upgrade Assessment Guide • This checklist is used to determine nuances between the current production system, and the ‘delivered’ operating system, and identifies pre-upgrade adjustments that need to be made PRIOR to the start of the upgrade. • Systems Deployment Guide • This document contains the details necessary to install, customize and deploy the operating systems upgrade. • System Information Document • This document is used to reflect the upgraded environment, document exceptions, and user modifications to the base model. Slide 4

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

6. Systems Deployment Guide • System Structure Overview • System Pre-upgrade Assessment Details • System Upgrade preparation tasks • System Restore Procedures • Primary configuration procedures • Build catalog Volume and environmental data sets. • Build Master catalog and populate with Operating system, and customer entries. • Build/Apply OMVS file system Updates (New, and existing, if applicable). • Local Customization • Standardization of Operating System parameters. • Standardization of User modifications to system. • Standardization of System Procedure libraries. • Standardization of TSO/ISPF Procedures and ISPF invocation methods. Slide 6

7. Systems Deployment Guide (continued) • Local Customization (continued) • Customization of OMVS parameters and files. • Customization of Security System Interface. • Customization of local SMP/E environment. • User Modification Jobs for SYS1.PARMLIB. • Pre-IPL Final Customization Checklist. • Systems Maintenance • Maintenance Procedure Checklist. • Maintenance Procedure. Slide 7

8. System Information Document • System Software Levels • System Catalog Structure • System Parameter libraries • Operating system Exits (DFP, SMF,etc) • Supervisor Call Modules • JES2 Parameter Information • Spool/checkpoint • JES2 User Exits • JFIX testing Subsystem • TSO Logon Procedures • ACS Standard • Customer Usage • ACS Libraries (Location of source, JCL, or customer specific information) • Operating System exceptions to the “delivered” ACS OS/Base • SMP/E Environment • SMP/E Global Zones • SMP/E Exceptions Slide 8

9. Operating Systems Deployment Primary Upgrade Process Slide 8a

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

11. 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. RSU0212 is the minimum level. • 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 10

12. 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 11

13. 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 12

14. 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 13

15. 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 14

16. 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 15

17. 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 16

18. 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 17

19. 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 18

20. Systems Deployment GuidePreparation Checklist • Pre-Upgrade Assessment checklist from ACS Systems Deployment Guide. • Checklist will be completed within 2 months of start of project. • Outlines additional tasks that are part of the process in getting the upgrade started. • It covers both the aspects of the technical assessment, and the client involvement required for the upgrade. • The resources to be used in the upgrade, DASD, Test LPAR versus standalone testing are outlined. • Request of the distribution package from the SES-PBCT team. • Once the DASD volumes have been received from SES-STOR, the construction phase can begin. Slide 19

21. Systems Deployment Guide Standalone System GenerationRestore Checklist • Z/OS Model 9 Upgrade Restore checklist from ACS Systems Deployment Guide • RF000100 Initialize “A” suite of Volumes - Executed by SES/STOR. • RF000150 Remove VTOC indexes from volumes - Executed by SES-STOR. • RF500000 Full Pack restore of system residence Volume 1. • RF500200 Full Pack restore of system Distribution volume 1. • RF500400 Logical restore of system SMP/E data sets. • RF500500 Logical restore of system volume 1. • RF500600 Full Pack Restore of Book Manager volume. • RF500700 Full Pack Restore of OMVS volume. • RF500800 Create Standalone Dump Text on Catalog volume - Executed by SES-STOR. Slide 20

22. Systems Deployment Guide Standalone System Generation Restore Checklist • Z/OS Model 3 Upgrade Restore checklist from ACS Systems Deployment Guide • RF000100 Initialize “A” suite of Volumes - Executed by SES/STOR. • RF000150 Remove VTOC indexes from volumes - Executed by SES-STOR. • RF500000 Full Pack restore of system residence Volumes 1 and 2. • RF500200 Full Pack restore of system Distribution volumes 1, 2, and 3. • RF500300 Full Pack restore of system OMVS HFS volume. • RF500400 Logical restore of system SMP/E data sets. • RF500500 Logical restore of system volume 1. • RF500600 Full Pack Restore of Book Manager volume. • RF500700 Full Pack Restore of OMVS volume. • RF500800 Create Standalone Dump Text on Catalog volume - Executed by SES-STOR. Slide 20a

23. Systems Deployment Guide Standalone System Generation Restore Checklist (continued) This step is optional until Implementation Day • Upgrade Restore checklist from ACS Systems Deployment Guide • CLAB0100 Initialize “B” suite of Volumes - Executed by SES/STOR upon request by SES-CMOS team. • CLAB0150 Remove VTOC indexes from volumes - Executed by SES/STOR upon request by SES-CMOS team. • CLAB1000Copy the “A” suite residence volumes to the “B”suite residence volumes. • CLAB1100 Copy the “A” suite distribution volumes to the “B”suite distribution volumes. • CLAB1200 Copy the “A” suite OMVS HFS /ETC to the “B”suite OMVS HFS /etc - must be mounted READ ONLY. • CLAB1300 Copy the “A” suite OMVS HFS /ROOT to the “B”suite OMVS HFS /root - must be mounted READ ONLY. • CLAB1400 Copy the “A” suite OMVS HFS /HOD to the “B”suite OMVS HFS /hod - must be mounted READ ONLY. Slide 21

24. Systems Deployment GuideStandalone System Generation Primary Configuration Checklist • Construct the New Master catalog for the upgrade • CA000300 Define Master Catalog and User Catalog. • CA000400 Define Master Catalog Base Entries. • CA000500 Define ACS System Entries for SYS2/SYSACS. • CA000900 Create Catalog Entries from production system. • CA000910 Apply Production system catalog entries. Slide 22

25. Systems Deployment GuideStandalone System Generation Primary Configuration Checklist (continued) • Generating the Production Catalog System Entries • CA000900 Create Catalog Entries from production system; • Edit the JCL for the master catalog name of the production system. • Edit the JCL for the output PDS data set name. • Submit and execute the job on the production system. • Examine IMPORT member to ensure catalog connects are valid. • Examine NONVSAM for non-system data sets in master catalog; • GDG’s are special, and will require frequent re-sync of the entries • Non-System Datasets will be relocated out of the master catalog • Examine MISC member for entries not processed by MCNVTCAT utility. These data sets must be accounted for. Slide 23

26. Systems Deployment GuideStandalone System Generation Primary Configuration Checklist (continued) Building the Environmental Data Sets • Required for Model Compliance • CA002800 Restore fixed data sets to catalog volume - This job is required. • CA004200 Create local SMP/E procedure (SMPEZS14). • Optional Steps – Needed for first time standalone system generation. • CA001000 Allocate Broadcast Data Set. • CA001200 Allocate/catalog DAE for the new system. • CA001400 Allocate/catalog Dump Data sets for new system. • CA001600 Allocate/Catalog SDSF ISF Index Data set. • CA002000 Allocate/Catalog/Build MMS data set SYS1.ENURMF. • CA002200 Allocate/Catalog Logrec. • CA002400 Allocate/Catalog SMF data sets. • CA002600/CA002601 Allocate/Catalog/Copy SYS1.UADS. If your existing UADS LRECL is not 172 use CA002601 to convert the UADS to the new format, and store the data set on XXCT01. This slide assumes SYS2 High Level Qualifier is in the master catalog. Slide 24

27. Systems Deployment Guide Standalone System Generation Primary Configuration Checklist (continued) • Building the Environmental Data Sets (continued) • Optional Steps - Needed for first time standalone system generation; • OMVS User HFS Data set; • CA002900 Create User HFS and Mount Point for User HFS. • CA003000 Create user directories within the User HFS. • CA003200 Build/populate standalone SMS configuration data sets. • CA003800 Define standalone Page data sets. • CA004000 Build local user modification source and staging libraries. • CA004300 Define standalone JES2 Spool, checkpoint, and build SYS2.PARMLIB JES2 members. • CA004500 Build standalone SYS1,PARMLIB and startup Parameter set. • CA004600 Build ACSIVP Configuration member for standalone IVP execution Slide 25

28. Systems Deployment GuideLocal System Customization • Customization of SYS1.PARMLIB – Use this process if job CA004500 was NOT executed. • Use symbolic parameters where ever possible; • &SYSNAME - 4 character System Name. • &SYSCLONE - 2 character Suffix (positions 1 and 4 of sysname). • &SYSR1 - 6 character Volume serial of residence volume 1. • &ZSRS2 - 6 character Volume serial of residence volume 2 for ACSPAC Model 9 z/OS • &Z3RS2 - 6 character Volume serial of residence volume 2 for ACSPAC Model 3 z/OS • &SYSC1 - 6 character Volume serial of cat volume. • &SYSPLEX - Name of SYSPLEX complex (if required). • &SYSACS - Indicates whether SYS2, or SYSACS is in use. • &SYSHOST - DFHSM Parameters. • Create new SYS1.PARMLIB members on the NEW catalog xxCT01 volume based uponproduction members, and required modifications due to the operating system level. • Model members can be found in SYS1.IBM.PARMLIB on XXRSA1 volume. The recommendations in the chart are only a guide. You need to make a thorough analysis of the production system parameters, and adjust your NEW parameter members accordingly. Slide 26

29. Systems Deployment GuideLocal System Customization (continued) • Establishing the order of libraries in the LPA List member • Several considerations must be made when merging the LPA list for OS/390 2.10 and the existing LPA data sets in use on the production system. • Place the “current” LE/370 LPA library ahead of SYS1.CEE.SCEELPA. • If the client uses SYNCSORT, instead of DFSort, place the SYNCSORT LPA library ahead of SYS1.SORTLPA. • Place any additional LPAR or product specific LPAR libraries at the end. • Be sure to check how the libraries you add to the list affect the private region area sizes. If the private region size changes, notify your SES-CMOS team manager for disposition. Note: Your application may vary somewhat, based upon local requirements. Slide 27

30. Systems Deployment GuideLocal System Customization (continued) • Establishing the order of libraries in the Link List member; • Several considerations must be made when merging the link list for OS/390 2.10 and the existing Link List data sets in use on the production system. • Place the “current” LE/370 Link List library ahead of SYS1.CEE.SCEERUN. • Place any additional LPAR or product specific LPAR libraries at the end. • Note: Your application may vary somewhat, based upon local requirements. Slide 28

31. Systems Deployment GuideLocal System Customization(continued) • Customization of SYS2.PARMLIB.&SYSNAME(WCRS) • Compare “production”SYS1.PARMLIB for unmatched members. • Copy Unmatched members to SYS2.PARMLIB.&SYSNAME. • Customization of SYS2.PARMLIB • SES-CMOS teamsegregated Parameters stored in this library. NOTE: The parameter members you relocate may have references in procedures, or JCL that must be resolved to access the member in the new parameter library data set.Any altered procedures should be stored in SYS2.PROCLIB.&SYSNAME. Slide 29

32. Systems Deployment Guide Local System Customization(continued) • Customization of SYS2.PROCLIB.WCRS • Compare “current”SYS1.PROCLIB for unmatched members. • Copy Unmatched members to SYS2.PROCLIB.WCRSon WSCT01. • Customization of SYS2.PROCLIB • Compare “current”SYS2.PROCLIB for unmatched members. • Copy Unmatched members to SYS2.PROCLIB on WSCT01. • Create JES2 User mod for I2JES2&SYSCLONE . • Verify JES2 Proc Symbolic parameters in JES2 PROC in SYS2.PROCLIB. • Verify Program Product JCL Procedures pre-placed by Build Process. • Verify JFIX JCL procedure present in SYS2.PROCLIB on WSCT01. • Verify and copy NET JCL Proc to SYS2.PROCLIB. Slide 30

33. Systems Deployment GuideLocal System Customization(continued) • Customization of SYS2.TSO.PROCLIB.WCRS • Verify all TSO Logon JCL procedures from assessment Phase. • Copy TSO Logon JCL Procedures to SYS2.TSO.PROCLIB.WCRS on WSCT01. Slide 31

34. Systems Deployment GuideLocal System Customization(continued) • Understanding the OMVS Environment • Root (“ / “) directory significance. • ETC (“/etc”) directory significance. • Mount Points and their functions. • Determining “Current” mount points using ISHELL/OMVS. • Relation of BPXPARMxx statements to the mounted Unix System Services file systems. • Key points to consider; • HFS data sets are mounted as READ/WRITE to OS/390, unless shared by other LPAR’s, or systems. • HFS ROOT and ETC data sets are specific to the maintenance level of the operating system. Slide 32

35. Systems Deployment GuideLocal System Customization(continued) • The OMVS Root (“ / “) directory significance • Top level Parent OMVS data set. • Root contains IBM Only Data and Directories , and mount points for other HFS data sets. • REQUIRED for USS operation. • Defined to OS/390 in the ROOT FILESYSTEM statement in SYS1.PARMLIB member BPXPRMxx. • Root can be UNMOUNTED to place it into READ ONLY mode for copy, or backup. • Important Directories; • /bin - Most common Unix commands. • /usr/sbin - Superuser commands • /etc - Files used by network, and NFS. • /var - Administrative files, logs, etc. • /var/spool - Temporary work space. • /usr/lib - Standard Libraries, such as libc.a. • /usr/local - Local programs and files. Slide 33

36. Systems Deployment GuideLocal System Customization(continued) • The OMVS ETC (“/etc”) directory significance • IBM supplied symbolic mount point defined in ROOT. • REQUIRED for USS operation. • Defined to z/OS in a MOUNT FILESYSTEM statement in SYS1.PARMLIB member BPXPRMxx. • The /etc file system can be UNMOUNTED to place it into READ ONLY mode for copy, or backup. Slide 34

37. Systems Deployment GuideLocal System Customization(continued) Type Perm Changed (GMT) Owner Size File File 644 04/11/2001 16:38 IBMUSER 2587 init.options Syml 777 04/09/2001 22:42 IBMUSER 22 ioepdcf Dir 755 05/10/2002 20:37 IBMUSER 8192 kirk • Understanding USS File Permissions • Permissions shown in this example are ‘absolute’ mode values. Permissions are also stated as; • r - Read (4) • w - Write(2) • x - Execute(1) • Permissions are applicable to files and directories within the USS File systems. • Permissions are separated into three areas, Owner, Group, and Other Access. • Access is specified for each area, and is combined to make the permission “bits” for the file, or directory. • Each access level is added or removed, using the CHMOD command. Slide 35

38. Systems Deployment GuideLocal System Customization(continued) • OMVS Mount Points and their functions • When an HFS data store is mounted, it is really a “link” between the MVS data set, and the Unix system Directory entry. When a mount point is created, it establishes that link. • Certain IBM and OEM vendor products may have an HFS, or be completely HFS based, and require a mount point in the HFS environment. • Display of Existing OMVS Structure (Command: D OMVS,F command) to determine any additional mount points installed in the current system. • The order of display of the mounted HFS data sets is ‘LIFO’, Last-In-First-Out. Slide 36

39. Systems Deployment GuideLocal System Customization(continued) • Relation of BPXPRMxx statements to the mounted Unix System Services file systems • Minimum Requirements; • HFS Root/root SYS1.OMVS.HFS.ROOT.&SYSRS1 • HFS Root/etc SYS1.OMVS.HFS.ETC.&SYSRS1 • HFS root and etc data sets are SPECIFIC to the level of operating system upgrade. • Controlled by SYS1.PARMLIB member BPXPRMWS (&SYSCLONE). • Root HFS contains mount points for other HFS data sets mounted. Slide 37

40. Systems Deployment GuideLocal System Customization(continued) • Customization of the Security System Interface. • RACF Security Server is installed in the delivered operating system. • CA-ACF2 and CA-TSS installations have specific requirements. • Each Security subsystem has it’s own installation checklists. • ACS required access for high level qualifiers ACSNS, ACSVS, CPAC, IBMBK, SYS1, (SYS2, or SYSACS) - whichever is in use. • Consult Vendor Web Site for latest OMVS segment updates for CA-ACF2, and CA-TSS. Slide 38

41. Systems Deployment Guide Local System Customization (continued) • ACSPAC Model 9 Z/OS SMP/E Procedure and Customization • Alternate “suite” methodology used for maintenance application. • Volume allocations controlled by DDDEF definitions within the SMP/E zones. • SMPEZS14 is standard SMP/E JCL procedure, stored in *SYS2.PROCLIB.&SYSNAME. • New SMP/E CSI’s delivered with each refresh, differentiated by put level in CSI data set name; • Current: SMPE.ZS14M9.P0404.GLOBAL.CSI • New: SMPE.ZS14M9.P0404.GLOBAL.CSI • Note: SMPPTS, and LOG data sets also provided with each refresh * This Slide assumes the “SYS2” HLQ is in use. Slide 39

42. Systems Deployment Guide Local System Customization (continued) • ACSPAC Model 3 Z/OS SMP/E Procedure and Customization • Alternate “suite” methodology used for maintenance application. • Volume allocations controlled by DDDEF definitions within the SMP/E zones. • SMPEZS14 is standard SMP/E JCL procedure, stored in *SYS2.PROCLIB.&SYSNAME. • New SMP/E CSI’s delivered with each refresh, differentiated by put level in CSI data set name; • Current: SMPE.ZS14M3.P0404.GLOBAL.CSI • New: SMPE.ZS14M3.P0404.GLOBAL.CSI • Note: SMPPTS, and LOG data sets also provided with each refresh * This Slide assumes the “SYS2” HLQ is in use. Slide 39a

43. Systems Deployment Guide Local System Customization (continued) • Z/OS SMP/E Procedure and Customization (continued) • Alternate suite is refreshed from the production suite, and maintenance is applied to the alternate volume suite. • All local exits and modifications have SMP/E user modification jobs. • Key Points; • When Replacing an IBM module, it will be replaced in “originating” library the module resided in. • When an IBM sample module is ADDED, it will be stored in SYS2.LINKLIB.&SYSNAME, or SYS2.LPALIB.&SYSNAME. • The exception to this addition rule are modules that are required to be stored in SYS1.NUCLEUS. Slide 40

44. Systems Deployment Guide Local System Customization (continued) Corporate user Modifications Installed • ACS Pre-Installed User Modifications • Corporate User Modifications applied to base system shown at left; • Source for corporate modifications is located in member CORPUMOD in SYS2.INSTLIB.&SYSNAME. ZS390M?.P????. Run this job to add the source members to your local SYS2.SOURCE.&SYSNAME data set. • JCL for corporate modifications is located in member CORPUJCL in SYS2.INSTLIB.&SYSNAME.OS3902A.P????. Run this job to add the application JCL members to your local SYS2.STAGELIB.&SYSNAME data set. Slide 41

45. Systems Deployment Guide Local System Customization (continued) • USERMODS for SYS1.PARMLIB • For each member shown in the chart, there will be a user modification job. • USERMOD job will; • Backup parm member. • Update Parm member from SYS2.SOURCE.&SYSNAME. • Compare old to new for differences. • Output from Parmlib USERMOD jobs stored in a print archival product for future reference. • Standardized procedure for the creation of SYS1.PARMLIB user modification jobs is shipped with package. Slide 42

46. Systems Deployment Guide Local System Customization (continued) • Building Your PARMLIB User Modification Jobs • ACS Corporate Provided Utility. • Copy control members. • Edit Control members. • Run Extract Job. • Copy Rexx Exec’s. • Execute the Rexx to generate PARMLIB user modifications jobs. • Updates to SYS1.PARMLIB to be done through USERMOD jobs only. • To be done at END of upgrade to prevent overlay, or confusion. • Output of USERMOD jobs will be archived for future reference needs. Thanks to the SES-CMOS-RED team for this contribution. Slide 43

47. Systems Deployment Guide Local System Customization (continued) • Pre-IPL Final Customization Checklist • “Suggested” Final Checklist, to be used prior to first IPL of z/OS 1.4 system. • Checklist verifies ONLY z/OS model components. • Verifies all environmental data sets. • Verifies IPL critical resources. • Deviations from the content of this checklist must be documented in the SID. • IPL the primary system, and run the baseline z/OS IVP processes to certify the system. • Baseline IVP’s; • Base IPL (OMVS, JES2, NET) • TSO/ISPF Logon • Batch IVP Executions Foil assumes the “B” suite is in use Slide 44

48. Systems Deployment Guide Primary Upgrade complete! Slide 45

49. Systems Deployment GuideOperating System “Refresh” Procedures Not all steps may be required, if a previous alternate suite is present. Consult with SES-CMOS team manager. • What is an Operating System “Refresh”? - Itprovides an operating system with a higher level set of maintenance. This summary Checklist defines; • Part 1 - Research and Preparation • Review Systems Information Document for system. • Review User modifications to current system. • Request of New Operating system Level package from SES-PBCT. • Part 2 - Restore OS refresh • Steps 10 and 11 require the assistance of TSG-STOR. • Model 3 z/OS • Full volume restore 6 volumes. • Logically Restore 2 volumes. • Model 9 z/OS • Full volume restore 2 volumes. • Logically Restore 1 volume. • Part 3 - Apply Local User Modifications • SMP/E Adjustments for new zones. • Re-Application of local User Modification Jobs. • Part 4 - Pre-IPL verifications • Part 5 - Post Refresh cleanup Foil assumes the “B” suite is in use Slide 46

50. Systems Deployment GuideOperating System “Refresh” Procedures (continued) • Operating System “Refresh” Flowchart - Part 1 - Research and Preparation • A refresh request will begin with a peregrine request, initiated by the customer, or processing requirement. • Review of the LPAR documentation to familiarize oneself with any special requirements; • System Information Document. • Post Mortems. • Generate a SMP/E User modification report from the SMP/E zone. • Compare user mods against ones listed in the SID (System Information Document). • Determine alternate suite to be used, and/or request volumes from SES-STOR. • Request Refresh Media and application JCL library from TSG-Software Delivery. • Refresh JCL library delivered is named SYS2.INSTLIB.&SYSNAME.ZS14M?.PYYMM (example: SYS2.INSTLIB.WCRS.ZS14M3.P0404). Slide 47