ACSPAC Operating Systems Standards Overview

1. ACSPAC Operating Systems Standards 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 used in the corporate deployment of mainframe operating systems by ACS. • The material presented during this overview is used to aid in enlightenment of ACS Systems Mainframe Engineers to the standards used in a standard ACSPAC system layout. Slide 2

3. Systems Standards Overview • Standard Symbolic set for Model 3 or Model 9 z/OS ACSPAC • Standard Volume Layout and System Data Set Placement • ACSPAC Standard System Executable Libraries • ACSPAC Standard Environmental Data Sets • Standard System Concatenation of Library Parameters • Standardized TSO/ISPF Environment Rules Slide 3

4. Standard Symbolic set for Model 9 z/OS ACSPAC • The Model 9 ACSPAC is shipped using the following Symbolic member as IEASYMxx, where xx is the &SYSCLONE value. In this example, the &SYSCLONE value is TS. • Dynamic Substitution is used in the symbolic lines to parse the volume names, removing furture need to alter this member when switching alternate suites. • Assumptions; • Characters 1 and 4 are used as the &SYSCLONE value Slide 4

5. Standard Symbolic set for Model 3 ACSPAC z/OS • The Model 3 ACSPAC is shipped using the following Symbolic member as IEASYMxx, where xx is the &SYSCLONE value. In this example, the &SYSCLONE value is TS. • Dynamic Substitution is used in the symbolic lines to parse the volume names, removing furture need to alter this member when switching alternate suites. • Assumptions; • Characters 1 and 4 are used as the &SYSCLONE value Slide 5

6. Standard Volume Layout and System Data Set Placement • Shown at left is the typical deployment of a model 9 z/OS ACSPAC operating system model • Local System Executable libraries are housed on the residence volume to allow flexibility when working with alternate suites of volumes • The catalog volume is used to house a number of critical data stores. The system master catalog being most notable. A number of other critical datasets are placed here to prevent regression in future upgrade cycles. • The recommended Page and system Spool volumes and data sets are also illustrated • The ACSPAC system Volume (xxSY01) is used to house a number of z/OS environmental data sets, and is also used for local executables that are either not on the z/OS ACSPAC, or are older versions of software needed by the client. • A number of these volumes are replaced with each upgrade or revision cycle. These volumes are; • xxRS?1 • xxDL?1 • XXOM?1 (Model 3 ACSPAC only) Slide 6

7. ACSPAC Standard System Executable Libraries • SYS2.LPALIB.&SYSNAME - This library is used to house the modules that are customer specific LPA modules. This library precedes SYS1.LPALIB in the system concatenation. All modules here will be represented by user modification via SMP/E in the system user modification library. • SYS2.LPALIB - This library is used to house the modules that are ACS Specific LPA modules. This library precedes SYS1.LPALIB in the system concatenation. All modules here will be represented by user modification via SMP/E in the system user modification library. • SYS2.LINKLIB.&SYSNAME - This library is used to house the modules that are customer specific link list modules. This library precedes SYS1.LINKLIB in the system concatenation. All modules here will be represented by user modification via SMP/E in the system user modification library • SYS2.LINKLIB - This library is used to house the modules that are customer specific link list modules. This library precedes SYS1.LINKLIB in the system concatenation. All modules here will be represented by user modification via SMP/E in the system user modification library. Slide 7

8. ACSPAC Standard Environmental Data Sets • SYS2.PROCLIB.&SYSNAME - This library is used to house the System, or Vendor JCL procedures that are LPAR specific. This library precedes SYS1.PROCLIB in the system concatenation • SYS2.PROCLIB - This library is used to house the started task procedures that are generic to ACS systems. This library precedes SYS1.PROCLIB in the system concatenation • SYS2.TSO.PROCLIB.&SYSNAME - This library is used to house the system/Vendor JCL procedures that are LPAR specific. This library precedes SYS1.PROCLIB in the system concatenation • SYS2.PARMLIB - This library is used to house the JES2 parameters that are LPAR/MAS specific. All Parameter members here will be represented by user modification via SMP/E in the system user modification library • SYS2.PARMLIB.&SYSNAME - This library is used to house the SDSF parameters that are LPAR specific. SDSF Parameters will be represented by user modification via SMP/E in the system user modification library • SYS2.CLIST This library is used for application and program product TSO command list scripts (CLIST). Any product invocation CLIST, or locally written CLIST should be placed in this library. It is at the top of the SYSPROC concatenation at logon allocation time. It has an alias of SYS2.TSG.CLIST for release compatibility. Slide 8

