A fix is available
APAR status
Closed as new function.
Error description
Support for the new BICPlusIBAN file format
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All using the new SWIFT BICPlusIBAN * * Directory * **************************************************************** * PROBLEM DESCRIPTION: MERVA ESA support for SWIFT BICPlusIBAN * * Directory * **************************************************************** * RECOMMENDATION: * **************************************************************** SWIFT will phase out the BIC Database Plus at the end of 2008 and users must migrate to the BICPlusIBAN Directory. This APAR introduces a new MERVA utility program, DWSBICPI, to extract data from the SWIFT BICPlusIBAN directory files for input to the MERVA correspondents and currency code files. DWSBICPI extracts information from the following BICPlusIBAN directory files: - BI file (BICPlusIBAN information) - CU file (ISO Currency Code information) The information is extracted to a data set in the format required by the existing MERVA utilities DWSCORUT, for the MERVA correspondents file, and DWSCURUT, for the MERVA currency code file. These utilities must then be run to add the data to the correspondents and currency files. The BICPlusIBAN files are provided by SWIFT as down-loadable zipped files. Each file consists of one header line, followed by separate data lines of variable length. The fields in each line are separated by tab characters. For details, refer to the Technical Specifications for BICPlusIBAN Directory from SWIFT. The files must be down-loaded from SWIFT to a workstation, unzipped, and then transferred from the workstation to the z/OS host where MERVA is installed. The BI file is very large, therefore you are recommended to allocate the data set in z/OS before transferring the file. The data set should be allocated as a sequential data set (PS) with the following specifications: Space units . . . . . MEGABYTE Primary quantity . . 65 Secondary quantity 10 Directory blocks . . 0 Record format . . . . VB Record length . . . . 1536 Block size . . . . . 32760 The size of the file (in 2008) is about 60 million bytes with nearly 300,000 records. To be prepared for future growth we recommend the allocation of at least 65MB primary space and a specification of 10MB as secondary space. The CU file is quite small, only about 10KB, so pre-allocation should not be necessary. TCP/IP FTP should be used to transfer the files from the workstation to z/OS using ASCII - EBCDIC character translation. Running FTP at the workstation you would need to: - login to MVS 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 MVS, - use the PUT command to transfer each file to the host. After transferring the files to z/OS you run the extraction utility DWSBICPI specifying the transferred data set as DD DWSFILE. DD DWSOUT defines the output data set to which the extracted records are written for input to DWSCORUT and DWSCURUT. Here is an example to extract correspondents data: //... JOB ... //BICIBAN EXEC PGM=DWSBICPI,REGION=4096K,PARM= //STEPLIB DD DISP=SHR,DSN=MERVA.LOADLIB // DD DISP=SHR,DSN=MERVA.SDSLLODB //SYSPRINT DD SYSOUT=* //DWSPRINT DD SYSOUT=* //DWSFILE DD DISP=SHR,DSN=MERVA.BICIBAN.TXT //DWSOUT DD DSN=MERVA.BICIBAN.OUT,DISP=(NEW,KEEP), // SPACE=(CYL,(10,10),,CONTIG),UNIT=SYSDA, // DCB=(DSORG=PS,RECFM=FB,LRECL=1248,BLKSIZE=14976) // Here is an example of the job's output in DWSPRINT: DWS983I 294179 input records of type BI processed DWS985I 231519 records without BIC code skipped DWS986I 62660 output records of type FI written By default only records containing a BIC code are extracted, records without a BIC code are skipped. Records without a BIC code cannot be used by MERVA for bank address expansion because the BIC code is used as search key in the correspondents file. Specify PARM=A in the EXEC statement if all records are to be extracted including those with an empty BIC code field. Here is an example job to extract data from the currencies file: //... JOB ... //CURRENCY EXEC PGM=DWSBICPI,REGION=4096K,PARM= //STEPLIB DD DISP=SHR,DSN=MERVA.LOADLIB // DD DISP=SHR,DSN=MERVA.SDSLLODB //SYSPRINT DD SYSOUT=* //DWSPRINT DD SYSOUT=* //DWSFILE DD DISP=SHR,DSN=MERVA.CUFILE.TXT //DWSOUT DD DSN=MERVA.CUFILE.OUT,DISP=(NEW,KEEP), // SPACE=(CYL,(1,1),,CONTIG),UNIT=SYSDA, // DCB=(DSORG=PS,RECFM=FB,LRECL=1248,BLKSIZE=14976) // An example of the job's output in DWSPRINT is: DWS983I 268 input records of type CU processed DWS986I 268 output records of type CU written If the DWSBICPI job ends with return code 0 or 4 the extracted information can be used as input to the MERVA utilities DWSCORUT (correspondents file) and DWSCURUT (currency codes file). The output data sets created by the DWSBICPI utility are input to DWSCORUT and DWSCURUT using the DWSTAPE DD statement. For details and examples of JCL, refer to the MERVA Operations Guide, Chapter 26 "Maintaining the S.W.I.F.T. Correspondents File" and Chapter 27 "Maintaining the S.W.I.F.T. Currency Code File". Example for importing correspondents data: //... JOB ... //IMPORT EXEC PGM=DWSCORUT,REGION=4096K //STEPLIB DD DISP=SHR,DSN=MERVA.LOADLIB // DD DISP=SHR,DSN=MERVA.SDSLLODC // DD DISP=SHR,DSN=MERVA.SDSLLODB //SYSPRINT DD SYSOUT=L //DWSCOR DD DISP=SHR,DSN=corrfile //DWSPRINT DD SYSOUT=L,DCB=(BLKSIZE=1370) //DWSTAPE DD DISP=SHR,DSN=MERVA.BICIBAN.OUT //DWSIN DD * UPDATE=UNCOND // Error and information messages issued by DWSBICPI utility: DWS983I nnnnn input records of type tt processed Explanation: The DWSBICPI utility program has processed nnnnn input records. The record identifier tt is either CU, indicating a currencies file, or BI, indicating a BICPlusIBAN directory file. System Action: None. User Response: None. DWS984I nnnnn records with invalid or unsupported tag skipped Explanation: The DWSBICPI utility program has found nnnnn input records with a record identifier which is neither CU, indicating a currencies file, nor BI, indicating a BICPlusIBAN directory file. System Action: The records have been skipped. Processing terminates with return code 4. User Response: Check the erroneous input file. It might be that an unsupported file was used as input, or the file was corrupted during file transfer to the host. Transfer to the host must be performed with ASCII to EBCDIC conversion. After correcting the file re-run the utility. DWS985I nnnnn records without BIC code skipped Explanation: The DWSBICPI utility program has found nnnnn input records in the BICPlusIBAN directory file which do not contain the optional BIC CODE field. Records without a BIC CODE cannot be used by MERVA for bank address expansion because the MERVA correspondents file uses the BIC CODE fields as search key. System Action: The records in question have been skipped. Processing has finished. User Response: Use the resulting output file, DWSOUT, as input to the MERVA DWSCORUT utility. DWS986I nnnnn output records of type tt written Explanation: The DWSBICPI utility program created nnnnn records in output file DWSOUT for input to the MERVA utilities DWSCORUT or DWSCURUT. The type of the created output records is either CU (currencies file) or FI (correspondents file in the BIC Database Plus format). System Action: None. User Response: None. DWS987I Invalid input file, TAG tt not supported Explanation: The DWSBICPI utility program found the unknown or unsupported record identifier tt in the second record of the input file. The tag must be either CU or BI. System Action: The file type could not be determined so processing terminates with return code 8. User Response: Check the erroneous input file. It might be that an unsupported file was used as input, or the file was corrupted during file transfer to the host. Transfer to the host must be performed with ASCII to EBCDIC conversion. After correcting the error, re-run the utility. DWS988I File ffffffff with unsupported record format or length nnnnn Explanation: The DWSBICPI utility program cannot process file ffffffff. fffffff is either the input file DWSFILE or output file DWSOUT. DWSFILE must have variable length record format (RECFM VB). DWSOUT must have fixed length record format (RECFM FB) with a record length of either 1248 or 1536. System Action: The file is not usable. Processing terminates with return code 8. User Response: Correct the file or the DD statement. DWS989I File ffffffff open error Explanation: The DWSBICPI utility program could not open file ffffffff. fffffff is either the input file DWSFILE or output file DWSOUT. This message occurs together with a system error message which details why the file could not be opened and can be found in the job log. System Action: Processing terminates with return code 8. User Response: Analyze the cause of the error and re-run the utility.
Problem conclusion
Temporary fix
Comments
MERVA ESA supports now the new SWIFT BICPlusIBAN Directory
APAR Information
APAR number
PK62368
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
Submitted date
2008-03-10
Closed date
2008-06-13
Last modified date
2008-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK37247
Modules/Macros
DWSBICPI DWSCSD41 DWSOMSC DWS983I DWS984I DWS985I DWS986I DWS987I DWS988I DWS989I H0B0410J
| SH12637500 |
Fix information
Fixed component name
MERVA ESA 4.1.0
Fixed component ID
5648B2900
Applicable component levels
R410 PSY UK37247
UP08/06/14 P F806
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 July 2008