Recently we migrated from CA File Master Plus for MVS and IMS from v9.1 to v10. Since v10 is a combined version of FMP MVS and IMS, we have populated common dataset for this version. We have already migrated to CA FMP v10 in all Test, and Production LPAR's. Now in user settings there's an DSN dataset which is still pointing to old dataset; @ FMP tool -> 0 Setup -> 3 Parm Files.

Earlier we had the following list of dataset:

DXX.CA.FMPIMS.DSNLIST

DXX.CA.FMPIMS.SELECT

DXX.CA.FMPIMS.LAYOUT

DXX.CA.FMPIMS.SEGXREF

DXX.CA.FMPIMS.IMSENV

Now we need to update it to:

DXX.CA.FMP.DSNLIST

DXX.CA.FMP.SELECT

DXX.CA.FMP.LAYOUT

DXX.CA.FMP.SEGXREF

DXX.CA.FMP.IMSENV

How can we change this, as most of the users have this setup? Is there any way to update it using any global option?

For the new users its correctly taking the new dataset, but for the users who already using File Master plus, even though they don't have any data in the dataset, its pointing to old dataset still.

Environment:

Upgrading File Master Plus for IMS

Answer:

Before answering your question, I'd like to comment on using one library for both FMP for MVS and FMP for IMS. The syntax for LAYOUT/CRL and selection criteria is different in these products. If a user would try to use selection criteria created under FMP for MVS in FMP for IMS (or vice versa), it wouldn't work. Same with a CRL. DSNLISTs are compatible between the 2 products. The SEGXREF and IMSENV data sets are used in FMP for IMS only.

Now the answer to your question: File Master keeps track of the names of the parameter files in an ISPF profile. This is saved in the ISPPROF PDS. The first time that a user executes File Master, we get default values from the clist and create the profile. If you want to change the name of a parameter file for all users, you'd have to update the ISPPROF for each user. To my knowledge, there is no easy way to do that.

The good news is that there is no need to update the data set names: data set aliases. I think that this procedure will work (showing the DSNLIST as an example): 1. rename DXX.CA.FMPIMS.DSNLIST to DXX.CA.FMPIMS.OLD.DSNLIST

2. define ALIAS DXX.CA.FMPIMS.DSNLIST and let it point to DXX.CA.FMP.DSNLIST ALIAS's are created with IDCAMS. Here's an example syntax: DEFINE ALIAS (NAME(DXX.CA.FMPIMS.DSNLIST) - RELATE(DXX.CA.FMP.DSNLIST)) - CATALOG(name.of.the.user.catalog) The CATALOG parameter is optional and its usage is site-specific. With that, there's no need to update the names of the parm files in FMP.