1 / 12

ACSPAC Systems Overview

ACSPAC Systems Overview. For Z/os Operating Systems. SES-PBCT Team – Winter, 2007 – Release 2.0. Slide 1. 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.

marialee
Download Presentation

ACSPAC Systems 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 Systems Overview For Z/os Operating Systems SES-PBCT Team – Winter, 2007 – Release 2.0 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. • Overview Outline • ACSPAC z/OS Systems Deployment Guide • System model overview • z/OS 1.4 • ACSPAC Model 9 deployment • ACSPAC Model 3 deployment • z/OS 1.7 • ACSPAC Model 9 deployment • ACSPAC Model 3 deployment • Deployment Option Overview • Upgrade Considerations for existing ACSPAC deployments Slide 2

  3. ACS z/OS Deployment Overview Separate guides exist for z/OS 1.4 and z/OS 1.7 • Standards of Delivered Model • Naming Standards • System Overrides • Requirements for data sets/libraries and concatenations • The z/OS Distribution Package - ACSPAC • Delivered Symbolic Symbols • z/OS 3390 Model 9 Distribution Package Overview • z/OS 3390 Model 3 Distribution Package Overview • Coexistence with previous ACSPAC deployments • Operating System Upgrade Procedures • Assessment of the target environment • Upgrade Preparation Checklist • Installation procedures for Model 9 deployment • Installation procedures for Model 3 deployment • Processing an IVP using ACSIVP • The ACSIVP processor is shipped and tailored during the installation process. It includes a standardized IVP that can be executed to ensure the installation is complete. • System Maintenance and Refresh Procedures • Appendixes • ACSPAC z/OS Systems Deployment Guide Slide 3

  4. System model overview for z/OS • ACSPAC 3390 Model 9 z/OS deployment • Two 3390 Model 9 volumes; • System residence Volume • System Distribution Volume • Two 3390 Model 3 volumes; • SMP/E Environment Volume • z/OS Environmental Volume • z/OS 1.7 Only • z/OS 1.7 OMVS Volume • Optional • z/OS Master catalog volume – This volume is to be used when isolation from 2.10 is required, or a first time installation of the ACS model for a client. Slide 4

  5. ACS z/OS Deployment Overview • ACSPAC 3390 Model 3 z/OS deployment • Seven 3390 Model 3 volumes; • 3 System residence Volumes • 1 OMVS/USS HFS Volume • 3 System Distribution Volumes • Two 3390 Model 3 volumes; • SMP/E Environment Volume • z/OS Environmental Volume • One 3390 Model 3 Volume • z/OS Master catalog volume – This volume is to be used when isolation from 2.10 is required, or a first time installation of the ACS model for a client. Slide 5

  6. ACS z/OS Deployment Overview • Deployment Option Overview – Standalone System • Minimum Requirements • 3390 Model 3 ACSPAC z/OS DASD Requirements • z/OS 1.4 • 2 3390 Mod 3 Residence Volumes (??RSA1/??RSA2) • 1 3390 Mod 3 OMVS/USS Volume (??OMA1) • 3 3390 Mod 3 Distribution Volumes (??DLA1,??DLA2,??DLA3) • 1 3390 Mod 3 SMP/E Volume (??PE01) • z/OS 1.7 • 3 3390 Mod 3 Residence Volumes (??RSA1/??RSA2/??RSA3) • 1 3390 Mod 3 OMVS/USS Volume (??OMA1) • 3 3390 Mod 3 Distribution Volumes (??DLA1,??DLA2,??DLA3) • 1 3390 Mod 3 Catalog Volume (??CT01) • 1 3390 Mod 3 ACS System Volume (??SY01) • 3390 Model 9 ACSPAC z/OS DASD Requirements • z/OS 1.4 • 1 3390 Mod 9 Residence Volume (??RSA1) • 1 3390 Mod 9 Distribution Volume (??DLA1) • z/OS 1.7 • 1 3390 Mod 9 Residence Volume (??RSA1) • 1 3390 Mod 9 Distribution Volume (??DLA1) • 1 3390 Mod 3 OMVS/USS Volume (??OMA1) • 1 3390 Mod 3 SMP/E Volume (??PE01) • 1 3390 Mod 3 Catalog Volume (??CT01) • 1 3390 Mod 3 ACS System Volume (??SY01) • SNA VTAM Procedure for the target LPAR • Name of VTAMLIB data set that must be authorized • Location of VTAM or NET JCL procedure • Security Interface • Site Specific – RACF/ACF2/TSS • Starter System RACF DB – Need working TSO ID on the Dallas system DCUF to utilize • Primary Restore Processing • Primary Customization Process • Pre-IPL Process for Standalone Copy Note: This system model must be installed according to the procedures outlined in the ACS z/OS Systems Deployment guide for the Standalone System Restore. Deviation from published procedures may result in failure of the system installation process. Slide 8

  7. ACS z/OS Deployment Overview Primary Restore Process Physical restore of residence Volume Physical restore of OMVS volume (if req) Physical restore of distribution volume Creation of Master/user cat/Aliases Logical restores for SMP/E and SYS volumes • Deployment Option Overview Primary Customization Process Allocate Environmental data sets Update/merge of Master catalog Logical restore of catalog volume data sets Creation of starter IPL parameters Creation of starter JES2 parameters/Spool/Checkpoint ACSIVP member Priming Slide 9

  8. ACS z/OS Deployment Overview • Upgrade Considerations for ACSPAC OS390 2.10-z/OS • System Residence Volume Differences • OS390 2.10 has two residence volumes (XXRSA1 and XXRSA2 – depending on suite) • Z/OS 3390 Model 3 utilizes two residence volumes (XXRSA1 and XXRSA2 – depending on suite) • Z/OS 3390 Model 9 utilizes only one 3390 Model 9 DASD unit, named XXRSA1 or XXRSB1 • System Distribution Volume Differences • OS390 2.10 has two residence volumes (XXDLA1 and XXDLA2 – depending on suite) • Z/OS 3390 Model 3 utilizes three distribution volumes (XXDLA1/2/3 – depending on suite) • Z/OS 3390 Model 3 utilizes only one 3390 Model 9 DASD unit for it’s Distribution Volume (XXDLA1) • OMVS HFS Data Volume • OS390 2.10 has one volume (XXOMA1 or XXOMB1 – depending on suite) • Z/OS 3390 Model 3 has one volume (XXOMA1 or XXOMB1 – depending on suite) • Z/OS 3390 Model 9 ships with the HFS data sets contained on the residence volume • ACS Systems Volume • OS390 2.10 provided only CPAC data sets on the XXSY01 volume • Z/OS 1.4 provides CPAC and all z/OS subsystem environmental configuration data sets • VSAM configuration data sets for z/OS subsystem operations • NON-VSAM configuration data sets for z/OS subsystem operations • ACSIVP Processor Installed and customized on xxSY01 volume • ACSBUILD processor Installed and customized on xxSYS01 volume Slide 10

  9. ACS z/OS 1.4 Deployment Overview • Upgrade Considerations for ACSPAC OS390 2.10 target systems • Master Catalog Concerns • The ACSPAC for z/OS 1.4 ships with a new Master catalog. It is named SYS1.MCAT.????, were ???? is the system name. This will conflict with system that already utilize this name. If you elect to use the same master catalog, you will need to adjust some of the installation jobs before beginning the process. These installation jobs affect the symbolic definitions and their references. These changes must be made regardless of which DASD model of z/OS 1.4 that you deploy. • Z/OS 1.4 3390 Model 9 coexistence with ACSPAC 2.10 OS390 Master Catalog • Use Installation job CA00042A instead of CA000400, and make the following edits; Change &Z3RS1 to &SYSR1 Change &Z3RS2 to &SYSR2 Change &Z3DL1 to &SYSD1 Change &Z3DL2 to &SYSD2 Change &Z3DL3 to &SYSD3 Change &Z3OMV to &SYSO1 • Use IEASYMM3 instead of IEASYMM9 in SYS1.PARMLIB on ??CT01 volume Add OS/390 2.10 symbols as needed Change &ZSRS1 to &SYSR1 Change &ZSRS2 to &SYSR2 (Value of &SYSR1) Change &ZSCAT to &SYSC1 (Value of ??CT01 where ?? = &SYSCLONE) Change &Z3CAT to &SYSC1 (Value of ??CT01 where ?? = &SYSCLONE) Change &Z3DL1 to &SYSD1 (Value of ??DLA1 where ??=&SYSCLONE) Change &Z3DL2 to &SYSD2 (Value of ??DLA1 where ??=&SYSCLONE) Change &Z3DL3 to &SYSD3 (Value of ??DLA1 where ??=&SYSCLONE) Change &Z3OMVto &SYSO1 (Value of &SYSR1) Slide 11

  10. ACS z/OS 1.4 Deployment Overview • Upgrade Considerations for ACSPAC OS390 2.10 target systems • Z/OS 1.4 3390 Model 3 coexistence with ACSPAC 2.10 OS390 Master Catalog • Use Installation job CA000400, and make the following edits; Change &Z3RS1 to &SYSR1 Change &Z3RS2 to &SYSR2 Change &Z3DL1 to &SYSD1 Change &Z3DL2 to &SYSD2 Change &Z3DL3 to &SYSD3 Change &Z3OMV to &SYSO1 • Use IEASYMM3 instead of IEASYMM9 in SYS1.PARMLIB on ??CT01 volume Add OS/390 2.10 symbols as needed Change &ZSRS1 to &SYSR1 Change &ZSRS2 to &SYSR2 (Value of &SYSR1) Change &ZSCAT to &SYSC1 (Value of ??CT01 where ?? = &SYSCLONE) Change &Z3CAT to &SYSC1 (Value of ??CT01 where ?? = &SYSCLONE) Change &Z3DL1 to &SYSD1 (Value of ??DLA1 where ??=&SYSCLONE) Change &Z3DL2 to &SYSD2 (Value of ??DLA1 where ??=&SYSCLONE) Change &Z3DL3 to &SYSD3 (Value of ??DLA1 where ??=&SYSCLONE) Change &Z3OMVto &SYSO1 (Value of &SYSR1) Slide 12

  11. ACS z/OS 1.4 Deployment Overview • Upgrade Considerations for ACSPAC OS390 2.10 target systems • Environmental Installation Jobs Use these considerations if you are reusing the master catalog volume, System Volume, and Master/User catalogs from the ACSPAC OS/390 2.10 Model • Primary Customization Job Considerations • CA000100/150 Unneeded Initializes and Un-indexes catalog Volume • CA000300 Unneeded Defines Master/user catalogs and defines aliases • CA000400/42A See previous Consideration on catalog co-existence • CA001000 Unneeded IF SYS1.BROADCAST already exists • CA001200 Unneeded IF SYS1.DAE already exists • CA001400 Unneeded IF SYS1.DUMP?? already exists • CA001600 Unneeded IF SYS1.ISF.HASPINDX.&SYSNAME already exists • CA002000 Unneeded IF SYS1.ENURMF already exists • CA002200 Unneeded IF SYS1.LOGREC&SYSNAME already exists • CA002400 Unneeded IF SYS1.MAN?.&SYSNAME already exists • CA002600/2601 Unneeded IF SYS1.UADS already exists, and converted • CA002800 Review IF SYS2.* data sets pre-exist, need refreshment • CA003200 Unneeded IF SYS1.DFSMS.ACDS/COMDS already exists • CA003800 Unneeded IF PAGE data sets already present • CA004300 Unneeded Build JES2 Spool/Check point and Parameters • CA004500 Unneeded Build SYS1.PARMLIB &SYSNAME IPL path Slide 13

  12. ACS z/OS 1.4 Deployment Overview • Upgrade Considerations for ACSPAC OS390 2.10 target systems • RACF data bases require new additions and template updates • JES2 initialization parameter APPLYCOPY has been deprecated in z/OS. It was introduced on OS/390 2.10 in the CKPTDEF and DEBUG parameter statements, and removed in z/OS. • Application of user modifications as published in the “ACS Systems Deployment Guide” required only FMIDSET and applicable RMID changes to re-apply. Slide 14

More Related