Problem:

How to use a fileshare server for the CICS VSAM files in ES

Resolution:

Enterprise Server shouldn't be setup to use fileshare globally but instead the CICS FCT entries need to be modifed (using the "Fileshare Server" box) so that they will use the fileshare server for those files. Any FCT entries that don't have the "Fileshare Server" entry set to a fileshare server will continue to use the local file system.

The utility "caspcupg" can be used to 'bulk update' specific groups to have the relevant FCT entry. This is done with the "/f" parameter as shown in the following example (with sample output):

caspcupg  /rEZA /dp=C:\\REGIONS /f(LOCALGRP,fsserver1)

where:

/r{region-name}                           = TX region name

/dp={resource-definition-path}    = Resource Definition Path

/f(group,fs-server-id)                   =  Set FCT FSID in group

CASRB0020I Upgrading file C:\\REGIONS\\dfhdrdat

CASRB0071I Processing FCT entries in group LOCALGRP, bulk update of Fileshare server (FSSERVER1)

CASRB0055I Upgraded FCT  group LOCALGRP entry EZACONF

CASRB0070I Modified FCT entry EZACONF in group LOCALGRP, FS Server ID was "<blank>" now "FSSERVER1"

CASRB0025I Upgrade log file: C:\\REGIONS\\rdoupgrd.log

CASRB0056I Processing completed with return-code=0000

If it is necessary to update any read-only FCT entries (i.e. in read-only groups), the group must be initially copied into a new goup where they can be updated. This new group can then be used in the Startup List in place of the original read-only group.

The MSS -> CICS -> "File Path" entry (CICS VSAM file path) will be used for the location of the CICS files whether they are on the local machine or on the remote fileshare server machine. These paths must exist on both machines for fileshare and non-fileshare file accesses to work. The VSAM CICS File Path can be a relative path (no leading 'slash') or an absolute path (with a leading 'slash). If a relative path is used it will be relative to the Fileshare/ES root path (which by default will be the directory in which Fileshare/ES was started). Note that it doesn't matter whether a forward slash (/) or a backward slash (\\) is used - it will be translated correctly for the relevant OS (e.g. if the fileshare server is on unix and the ES is running on a Windows machine)

NOTES 1. The CICS VSAM file path must NOT contain the $$fsserver redirect.