Amend CPSM API Install for FILEDEF to allow override values.

This requirements has been re-assessed. We have no plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

This is a candidate for a future release

We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server

This is a candidate for a future release.

I have potentially 400+ development CICS regions to support each with their own versions of 250 files. As each file name contains the name of the environment this results in a file definition in BAS for each file for each region. So potentially 10,000 file definitions. Using RASGNDEFS within the WUI I can use an override field to set the file name for a region but this is a manual process. However, from outside the WUI the override is not available so I cannot use an installer REXX to install a file to an individual CICS region. Therefore, we cannot use a BAS environment to define and install new files from TSO/ISPF. The only other way would be to define a FILEDEF for each and every file for each and every region. This would still require a RASGNDEF to install and because each FILEDEF would now be unique there would have to be a 1:1 ration of RASGNDEF to FILEDEF. I think you would agree this is a lot of definitions.

For single file installs, the FILEDEF resource table does provide an OVERRIDE parameter for the INSTALL action and it is this parameter that the WUI uses. For example a valid parameter string for FILEDEF might be:
PARM(OVERRIDE('ADD=YES,BROWSE=YES') OVERTYPE(TARGET) USAGE(LOCAL) TARGET(cics_system_name).)

The list of action parameters can be seen here (http://www-01.ibm.com/support/knowledgecenter/SSGMCP_5.2.0/com.ibm.cics.ts.doc/eyua6/FILEDEFtab.html?lang=en) in table 1 "Valid CPSM operations". Look for the PERFORM SET operation and the INSTALL action. It is agreed that it is not clear how to use these actions and the useful information around setting those action parameters is not available in the resource table reference guide. It would be reasonable for us to look at improving this information. At the moment the information is generated automatically from the code.

It would be useful to understand more the overall goal here is with a view to providing some guidance as to best practice. You mention single file installs, but also in the business justification, there is reference to how many RASGNDEFs are required to create a BAS file infrastructure. For single file installs, the advice above will work. For larger BAS infrastructure questions we will need more information about whatis trying to be achieved..