z/OS

This section describes requirements for the System z servers running z/OS.

Hardware Requirements

Any mainframe system that supports the minimum software requirements listed in the Software Requirements section can be used. Data Manager requires the following amount of disk space:

183 MB disk space available for product installation
3 MB of disk space per analyzed archive (50 fields)

Software Requirements

The following software is supported for z/OS:

MVS, OS/390 2.5 or later, or z/OS 1.1 or later
Language Environment 6.1 or later
IBM DB2 (z/OS version, or OS/390 version 8 or later)

DB2 Database Requirements

Data Manager for z/OS uses a DB2 database that contains about 150 tables and views. The database must be at least DB2 V7R1 with proper DDF configuration.

The tablespace definition for one table and the DDL statements used to create the database and are shown below.

CREATE TABLESPACE      ANURDCLA                                   
       IN              &URDBASE                                   
       USING STOGROUP  &URSGROUP                                  
       PRIQTY              $PQTY                                      
       SECQTY              $SQTY                                      
       FREEPAGE         $FPAGE                                     
       PCTFREE            $PFREE                                     
       BUFFERPOOL    &URBPTS                                    
       SEGSIZE 64                                                 
       COMPRESS         $COMPRESS;                                 
CREATE TABLE  &UROWNER..ANURDCLA                                  
(MCRECID                SMALLINT             NOT NULL WITH DEFAULT,
 FILRECID                  INTEGER               NOT NULL WITH DEFAULT,
 FLDRECID                 INTEGER              NOT NULL WITH DEFAULT,
 CLATYPE                  SMALLINT            NOT NULL WITH DEFAULT,
 PRG                            SMALLINT            NOT NULL WITH DEFAULT,
 CDRULECLA            INTEGER               NOT NULL WITH DEFAULT,
 CONFID                     INTEGER               NOT NULL WITH DEFAULT, 
 FLAGDEL                  CHAR      (001)      NOT NULL WITH DEFAULT, 
 BESTCLA                   CHAR      (001)      NOT NULL WITH DEFAULT) 
 IN  &URDBASE..ANURDCLA;

Data Set Requirements

Data Manager for z/OS uses 45 partitioned data sets (PDS) and 4 sequential data sets (SEQ). PDS and SEQ data sets are identified by the combination of a prefix and a suffix. However, the user can only choose the prefix.

The current prefixes are MFDATA.VxRx for the VR release library, MFDATA.VxRxPTF for the PTF library, and MFDATA.VxRxPER for the Personalized library. These prefixes can be modified. Suffixes (for example, BIND, CLIST, and DDL) cannot be modified.

Data Manager for z/OS uses the following 45 partitioned data sets:

MFDATA.V2R0.BIND        
MFDATA.V2R0.CBL         
MFDATA.V2R0.CLIST       
MFDATA.V2R0.COPY    
MFDATA.V2R0.DBRMLIB        
MFDATA.V2R0.DDL         
MFDATA.V2R0.DDLALTER
MFDATA.V2R0.FTOUTPUT    
MFDATA.V2R0.JCL         
MFDATA.V2R0.LOAD        
MFDATA.V2R0.OBJ         
MFDATA.V2R0.PACKAGE     
MFDATA.V2R0.PANEL       
MFDATA.V2R0.SKEL        
MFDATA.V2R0.SYSPUNCH
MFDATA.V2R0PTF.BIND        
MFDATA.V2R0PTF.CBL         
MFDATA.V2R0PTF.CLIST       
MFDATA.V2R0PTF.COPY    
MFDATA.V2R0PTF.DBRMLIB        
MFDATA.V2R0PTF.DDL         
MFDATA.V2R0PTF.DDLALTER
MFDATA.V2R0PTF.FTOUTPUT    
MFDATA.V2R0PTF.JCL         
MFDATA.V2R0PTF.LOAD        
MFDATA.V2R0PTF.OBJ         
MFDATA.V2R0PTF.PACKAGE     
MFDATA.V2R0PTF.PANEL       
MFDATA.V2R0PTF.SKEL        
MFDATA.V2R0PTF.SYSPUNCH
MFDATA.V2R0PER.BIND        
MFDATA.V2R0PER.CBL         
MFDATA.V2R0PER.CLIST       
MFDATA.V2R0PER.COPY    
MFDATA.V2R0PER.DBRMLIB        
MFDATA.V2R0PER.DDL         
MFDATA.V2R0PER.DDLALTER
MFDATA.V2R0PER.FTOUTPUT    
MFDATA.V2R0PER.JCL         
MFDATA.V2R0PER.LOAD        
MFDATA.V2R0PER.OBJ         
MFDATA.V2R0PER.PACKAGE     
MFDATA.V2R0PER.PANEL       
MFDATA.V2R0PER.SKEL        
MFDATA.V2R0PER.SYSPUNCH

Data Manager uses the following four sequential data sets:

MFDATA.V2R0.IMPSRC
MFDATA.KBPARAM
MFDATA.V2R0.ALLDDL
MFDATA.V2R0.ALLBNDPK

The installer can modify the names of the first and second qualifier of a data set (for example: MFDATA.V2R0, MFDATA.V2R0PTF, and MFDATA.V2R0PER) according to your requirements.

Note: The total space occupied by all data sets does not exceed 50 MB.

User Credential Requirements

Data Manager for z/OS users must be suitably configured both at the TSO and DB2 level. For a proper configuration, the following authorizations are required:

RACF authorizations (create, update, and delete) to the product PDS and sequential files (for example, JCL, CLIST, and SKEL).
Authorizations to the creation of the product DB2 database (storage group and database).
Authorizations to the creation of the DB2 tablespaces, views, and indexes.
Authorizations to the execution of package and plan binds.

Site-specific Requirements

Most activities in Data Manager for z/OS consist of batch jobs executed through JCLs, which are normally created by specific submission functions by updating predefined skeletons (parameters, environment, and database specifications).

Note: If necessary, you can create permanent copies of the updated JCLs and adjust them to your organizational requirements.

The following actions may be performed in order to customize the product to meet organizational standards:

Modify job names (function supported during product installation).
Customize the skeletons.
Start work with proprietary or third-party products for scheduling or controlling jobs.

Make adjustments as required to provide interfaces with scheduling products

CREATE STOGROUP &URSGROUP VOLUMES (xxxxxxxx) VCAT xxx;
CREATE DATABASE &URDBASE STOGROUP &URSGROUP;

Modify names such as the DB2 storage group group (STOGROUP), database, and owner (function supported during product installation)
Modify names of tablespaces, tables, views, and indexes (function not supported during product installation) Define ALIAS or SYNONYM
During the installation phase at your site, the installer will need to know your standards for:
- Jobs names, accounting, etc.
- Names of each DB2 subsystem, name of the DB2 load library, name and plan of DSNTIAD, name and plan of DSNTIAUL.
- Name of the volume on which to allocate your partitioned data sets.