Message Entry and Repair Facility Use

WebSphere Business Integration for Financial Networks
for z/OS
Message Entry and Repair Facility
User's Guide
Version 3 Release 1
SH12-6904-06
for z/OS
User's Guide
Version 3 Release 1
SH12-6904-06
Note
Before using this information and the product it supports, be sure to read the general information under Appendix C,
“Notices,” on page 49.
This edition applies to Version 3 Release 1 of IBM WebSphere BI for FN (5655-FIN) and to all subsequent releases
and modifications, until otherwise indicated in new editions.
Changes to this edition relative to SH12-6904-05 are marked with a vertical bar.
Reference key: 20101027-1538
© Copyright IBM Corporation 2009, 2010.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this document . . . . . . . . . v Authorizing a message . . . . . . . . . . 35
How to send your comments . . . . . . . . . v Retyping values in a message . . . . . . . . 36
Summary of changes . . . . . . . . . . . v Relaying a message. . . . . . . . . . . . 37
Unlocking a message . . . . . . . . . . . 37
Chapter 1. Working with the Message
Entry and Repair Facility . . . . . . . 1 Chapter 4. Tasks of a message
Message domains . . . . . . . . . . . . . 2 administrator . . . . . . . . . . . . 39
Concept . . . . . . . . . . . . . . . . 3 Deleting a message . . . . . . . . . . . . 39
Queues . . . . . . . . . . . . . . . . 4 Copying a message . . . . . . . . . . . . 39
Purpose . . . . . . . . . . . . . . . 4 Moving a message to another queue . . . . . . 40
Types . . . . . . . . . . . . . . . . 5 Unlocking a message . . . . . . . . . . . 40
Queue list . . . . . . . . . . . . . . 5 Retrying routing of a message . . . . . . . . 41
Messages . . . . . . . . . . . . . . . 6
Draft . . . . . . . . . . . . . . . . 6 Chapter 5. Tasks of a template
Template. . . . . . . . . . . . . . . 6 administrator . . . . . . . . . . . . 43
Data entry concepts . . . . . . . . . . . . 7 Creating and maintaining templates . . . . . . 43
Entering data in message fields . . . . . . . 7
Selecting a code word . . . . . . . . . . 7
Appendix A. Keyboard shortcuts . . . 45
Selecting an option . . . . . . . . . . . 8
Expanding sections . . . . . . . . . . . 9
Repeatable sequence . . . . . . . . . . . 9 Appendix B. Icons . . . . . . . . . . 47
BIC address information . . . . . . . . . 10
Conditional sections . . . . . . . . . . 12 Appendix C. Notices . . . . . . . . . 49
Trademarks . . . . . . . . . . . . . . 51
Chapter 2. User Interface components 13
Common elements . . . . . . . . . . . . 13 Glossary of terms and abbreviations 53
Message Entry and Repair page . . . . . . . 13
The message processing page . . . . . . . . 15 Bibliography . . . . . . . . . . . . 61
Views . . . . . . . . . . . . . . . 15 WebSphere BI for FN for z/OS publications . . . 61
Actions . . . . . . . . . . . . . . . 22 WebSphere MQ publications. . . . . . . . . 61
Display of message lists . . . . . . . . . . 24 DB2 publications . . . . . . . . . . . . 61
WebSphere Application Server webcasts and
Chapter 3. Tasks of the message editor 27 publications . . . . . . . . . . . . . . 61
Creating a SWIFTNet FIN message . . . . . . 27 MERVA ESA publications . . . . . . . . . . 61
Creating a message using templates . . . . . 29 Other IBM publications . . . . . . . . . . 62
Creating a SWIFTNet MX message . . . . . . 30 SWIFT publications . . . . . . . . . . . . 62
Viewing a message . . . . . . . . . . . . 32
Editing a message . . . . . . . . . . . . 33 Index . . . . . . . . . . . . . . . 63
Redirecting a message . . . . . . . . . . . 34
© Copyright IBM Corp. 2009, 2010 iii

iv WebSphere BI for FN for z/OS: MER Facility: User's Guide
About this document
This document describes how to use the Message Entry and Repair (MER) Facility
of the Message Management feature of IBM® WebSphere® Business Integration for
Financial Networks Version 3 Release 1.0 (abbreviated to WebSphere BI for FN).
Readers of this document should be familiar with the Internet Browser of their
environment. WebSphere BI for FN Version 3.1.0 is supporting the following
browser versions:
v Mozilla Firefox, Version 3.0x and later service releases.
v Microsoft Internet Explorer, Version 7.x and later service releases.
For installation questions and information, refer to WebSphere BI for FN: Planning,
Installation, and Customization.
How to send your comments

Your feedback is important in helping to provide the most accurate and
high-quality information. If you have any comments about this document or any
other WebSphere BI for FN documents, please send your comments in one of the
following ways:
v By e-mail to swsdid@de.ibm.com
v By fax to +49-7031-16-4881
Be sure to include the title of the document, its form number, and, if applicable,
the page number of the text you are commenting on.
Summary of changes
| Enhancements to WebSphere BI for FN Version 3 Release 1 (October 2010):
| New information about how to maintain tables
| Some WebSphere BI for FN tables contain an identity column and, under
| certain circumstances, require special maintenance. There is a new section
| that describes how to maintain such tables.
| New information about how to tune database performance
| If you use the SIPN FIN or MSIF service bundles, you might need to tune
| the performance of the database tables used by the services they contain.
| There is a new section that describes how to tune the performance of these
| tables.
| Editorial changes
| Some descriptions have been improved. All known errors have been
| corrected.
Enhancements to WebSphere BI for FN Version 3 Release 1 (August 2010):

New message definitions
WebSphere BI for FN now contains definitions for SWIFTNet Exceptions
and Investigations 1.1 (bank-to-bank) messages. The WebSphere BI for FN
message entry, routing, and printing services can now process such
messages.
© Copyright IBM Corp. 2009, 2010 v

MTXML format for SR2010
A new MTXML format lets applications and services exploit the
capabilities provided by XML when processing FIN messages that comply
with SWIFT Standards Release 2010 (SR2010). For more information, see
WebSphere BI for FN: Concepts and Components.
Testing message definition sets
For testing purposed, you can now specify that a message definition set is
to be used first for messages of a particular message domain, regardless of
its activation or deprecation dates. For more information, see WebSphere BI
for FN: System Administration.
Changed names of DNPRDU trace and log files
The names that the Reference Data Utility (DNPRDU) generates for its
trace and log files have changed. The names of trace files now end in .trc,
and the names of log files now end in .log. For more information, see
WebSphere BI for FN: System Administration.
Reorganizing table spaces
The WebSphere BI for FN documentation now describes how to run the
REORG utility to reorganize certain table spaces and thereby improve
database performance. For more information, see WebSphere BI for FN:
System Administration.
Placeholder information
The WebSphere BI for FN documentation now describes whether each
customization placeholder is mandatory or optional. For a mandatory
placeholder, a value must be specified during customization; for an
optional placeholder, the value can be specified later, by replacing the
placeholder in the generated resource file with the appropriate value.
Enhancements to WebSphere BI for FN Version 3 Release 1 (June 2010):

Switching SAG MP option sets
A SendMsg or SendFile scenario can use an SAG MP option set group
instead of a particular SAG MP option set. If such a scenario encounters a
recoverable error and exhausts all of its automatic recovery attempts (for
example, because the SAG specified by the first SAG MP option set in the
group is not running), the MSIF Transfer Service, instead of returning an
error response, switches to the next SAG MP option set in the group and
tries again.
When a scenario switches to a new SAG MP option set in a group, the
MSIF Transfer Service automatically sets that option set to be the new
active option set for the group. An operator can manually set the active
SAG MP option set of a group, and can query the active SAG MP option
set of a group.
Automatic resubscription
When an SAG for which the MSIF Transfer Service is subscribed to receive
FileAct events is stopped, the subscription is lost. However, when an SAG
at level Release 6.3 or later is restarted, it automatically notifies the MSIF
Transfer Service, which now automatically resubscribes to receive FileAct
events from that SAG.
Accounting information for file transfers includes transactions
The accounting information that WebSphere BI for FN reports for FileAct
file transfers that were processed by the MSIF Transfer Service now
includes not only the number of files and the number of kilobytes that
vi WebSphere BI for FN for z/OS: MER Facility: User's Guide

were transferred, but also the sum of the number of transactions specified
in the HeaderInfo folders of the corresponding FileAct primitives.
Enhancements to WebSphere BI for FN Version 3 Release 1 (April 2010):

Multiple selection in MER message lists
The MER Facility now provides a way for users to select more than one
message in a list. This enables users to carry out an action on several
messages at once, rather than having to repeat the same action for each
message individually.
Improved MER message list
In the MER Facility, the message list has been changed so that the push
buttons are visible regardless of how many messages are displayed. You no
longer need to scroll to locate the buttons when the list of messages
exceeds the window size.
Message definitions for SWIFT Standards Release 2008 have been removed
It is no longer possible to select messages from the message definition set
FIN2008 for creation of new messages.
The MER Facility now displays the message ID of each newly created message
Each message that is created using the MER Facility is assigned a unique
message ID. This ID is now displayed when the message is created.
Reply-to queue information for the DnqFinServiceOutput node
The DnqFinServiceOutput node now contains a new property that can be
used to set information about the reply-to queue. This makes it easier for
you to integrate your applications with the services that employ this node.
Enhancements to WebSphere BI for FN Version 3 Release 1 (December 2009):

New message definitions
WebSphere BI for FN now contains definitions for the following types of
SWIFTNet messages:
v SWIFTNet Exceptions and Investigations 1.2
v SWIFTNet Funds 4.1
v SWIFTNet System 6.3
The WebSphere BI for FN message entry, routing, and printing services can
now process such messages. The MER routing sample project
DNI_DnqErSwiftNetFunds has been renamed to DNI_DnqErSwiftNetMX
to reflect the fact that its message flows can process the messages of any
MX message domain.
MER Facility runs on Microsoft Windows and Solaris Operating Environment
The MER Facility enterprise application can now run on an application
server that runs on Windows and Solaris. For information about specific
operating system requirements, refer to the WebSphere Application Server
documentation for that operating system.
Improved message type selection and message list display
The selection of message types has been simplified so that categories are
no longer displayed. The message type subcategory is shown directly. If
there is only one category, it is automatically expanded. Message lists use
color to highlight alternate rows, which makes it easier to read the lists.
About this document vii

Display explanations for negative acknowledgments (NAKs)
When SWIFT negatively acknowledges a message, it sets a reason code,
called a NAK code, to identify the cause of the problem. The MER Facility
now displays NAK code descriptions.
Changed SAG release levels
The SAG Configuration and Operation services now support for SWIFT
Alliance Gateway (SAG) release 6.3. Support for SAG release 5.0 was
removed from these services.
Output routing nodes can set precedence for reply-to queue
The routing nodes DnqErFinOutput and DnqErMsifOutput can now
specify which of the following is to take precedence:
v The reply-to queue and queue manager that are specified by means of
node properties
v The reply-to queue and queue manager that are specified in the message
Improved MER FIN routing samples
The MER FIN routing samples have been enhanced and now demonstrate
the handling of OSN messages.
SDF Users of the Sequential Data Facility (SDF) can now specify for which OU
the SDF is to process messages.
Routing to FMT FIN service
The DnqErFinOutput node is now able to send messages to the FMT FIN
service.
Updated message sets
The message sets DNI_DnqMsgSetEnv and DNI_DnqMsgSetMqrfh2 have
been updated to reflect the latest changes to the WebSphere BI for FN
message definitions.
New schema definitions for SWIFT Standards Release 2009
WebSphere BI for FN provides schema definitions for SWIFT Standards
Release 2009.
SWIFTNet InterAct application header fields
The MSIF Transfer Service can now process elements of InterAct
application headers, and applications that use the MSIF Transfer Service
can provide data for all InterAct header elements.
Product information fields
Applications that use the MSIF Transfer Service can use newly introduced
fields to provide product information (vendor names, product names, and
product versions) to SWIFT.
Message domain for a MsgReceived scenario
A new message-receive option has been introduced that can be used to
specify a message domain for a received InterAct message. This is useful
when such messages are to be processed by a routing flow.
Automatic recovery
Automatic recovery has been introduced for SendFile scenarios and
improved for FileReceived scenarios.
FileAct non-delivery warnings
Non-delivery warnings for FileAct scenarios can now be requested and
processed.
SAG restart signal
When an SAG at release level 6.3 is restarted, it issues a restart signal. The
viii WebSphere BI for FN for z/OS: MER Facility: User's Guide

