Steps for creating a message catalog from the shipped catalog and preserving its timestamp

After using these steps you can then update the file with your local modifications and create a new FTP catalog with the preserved timestamp. Perform all of these steps from the z/OS® UNIX shell; the commands indicated are z/OS UNIX commands.

Before you begin

This example assumes that the FTP code and catalog are at the correct levels and that only local customization to the catalog is to be performed. Also, if you customize a catalog, IBM® Service personnel might require that you use the shipped level of the catalog to recreate and diagnose a reported problem.

Procedure

Perform the following steps to create a file from the shipped catalog and preserve its timestamp:

Copy the official z/OS UNIX catalog that is shipped with the release or service to a backup file.
```
cp  /usr/lpp/tcpip/lib/nls/msg/C/ftpdmsg.cat  /tmp/ftpdmsg.cat.backup
```
Using the dspcat command, convert a copy of the backup catalog that you just copied to a copy that you can edit. This is the file that you need to update to preserve the timestamp, and that you will update to support any local user message changes.
```
dspcat -t -g  /tmp/ftpdmsg.cat.backup  >/tmp/ftpdmsg.cat.copy
```
Change the first line in the catalog from a comment to a z/OS UNIX gencat command, which enables the timestamp to be imbedded in the catalog when it is rebuilt.
1. Edit the file to be updated.
```
oedit /tmp/ftpdmsg.cat.copy
```
2. Change the first line comment to add a gencat command to preserve the timestamp when the directory is built. The first line in the file will be similar to the following line:
```
The time stamp of catalog /tmp/ftpdmsg.cat.backup is: 2006 095 20:30 UTC 
```
  Replace the leading text on the line with the gencat subcommand $timestamp as follows:
```
$timestamp 2006 095 20:30 UTC
```
  If this step is omitted and the original line is left in the catalog, when an attempt is made to generate a catalog from this file, you will see a message similar to the following message:
```
FSUM5108 gencat: Invalid message number.
```
3. Save the file.
Update the catalog (/tmp/ftpdmsg.cat.copy) with any local modifications and save the file.
Build a new and customized catalog using the z/OS UNIX gencat command, and save a copy of the shipped level of the catalog.
```
gencat   /tmp/ftpdmsg.cat   /tmp/ftpdmsg.cat.copy
```
The correct response is:
```
FSUM5105 gencat: Message catalog generated normally.
```
Browse the new catalog and verify that the timestamp from step 3 matches what is in the file.
```
obrowse /tmp/ftpdmsg.cat
```
The first record contains the time stamp (yyyy ddd hh:mm UTC). For example:
```
…2006 095 20:30 UTC
```
Replace the official z/OS UNIX catalog that is shipped with the release with the updated catalog that you created in step 5.

Results

You know you are done when you test the catalogs to verify correct synchronization by performing the following actions:

Start the FTP server and inspect the syslog output (console if no syslog is running). Message EZYFS30W should not appear.
Using the FTP client, connect to the FTP server and inspect the SYSPRINT output. Message EZYFS31W should not appear.

For more information about the dspcat and gencat utilities, see z/OS UNIX System Services Command Reference.