Maintaining File Manager Service Provider

If service is applied, some maintenance steps are necessary.

Before you begin

If service is applied to the FMNZCEE member of the SFMNSAM1 data set, some maintenance steps are necessary.

Note: If the service provider is not already installed into the z/OS Connect environment, then maintenance is not applicable, and the installation steps should be followed instead.

The maintenance procedure is conducted in the UNIX® System Services environment and has the following environmental prerequisites:

The shell environment must have a z/OS® Connect EE-compatible version of Java™ available on the environment PATH variable. You can check the PATH variable by using the UNIX® System Services echo $PATH command.
The z/OS® Connect installation directory <ZCON_INST_DIR>/v3r0/wlp/bin must be in the PATH environment variable.

About this task

The File Manager Service Provider for z/OS® Connect feature is shipped as a binary archive in the SFMNSAM1 data set as member FMNZCEE. The archive contains the following files:

com.hcl.zosconnect.fm.provider.feature_n.n.n.n.esa	Feature archive
fmService.sar	File Manager Base component service archive
fmIMSService.sar	IMS™ service archive
fmDB2Service.sar	Db2® service archive
filemanager.properties	Properties file
com.hcl.zosconnect.buildtoolkit.filemanager.jar	Build Toolkit plug-in

The following procedure includes stopping and restarting the z/OS® Connect WLP server. In high-availability environments this may be undesirable. For alternative procedures refer to the following topics:

Procedure

Extract the File Manager Service Provider for z/OS® Connect archive from the SFMNSAM1 data set using the UNIX System Services pax command.
```
pax -rf "//'<hlq>.SFMNSAM1(FMNZCEE)'"
```
This command extracts the FMNZCEE archive into the current working directory.
Copy the service archive files to the z/OS® Connect service directory.
For example:
```
cp fm*.sar
   /var/zosconnect/servers/<yourWLPServer>/resources/zosconnect/services
```
Ensure that the service archive files are readable by the z/OS® Connect WLP started task user.
(Optional) If you use the zconbt command to create SAR files, copy the File Manager Build Toolkit plug-in to the Build Toolkit /plugins directory.
For example:
```
cp com.hcl.zosconnect.buildtoolkit.filemanager.jar /var/zconbtv3/plugins
```
Check APAR HOLDDATA before continuing to the next step in case there are additional steps that need to occur at this point.
Stop the z/OS Connect WLP server.
Uninstall the current File Manager Service Provider using the installUtility command.
For example:
```
installUtility uninstall filemanager:fmProvider-2.0
```
Reinstall the File Manager Service Provider feature into z/OS Connect using the installUtility command.
For example:
```
installUtility install
com.hcl.zosconnect.fm.provider.feature_2.0.0.0.esa --to=filemanager
```
Note that the .esa filename may vary by version.
Restart the z/OS Connect WLP server.