MSIF Transfer Service uses this signal to generate an event that indicates to
an operator which SAG was restarted.
Traffic distribution
Administrators can now configure groups of SAG MP option sets for the
MSIF Transfer Service. This enables the MSIF Transfer Service to receive
message traffic from SWIFT regardless of to which SAG it has been routed
or to which message partner it is addressed.
Transfer window
To prevent the MSIF Transfer Service from passing to an SAG more
SendFile requests than it can comfortably handle, you can configure, for
each SAG, a transfer window. This window limits the number of requests
for which a response can be outstanding at any one time. If this limit is
reached, the MSIF Transfer Service buffers SendFile requests until the
number of requests for which a response is outstanding drops back below
the window size, at which time it passes the buffered requests to the SAG.
If this option is not set, the window size is unlimited and no requests are
buffered.
Enhancements to WebSphere BI for FN Version 3 Release 1 (August 2009):

Automatic generation of log file names during RM import
Each time the RM import command is issued, a log file is created. If a
name for the log file is not specified, one is generated. You cannot specify
a log file that already exists. The access rights for log files are set to
rw-r--r--.
Description of sample routing message flows
The following sample general purpose routing flows are now described:
DNQ_O_SFI
Routing flow for FIN messages from a sending application that are
to be routed to the SIPN.
DNQ_O_SFO
Routing flow for FIN messages from the SIPN that are to be routed
to a receiving application.
DNQ_O_SMX
Routing flow for MX messages regardless of whether they were
received from a sending application or the SIPN.
Wildcard for role definitions
You can now use a wildcard character when adding COs and attributes to
roles. The escape character used to flag this wildcard in list output is
customizable.
Enhancements compared to WebSphere BI for FN Version 2 Release 2:

Message entry and repair
Users use the Message Entry and Repair (MER) Facility to manually
process (for example, create, edit authorize, retype, and display) SWIFT
messages. Create custom message flows that determine the sequence of
message processing activities.
Message routing
New nodes and sample flows make it easier to create your own message
flows to route messages.
About this document ix

Message printing
Use the Message Printing Service to send messages to a printer or to
another output medium such as file.
Import and export messages
Use the Sequential Data Facility to:
v Import FIN messages from an input file to a target queue
v Export FIN messages from a source queue to an output file
Consolidated messaging service for InterAct and FileAct
WebSphere BI for FN now offers a single service that sends and receives
business messages via SWIFTNet Interact and transfers files via SWIFTNet
FileAct. This service can also be used to operate SWIFT store and forward
(SnF) queues.
Reference data management
WebSphere BI for FN provides database tables that make reference data
(that is, BICPlusIBAN data and currency code and country code data)
available to WebSphere BI for FN services, and a utility called the
Reference Data Utility (RDU) that lets you maintain the reference data.
Scenarios now employ separate transfer and notification phases
In WebSphere BI for FN Version 2, the Enhanced FileAct service processed
a file transfer and its corresponding delivery notification sequentially, that
is, it sent a DeliveryAck notification only after it sent the corresponding
SendFile response or FileDownloaded notification. In WebSphere BI for FN
Version 3, the MSIF Transfer Service processes each scenario in two
separate, simultaneous, and asynchronous phases that both begin when the
scenario begins:
v A transfer phase, in which a message transfer or file transfer is
processed
v A notification phase, in which the corresponding system messages and
delivery notification (if any) are processed
Consequently, it now can happen that a DeliveryAck notification is passed
to an application before the corresponding SendFile response or
FileDownloaded notification.
x WebSphere BI for FN for z/OS: MER Facility: User's Guide

Chapter 1. Working with the Message Entry and Repair
Facility
The Message Entry and Repair (MER) Facility of the Message Management feature
of WebSphere BI for FN lets users manually enter and repair SWIFT messages (FIN
and selected MX message standards) using a Web-browser-based user interface that
works with an enterprise application that runs on IBM WebSphere Application
Server.
To log on to the MER Facility using a web browser, enter the following link in the
address line:
https://<server_name_or_IP>:<port>/home
where:
<server_name_or_IP>
The host name or IP address of the server on which the MER Facility
enterprise application is installed.
<port>
The configured port number that is set within the application or web
server to listen for this application.
Figure 1. Home Page
Notes:
1. Contact your system administrator for the correct link to access the application
in your organization.
2. If your environment has been configured for load balancing, contact your
system support representative to receive the correct link to access the MER
Facility.
© Copyright IBM Corp. 2009, 2010 1

You will then have access to the general information page of the Message
Management feature of WebSphere BI for FN. The Message Entry and Repair
functions can be selected from this page.
When you work with the functions of the MER Facility, please ensure that you use
the supplied action buttons and not the Backward/Forward buttons supplied
through the browser. Also ensure that you do not use different browser tabs or
browser windows to work with multiple messages at the same time.
Message domains
SWIFT maintains different versions of the various message standards. In
WebSphere BI for FN, information about a particular message standard is stored in
a message definition set. There is one message definition set for each version of a
particular message standard which are grouped to message domains holding all
different versions of a particular message standards.
The Message Management feature of WebSphere BI for FN currently supports the

following message domains:
DNIFIN - SWIFT Standards MT messages
This domain contains all SWIFTNet FIN user and system messages. The
supported set of message definitions in this release is:
v SWIFT MT Standards Release 2009
v SWIFT MT Standards Release 2010
DNIFUNDS - SWIFT Funds solution messages
This domain contains the SWIFTNet Funds messages. The supported set of
message definitions in this release is:
Note: The message definition sets have been separated due to different
user groups and availability dates of the SWIFTNet Funds message
definitions.
DNIENI - SWIFT Exceptions and Investigations solution messages
The DNIENI domain contains SWIFTNet Exceptions and Investigations
messages. The supported set of message definitions in this release is:
v SWIFTNet Exceptions and Investigations 1.1 (bank-to-bank)
v SWIFTNet Exceptions and Investigations 1.2 (corporate-to-bank)
DNISNSYS - SWIFTNet System messages
Messages in this domain conform to a SWIFTNet System Messages
standard. The supported set of message definitions in this release is:
v SWIFTNet System Messages 6.3
| For a definition of all possible message types, refer to the corresponding SWIFT
| documentation. The system supports multiple message standards in parallel, so
| you can have for example SWIFT MT Standards Release 2009 and SWIFT MT
| Standards Release 2010 installed in your system at the same time.
Further messages standards or updated versions may be provided at a later time.

Please refer to WebSphere BI for FN: Concepts and Components for further information
about message domains and their associated definition sets.
2 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Concept
The Message Entry and Repair Facility implements a message workflow using
queues. Each queue contains messages in a certain processing state. After each
processing step, a message and its associated information is evaluated and the next
queue is determined by the business workflow. The concept of queues and
messages and the actions that are applied to messages are described in the next
sections.
Edit
Redirect Backout Draft

Message
Create Authorize
Routing
Draft Backout Templates Redirect Backout
Retype
Queue types
Main
Draft Redirect Backout
Redirect
Backout
Templates
Figure 2. Concept - Example queue and routing setup
Note: The connection between the queues in the picture above represents an
example and is used for illustration purposes only. For more information
about the routing setup, see WebSphere BI for FN: Concepts and Components.
| As shown in the concept figure, each main queue has a number of associated
| queues for different purposes. The main queues are explicitly defined through
| configuration of the WebSphere BI for FN instance, whereas the associated queues
| will be automatically defined by the system. The CREATE main queue for example
| has three associated queues for the purpose of storing draft messages, maintaining
| templates and a backout queue in which a message that encounters a routing error
| are placed.
The connection between the steps of the message workflow is provided through
message routing that has been defined within the system. An action on a message
will trigger the evaluation and execution of the routing conditions which, in turn,
will determine the next processing step of the workflow.
Chapter 1. Working with the Message Entry and Repair Facility 3

Queues
The Message Entry and Repair queues are containers to collect messages for a
specific type of operation or serve as a starting point for creation of new messages.
Each queue has a purpose and a type. For example, a queue with the purpose
CREATE is used when creating messages, and a queue with the purpose
AUTHORIZE is used when authorizing messages.
Purpose
A queue is configured within WebSphere BI for FN and a specific queue purpose is
assigned. The queue purpose determines the business associated with that queue.
For example, if you define a queue having the name “myNewMsg” and assign it
to the purpose CREATE, you will be able to create new messages when selecting
this queue.
The following queue purposes are available:

Table 1. Queue purpose
Queue purpose Description
CREATE Queues of this type contain newly created messages.
EDIT Messages can be edited within EDIT queues to correct or change
the message content.
AUTHORIZE Queues of this purpose are used to authorize messages.
SECOND This purpose differs from the authorize purpose in that a second
AUTHORIZE person must authorize the message after a previous authorize
action.
RETYPE To reduce the likelihood of typographical errors, some fields of a
message require that their values are entered more than once. This
operation is called retyping. The RETYPE queue purpose is used
for this action.
DISPLAY These queues can be used to display messages in a workflow step.
Display queues are similar to authorize queues, that is, the

processing of messages can be deferred, but the user does not have
the authority to reject messages explicitly.
APPLICATION Messages can be collected for routing purposes without user
interaction. This is needed when two routing flows process
messages one after another. Application queues are used for Entry
and repair to serve as starting point for routing of messages. The
routing conditions then can be used to distribute the messages to
different queues within the workflow.
Note: Application queues are visible only to a message
administrator. This is required to allow retry of routing operations
in case of routing problems.

Types
A queue type represents the associated usage of the queue.
Table 2. Queue types
Queue types Description
MAIN Stores messages that are to be processed according to the purpose of
the queue. Each main queue can have at most one associated queue
per type.
DRAFT Stores messages that have been modified or created by the end user,
but that are not considered to be complete for subsequent workflow
processing. DRAFT queues are available for the queue purpose
CREATE and EDIT.
BACKOUT Stores messages for which a problem had been detected in routing
when the next queue is to be determined. If a message has been
stored in a backout queue because of a routing problem, the retry
routing operation can be used to initiate the routing action again.
REDIRECT Stores messages that are considered to be in an unexpected queue by
a user. A message administrator can examine the message and decide
on subsequent actions.
TEMPLATE Template type queues can be associated with CREATE queues only
and contain messages that can be used as templates to create a new
message. Templates are created by users having the template
administration role and are managed within a queue of type
TEMPLATE.
A message editor can use exactly those templates that are stored in
the template queue which is associated with the CREATE queue.
Note: The associated queues of type DRAFT, BACKOUT and REDIRECT will only
appear in the queues list if they contain messages.
Queue list
The queues available to the user are shown after selection of the organizational
unit (OU) to work with. A page is displayed as shown in Figure 16 on page 13.
The list of OUs represents all the OUs for which the user is authorized. The user
can select an OU by clicking on the OU name. For more information about OU, see
WebSphere BI for FN: Concepts and Components.

