Steps for customizing the cron, uucp, and mail utilities

The steps assume that you have used cron, uucp and mail and have not followed the recommended customization in z/OS Migration. These changes to the /var directories must be performed on every /var directory on every system image in the sysplex.

Requirements: Before beginning these tasks, you must meet the following requirements:

Have superuser authority, such as UID(0). If you have READ access to the BPX.SUPERUSER resource in the FACILITY class, you can execute setuid(0) or the su command to gain superuser authority. If you have permission to the corresponding UNIXPRIV class profile, you will have authority to use specific authorized services.
Log in to the shell environment through TSO, telnet, rlogin, or OpenSSH.

First step: If you have used cron, uucp, or mail and have not followed the recommended customization in z/OS Migration you must move the contents of the /usr/spool directory to the /var directory and create a symbolic link. Ensure that no file systems are mounted on the /usr/spool directory or on any mount point under this directory. If there are any, they must be unmounted.

Create a directory called /var/spool. Issue:
```
mkdir /var/spool
```
Optional. Because spool directories tend to be used heavily, it is good practice to create a new file system and mount it on /var/spool.
Change the permission setting of the /var/spool directory to 755. Issue:
```
chmod 755 /var/spool
```
Change the current working directory to /usr/spool. Issue:
```
cd /usr/spool
```
Copy the contents of the /usr/spool directory into /var/spool. Issue:
```
pax -rw -pe ./ /var/spool
```
You can choose to move the contents to a directory other than /var/spool (for example: /etc/spool). If you do, you will have to create another symbolic link later.
Repeat steps 1-5 for every system image in your sysplex.
Check that the copy was successful. If the copy was successful, then remove the /usr/spool directory. Issue:
```
rm -fr /usr/spool    
```
Create a symbolic link for /usr/spool that points to /var/spool. Issue:
```
ln -s ../var/spool /usr/spool
```

When you are done, you have moved the contents of the /usr/spool directory to the /var/spool directory and created a symbolic link for /usr/spool that points to /var/spool.

If you moved the contents of the /usr/spool directory to a directory other than /var/spool (for example: /etc/spool), you will have to create another symbolic link from /var/spool that points to /etc/spool. Use these steps:

Change the current working directory to the /var directory. Issue:
```
cd /var
```
Remove the /var/spool directory after making sure that it is empty. If it is not empty, then move the items from this directory into /etc/spool. Issue:
```
rmdir /var/spool
```
Create a symbolic link for /var/spool that points to /etc/spool. Issue:
```
ln  -s  ../etc/spool   /var/spool
```

Second step: If you have used cron, uucp, or mail and have not followed the recommended customization in z/OS Migration, you must move the contents of the /usr/lib/cron directory to the /var directory and create a symbolic link. Ensure that no file systems are mounted on the /usr/lib/cron directory or on any mount point under this directory. If there are any, they must be unmounted.

Create a directory called /var/cron. Issue:
```
mkdir /var/cron
```
Change its permission setting to 755. Issue:
```
chmod 755 /var/cron
```
Change the current working directory to /usr/lib/cron. Issue:
```
cd /usr/lib/cron
```
Copy the contents of the /usr/lib/cron directory into/var/cron. Issue:
```
pax -rw -pe ./ /var/cron
```
You can choose to move the contents to a directory other than /var/cron (for example: /etc/cron). If you do, you will have to create another symbolic link later.
Repeat steps 1-4 for every system image in your sysplex.
After you are sure that the copy was successful, you can remove the /usr/lib/cron directory. Issue:
```
rm -fr /usr/lib/cron 
```
Create a symbolic link for /usr/lib/cron that points to /var/cron. Issue:
```
ln -s ../../var/cron /usr/lib/cron
```

When you are done, you have moved the contents of the /usr/lib/cron directory to the /var/cron directory and created a symbolic link for /usr/lib/cron that points to /var/cron.

If you chose to move the contents of the /usr/lib/cron directory to a directory other than /var/cron (for example: /etc/cron), you will need to create an additional symbolic link from /var/cron to /etc/cron. Use these steps:

Change the current working directory to the /var directory. Issue:
```
cd /var
```
Remove the /var/cron directory after making sure that it is empty. If it is not empty, then move the items from this directory into /etc/cron. Issue:
```
rmdir /var/cron
```
Create a symbolic link for /var/cron that points to /etc/cron. Issue:
```
ln  -s  ../etc/cron   /var/cron
```

Third step: If you have used cron, uucp, or mail and have not followed the recommended customization in z/OS Migration, you must move the uucp files and create a symbolic link.

