Upgrading file control

This section covers the actions to take to migrate file control resources when you upgrade from one release of CICS to another.

Upgrade actions

Your current version Action Mandatory or optional?
V4.1
V4.2
Change file and transaction resource definitions Mandatory
V4.1
V4.2
Adapt to changes in LSR pool settings Optional

Change file and transaction resource definitions

If transaction isolation is active, and a program attempts to issue a file control write or update request against a file where the VSAM data set associated with the file uses VSAM nonshared resources (NSR), the program abends with the abend code AFDK. Requests to read or browse the file that do not attempt to update the file in any way do not result in an abend.

To avoid this situation, choose one of the following solutions:
  • If the file requires transaction isolation, change the FILE resource definition so that the file uses either VSAM record-level sharing (RLS) or VSAM local shared resources (LSR). RLSACCESS(YES) specifies that CICS® opens the file in RLS mode. LSRPOOLNUM(number) specifies the number of an LSR pool to be used by the VSAM data set associated with the file.
  • If the file does not require transaction isolation, change the TRANSACTION resource definition to specify ISOLATE(NO). Setting this value causes the individual transaction to run without transaction isolation.

Back to top

Adapt to changes in LSR pool settings

Before CICS TS for z/OS®, Version 4.2, you specified the number of the LSR (local shared resource) pool in FILE and LSRPOOL resource definitions by using the LSRPOOLID attribute, which has values in the range 1 - 8. From CICS TS for z/OS, Version 4.2, the value that is specified for LSRPOOLID in existing FILE and LSRPOOL resource definitions is transferred to the new option LSRPOOLNUM, which has values in the range 1 - 255.
If you share a CSD
Releases up to Version 4.2 only recognize LSRPOOLID, so, if you share a CSD with earlier releases of CICS, use the compatibility mode in CEDA and DFHCSDUP to set a value for LSRPOOLID. If you specify a value for LSRPOOLNUM, it is used only in this release.
If you use BAS to install a file or LSR pool definition
In CICSPlex® SM Business Application Services (BAS), if you install a FILE or LSRPOOL definition that specifies an LSR pool number greater than 8 into CICS TS for z/OS, Version 4.1 or earlier, the default value of 1 is used. You can use CICSPlex SM to specify a number in the range 1 - 8.

Existing programs that use the commands EXEC CICS CREATE FILE, EXEC CICS CREATE LSRPOOL, EXEC CICS CSD DEFINE FILE, EXEC CICS CSD DEFINE LSRPOOL, EXEC CICS CSD ALTER FILE, or EXEC CICS CSD ALTER LSRPOOL with the LSRPOOLID attribute continue to work correctly. CICS substitutes the value in LSRPOOLNUM for the value in LSRPOOLID when the command is run.

Batch jobs that use the CICS system definition utility program (DFHCSDUP) and issue the commands ALTER FILE, DEFINE FILE, ALTER LSRPOOL, or DEFINE LSRPOOL with the LSRPOOLID attribute continue to work correctly. When compatibility mode is used, CICS uses the value in the LSRPOOLID attribute as the number of LSR pools. When compatibility mode is not used, CICS substitutes the value in LSRPOOLNUM for the value in LSRPOOLID.

Back to top



upgrade_file.html | Timestamp icon Last updated: Sunday, 4 June 2017