A fix is available
APAR status
Closed as new function.
Error description
The BIC Directory will be discontinued in November 2018. There is no migration from the BIC Directory in EBCDIC format to the BIC Directory 2018 in TXT format.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All MERVA users. * **************************************************************** * PROBLEM DESCRIPTION: The BIC Directory 2018 is the successor * * of the current BIC Directory. The BIC * * Directory is produced in EBCDIC format. * * The BIC Directory 2018 is only produced * * in TXT and XML formats. Both formats * * cannot be used in MERVA where the * * EBCDIC format is required. There is no * * migration from the BIC Directory to the * * BIC Directory 2018. * **************************************************************** * RECOMMENDATION: This has been enabled. The utility DWSX2018 * * now converts two BIC Directory 2018 files * * into EBCDIC format. The converted files can * * then be used as input to the SWIFT * * correspondents file utility DWSCORUT and the * * currency file utility DWSCURUT. * ****************************************************************
Problem conclusion
Temporary fix
Comments
Problem conclusion The BIC Directory 2018 zip package is available on the SWIFT website (http://www.swiftrefdata.com/). The version in TXT format is named BICDIR2018_YYYYMMDD_TXT.zip. YYYYMMDD is the publication date of the package and its files. Two of the contained files are required: * BICDIR2018_V1_FULL_YYYYMMDD.txt It contains FI records. This is the data required for utility DWSCORUT. * CURRENCY_CODE_YYYYMMDD.txt It contains CU records. This is the data required for utility DWSCURUT. BICDIR2018_YYYYMMDD_TXT.zip must be downloaded from SWIFT to a workstation and unzipped. Then the files must be transferred from the workstation to the host where MERVA is installed. Input Data Set(s) ================= Before transferring a file, one or two input data sets at the host must be allocated. You can use a single data set to contain the FI or CU records separately. Then only one record type, FI or CU, can be transferred to be converted later. Or you use two data sets, one for the FI records, the other for the CU records. The data set must be allocated as a sequential data set (PS) with the following specifications: Space units .......... MEGABYTE Primary quantity ..... 17 (1) Secondary quantity 1 (1) Directory blocks ..... 0 Record format ........ VB Record length ........ 852 Block size ........... 32760 The primary and secondary quantity is related to a single data set and reflects the space requirements for the FI records. When using two data sets, the values enclosed in parentheses show the quantities for the CU records. Output Data Set =============== An output data set must be allocated. It contains the converted data: either the FI or CU records in EBCDIC format. When containing FI records, this is the input data set for utility DWSCORUT. When containing CU records, this is the input data set for utility DWSCURUT. The data set must be allocated as a sequential data set (PS) with the following specifications: Space units .......... MEGABYTE Primary quantity ..... 50 (3) Secondary quantity 10 (1) Directory blocks ..... 0 Record format ........ FB Record length ........ 855 Block size ........... 10260 The primary and secondary quantity reflects the space requirements for the FI records. The values enclosed in parentheses show the quantities for the CU records. Transfer Files to MERVA ======================= TCP/IP FTP should be used to transfer the files from the workstation to the host using ASCII - EBCDIC character translation. Running FTP at the workstation you would need to: * Login to the host with a userid permitted to write to the allocated data set, * Use the ASCII command to set the transfer mode to character translation, * Use the CD (change directory) command to switch to the required data set on the host, * Use the PUT command to transfer each file to the host. Sample Job ========== After transferring the files to z/OS, you run the conversion utility DWSX2018 specifying the input data set as DD DWSFILE. DD DWSOUT defines the output data set to which the records in EBCDIC format are written for input to DWSCORUT or DWSCURUT. //... JOB ... //BICD2018 EXEC PGM=DWSX2018,REGION=0M //STEPLIB DD DSN=MERVA.LOADLIB,DISP=SHR Contains DSLPRM // DD DSN=MERVA.SDSLLODB,DISP=SHR Contains DWSX2018 //SYSPRINT DD SYSOUT=* //DWSPRINT DD SYSOUT=* //DWSFILE DD DSN=MERVA.BICD2018.TXT,DISP=SHR //DWSOUT DD DSN=MERVA.BICD2018.OUT,DISP=OLD Here is an example of the job's output in DWSPRINT after conversion of FI records: DWS940I 113667 input records of type FI processed DWS942I 113667 output records of type FI written The data set specified as DD DWSOUT is the input data set for DWSCORUT and DWSCURUT. DD DWSTAPE defines this data set both in the DWSCORUT and DWSCURUT job. If the DWSX2018 job ends with return code 0 or 4, the DD DWSOUT data set can be used as input to DWSCORUT or DWSCURUT.
APAR Information
APAR number
PI92675
Reported component name
MERVA ESA 4.1.0
Reported component ID
5648B2900
Reported release
410
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-19
Closed date
2018-02-07
Last modified date
2018-03-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI53657
Modules/Macros
DWSCORPG DWSCSD41 DWSCURUT DWSOMSC DWSX2018 DWS940I DWS941I DWS942I DWS943I DWS944I DWS945I H0B0410J
Fix information
Fixed component name
MERVA ESA 4.1.0
Fixed component ID
5648B2900
Applicable component levels
R410 PSY UI53657
UP18/02/09 P F802
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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7LGL","label":"MERVA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"","label":""}},{"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":"410","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 March 2018