9. ACSPAC Standard Environmental Data Sets (continued) • SYS2.REXX This library is used for application and program product REXX scripts. Any product invocation REXX, or locally written REXX should be placed in this library. It is at the top of the SYSEXEC concatenation at logon allocation time. • SYS2.PANELS This library is used for application and program product ISPF Panels. Any product invocation PANEL, or locally written PANEL should be placed in this library. It is at the top of the ISPPLIB concatenation at logon allocation time. • SYS2.MESSAGES - This library is used for application and program product ISPF messages. Any product invocation message member, or locally written message member should be placed in this library. It is at the top of the ISPMLIB concatenation at logon allocation time. • SYS2.SKELETON - This library is used for application and program product ISPF skeletons. Any product invocation skeleton member, or locally written skeleton member should be placed in this library. It is at the top of the ISPSLIB concatenation at logon allocation time. • SYS2.TABLES - This library is used for ACS specific, or program product ISPF tables. Any product table, or ACS generic(one fits all) table members should be placed in this library. It is at the top of the ISPTLIB concatenation at logon allocation time. • SYS2.TABLES.&SYSNAME - This library is used for system specific ISPF tabless. Any system specific, or locally written table member should be placed in this library. It is at the top of the ISPTLIB concatenation at logon allocation time. Slide 9

10. Standard System Concatenation of Libraries • Required LPA Library Concatenation Order There is a fixed requirement for the order of data sets specified in the LPA List parameter member in SYS1.PARMLIB(LPALSTxx). This order is: • ·         SYS2.LPALIB.&SYSNAME (or SYSACS.LPALIB.&SYSNAME) • ·         SYS2.LPALIB (Or SYSACS.LPALIB) • ·         SYS2(SYSACS).ACF2, or TSS LPA libraries • ·         SYS1.LPALIB • ·         Other ISV/LPAR LPA libraries • Required Link List Library Concatenation Order There is a fixed requirement for the order of data sets specified in the Link List parameters in the PROGxx member in SYS1.PARMLIB. This order is: • ·         SYS2.LINKLIB.&SYSNAME (or SYSACS.LINKLIB.&SYSNAME) • ·         SYS2.LINKLIB (or SYSACS.LINKLIB) • ·         SYS2(SYSACS).ACF2, or TSS LINKLIST libraries • ·         SYS1.LINKLIB • ·         Other ISV/LPAR LINKLIST libraries The override of SYS1.LPALIB, and SYS1.LINKLIB is accomplished via the SYSLIB statements in the PROGxx member in SYS1.PARMLIB. Slide 10

11. Standard System Concatenation of Libraries(continued) • Required Master Scheduler JCL Library Concatenation Order There is a fixed requirement for the order of data sets specified in the master scheduler JCL member in SYS1.PARMLIB(MSTJCLxx). This order is: • ·         SYS2.PROCLIB.&SYSNAME (or SYSACS.PROCLIB.&SYSNAME) • ·         SYS2.PROCLIB or (SYSACS.PROCLIB) • ·         SYS1.PROCLIB • Required JES2 Procedure Library Concatenation Order There is a fixed requirement for the order of data sets specified in the PROC00 DD statement in the JES2 procedure; • ·         SYS2.PROCLIB.&SYSNAME (or SYSACS.PROCLIB.&SYSNAME) • ·         SYS2.PROCLIB or (SYSACS.PROCLIB) • ·         SYS1.PROCLIB Slide 11

12. Standardized TSO/ISPF Environment Rules The TSO Logon procedure under the ACS systems model has several requirements; • No ISV product or customer specific DD statements may be coded in the Logon Procedure JCL Product/Service invocations for ISV products, and customer scripts must use dynamic allocations. Current TSO Logon JCL procedures that contain DD statements should be converted to utilize a dynamic allocation method for the data sets needed for the application, and remove the DD JCL statements from the TSO Logon Procedure. • Product Invocation CLIST/REXX executables should be located in the libraries SYS2.CLIST or SYS2.REXX Dynamic allocation CLIST/REXX executables should utilize the following services; LIBDEF (ISPF) For JCL DD statements: ISPPLIB, ISPMLIB, ISPSLIB, and ISPTLIB ALTLIB (TSO) For JCL DD statements: SYSPROC, and SYSEXEC STEPLIB (TSO) For STEPLIB JCL DD Statements Allocation of ISPF table DD statements for the DD name ISPTABL should be done in the invocation CLIST/REXX script. Any other DD statements that are required by the product or dialog will also need to be allocated and de-allocated by the invocation CLIST/REXX script. Slide 12