A fix is available
APAR status
Closed as program error.
Error description
When the KEYLENGTH field is not specified on the File Control request, UEP_FC_RECORD_ID_L contains binary zeroes. This means that the exit XFCFRIN cannot specify the KEYLENGTH field as it addresses this field through UEP_FC_RECORD_ID_L. If the XFCFRIN exit sets UEP_FC_RECORD_ID_L to the address of a half-word with the desired key-length, this is ignored by CICS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users * **************************************************************** * PROBLEM DESCRIPTION: XFCFRIN unable to set LENGTH and * * KEYLENGTH fields for remote files * * when not specified on the API call. * **************************************************************** * RECOMMENDATION: * **************************************************************** Currently XFCFRIN is unable to set the KEYLENGTH field for remote files as the corresponding exit parameter, UEP_FC_RECORD_ID_L, was set to binary zeroes, because KEYLENGTH was not specified. This meant that it could not be modified by XFCFRIN. A similar situation applies with the LENGTH field, as UEP_FC_RECORD_L is set to binary zeroes when the LENGTH field is not specified. Similarly, this prevented the LENGTH field being set for a remote file by XFCFRIN if it was not specified on the API call. Additional Keywords: UEPAR GLUE Global User Exit PK10429
Problem conclusion
Two new XFCFRIN exit parameters have been created: UEP_FC_M_RECORD_ID_L and UEP_FC_M_RECORD_L. These can be set to specify the KEYLENGTH and record LENGTH respectively for a remote file when not specified on the API call. In the CICS Customization Guide, for CICS Transaction Server Version 3 Release 1, (SC34-6429-01) in Part 1, Chapter 1, under section titled 'File control domain exits, XFCFRIN and XFCFROUT' two new parameters will be added at the end of XFCFRIN: UEP_FC_M_RECORD_L Address of a fullword containing the modified record length field. This can be used to change the LENGTH for remote files only, when the LENGTH field is not specified on the API call. If the LENGTH field is specified on the API call, then UEP_FC_RECORD_L should be used, as changing the value at the address stored by UEP_FC_M_RECORD_L will have no effect. UEP_FC_M_RECORD_ID_L Address of a halfword containing the modified key length field. This can be used to change the KEYLENGTH for remote files only, when the KEYLENGTH field is not specified on the API call. If the KEYLENGTH field is specified, then UEP_FC_RECORD_ID_L should be used, as changing the value at the address stored by UEP_FC_M_RECORD_ID_L will have no effect. ------ Also update the definitions of UEP_FC_RECORD_L by adding the following at the end of the paragraph starting 'For a WRITE or REWRITE, this is an optional field...': If the field is not specified, the fullword will contain binary zeroes. To modify the record length for a remote file in this scenario, UEP_FC_M_RECORD_L should be used instead. ------ Also update the definitions of UEP_FC_RECORD_ID_L by adding the following at the end of the sentence starting 'KEYLENGTH is an optional input parameter...': If the field is not specified, the halfword will contain binary zeroes. To modify the key length for a remote file in this scenario, UEP_FC_M_RECORD_ID_L should be used instead. ---------------------- In CICS Data Areas, for CICS Transaction Server Version 3 Release 1 (LY33-6107-00), in Chapter 1 "CICS Transaction Server for z/OS Data Areas", under section "UEPAR Global user exit plist", under the XFCFRIN parameters at offset x'A8', update it to: (A8) ADDRESS 4 UEP_FC_M_RECORD_L Address of fullword modified record length ------- Add at offset x'AC': (AC) ADDRESS 4 UEP_FC_M_RECORD_ID_L Address of halfword modified key length
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK10418
Reported component name
CICSTS 3.1 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-08-17
Closed date
2005-09-30
Last modified date
2005-11-03
APAR is sysrouted FROM one or more of the following:
PK09052
APAR is sysrouted TO one or more of the following:
Modules/Macros
DFHAPEX DFHAPEXA DFHAPEXM DFHAPEXR DFHAPEXT DFHEXITP DFHFCFR DFHUEXIT
SC34642901 | LY33610700 |
Fix information
Fixed component name
CICSTS 3.1 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R400 PSY UK07702
UP05/10/05 P F510
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 November 2005