Messages
In addition to the messages processed throughout the WebSphere BI for FN
instance, the Message Entry and Repair Facility adds two new categories for
messages, as explained in the following sections.
Draft
A draft message represents a message that was created and which has been saved
for further editing. It is considered to be a draft until it has been submitted. A draft
message is stored in the associated draft queue to the main queue which was used
to create the message. If you continue working with the draft message and finally
submit it, the message will be removed from the draft queue.
Messages in draft queues cannot be redirected or copied.
Template
A message template can be used to create new messages having the same
characteristics as the template. A template is generated by a user having the
template administration role and is stored in a template queue. Each create queue
can have an associated template queue. When creating messages using templates,
the content of the fields is copied to the new message and the template will still be
available for further use - it is not removed from the queue.
Templates cannot be redirected or copied, but you can create a new template and
use existing templates as basis for this new one.

Data entry concepts
This section describes how to work with messages, using various illustrative
examples. First, some general message editing concepts are explained including
these sections:
v Entering data in message fields
v Selecting a code word
v Selecting an option
v Expanding sections
v Repeatable sequences
v BIC address information
v Conditional sections
Entering data in message fields

You must enter data in the message fields in the format specified in the “SWIFT
User Handbook”. The field label texts reflect the individual fields according to the
SWIFT User documentation, whereas the field tag (for example 103) can be used to
directly identify the field. While entering data you can use the tab key to jump to
the next input field.
Figure 3. Entry fields example
Mandatory fields are marked using a '*' character in front of the field tag as shown
for field 20 (Sender's Ref) in the picture above. The contents of disabled or
read-only fields cannot be changed. They are shown as in Figure 4.
Figure 4. Disabled/read-only fields
Selecting a code word

A field that contains one of a predetermined set of values is marked by a
symbol. Clicking on this symbol displays a list of the possible values for that field.
Then select one item from the list.

Figure 5. Selecting a code word
Selecting an option
Some fields let you select one option of several alternative options, or select no
option at all (see Figure 6). To select no option, select leave this field empty.
Figure 6. Choose an option
When you select an option, new fields might be displayed, as shown in Figure 7.
Figure 7. New fields displayed - Option A

If a different alternative is chosen for the same element, the fields displayed will be
changed according to the selected option. When selecting Option B for the same
tag as shown in Figure 7 on page 8, the display of the field will be changed as
shown in Figure 8.
Figure 8. New fields displayed - Option B
Expanding sections
Fields may be combined into sections. Each section can be expanded or collapsed
by clicking on the section title. An expanded sequence that is indicated by the
following sign shows you the header line and all fields. A collapsed sequence
that is indicated by the following sign shows you only the header line.
Figure 9. Display of a section (expanded)
Repeatable sequence
A repeatable sequence is a field or group of fields that can be successively entered
in a message more than once. Each repetition of a repeatable sequence is called an
occurrence. A field or section that can occur more than once is identified by
displaying the number of sequences within the section title. Click the New icon
to create a new occurrence. If the maximum number of occurrences is reached,
the New icon is no longer available.

Figure 10. Repeatable sequence
To delete an occurrence, press its symbol.
Figure 11. Display of more than one occurrence
BIC address information

If a message contains a bank identification code (BIC) field, this will be represented
through a combination field to enter or search for a specific address. Press the
expand/collapse button to execute an operation according to the mode
described below.
Note: You can also expand the field by pressing the ALT-Keydown key
combination.
A BIC address field operates in two modes:

Mode 1 - Direct entry
If you enter the full BIC address in the field and expand it by pressing the
button, the address information for the entered address is retrieved and
shown in the connected display area.

Figure 12. Expanded BIC address
If the display area for the BIC address is already shown, an expand
operation will collapse it. A collapsed area will not require space on the
screen as shown in Figure 13.
Figure 13. Collapsed BIC address
Mode 2 - Address search

Enter at least 6 characters to retrieve a list of possible matching BIC
addresses as shown in Figure 14.
Figure 14. Search for a BIC address
Pressing the expand/collapse button will show the list of addresses that
start with the same 6 characters. Select the required entry from the list or
press ESC to cancel the selection. If you select an entry from the list, the
selected address is retrieved and shown in the connected display area. If
the display area for the BIC address is already shown, pressing the
expand/collapse button will hide the detailed address information. Press
the expand/collapse button to show the information again.

Conditional sections
Some message definitions, especially in the SWIFTNet MX message space, may
contain a large number of variable fields which are only required depending on
the selection of other fields. In these cases, it might be required to reload the
selected definitions. The Message Entry and Repair Facility will display the
conditional sections using highlighted entries together with an indication to reload
the section as shown in Figure 15.
Figure 15. Reload indication for conditional sections

Chapter 2. User Interface components
Common elements
The following common elements will be shown in the header section of the pages:
Current user
The user ID of the current user is displayed in the header section.
About Select this link to display information about the product.
Help Select this link to show context help for the current page.
Logout
Select this link in the header to log out the current user and to return to
the home page.
Message Entry and Repair page

The Message Entry and Repair (MER) page represents the main entry for users and
administrators. Figure 16 shows a sample list of organizational units (OU) and
queues available for a user.
Figure 16. OU and queues list
Tip: You can save the link to the MER page within your browser to use as a direct
access to the queues you can work with.
This page displays the organizational units that were defined within the system
and for which you have access rights. Click the OU name to see the queues that
you are authorized to work with for that OU.

When selecting an OU, the queue list gets filled and the selected entry is
highlighted. You can select a queue by clicking on the queue name in the table.
When a queue gets selected, it is highlighted
The queues list contains the following elements:

Queue name The queue name column shows the name of each of the queues to
which you have access. Associated queues are displayed in an
italic font below their main queues. For example, the draft queue
for the FIN1Create queue shown in Figure 16 on page 13 is
indicated through the indented italic string FIN1Create - Draft.
Purpose The purpose of the main queues:
Create For creating messages
Edit For editing messages
Authorize
For authorizing messages
Second Authorize
For authorizing messages a second time
Retype
For ensuring the correctness of important data
Display
For verification of the message content
Application
For general message queues
For more information, refer to “Purpose” on page 4. Refer to
“Types” on page 5 for a list of associated queues for each queue
purpose.
# The number of messages per queue shows the number of message
awaiting processing.
Note: The number of messages which the current user can access
may be less than the number shown in the queues list. The
actual number a user can see/work on is depending on his
access rights.
Use the refresh button or the “Refresh” link at the bottom of the queue list to
refresh the list.

The message processing page
The message-processing window displays the contents of a message, and provides
the means to carry out functions for that message, such as validating it or
submitting it for further processing.
The following picture shows the general layout of the message processing pages:
Page
View tabs Message type Operation
View body
Action buttons MessageID
Figure 17. Page structure
View Tabs The tabs at the top of the notebook let you select
different representations of a message, called views.
These are described in “Views.”
Message type The message type field contains the description of
the current message type displayed.
Operation This field indicates the currently selected operation
within the selected queue. For example, if a
message is opened in view mode, this field will
show the string VIEW as identification.
View body The body section contains information according to
the selected view.
Action buttons The Actions section contains icons that correspond
to actions that can be carried out for the currently
displayed message.
Message ID An ID that uniquely identifies a message. The
message ID is generated and maintained by the
MER Facility. It allows to identify messages in the
message list and message processing page.
Views
For each message, the MER Facility offers one or more of the following views:
Formatted
This view displays the message as a series of fields and their values. This
makes it easy to understand its content, and lets you enter data without
having to know the message format required by the network.
Unformatted
This view displays the message in its native format, as it is transmitted
over the network.
Context
This view displays message context data.
History
This view displays the history information that has been recorded for this
particular message throughout the workflow.

These views are described in the following sections. Use the tabs at the top of the
message notebook to switch between views. All views might not be available for a
particular message. Only the context view is available for all messages.
Formatted view
This view displays the message as a series of fields and their values. For some
fields, code word selection or BIC expansion is available to make it easier to enter
data.
Figure 18. Formatted view of a message
Unformatted view
This view, shown in Figure 19 on page 17, displays the message in its native
format, as it is transmitted over the network. This view is not available for
messages in queues with the purpose RETYPE. In the unformatted view:
v You cannot look up values such as code words or BIC addresses.
v You cannot change security-related data such as the message type or sender.
A message that cannot be correctly formatted is shown in the unformatted view.
After it has been corrected, other views will also be available for the message.

Figure 19. Unformatted view of a message
Note: If you enter empty elements for SWIFTNet MX messages, for example
<abc/>, these elements will be removed when switching between the views
or if the message is validated from within the user interface.
Context view
This view, shown in Figure 20, displays message context data. The context view
can include these sections:
v “General” on page 18
v “Comment” on page 20
v “Header fields” on page 20
Figure 20. Context view of a message

General This section of the context view contains information about the
message in general. It provides the following information:
Table 3. Context view - General fields
Field Description
Message ID An ID that uniquely identifies the message within the MER Facility.
If a message was copied, it will be marked as copied and the parent
reference will be included. The parent reference is the unique
identifier sequence included in the MQMD. For more information,
refer to WebSphere BI for FN: Application Programming.
Locking user and If the message is locked, this indicates who locked the message and
time when.
Message type The message type as determined by the system.
Message domain The domain to which this message belongs (i.e DNIFUNDS).
Message definition The message definition set used for the message, for example the
set value “fin2009” which indicates the SWIFTNet FIN Standards release
2009.
Network type
SWIFTNETFIN
The message was processed by the SIPN FIN service.
FMTFIN
The message was processed by the FMT FIN service.
SWIFTNETINTERACT
The message was processed by the MSIF service.

Table 3. Context view - General fields (continued)
Field Description
Completion code The overall completion code indicates the overall result of the
message processing. This value depends on the reason codes
specified in the reason folders of the message:
Ok The message processing finished successfully. All of the
Reason folders contained the reason code Ok.
PartialOk
The message processing finished with at least one
recoverable error. At least one of the Reason folders
contained the reason code PartialOk, and none of them
contained the reason code Failed.
Failed The message processing finished with at least one
unrecoverable error. At least one of the Reason folders
contained the reason code Failed.
A message can contain up to 10 reason folders, each of which

indicates the result of the portion of the message processing. For
each reason folder, a separate code indicates the result. The result
will be displayed using the following icons together with the text for
the given reason.
Status: Ok
Status: PartialOk
Status: Failed
The following example shows the display of completion code

information.
Note: Use the right/left keys on your keyboard to scroll through the
entire text line if truncated.
Network string FIN A21 or F21 APDU if a positive or negative ACK was received
from SWIFT (SIPN FIN only).

Table 3. Context view - General fields (continued)
Field Description
Network code v ACK – successful transmission to SWIFT.
v NAK – unsuccessful transmission to SWIFT (SIPN FIN only).
In case a negative acknowledgement (NAK) has been received

together with an indication of the failure, this code will be displayed
in the network code field. You then can move the mouse pointer
over this code to get the description in a flyover panel. The
following picture shows the flyover displayed for NAK code E02:
If the full description does not fit into the flyover panel, you can
click on the code to open the panel in fixed mode so that scrolling is
possible. Then you have to manually close the panel using the Close
link in the flyover.
Application Data that may be set by an external application.
information
Possible duplicate Indicates if any information exists that marks the request as possible
duplicate
v True – if an indicator exists.
v False – if no indicator is found.
Comment You can use the comment field to enter any additional information
that you want to store with the message. You can use this field
during Authorization to indicate the reason of rejection of a
message.
Header fields This section, if available in the message, displays additional
information provided by elements in the ComIbmDni message
header if the message is not within the DNIFIN message domain.
Depending on the operation (CREATE/EDIT etc.), the fields are
either editable or can be viewed only.
All InterAct Application Header fields contain parts of the InterAct
application header structure. This structure is used to transport
business information related to the InterAct business payload,
typically a MX message. For details refer to the "SWIFTNet
Standards General Information" manual.

Table 4. Context view - Header fields
Field Description
Local address This is the local address that is relevant for the
processing of the message. For an InterAct message to
send (MSIF SendMsg request) this is the sender's
distinguished name (DN) of the message. For a
received InterAct message (MSIF MsgReceived request
or notification) this the receiver's DN of the message.
Remote address This is the remote address that is relevant for the
processing of the message. For an InterAct message to
send (MSIF SendMsg request) this is the receiver's
distinguished name (DN) of the message. For a
received InterAct message (MSIF MsgReceived request
or notification) this the sender's DN of the message.
Transfer option set This is the name of the MSIF TransferOptionSet that
the MSIF Transfer Service uses when processing the
message.
InterAct application header This field contains a message reference by an
message reference (xxx) application.
InterAct application header This indicates that the message is a possible duplicate
duplicate reference (xxx) from an application point of view. It refers to the
InterAct Application Header Message Reference to
which it may be a duplicate.
InterAct application header This provides free form information to the duplicate
duplicate info (xxx) message.
where (xxx) can be either (Request) or (Response) depending on

the header information available.
History view
This view displays the history information that has been recorded for this
particular message throughout the workflow. Special permission is required to see
the history list.
Figure 21. History view of a message
The history view contains the following information:

Date & Time
The date and time information for the history entry.
Service
The service identification of the function that operated on the message. For

example, this field will contain the value "ER" for MER functions and
"ROUTING" for any routing operation that happened during processing of
the message.
Useraction
If an MER user action was taken, this field will contain the action that was
triggered by the user (for example "SAVE").
Function
The function column contains the information which function did process the
message. This can be a value like CREATE, RETYPE or AUTHORIZE. The
value LIST is used to indicate that the user action has been submitted from
the message list.
Result
The column result contains the result information of the executed function.
Possible values are Ok and Failed.
User
The user who has performed the function is listed in this column. The user
information for MER functions represents the user unique name.
Queue information
The queue information contains the name and queue type of the target queue
after the action was performed
Destination
A field that is used to indicate a logical destination (for example “OFAC”),
not a physical queue. This field is set by routing.
Actions
The display of messages within queues provides actions using the buttons
indicated in Table 5, and described in the following list.
Table 5. Buttons
Action
Validate Submit Save as Accept Reject Quit
Queue Purpose Draft
CREATE X X X X
EDIT X X X X
DISPLAY X X
AUTHORIZE X X X
SECOND X X X
AUTHORIZE
RETYPE X X X
APPLICATION X
Validate Validates the content of the message. Each error is described in a

separate error message on the panel, and a symbol is
displayed next to the corresponding field, as shown in Figure 22 on
page 23. Click on an error message to jump to the field in error.
The validation button is not available if the message does not
contain a payload.
Submit Validates and submits a message for further processing for queues
with purpose CREATE and EDIT. If there are validation errors,
error messages are displayed and the message is not submitted. If

there are no validation errors, the message is stored and processed
according to the implemented business routing.
For queues with purpose DISPLAY, the submit action releases the
message for further processing.
Save as Draft Saves the message as a draft message to be further processed at a
later time. The message is posted to the associated Draft queue
from which you can resume working with the message.
Accept Authorizes the message.
Reject Rejects the message.
Quit Closes the page without saving any changes that were made, and
unlocks the message if it has been locked during the current
operation.
The Quit action is always available when messages are opened in
view mode.
Figure 22. Displaying validation errors
Use the print function of the browser to print the message directly as shown on
the page. All fields and sections are printed as is - collapsed sections will not be
expanded.

Display of message lists
| If you select a queue other than a create queue, a table with the messages on that
| queue is displayed. Each row in the table corresponds to one message. Only
| messages to which you have access will be shown. The queue name and its
| corresponding queue type are displayed together with the OU name in the right
| hand heading of the list.
Figure 23. Displaying a message list
| The icons in the "Actions" column of the table indicate which actions can be
| performed on that message. The displayed icons depend on the queue type and
| purpose, and on your access rights. To perform an action on a particular message,
| click on the corresponding icon in the table row of that message.
| Some actions can be performed on several messages at once. These actions are
| shown as buttons below the table. Use the checkboxes in the front of the rows to
| select one or more messages, then click on a button to perform that operation on
| all selected messages. If you do not have the required access rights for that action
| on all selected messages, a warning will be displayed. You can then choose to
| cancel the action, or to perform it only on those messages for which the access
| rights are available.
| When an action other than View or Unlock is performed on a message, that

| message is usually no longer on the current queue. In the message list, the
| messages on which an action has been performed are greyed out. This allows for
| quick orientation in long message lists. A click on the Refresh button will fetch an
| updated list of messages on the queue.
The following information can be displayed for each message.

Table 6. Possible columns of a message list
Column Description
Actions This column contains one symbol for each action you are authorized to perform (depending on
access rights)
View the message in read-only mode.
Open the message for the current queue purpose. For example, pressing this button within
a EDIT queue will let you edit the message.
Redirect the message. Do this if the message is in the wrong queue. From the redirect
queue, a message administrator can move it to another queue.
Undo a previous redirect.
Move the message to a different queue.
Copy the message to a different queue.
Delete the message.
Retry routing for messages in BACKOUT queues.
Unlock a message that is locked by someone else (special permission needed).
Unlock a message that is locked by you.

Lock The symbol in this column indicates whether a message is locked:
Message locked by someone else
Message locked by you

Note: A message is locked if an action is selected that potentially will modify the message. A lock
will prevent modification from other users. A VIEW action will not set a lock as this action does
not modify the message.
Message ID Unique ID of a message within the MER Facility.
Message The message domain, for example DNIFIN.
domain
Message type The message type, for example, FIN103.
Local address For outgoing messages, the local address column will contain the information of the sender, for
example, the sender LT name. For received messages, this column will contain the destination
address as specified by the correspondent.
Reference The application reference. For FIN messages, the content of field 108 of a FIN message, or, if this is
not available, the content of field 20 will be displayed. For Funds messages, the order reference
(OrdrRef) field is used.
Remote For outgoing messages, the remote address column will contain the information of the receiver, for
address example, the receiver LT name. For received messages, this column will contain the sender address.
Amount The amount information (if available for the message type). The amount is displayed using the
browser settings for the current language.
Date Date to which the transaction is to apply (if available for the message type). The date is displayed
using the browser settings for the current language.
ISN Input sequence number (if available for the message type).
OSN Output sequence number (if available for the message type).

Table 6. Possible columns of a message list (continued)
Column Description
Session ID Unique ID of the session (if available for the message type).
Message Priority of the message (if available for the message type).
priority
The permissions you have for a message determine which action icons are shown
next to the message in the actions column.
| Depending on the type of the queue for which messages are listed, a button for
| one of the following actions can be available:
| Create Message
| For queue type DRAFT, use this button to create a new message.
| Create Template
| For queue type TEMPLATE, use this button to create a new message
| template.
To leave the page, you can either press the Return to Queue Selection button or
select the QUEUES link in the header.

Chapter 3. Tasks of the message editor
A message editor is a user to whom the role DnqERMsgEditor has been assigned.
That role authorizes a user to:
v Create new messages
v View messages
v Edit a message
v Authorize messages
v Retype messages
Creating a SWIFTNet FIN message

If you have access to a create queue, you can enter a new message either directly
by selecting the type of message, or, if the message administrator has set up
templates, by selecting the required template as starting point for the new message.
The type of message to be created depends on the target domain in which the
message is to be processed.
This section illustrates how to create a SWIFTNet FIN message.

1. On the MER page, select an OU and a CREATE queue you want to create the
message in.
2. The Create Message page will be displayed containing the message domains
defined for the selected CREATE queue and for which you are authorized.
Choose the DNIFIN message domain for the new message. This updates the
page to display the sender selection.
3. Choose one of the senders. This updates the page to display the message
definition set selection.
Note: The sender cannot be changed during the further message entry steps.
4. Select the message definition set. The message types included in this message
domain and the selected message definition set will be displayed. The list
includes only the messages you can access. The page is updated as shown in
Figure 24 on page 28.
Note: If a test message definition set was configured, it will be marked in the
list using an italic font, the identifier (Test), and a different background
color.

Figure 24. Selection of a message type
Tip: Create a bookmark in your browser for the message types that you often
use. For example in the FireFox browser: right click on the message type
for which the bookmark is to be created and select the "Bookmark this
link" action from the popup menu.
5. Use the text marked with a sign to expand the message type sections and
to collapse the sections.
6. Click the type of message to be created, for example FIN103. The input panel
for that message type is shown in Figure 25 on page 29.

Figure 25. Input panel for a FIN103 message
7. Enter the necessary data. Which fields are required and the values they can
have is governed by SWIFT specifications. When you are finished, click
Submit. The message is validated. If no errors are detected, the message is
submitted for further processing according to the implemented business
workflow.
Creating a message using templates

If templates have been set up by the template administrator, you can select a
template to be used as starting point for the newly to be created message by
pressing the From Template button on the create messages page. The list of
templates will be displayed as shown in Figure 26 on page 30.
Chapter 3. Tasks of the message editor 29

Figure 26. List of templates for message creation
You can filter the message templates shown in the list by selecting the message
type from the filter drop-down control. This will force only those templates to be
shown in the list which have the same message type. To show all templates again,
select All in the drop-down filter.
Press the Direct Message Entry button if you decide to create a new message
directly, without using a template.
Creating a SWIFTNet MX message

This section illustrates how to create a SWIFTNet MX message using a SWIFTNet
Funds message as example. This serves as a reference how to create other
SWIFTNet MX message types like SWIFTNet Exceptions and Investigations or the
creation of system messages.
1. On the MER page, select an OU and a CREATE queue you want to create the
message in.
2. The Create Message page will be displayed containing the message domains
defined for the selected CREATE queue and for which you are authorized.
Choose the DNIFUNDS 1 message domain for the new message. This updates
the page to display the sender selection.
3. Choose one of the senders. This updates the page to display the message
definition set selection.
Note: The sender cannot be changed during the further message entry steps.
4. Select the message definition set. The message types included in this message
domain and the selected message definition set will be displayed. The list
includes only the messages you can access. The page is updated as shown in
Figure 27 on page 31.
1. Use message domain DNIENI for SWIFTNet Exceptions and Investigations and DNISNSYS for SWIFTNet System messages.

Figure 27. Selection of a SWIFTNet Funds message type
Tip: Create a bookmark in your browser for the message types that you often
use. For example in the FireFox browser: right click on the message type
for which the bookmark is to be created and select the "Bookmark this
link" action from the popup menu.
5. Use the text marked with a sign to expand the message type sections and
to collapse the sections.
6. Click the type of message to be created, for example setr.001.001.03. The input
panel for that message type is shown in Figure 28 on page 32.

Figure 28. Input panel for a Funds setr.001.001.03 message
7. Enter the necessary data. Which fields are required and the values they can
have is governed by SWIFT specifications.
8. Enter the receiver of the message into the header field Remote address in the
context view.
9. When you are finished, click Submit. The message is validated. If no errors are
detected, the message is submitted for further processing according to the
implemented business workflow.
Note: You can also use templates to create new SWIFTNet Funds messages if the
message administrator has set up templates. For details on the usage of
templates, refer to “Creating a message using templates” on page 29.
Viewing a message
If you are authorized to see a message, the icon is displayed in the Actions
column of the message list. Click the icon to open the message in read-only mode.

Figure 29. Message list containing view buttons
Editing a message
You can use the MER Facility to edit messages, for example to fix errors detected
during validation or processing. Messages stored in an EDIT queue can be opened
to modify fields. The message will be displayed in the same manner as during
creation of the message. You can for example correct incorrect values and problems
reported during authorization of the message and submit the message again.
If the routing connections (DnqERxxxInput) cannot convert a message to a format

which can be handled by the MER Facility, this message is routed to the EDIT
queue as UNPARSABLE. In this case, the message type is set to the value
'DNIUNPARSABLE' (see Figure 30). You can work on those messages if you have
rights on the EDIT queue for sender DNIUNPARSABLE and message type
DNIUNPARSABLE.
Figure 30. Message list containing an unparsable message
When you edit an unparsable message, the following page will be displayed, so
that you can correct the message:

Figure 31. Editing of an unparsable message
After correcting the message content, use the button Parse to check the message for
correctness according to the selected message type and, if specified by date, the
message definition set. If correct, press Proceed to continue.
If you click the Proceed button and no validation errors occur, the sender and the
message type are changed to the corresponding values within the edited message
and further processing of the message, according to business workflow, may occur.
Note: If a message has failed validation and is opened in edit, it may be possible
that the edit function will not show a validation problem when you press
the Parse or Proceed button. This is caused by some automatic corrections
performed by the MER Facility when the message is opened for edit. The
corrections performed are:
v uppercase conversion
v omission of empty fields
v automatic insertion of field 15 or field 16
v additional implicit modifications
Redirecting a message
If a message is in the wrong queue, you can redirect it by clicking the redirect
button . The message is then moved to the redirect queue associated with the
current queue. A message administrator can then move this message from the
redirect queue to the appropriate destination queue.
You can undo the redirecting of the message by selecting the redirect queue and
clicking the Undo Redirect button .

Figure 32. Messages in a redirect queue
Authorizing a message
To improve security and reduce the likelihood of errors, some messages must be
authorized. Authorization entails reviewing the contents of a message and either
accepting or rejecting it. Such messages are routed to the authorize or second
authorize queues.
1. Each message in the authorization queue must be authorized by one user.
2. Each message in the second authorization queue has already been authorized
by one user and now needs authorization by a second different user.
The message is displayed in a formatted view in read-only mode as shown in the

next figure.
Figure 33. Message authorization

Note: Second authorization is available to a user only if the last Create, Edit,
Retype, or Authorize operation was performed by a different user.
Use the Accept button to authorize the message, use Reject to mark the message
failing authorization.
Note: If you want to add comments for the action performed, use the comment
field in the context view. This can be used for example to give a hint why
the message was rejected to the next user/action in the workflow.
Retyping values in a message

To reduce the likelihood of typographical errors, some fields require that their
values are entered more than once. This operation is called retyping. Messages
containing such fields should be routed to the retype queue.
Note: The definition of fields to be entered more than once is included for selected
FIN messages only. SWIFTNet Funds messages will be displayed in view
mode without retype fields.
To retype values for a message:

1. Select the message from the message list. The formatted view is displayed, and
only the fields for which values are to be retyped are enabled, as shown in
Figure 34. The unformatted view is not available; this prevents the user from
being able to see the data that is to be retyped.
2
Figure 34. Retyping a message
2. Enter the required data and click Accept. If the retyped data is correct, the
message is accepted for further processing.
2. The ellipses shown in the picture above are used for illustration only.

Figure 35. Successful retyping
If the retyped data is incorrect, an error information is displayed containing the

information, which field was incorrect. You can retry the operation three times.
The message is rejected if this limit is reached.
Clicking Reject causes the message to be routed according to the routing

definitions. The sample routing definitions pass the message to an edit queue.
Clicking Quit closes the view without saving any changes.
Relaying a message
Relaying a message means passing a message to another queue without changing
its contents.
Only messages in display queues can be relayed. Relay the message by pressing
the Submit button
Unlocking a message
If a message has been locked through an operation, for example, if you did not
finish message editing, this lock needs to be removed so that others can work with
this message. The task of unlocking a message is either implicit if the message
editing function is finished correctly or through an explicit unlock action. If you
hold a lock on a message, this is indicated in the message list through the
icon.
To unlock the message, press the icon in the action column.

Chapter 4. Tasks of a message administrator
A message administrator is a user to whom the role DnqERMsgAdmin has been
assigned. That role authorizes a user to:
v Delete messages from queues
v Copy messages
v Unlock locked messages
v Move messages to other queues
v Retry routing
Deleting a message
A message administrator with the access right to delete messages will see the
icon in the message list. When the icon is selected, a confirmation message will be
displayed to confirm the delete operation.
Figure 36. Message deletion initiated
After clicking the OK button, you are informed that the delete action has been
initiated.
Copying a message
The copy operation generates a duplicate of a message and stores it in another
queue. This operation requires special permission. To copy a message, click the
copy icon in the Actions column and select a target queue from the
drop-down list of queues that is displayed. The list contains only main queues of
the same OU that have purposes other than CREATE.

Figure 37. Copying a message
Moving a message to another queue

You can move messages only from a redirect queue. Click the move icon in
the Actions column and select a target queue from the drop-down list of queues
that is displayed.
Note: Other than in copy actions, the target queue for a move action has to be
different than the source queue.
Unlocking a message
The task of unlocking a message is required if a message has been locked by
another user ID and now this lock needs to be removed. This is the case, for
example, if a user did not finish message editing. The user who last worked on a
message locks it and only that user can work on it again, with the exception of the
user who has the right to unlock messages. The following icons deal with locking
and unlocking:
Message locked by you
Unlock a message that is locked by someone else (special permission

needed)
Unlock a message that is locked by you
Figure 38. Message List with lock and unlock symbol

Retrying routing of a message
If a message has been stored in a backout queue because of a routing problem, the
retry routing icon can be used to initiate the routing action again. The
operation applies only to backout queues. This might be helpful if a temporary
routing problem exists and the message can be processed as expected after the
routing problem has been resolved.
Figure 39. Retry routing from a backout queue
Figure 40. Retry routing initiated
Chapter 4. Tasks of a message administrator 41

Chapter 5. Tasks of a template administrator
A template administrator is a user to whom the role DnqERTemplateAdmin has been
assigned. That role authorizes a user to create and maintain message templates.
Creating and maintaining templates

The template administrator is able to create new message templates in the system.
He maintains existing templates to add or change values in fields of the template.
A new message template is created by selecting a template queue and pressing the
Create Template button. The following picture shows a template queue.
Figure 41. Template queue
The template queue will contain all templates for all message types which have
been created for this OU. In accordance with other queues, you can use the actions
listed in the actions column to work with the templates. Use the icon to view
a template in read-only mode. Press the button to open the template in edit
mode in order to change values within the template. A template can be deleted by
pressing the button.
Note: The description for a template can be used to describe the contents or use of
the template for the users of this template. To set the description, switch to
the context view and enter the text in the Comment area for the template.

Appendix A. Keyboard shortcuts
To make the window and functions easy to use, the following keyboard shortcuts
are available. Please note that the available shortcuts depend on the page or
function selected.
Note: Not all shortcuts might be available if a key combination is already assigned
to a different application running in your environment.
Table 7. Keyboard shortcuts
Shortcuts
Function Page
Firefox Internet Explorer
Alt + Shift + 1 Alt + 1 Display formatted view Message processing
Alt + Shift + 2 Alt + 2 Display unformatted view Message processing
Alt + Shift + 3 Alt + 3 Display context view Message processing
Alt + Shift + 4 Alt + 4 Display history view Message processing
Alt + Shift + v Alt + v Validate Message processing
Alt + Shift + s Alt + s Submit Message processing
Alt + Shift + 5 Alt + 5 Save as Draft Message processing
Alt + Shift + q Alt + q Quit Message processing
Alt + Shift + q Alt + q Return to Queue Selection Message list
List
Alt + Shift + a Alt + a Accept Message processing
Alt + Shift + r Alt + r Reject Message processing
Alt + Shift + r Alt + r Refresh Message list or Queue List
ALT-keydown ALT-keydown Expand/Collapse BIC entry Message processing
Alt + Shift + 1 Alt + 1 Create Message Message list - Draft
Alt + Shift + 1 Alt + 1 Direct Message Entry Message list - Create
Alt + Shift + T Alt + T Create Template Message list - Create
Alt + Shift + 1 Alt + 1 Create Message Message list - Draft
Alt + Shift + 2 Alt + 2 Create Template Message list - Template
| Alt + Shift + 5 Alt + 5 Move messages Message list
| Alt + Shift + 6 Alt + 6 Copy messages Message list
| Alt + Shift + 7 Alt + 7 Delete messages Message list
| Alt + Shift + 8 Alt + 8 Redirect messages Message list 1
| Alt + Shift + 8 Alt + 8 Undo redirect messages Message list 1
| Alt + Shift + 8 Alt + 8 Retry routing of messages Message list 1
| Alt + Shift + U Alt + U Unlock messages Message list
| Notes:
| 1. The shortcut key is shared between these functions because only one is visible at a time.

Appendix B. Icons
Symbol Definition
Code word list available
Wrong data entered into the preceding field
Create new occurrence
Delete a message
Collapsed segment
Expanded segment
Display a message
Edit a message
Message you locked
Unlock a message that is locked by someone else
Unlock message you locked
Copy a message
Move a message
Redirect a message
Undo redirect
Retry routing
Message processing status: Ok
Message processing status: Partial Ok
Message processing status: Failed

Appendix C. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Deutschland GmbH
Dept. M358
IBM-Allee 1
71139 Ehningen
Germany
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement
or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This document contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation, registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the web at “Copyright
and trademark information”:
http://www.ibm.com/legal/copytrade.shtml
Adobe is either a registered trademark or a trademark of Adobe Systems

Incorporated in the United States, and/or other countries.
Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Linux is a registered trademark of Linus Torwalds in the United States, other

countries or both.
Other company, product, and service names may be trademarks or service marks
of others.
Appendix C. Notices 51
Glossary of terms and abbreviations
The following terms and abbreviations are used bank identifier code (BIC). A code used to uniquely
in the WebSphere BI for FN customer identify a bank, logical terminal, or branch within a
documentation. SWIFT network. See also:
v BIC8
API. See application programming interface. v BIC9
v BIC12
APPC. Advanced Program-to-Program
Communication based on SNA LU 6.2 protocols. BIC. See bank identifier code.
application delivery notification. A delivery BIC8. An 8-character code used to uniquely identify a
notification that is passed to an application. Typically, financial institution within a SWIFT network. Also
an application delivery notification is based on a called a destination.
network delivery notification (for example, a FileAct
delivery notification), but has been modified in some BIC9. A 9-character code that consists of a destination
way by the service that exchanges data directly with (BIC8) plus a 1-character logical terminal code. A BIC9
the application. is used to uniquely identify an LT within a SWIFT
network. Also called an LT name.
application LT. An LT that is used by one or more
applications, but that is not used for LT sessions. BIC12. A 12-character identifier that consists of a
Logical Terminal Identifier (BIC9) plus a 3-character
application programming interface (API). An branch code. A BIC12 is used to uniquely identify a
interface that allows an application program that is branch within a SWIFT network.
written in a high-level language to use specific data or
functions of the operating system or another program. binary large object (BLOB). A data type used by
databases for large, non-text objects.
attribute. A property, quality, or characteristic whose
value contributes to the specification of an element or BLOB. See binary large object.
program function. For example, "cost" or "location" are
CCSID. See coded character set identifier.
attributes that can be assigned to a resource.
CDD. See customization definition document.
authentication. The security service that provides
proof that a user of a computer system is genuinely CDP. See Customization Definition Program.
who that person claims to be. Common mechanisms for
implementing this service are passwords and digital cleanup period. The time period during which a
signatures. Authentication is distinct from database record that has reached its final state or
authorization; authentication is not concerned with condition is to remain in the database. After the
granting or denying access to system resources. cleanup period expires for such a record, database
cleanup causes the record to be deleted from the
authenticator key. A set of alphanumeric characters database.
used for the authentication of a message sent via the
SWIFT network. CLI. See command line interface.
authorisation. A document that authorizes one client message. A message from a client application
destination to send FIN messages to or receive FIN that is to be sent via a network to its destination, or a
messages from another destination. message that is routed to a client application to
acknowledge the receipt of a client message by a
authorisation record. A database record used to store network.
the information that corresponds to an authorisation.
CO. See configuration object.
authorization. The process of granting a user, system,
or process either complete or restricted access to an COA. See confirm on arrival.
object, resource, or function.
COD. See confirm on delivery.
AV service-bundle set. Authentication and validation
service-bundle set. coded character set identifier (CCSID). The name of a
coded set of characters and their code point
assignments.

commit. An operation that applies all the changes servers, and which service bundles are assigned to each
made during the current unit of recovery or unit of server-OU combination), and to create the
work. After the operation is complete, a new unit of corresponding deployment data. (2) The information
recovery or unit of work begins. contained in a customization definition document,
which describes the layout of a WebSphere BI for FN
configuration administration. The administration of instance.
the configuration object types (CTs), configuration
objects (COs), and configuration object sets (COSs) that customization definition document (CDD). An XML
comprise the configuration data of organizational units document that describes the layout of a WebSphere BI
(OUs). This is carried out after the product has been for FN instance (that is, its OUs and servers, and which
installed and customized. See also security service bundles are assigned to each server-OU
administration. combination). The CDP uses a CDD to determine
which deployment data to produce for an instance.
configuration entity. WebSphere BI for FN entities
used to model an organization, and to specify how Customization Definition Program (CDP). A
messages are processed. These entities include WebSphere BI for FN program used to generate
configuration object types (CTs), organizational units deployment data based on information contained in a
(OUs), configuration object sets (COSs), configuration customization definition document (CDD). It also
objects (COs). generates reports that describe the resulting instance.
configuration object (CO). An instance of a customization definition report. A report, generated