Create a directory called /var/uucp. Issue:
```
mkdir /var/uucp
```
Change its permission setting to 774. Issue:
```
chmod 774 /var/uucp
```
Change the current working directory to /usr/lib/uucp. Issue:
```
cd /usr/lib/uucp
```
Issue ls -al to see if the following files are in /usr/lib/uucp.
```
Systems
Devices
Dialers
Dialcodes
Permissions
config
```
If none of these files show up in the directory listing, then you are done.
If any of the files listed in Step 4 exist, copy them to the /var/uucp directory by using the cp command. For example, if all the files exist, then you must copy them to the /var directory. Issue:
```
cp -p Systems /var/uucp/Systems
cp -p Devices /var/uucp/Devices
cp -p Dialers /var/uucp/Dialers
cp -p Dialcodes /var/uucp/Dialcodes
cp -p Permissions /var/uucp/Permissions
cp -p config /var/uucp/config
```
You can choose to move the contents to a directory other than /var/uucp (for example: /etc/uucp). If you do, you will have to create an additional symbolic link later.
Repeat Steps 1-5 for every system image in the sysplex.
After you are sure that the files were copied successfully, you can remove them from the /usr/lib/uucp directory. Issue:
```
rm Systems
rm Devices
rm Dialers
rm Dialcodes
rm Permissions
rm config
```

Create symbolic links for these files from /usr/lib/uucp to /var/uucp. Issue

ln -s ../../../var/uucp/Systems Systems
ln -s ../../../var/uucp/Devices Devices
ln -s ../../../var/uucp/Dialers Dialers
ln -s ../../../var/uucp/Dialcodes Dialcodes
ln -s ../../../var/uucp/Permissions Permissions
ln -s ../../../var/uucp/config config

If you chose to copy the files from the /usr/lib/uucp directory to a directory other than /var/uucp (for example: /etc/uucp), you must create additional symbolic links from /var/uucp to this directory. You can use these commands to perform these actions:

Change the current working directory to the /var directory. Issue:
```
cd /var
```

If the following files exist, copy them to /etc/uucp. Issue:

cp -p Systems /etc/uucp/Systems
cp -p Devices /etc/uucp/Devices
cp -p Dialers /etc/uucp/Dialers
cp -p Dialcodes /etc/uucp/Dialcodes
cp -p Permissions /etc/uucp/Permissions
cp -p config /etc/uucp/config

Remove the following /var/uucp files, if they exist. Issue:

rm Systems
rm Devices
rm Dialers
rm Dialcodes
rm Permissions
rm config

Create symbolic links for these files from /var/uucp to /etc/uucp. Issue:

ln -s ../../etc/uucp/Systems Systems
ln -s ../../etc/uucp/Devices Devices
ln -s ../../etc/uucp/Dialers Dialers
ln -s ../../etc/uucp/Dialcodes Dialcodes
ln -s ../../etc/uucp/Permissions Permissions
ln -s ../../etc/uucp/config config

Fourth step: If you have used cron, mail, or uucp and have not followed the recommended customization in z/OS Migration, you must move the contents of the /usr/mail directory to the /var directory and create a symbolic link. Ensure that no file systems are mounted on the /usr/mail directory or on any mount point under this directory. If there are any, they must be unmounted.

Before you begin: You need to login to the shell environment through TSO, telnet, rlogin, or OpenSSH.

Perform the following steps to customize the mail utility.

Create a directory called /var/mail.
```
mkdir /var/mail
```
Change its permission setting to 775.
```
chmod 775 /var/mail
```
Change the current working directory to /usr/mail.
```
cd /usr/mail
```
Copy the contents of the /usr/mail directory into /var/mail. Issue:
```
pax -rw -pe ./ /var/mail  
```
You can choose to move the contents to a directory other than /var/mail (for example: /etc/mail). If you do, you will have to create an additional symbolic link later.
Repeat steps 1-4 for every system image in your sysplex.
After you are sure that the copy was successful, you can remove the /usr/mail directory:
```
rm -fr /usr/mail
```
Create a symbolic link for /usr/mail that points to /var/mail. Issue:
```
ln -s ../var/mail /usr/mail
```

When you are done, you have customized the mail utility. If you unmounted any file systems that were mounted on or below /usr/mail, you can mount them now using the same mount point as before. That directory must contain the contents of /usr/mail.

If you chose to move the contents of the /usr/mail directory to a directory other than /var/mail (for example: /etc/mail), you will need to create an additional symbolic link from /var/mail to this directory using these instructions:

Change the current working directory to the /var directory. Issue:
```
cd /var
```
Remove the /var/mail directory after making sure that it is empty. If it is not empty, then move the items from this directory into /etc/mail.
```
rmdir /var/mail
```
Create a symbolic link for /var/mail that points to /etc/mail. Issue:
```
ln -s ../etc/mail  /var/mail
```