Unified Install Process › Setting Up a File System for the Pax File › Allocate and Mount a File System

Allocate and Mount a File System

The following provides an overview of the allocating and mounting a file system process. The steps to perform this task are available following this overview.

You need a UNIX System Services (USS) directory and a file system with adequate space to perform the following tasks:

• Receive product pax files from http://ca.com/support.
• Perform utility functions to unpack the pax file into MVS data sets that you can use to complete the product installation.

We recommend that you allocate and mount a file system that is dedicated to Pax ESD. The amount of space that you need for the file system depends on the following variables:

• The size of the pax files that you intend to download.
• Whether you plan to keep the pax files after unpacking them. We do not recommend this practice.

We recommend that you use one directory for downloading and unpacking pax files. Reusing the same directory minimizes USS setup. You need to complete the USS setup only one time. You can reuse the same directory for subsequent downloads. Alternatively, you can create a directory for each pax download.

Important! Downloading pax files for the SMP/E installation as part of the Pax ESD process requires write authority to the UNIX System Services (USS) directories that are used for the Pax ESD process. In the file system that contains the Pax ESD directories, you also need free space approximately 3.5 times the pax file size to download the pax file and unpack its contents. For example, to download and unpack a 14 MB pax file, you need approximately 49 MB of free space in the file system hosting your Pax ESD directory.

You can use the zSeries File System (zFS) or hierarchical file system (HFS) for product downloads.

This procedure describes how to perform the following tasks:

• Allocate a zFS or an HFS.
• Create a mount point in an existing maintenance USS directory of your choice.
• Mount the file system on the newly created mount point.

  Note: You must have either SUPERUSER authority, or the required SAF profile setting to allow you to issue the USS mount command for the file system.

  Important! For new zFS, allocate and mount appropriate resource class FSACCESS authority must be granted to the LDAP4SRV (CA LDAP Server) and DSI4SRV (CA DSI Server for CIA Real-Time) started task which access the new zFS file.

• Optionally, permit write access to anyone in the same group as the person who created the directory.

  Important! USS commands are case-sensitive.

Follow these steps:

1. Allocate the file system by customizing one of the following samples to your site requirements.
   • On a zFS, use the following sample:

     //DEFINE   EXEC PGM=IDCAMS
     //SYSPRINT DD   SYSOUT=*
     //SYSUDUMP DD   SYSOUT=*
     //AMSDUMP  DD   SYSOUT=*
     //SYSIN    DD *
       DEFINE CLUSTER ( +
       NAME(your_zFS_data_set_name) +
       STORAGECLASS(class) +
       LINEAR +
       CYL(primary secondary) +
       SHAREOPTIONS(3,3) +
       )
     /*
     //FORMAT   EXEC PGM=IOEAGFMT,REGION=0M,
     // PARM=('-aggregate your_zFS_data_set_name -compat')
     //SYSPRINT DD   SYSOUT=*
     //SYSUDUMP DD   SYSOUT=*
     //STDOUT   DD   SYSOUT=*
     //STDERR   DD   SYSOUT=*
     //CEEDUMP  DD   SYSOUT=*
     //*
     

   • On an HFS, use the following sample:

     //ALCHFS EXEC PGM=IEFBR14 
     //CAPAX  DD   DSN=your_HFS_data_set_name,
     //            DISP=(NEW,CATLG,DELETE),UNIT=3390,
     //            DSNTYPE=HFS,SPACE=(CYL,(primary,secondary,1))
     

   The file system is allocated.

   Note: Ensure that the zFS or HFS data set name that you use conforms to your data set naming conventions for USS file systems. If the allocation of the file system data set fails, it is because of environmental settings not allowing for the allocation. On an HFS, try using the ISPF 3.2 Data Set Utility to allocate your HFS data set.

2. Create a mount point for the file system. This example shows how to create a /CA/CAPAX directory in an existing directory, /u/maint. From the TSO OMVS shell, enter the following commands:

   cd /u/maint/
   mkdir CA
   cd CA
   mkdir CAPAX
   

   Note: This document refers to this structure as yourUSSpaxdirectory.

   The mount point is created.

3. Mount the file system by customizing one of the following samples to your site requirements:
   • On a zFS, use the following sample:

     MOUNT FILESYSTEM('your_zFS_data_set_name')
           MOUNTPOINT('yourUSSpaxdirectory')
           TYPE(ZFS)  MODE(RDWR)
           PARM(AGGRGROW)
     

   • On an HFS, use the following sample:

     MOUNT FILESYSTEM('your_HFS_data_set_name') 
           MOUNTPOINT('yourUSSpaxdirectory') 
           TYPE(HFS)  MODE(RDWR)
     

   The file system is mounted.

4. (Optional) Set security permissions for the directory. You can use the chmod command to let other users access the Pax ESD directory and its files. For example, to allow write access to the Pax ESD directory for other users in your USS group, from the TSO OMVS shell, enter the following command:

   chmod -R 775 /yourUSSpaxdirectory/
   

   Write access is granted.

   Note: For more information about the chmod command, see the IBM z/OS UNIX System Services User Guide (SA22-7802).