configuration object type (CT) that represents an object by the CDP, that describes the servers, OUs, and
in an organizational unit (OU). Which attributes can be services of an instance, and how they are distributed
added to a CO is determined by the definition of the within the instance.
CT on which the CO is based.
customization deployment. Using the deployment
configuration object set (COS). A set of configuration data created during customization definition to create
objects, used to limit the scope of configuration data the resources required by your runtime systems.
provided to WebSphere BI for FN message flows.
daemon. A program that runs unattended to perform
configuration object type (CT). A description of the continuous or periodic system-wide functions, such as
class of configuration objects, including the attributes network control.
that each member of this class can have.
database cleanup. The act of deleting from a database
confirm-on-arrival (COA) report. A WebSphere MQ those records for which the cleanup period has expired.
report message type created when a message is placed
on that queue. It is created by the queue manager that datagram. A form of asynchronous messaging in
owns the destination queue. which an application sends a message, but does not
require a response.
confirm-on-delivery (COD) report. A WebSphere MQ
report message type created when an application DB2®. A family of IBM licensed programs for
retrieves a message from the queue in a way that relational database management.
causes the message to be deleted from the queue. It is
created by the queue manager. DBMS. Database management system.
correspondent. An institution to which your DBRM. Database request module.

institution sends and from which it receives messages.
dead-letter queue. A queue to which a queue
COS. See configuration object set. manager or application sends messages that it cannot
deliver. Also called undelivered-message queue.
csv file. Text file containing comma separated values,
that is, tabular values delimited by commas. delta deployment. Deployment of only that data that
is required to transform a current runtime environment
CT. See configuration object type. into a target runtime environment. Contrast with full
deployment.
current customization definition. A customization
definition that describes a WebSphere BI for FN deployment data. The resource files, generated during
instance for which the corresponding resources have customization, that are used to create the resources for
already been deployed and are running. an instance.
customization definition. (1) Using the Customization deployment data set. A data set containing the
Definition Program (CDP) to describe the layout of a resource files generated during customization.
WebSphere BI for FN instance (that is, its OUs and

deployment directory. The directory containing the File Transfer Adapter. A SWIFTAlliance Gateway
subdirectories and resource files created during (SAG) component that transfers files to or from the
customization. FileAct directory used by an SAG. Formerly called File
Transfer Agent.
deployment instructions. Instructions, generated by
the Customization Definition Program (CDP) during FileAct directory. A directory used exclusively to store
customization definition, that describe how to execute files involved in FileAct transfers.
the resource files, and thereby deploy, on the runtime
systems, the resources required by the instance. FIN. SWIFT's store-and-forward message-processing
service defining message standards and protocols. See
deployment vehicle. A job or other executable file that also SWIFTNet FIN.
is used to deploy resources. Each vehicle corresponds
to a particular resource file. FMT FIN. A term used to describe the group of
WebSphere BI for FN services used to transfer FIN
destination. See BIC8. messages internally, rather than via the SIPN. See
financial message transfer for FIN messages.
dual authorization. A setting requiring that an action
carried out by one person must be confirmed by a FSM. See finite state machine.
second person. This prevents a single person from
being able to carry out actions requiring a high level of FSM instance directory. A directory used by the FSM
security, for example, the distribution of funds or the to store temporary files, such as shared memory
granting of access rights. Contrast with single handles and trace files.
authorization.
FTA. See File Transfer Adapter.
dynamic mode. An operating mode of node
DniConfigProvider, in which this node accesses the FTP. See file transfer protocol.
configuration database tables to retrieve configuration
full deployment. Deployment of all the data required
data and store it in the message. A configuration object
to set up the resources for an entire instance. Contrast
set (COS) determines which data is to be retrieved. This
with delta deployment.
mode is enabled, if the 'DSN of Configuration DB'
property is filled in. GMT. See Greenwich Mean Time.
ESM. See External security manager. Greenwich Mean Time (GMT). The time at zero
degrees of longitude; informally equivalent to Universal
event. A unit of information that describes an error or
Coordinated Time (UTC).
warning, or that provides other information about a
particular situation. History. A data structure that is part of the WebSphere
BI for FN header of each WebSphere BI for FN request.
exception queue. A queue to which messages
It provides a view on the lifecycle of each request and
associated with certain exceptional conditions, such as
provides information about the most significant
errors, are routed.
processing steps. See History entry.
exception report. A WebSphere MQ report message
History entry. A History entry provides information
type that is created by a message channel agent when a
about a significant step in the processing of a
message is sent to another queue manager, but that
component (WebSphere BI for FN or customer). The
message cannot be delivered to the specified
History entries are ordered, and the most recent
destination queue.
History entry is the last History entry in the History.
Extensible Markup Language (XML). A standard See History.
metalanguage for defining markup languages that was
IAMS. Incoming Application Message Store.
derived from and is a subset of SGML.
Incoming Application Message Store. A message
external command. A command that causes the CLI to
store, implemented as the database table DNF_IAMS,
generate a WebSphere BI for FN message and send it to
in which messages received from remote applications
a service to be processed.
(OSN messages) are stored.
external security manager (ESM). A security product
initial CDD. A customization definition document
that is invoked by the System Authorization Facility.
(CDD) to which placeholders have not yet been added.
RACF® is an example of an ESM.
input node. A message flow node that represents a
source of messages for a message flow or subflow.
input queue. See service input queue.
Glossary of terms and abbreviations 55

input terminal node. A primitive through which a MER. See Message Entry and Repair facility.
message is received by a subflow. Each input terminal
node is represented as an input terminal of the message body. The part of the message that contains
corresponding subflow node. the message payload. See also message header.
instance. A set of servers that share a common message category. A group of messages that are
runtime database, plus their corresponding brokers and logically related within an application.
queue managers.
message channel. In WebSphere MQ, distributed
instance directory. See FSM instance directory. message queuing, a mechanism for moving messages
from one queue manager to another. A message
interface queue. See service interface queue. channel comprises two message channel agents (a
sender and a receiver) and a communication link.
intermediate CDD. A customization definition
document (CDD) to which placeholders have been message domain. A construct employed by
added, but for which placeholder values have not yet WebSphere BI for FN to categorize messages that share
been specified. the same message sets and other components.
internal command. A command that is processed Message Entry and Repair Facility. A WebSphere BI
directly by and that controls the CLI. for FN facility that lets users process financial
messages. Typical user actions are editing messages to
LAU. See local authentication. fix errors and authorizing messages for subsequent
processing.
large object (LOB). A data type used by databases for
large objects. message file. A file containing messages sent in bulk
via a message bulking service.
LOB. See large object.
message flow. A directed graph of message processing
local queue. In WebSphere MQ, a queue that belongs nodes that represents the set of actions performed on a
to a local queue manager. A local queue can contain a message when it is received and processed by a broker.
list of messages waiting to be processed. Contrast with Each node in a message flow represents a processing
remote queue. step, and the connectors in the flow determine which
processing steps are carried out, and in which order. A
local queue manager. In WebSphere MQ, the queue
message flow must include an input node to provide
manager to which the program is connected, and that
the source of the messages processed. A message flow
provides message queuing services to that program.
represents a process that can be executed by a broker
Queue managers to which a program is not connected
and therefore can be deployed. See also subflow.
are remote queue managers, even if they are running
on the same system as the program. message header. The part of a message that specifies
the sender and receiver of the message, the message
logical partition. A logical partition is made up of one
priority, and the type of message. See also message body.
or more physical partitions and their associated LOB
table spaces. Physical partitions belonging to the same Message Printing Service. The WebSphere BI for FN
logical partition span the same interval of time. automatic print service that sends essages to a printer
or to an output medium (for example, a file).
logical terminal. In SWIFT, the logical entity through
which users send and receive SWIFT messages. A message processing node. A node in a message flow
logical terminal is identified by its LT name. that represents a processing step. A message processing
node can be either a primitive or a subflow node.
logical terminal table. A MERVA table used to define
logical terminals, their synonyms, and other attributes. message processing unit. A message processing unit
is used to correlate information within a WebSphere BI
LT. See logical terminal.
for FN message (for example, reason or completion
LT code. The ninth character of an LT name. For information) and a WebSphere BI for FN message text.
example, the LT code of the LT name XXXXUSNYA is
message queue. See queue.
A.
MERVA for ESA. An IBM licensed program that is a
LT name. A nine-character name of the form
message queuing and routing system that allows a
BBBBCCLLX, where BBBBCCLL represents the
financial institution to process all kinds of financial
eight-character bank identifier code (BIC8), and X
messages.
represents the LT code. Also called a BIC9.
Message Reception Registry. The registry where
LTT. See logical terminal table.
SWIFT stores the central routing rules. Each receiver

defines its own rules and submits them to SWIFT. output terminal node. A primitive in a subflow that
SWIFT uses these rules to determine the destination of provides the means for messages to be propagated to
message traffic, that is, to which store-and-forward subsequent nodes of the message flow in which the
queue or to which SWIFTNet Link it is to route each subflow is embedded. Each output terminal node
message. corresponds to an output terminal on the subflow node
that corresponds to the subflow.
message warehouse table. A table in which the
message warehouse service stores index and status Outgoing Application Message Store. A message
information about each message processed by store, implemented as the database table DNF_OAMS,
WebSphere BI for FN services. in which messages sent by local applications (ISN
messages) and their acknowledgement messages (ISN
MPU. See message processing unit. ACKs) are stored.
MQHA. See MQSeries® Host Adapter. PDS. Partitioned data set.
MQSeries. See WebSphere MQ. placeholder. A variable that is replaced with a value.
For example, in the statement DSN SYSTEM(<DB2SSID>),
MQSeries Host Adapter (MQHA). SAG software that the variable <DB2SSID> (including the angle brackets) is
provides connectivity between the SAG and WebSphere a placeholder, and is replaced with the value you
MQ. require. If you require the value DSN1, after
replacement the statement looks like this: DSN
MRN. Message reference number.
SYSTEM(DSN1).
MRR. Message Reception Registry.
PKI. See public key infrastructure.
MSN. Message sequence number.
primary server. The server on which all resources that
MT. Message type. are to be deployed exactly once per instance or once
per OU are deployed.
MVS™. Multiple virtual storage.
primitive. A message processing node that cannot be
network delivery notification. A delivery notification further subdivided. See also subflow node.
received from a network. Contrast with application
delivery notification. private service bundle. A service bundle that is not
explicitly mentioned in the CDD, but that is included in
network identifier. A single character that is placed a service bundle set and provides resources required by
before a message type to indicate which network is to another service bundle. In a customization definition
be used to send the message; for example, S for SWIFT. report, private service bundles are listed, and their
names are followed by the string [private].
NFS. Network file system.
pseudo attribute. An attribute that cannot have a
node. See message processing node. value, and is used to indicate a binary state such as
yes/no or on/off. For example, the attribute local
OAMS. Outgoing Application Message Store. might be present for some resources and absent for
others, indicating whether the resource is local. Pseudo
OMVS. Open edition multiple virtual storage.
attributes are especially useful for implementing access
option. A parameter that determines how a message is rights (for example read, update, or delete).
to be processed.
public key infrastructure. A system of digital
option set. A named group of options and their certificates, certification authorities, and other
settings that can be specified in a request or in another registration authorities that verify and authenticate the
option set, thereby eliminating the need to specify each validity of each party involved in a network
option individually. transaction. See also SWIFTNet public key infrastructure
(SWIFTNet PKI).
organizational unit (OU). A body whose data is to be
kept separate from that of other, similar bodies. queue. A WebSphere MQ object. Message queuing
WebSphere BI for FN uses OUs to control access to applications can put messages on, and get messages
resources, and to ensure data segregation. Typically, from, a queue. A queue is owned and maintained by a
OUs are used to represent different financial queue manager.
institutions, or different departments within a financial
queue manager. A WebSphere MQ system program
institution.
that provides queuing services to applications. It
OU. See organizational unit. provides an application programming interface so that

programs can access messages on the queues that the resource class. An attribute of a resource that is used
queue manager owns. See also local queue manager and to group resources according to the subsystem to which
remote queue manager. they belong and the purpose for which they are used.
RACF. See Resource Access Control Facility. resource distribution report. A report that describes
the resources required by an instance.
RDU. Reference Data Utility. The RDU is a Java-based
command line tool. It can be used to create and update RM. See relationship management.
country, currency, and BICPlusIBAN data.
RM distribution file. A file used to exchange
real attribute. An attribute that must have a value relationship data with an RMA. In WebSphere BI for
(contrast with pseudo attribute). FN, it is the file that is created when you export
bootstrap authorisations, and it is the file from which
Reference Data Utility. See RDU. you import authorisations from an RMA.
remote queue. In WebSphere MQ, a queue that RMA. See relationship management application.
belongs to a remote queue manager. An application can
put a message into a remote queue, but cannot retrieve RMA authorisation. An authorisation that has been
a message from a remote queue. Contrast with local processed by an RMA.
queue.
RMDS. See Relationship Management Data Store.
remote queue manager. In WebSphere MQ, a queue
manager other than the queue manager to which the RM report. A report used to determine whether all
program is connected. the relationships that are required when using PV03
exclusively have already been recorded, and whether
relationship management application (RMA). An corresponding authorisations already exist.
application used to manage authorisations. Among
other things, it converts bootstrap authorisations role. A collection of access right that can be assigned
created by WebSphere BI for FN into the RMA to a user, group of users, system, service, or application
authorisations required to satisfy FIN PV03. that enable it to carry out certain tasks.
Relationship Management Data Store (RMDS). A set runtime environment. The runtime systems that
of database tables in which WebSphere BI for FN stores belong to a single WebSphere BI for FN instance.
data about bootstrap and RMA authorisations.
SAG. See SWIFT Alliance Gateway.
reply message. In WebSphere MQ, a type of message
used for replies to request messages. SAG MQ connection. An entity within an SAG that
encapsulates a WebSphere MQ connection.
reply queue. In WebSphere MQ, the name of a queue
to which the program that issued an MQPUT call SDF. Sequential Data Facility. A tool for FIN messages
wants a reply message or report message sent. to be the imported into and exported from WebSphere
BI for FN. It can be issued via command line or script.
ReplyToQueue. The name of the queue to be passed
to the WebSphere BI for FN functions that handle the Secure Internet Protocol Network. A SWIFT network
imported messages. based on the Internet Protocol (IP) and related
technologies.
report message. In WebSphere MQ, a type of message
that gives information about another message. A report security administration. The administration of roles
message usually indicates that the original message and the assignment of roles in conjunction with
cannot be processed for some reason. organizational units to users. See also configuration
administration.
request message. In WebSphere MQ, a type of
message used for requesting a reply from another security entity. WebSphere BI for FN entities used to
program. specify what a user is authorized to do. Security
entities include roles and users.
Resource Access Control Facility (RACF). An IBM
licensed program that provides access control by sequence number. A number assigned to each
identifying users to the system; verifying users of the message exchanged between two nodes. The number is
system; authorizing access to protected resources; increased by one for each successive message. It starts
logging detected, unauthorized attempts to enter the from zero each time a new session is established.
system; and logging detected accesses to protected
Sequential Data Facility. See SDF.
resources. RACF is included in OS/390® Security Server
and is also available as a separate program for the MVS
and VM environments.

server. In WebSphere BI for FN, a logical construct SSN. See session sequence number.
that corresponds to the component in a runtime
environment in which one or more WebSphere BI for subflow. A directed graph composed of message
FN services run. processing nodes and connectors that is designed to be
embedded in a message flow or in another subflow. A
server message. A message that is routed to a server subflow must include at least one input or output
application for processing, or a delivery notification terminal node. A subflow can be executed by a broker
that is routed to a client application to acknowledge the only as part of the message flow in which it is
receipt of a client message by its destination. embedded, and therefore cannot be deployed. See also
message flow.
service. A component that accepts as input a message,
and processes the message; for example, translates its subflow node. A message processing node that
payload into a different format, or routes it to one of represents a subflow.
several output queues. In WebSphere BI for FN, most
services are implemented as message flows or SVB. See service bundle.
primitives.
SWIFT or S.W.I.F.T. Society for Worldwide Interbank
service bundle. A set of services that logically belong Financial Telecommunication s.c.
together, for example, because they share resources
such as a status table or error processing queue. A SWIFT Alliance Gateway (SAG). A SWIFT interface
service bundle contains the definition files for all product extending SWIFTNet Link by additional
resources required to provide the services, for example services as profile based processing and offering a
definition files for message flows, queues, and database WebSphere MQ interface.
tables. A service bundle has a unique name in the
SWIFTNet FileAct. SWIFT's interactive
scope of a WebSphere BI for FN instance. A service
communication service supporting exchange of files
bundle must be assigned to an organizational unit and
between two applications.
loaded into a server before it is operational.
SWIFTNet FIN. SWIFT's service providing FIN access
service input queue. The queue from which a service
via the SIPN.
retrieves the messages it is to process. In WebSphere BI
for FN, this queue is implemented as a WebSphere MQ SWIFTNet FIN batching. Transporting more than one
local queue. FIN message within a single InterAct message.
service interface queue. The queue into which SWIFTNet InterAct. SWIFT's interactive
applications place messages that are to be processed by communication service supporting exchange of request
a service. In WebSphere BI for FN, each OU that uses a and response messages between two applications.
particular service has its own service interface queue,
and this queue is implemented as a WebSphere MQ SWIFTNet Link (SNL). SWIFT's mandatory software
alias queue. product to access all SWIFTNet services.
session sequence number. A sequentially incremented SWIFTNet public key infrastructure (SWIFTNet
10 byte identifier that is assigned to each request unit PKI). SWIFT's mandatory security software and
in an LT session. It is formed by concatenating the 4 hardware installed with SWIFTNet Link.
byte session number with a 6 byte sequence number.
SWIFTNet service applications. Applications that use
single authorization. A setting allowing an action to SWIFTNet services. Financial organizations such as
be carried out by a single person. Contrast with dual Continuous Linked Settlement (CLS) or the Global
authorization. Straight Through Processing Association (GSTPA) offer
such applications to financial institutions.
SIPN. See Secure Internet Protocol Network.
SWIFTNet service. SWIFT's IP-based communication
SIPN FIN. A term used to describe the group of services that run on the SIPN.
WebSphere BI for FN services used to transfer
individual FIN messages via the SIPN. SYSOU. System administration organizational unit.
SPUFI. SQL processor using file input. target CDD. A customization definition document
(CDD) to which placeholders have been added, and for
static mode. An operating mode of node which placeholder values have been specified. A target
DniConfigProvider, in which this node inserts CDD describes a particular target customization
environment data and values of its properties in the definition.
incoming message. This mode is enabled, if the 'DSN of
Configuration DB' property is empty. target customization definition. A customization
definition that describes a changed version of a current

customization definition. Each target customization
definition has a target CDD that describes it.
TCP/IP. See Transmission Control Protocol/Internet

Protocol.
Transmission Control Protocol/Internet Protocol

(TCP/IP). An industry-standard, nonproprietary set of
communications protocols that provide reliable
end-to-end connections between applications over
interconnected networks of different types.
T&T. See Test and Training.
undelivered-message queue. See dead-letter queue.
Universal Time Coordinated (UTC). The time at zero

degrees of longitude; informally equivalent to
Greenwich Mean Time (GMT).
UTC. See Universal Time Coordinated.
WebSphere BI for FN message. A WebSphere MQ

message that has a folder labeled ComIbmDni in the
MQRFH2 header. This folder provides the data that is
required by WebSphere BI for FN to process the
message.
WLM. Workload manager.
XML. See Extensible Markup Language.

Bibliography
v WebSphere MQ for AIX®: Quick Beginnings,
WebSphere BI for FN for z/OS GC34-6478
publications
v WebSphere BI for FN for z/OS: Concepts and DB2 publications
Components, SH12-6899
The most current versions of all DB2 publications
v WebSphere BI for FN for z/OS: Planning,
are available from the following websites:
Installation, and Customization, SH12-6900
v DB2 V8 for z/OS®:
v WebSphere BI for FN for z/OS: System
Administration, SH12-6901 http://www.ibm.com/software/data/db2/zos/
v8books.html
v WebSphere BI for FN for z/OS: Application
Programming, SH12-6902 v DB2 V9 for z/OS:
v WebSphere BI for FN for z/OS: Messages and http://www.ibm.com/software/data/db2/zos/
Codes, SH12-6903 v9books.html
v WebSphere BI for FN for z/OS: Message Entry and
Repair Facility User's Guide, SH12-6904 WebSphere Application Server
v WebSphere BI for FN for z/OS: Program Directory, webcasts and publications
GI19-0044
v Webcast IBM WebSphere Application Server and
v WebSphere BI for FN for z/OS Base Product: 64-bit platforms: 64-bit Performance Demystified,
License Information, GH12-6898 which can be downloaded from:
http://www.ibm.com/support/
The most current editions of these publications
docview.wss?rs=180&context=SSEQTP
are available from the WebSphere Business
&uid=swg27012455
Integration for Financial Networks library
website: v WebSphere Application Server Version 6: System
Management and Configuration Handbook, which
http://www.ibm.com/software/integration/ can be downloaded from:
wbifn/library/ http://www.redbooks.ibm.com/abstracts/
sg246451.html?Open
WebSphere MQ publications v WebSphere Application Server Network Deployment
Version 6: High Availability Solutions, which can
v WebSphere MQ: Application Programming Guide,
be downloaded from:
SC34-6064
http://www.redbooks.ibm.com/abstracts/
v WebSphere MQ: Application Programming
sg246688.html?Open
Reference, SC34-6062
v WebSphere MQ: Command Reference, SC33-1369
MERVA ESA publications
v WebSphere MQ: Queue Manager Clusters,
SC34-6061 v MERVA for ESA Version 4: Concepts and
Components, SH12-6381
v WebSphere MQ: Messages, GC34-6057
v MERVA for ESA Version 4: Customization Guide,
v WebSphere MQ: System Administration Guide,
SH12-6380
SC34-6068
v MERVA for ESA Version 4: Diagnosis Guide,
v WebSphere MQ for z/OS: System Setup Guide,
SH12-6382
SC34-6052
v MERVA for ESA Version 4: Macro Reference,
v WebSphere MQ: Using C++, SC34-6067
SH12-6377
v WebSphere MQ for Windows: Quick Beginnings,
v MERVA for ESA Version 4: Messages and Codes,
GC34-6476
SH12-6379
v WebSphere MQ for Solaris: Quick Beginnings,
GC34-6477

v MERVA for ESA Version 4: Operations Guide, v SWIFTNet Service Design Guide
SH12-6375 v SWIFTNet FIN Planning Guide
v MERVA for ESA Version 4: User's Guide, v SWIFTNet Messaging Operations Guide
SH12-6376
v SWIFTNet Naming and Addressing Guide
The most current editions of these publications v SWIFTNet FIN Vendor Specifications
are available from the IBM MERVA library v SWIFTNet RMA Service: RMA Planning Guide
website: v SWIFTNet FileAct: Using the Enhanced Header
v SWIFTNet Messaging Operations Guide
http://www.ibm.com/software/solutions/
finance/merva/library/ v SWIFTNet Link: Installation and Administration
Guide
v SWIFTNet Link: Installation and Administration
Other IBM publications Guide for UNIX Systems
v UNIX System Services: Planning, SC28-1890 v SWIFTNet Link: Interface Specification
v z/OS MVS Planning: Workload Management, v SWIFTNet Link: Error Codes
SA22-7602
v z/OS Security Server (RACF): Command Language
Reference, SA22-7687
v z/OS C/C++ Programming Guide, SC09-4765
v z/OS MVS Initialization and Tuning Reference,
SA22-7592
v z/OS TSO/E Command Reference, SA22-7782
v z/OS MVS Programming: Authorized Assembler
Services Guide, SA22-7608
v z/OS Language Environment® Run-Time Messages,
SA22-7566
You can order many IBM publications, such as

product manuals and IBM Redbooks®, online at
the following website:
http://www.elink.ibmlink.ibm.com/public/
applications/publications/cgibin/pbi.cgi
SWIFT publications
v SWIFT User Handbook
v SWIFT FIN Error Codes
v SWIFT FIN Copy Service Description
v SWIFTAlliance Gateway: Operations Guide
v SWIFTAlliance Gateway: Error Guide
v SWIFTAlliance Gateway: Installation Guide
v SWIFTAlliance Gateway: Developer Guide
v SWIFTAlliance Gateway: File Transfer Interface
Guide
v SWIFTAlliance Gateway: MQ Host Adapter
Configuration Guide
v SWIFTAlliance Gateway: Developers Toolkit
Installation Guide
v SWIFTNet Certificate Administration Guide

Index
A F messages (continued)
routing 41
action fields, Header 32 templates 43
accept 22 FIN message unlocking 37, 40
quit 22 authorizing 35 Messages 6
reject 22 creating 27 Draft 6
save as draft 22 editing 33 Template 6
submit 22 redirecting 34 moving a message 40
validate 22 retyping values 36 MSIF 20
Actions 24 Funds message
address, BIC 10 creating 30
API 53
Application Server, WebSphere 1 N
authorizing a SWIFTNet FIN
message 35
H Network
Network
code 18
string 18
Header fields 32 Network type 18
Notices 49
B I
backout queue 41
BIC address 10
InterAct O
application header 20 occurrence 9
browser v, 1, 13
Operation 15
organizational unit 5
C K organizational units 13
keyboard shortcuts 45 OU 5, 13
collapse 9, 10
Concept 3
context view
comment 20 L P
General 17 lists, message 24 print 23
header fields 20 log on 1 Purpose 14
copying a message 39
create message 26
create template 26 M Q
creating a SWIFTNet FIN message 27 queue
message
creating a SWIFTNet Funds message 30 list 5
authorizing 35
copying 39 Queue 14
creating 27, 30 queue, backout 41
D editing 33 queues 13
Data entry 7 entering data 7 Queues 4
code words 7 message-processing page 15 Purpose 4
expanding sections 9 moving 40 Types 5
message fields 7 redirecting 34
options 8 relaying 37
sections 9 retyping values 36 R
deleting a message 39 templates 29 redirecting a SWIFTNet FIN message 34
DNIENI 2 viewing 32 refresh 14
DNIFIN 2 message administrator relaying a message 37
DNIFUNDS 2 tasks 39 Repeatable sequence 9
DNISNSYS 2 Message definition set 18 RETYPE 16
DNIUNPARSABLE 33 Message domain 25 retyping values in a SWIFTNet FIN
Domain, Message 25 message fields message 36
entering data 7
Message ID 15
E message lists 24
Message Management S
editing a SWIFTNet FIN message 33 sequence, Repeatable 9
message editor 27
Entry and Repair Server, WebSphere Application 1
message processing 15
working with 1 SWIFTNet FIN message
Message type 15
Entry and Repair page 13 authorizing 35
messages
entry, Data 7 creating 27
deleting 39
expand 9, 10

SWIFTNet FIN message (continued)
editing 33
redirecting 34
retyping values 36
SWIFTNet Funds message
creating 30
T
template administrator
tasks 43
type, Message 15
U
unit, organizational 5
units, organizational 13
unlocking a message 37, 40
using templates 29
V
viewing a message 32
Views 15
context view 17
formatted view 16
History view 21
unformatted view 16
W
WebSphere Application Server 1

Readers’ Comments — We'd Like to Hear from You
for z/OS
User's Guide
Version 3 Release 1
Publication No. SH12-6904-06
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, your
IBM business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use
the personal information that you supply to contact you about the issues that you state on this form.
Comments:
Thank you for your support.

Submit your comments using one of these channels:
v Send your comments to the address on the reverse side of this form.
v Send a fax to the following number: +49-7031-164880
v Send your comments via email to: swsdid@de.ibm.com
If you would like a response from IBM, please fill in the following information:
Name Address
Company or Organization
Phone No. Email address

___________________________________________________________________________________________________
Readers’ Comments — We'd Like to Hear from You Cut or Fold
SH12-6904-06 Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ do
_ _ not
_ _ _staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
PLACE
POSTAGE
STAMP
HERE
IBM Deutschland Research & Development GmbH

User Experience & Information Development
Schoenaicher Strasse 220
71032 Boeblingen
Germany
________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
SH12-6904-06 Along Line

Program Number: 5655-FIN
SH12-6904-06

Message Entry and Repair Facility Use

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Message Entry and Repair Facility Use

Diunggah oleh

Hak Cipta:

Format Tersedia

WebSphere Business Integration for Financial Networks

for z/OS

Message Entry and Repair Facility

Message Entry and Repair Facility

© Copyright IBM Corp. 2009, 2010 iii

How to send your comments

Enhancements to WebSphere BI for FN Version 3 Release 1 (August 2010):

© Copyright IBM Corp. 2009, 2010 v

Enhancements to WebSphere BI for FN Version 3 Release 1 (June 2010):

vi WebSphere BI for FN for z/OS: MER Facility: User's Guide

Enhancements to WebSphere BI for FN Version 3 Release 1 (April 2010):

Enhancements to WebSphere BI for FN Version 3 Release 1 (December 2009):

About this document vii

viii WebSphere BI for FN for z/OS: MER Facility: User's Guide

Enhancements to WebSphere BI for FN Version 3 Release 1 (August 2009):

Enhancements compared to WebSphere BI for FN Version 2 Release 2:

About this document ix

x WebSphere BI for FN for z/OS: MER Facility: User's Guide

Figure 1. Home Page

© Copyright IBM Corp. 2009, 2010 1

The Message Management feature of WebSphere BI for FN currently supports the

Further messages standards or updated versions may be provided at a later time.

2 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Redirect Backout Draft

Figure 2. Concept - Example queue and routing setup

Chapter 1. Working with the Message Entry and Repair Facility 3

The following queue purposes are available:

Display queues are similar to authorize queues, that is, the

4 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Chapter 1. Working with the Message Entry and Repair Facility 5

Messages in draft queues cannot be redirected or copied.

6 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Entering data in message fields

Figure 3. Entry fields example

Figure 4. Disabled/read-only fields

Selecting a code word

Chapter 1. Working with the Message Entry and Repair Facility 7

Figure 6. Choose an option

Figure 7. New fields displayed - Option A

8 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Figure 8. New fields displayed - Option B

Figure 9. Display of a section (expanded)

Chapter 1. Working with the Message Entry and Repair Facility 9

To delete an occurrence, press its symbol.

Figure 11. Display of more than one occurrence

BIC address information

A BIC address field operates in two modes:

10 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Figure 13. Collapsed BIC address

Mode 2 - Address search

Figure 14. Search for a BIC address

Chapter 1. Working with the Message Entry and Repair Facility 11

Figure 15. Reload indication for conditional sections

12 WebSphere BI for FN for z/OS: MER Facility: User's Guide

Message Entry and Repair page

Figure 16. OU and queues list

© Copyright IBM Corp. 2009, 2010 13

The queues list contains the following elements:

14 WebSphere BI for FN for z/OS: MER Facility: User's Guide

View tabs Message type Operation

Action buttons MessageID

Figure 17. Page structure

Chapter 2. User Interface components 15

Figure 18. Formatted view of a message