IMPORTING DATA INTO GLOBUS
Objectives


To understand the working of the TAKEOVER.MAPPING application in Globus that helps
importing data into Globus from a flat file
To understand the working of the EBS.AUTO.FUNCTION application in Globus that helps in
automatic commit/authorization of records in Globus
1.1 Introduction
GLOBUS gives the facility of importing data from DOS fixed length text files into the
GLOBUS database as an unauthorized stage easily. However, this facility should be handled with
caution because it requires precision in defining the correct structure of the record in GLOBUS data
tables.
2.1 The TAKEOVER.MAPPING Application
The TAKEOVER.MAPPING application is designed to load data from a sequential
(flat) file into the required GLOBUS format. Records are loaded as IHLD. The records can then be
input and authorised, to ensure that the data validates through the GLOBUS application. The utility
EBS.AUTO.FUNCTION (described in the next section) can be used to input and authorize the
records, to automate the input and authorisation process. The TAKEOVER.MAPPING record defines
the location of the flat file, and the mapping of the data.
3.1 Steps To Import Data Into Globus Using TakeOver Mapping
Example 1
Import 3 records into the CUSTOMER application in GLOBUS using TAKEOVER.MAPPING
application
Solution 1
Step1: Note
Note down the names of fields of the application whose data needs to be imported
into Globus . All the mandatory fields of the application whose data needs to be imported (In this case
the CUSTOMER application) needs to be included.
Mandatory fields of the CUSTOMER application
Id
Mnemonic
Short Name
GB Name.1
Street
Sector
Account Officer
Industry
Target
Nationality
Customer Status
Residence
Language
Temenos Training Publications
1
Step 2
Create the flat file (with extension .txt – In this example the file name used is cust.txt )
which will contain data for the above mentioned fields. Note the length of each field and create a text
file having fixed length fields, thus having a fixed length record. Use any editor to do this. e.g.,
Notepad,WordPad(Windows) or vi(Unix).It is mandatory to have fixed length records in order to import
data in Globus using the TAKEOVER.MAPPING application.
Field name
Id
Mnemonic
Short Name
GB Name.1
Street
Sector
Ac Off
Industry
Target
Nationality
Customer Status
Residence
Language
No Of Char
6
4
4
5
4
4
1
4
3
2
1
2
1
Starting Position
1
7
11
15
20
24
28
29
33
36
38
39
41
Ending Position
6
10
14
19
23
27
28
32
35
37
38
40
41
Figure 2.1 Field Names, Length, Starting And Ending Positions
100010CUS1CUS1CUS01STR1100011000999IN1IN1
100011CUS2CUS2CUS02STR2100011000999IN1IN1
100012CUS3CUS3CUS03STR3100011000999IN1IN1
Figure 3.1 Flat File cust.txt with the 3 customer records
Note :
Step2: Create a non-hashed file from Universe or use an already existing one, to act as a directory in
Not all the times, can one field have same length values across all records. In the above
Not alUNIX in Order to store the DOS text file into it.
example, the field Street , across 3 records has vales that are 4 characters long. This might not be the
case always. Assume the field Street has values like
Step3: Import the DOS text file to UNIX (FTP, Reflection Transfer File…) into the location:
/data/globus/test/test.run/TEXT.FILE/
CNC ROAD
e.g.: /data/globus/test/test.run/TEXT.FILE/category.txt
FIRST STREET
LAKEVIEW ROAD
Note down the length of the longest value(14) and create the records as below
100010CUS1CUS1CUS01CNC ROAD
100011000999IN1IN1
100011CUS2CUS2CUS02FIRST STREET 100011000999IN1IN1
100012CUS3CUS3CUS03LAKE VIEW ROAD100011000999IN1IN1
Values for the field Street. All 14 characters long.(Note the trailing
spaces for the values “CNC ROAD” and “FIRST STREET”.)
Type the values for the fields as usual, except that when typing the values for the field Street, type in
the values(Values that are lesser than 14 characters long) followed by spaces so that it is 14
characters long , thus resulting in a fixed length record.
Temenos Training Publications
2
Step 3
Create a non-hashed file in jBase that will hold the text file that has just been created.
CREATE.FILE CUST.TRY TYPE=UD
Figure 4.1 Creation Of Non-Hashed File In jBase
Step 4
Transfer the text file(cust.txt) into the non-hashed file(CUST.TRY) just created.
Use
1. Start -> Programs -> Reflection -> FTP Client if the operating system is windows and transfer the
file created to the directory.
(or)
2. If the operating system is Unix
Use the Unix ‘cp’ command to copy the file from the source directory to the new non-hashed file that
you have just created.
Step5
Change all the permissions to the imported file:
$cd /data/globus/test/test.run/CUST.TRY
$chmod 777 cust.txt
$chgrp GroupName cust.txt
$chown OwnerName cust.txt
Step6
Make sure the text file is under the directory that you have created using the following
command.
jsh…> LIST CUST.TRY
The name of the text file (cust.txt) copied should appear in the displayed list.
Figure 5.1 Contents Of CUST.TXT Directory
Temenos Training Publications
3
Step 7
The next step is to define the DOS text file record structure in the
TAKEOVER.MAPPING application.
Figure 6.1 The TAKOVER.MAPPING record To Import Customer Records
Field 1 SOURCE DIRECTORY
Contains the name of the directory where the text file that
needs to be imported is present.
Field 2 SOURCE FILE
Contains the name of the text file that needs to be imported.
Field 3 NO TO PROCESS
Contains the number of records that need to be processed
from the text file mentioned in field 2. Usually the value
supplied is ‘ALL’. You could also supply an integer.
Field 4 ALLOW NOINPUT
Whether or not data is permitted in NOINPUT fields. If "Y"
then data in a NOINPUT field will not be treated as an error.
Temenos Training Publications
4
Field 5 UPDATE FILES
Whether or not to update the Globus data files. When data is
initially loaded, a test on portion of the file may be preferred
with this field set to "N", in order to view the error report.
If "Y" then the record will be loaded as unauthorised.
Field 6 PRINT ERROR REPORT
Whether or not to print the error report.
Valid values – ‘Y’ and ‘N’
Field 7 BLOCK SIZE
The logical record size of the sequential (flat) file.
The user needs to calculate the size of one record, add one
to the total size and specify it here. In the above example,
records end at position 41. Therefore the BLOCK SIZE is
42(41+1).
Field 8 OFFSET BASE
File Layout can be relative to 0 or 1. Usually set to 1
Field 9 RECORDS PRE EXIST
This field defines whether or not the records being loaded
should already exist in Globus. The possible values being:
Y - record must already exist.
N - record must not already exists.
M - record may or may not already exist (Usually set to M)
Field 13
Field 14
Field 15
Field 16
Field 17
Associated multi value set to define the various fields that
need to be imported. If the field to be imported is a muliti
value field or a sub value field then the Globus multi value
number or the sub value number needs to be specified in
field 16 and 17. The Globus field number of the field that
needs to be imported, the starting position and the length of
the field (Already noted – Refer Figure 2.1) need to be
specified in field 13,14 and 15 respectively.
FIELD NO
INPUT POSITION
INPUT LENGTH
MULTI VALUE
SUB VALUE
Step 8
The next step is the actually import the data into Globus. To do so, the record in the
TAKEOVER.MAPPING application needs to be verified. Once verified, the records will update the
respective file in the INAU status. Then it is our responsibility to authorize them.
Once verified, Globus will prompt the following message
“Continue with file update (Y/N)?”
Supply the value ‘Y’ so that Globus files get updated. If you wish to terminate the process, supply the
value ‘N’
Once the value ‘Y’ is supplied to the above question, Globus will display the following message
Completed. Records processed = 3, updated = 3 - RETURN when ready
Once the above mentioned message appears with thr correct number of records as in the text file, it
denotes that the takeover is complete. Now go to the customer application and check if the records
are in the IHLD status.
The Id of the record is the Name of the Globus Application which is being mapped with an optional
numeric suffix.
4.1 EBS.AUTO.FUNCTION
We were able to import data into Globus using the TAKEOVER.MAPPING
application. As you would be aware by now, the records imported using the TAKEOVER.MAPPING
application would be in IHLD status. It is our responsibility to get them to the INAU status and then
Temenos Training Publications
5
authorize them. This task of authorising records can be automated using the EBS.AUTO.FUNCTION
application. This application allows you to manipulate group of records through series of keystrokes
including function keys. Recording a macro is done through the application EBS.AUTO.FUNCTION.
The macro facility should be used with cautions, since the user might not be aware of the warning
message.
Example 2
Commit and authorize the 5 customer records that have been imported into Globus
using the TAKEOVER.MAPPING application.
Solution 2
Step 1
Input a record in the EBS.AUTO.FUNCTION application. The ID of the record has to
be the name of the application whose records we wish to authorize.
A sequence number is appended to the file name, thus allowing different auto
functions to be set up per file.
Figure 7.1 EBS.AUTO.FUNCTION Record For Committing Customer Records
Field 1 SELECTION
Used to specify the selection criteria that will be used to pick up the
necessary records for processing.
Field 2 FUNCTION
The function that needs to be used to commit/authorize the records.
In this example, we need to send the records to the INAU status from
IHLD. In order to do that we need to specify the function as ‘I’.
Field 3 SAMPLE SIZE
The number of records that need to be processed,
Field 4 INPUT BUFFER
The sequence of actions that need to be automated in order to
commit/authorize the records.
Note:
In order to know the sequence of actions that are required to be input to
commit/authorize a record, manually commit/authorize a record that has been imported into Globus.
Note down the actions and then map them on to the field INPUT BUFFER in the
EBS.AUTO.FUNCTION application. If there are records that require different sets of key strokes
that we cannot automate the committing/authorizing process suing the EBS.AUTO.FUNCTIUON
application.
Temenos Training Publications
6
Note :
Field 6 : File Suffix
This field by default refers to the unauthorized file of the application for which EBS.AUTO.FUNCTION is being
used. (ie) The file suffix is always set to $NAU unless specified ‘NO’ in this field. If ‘NO’ is specified in this
field, then records will be picked up from the live file. In such a case, Field 1(Selection) should contain a valid
selection like “WITH INPUTTER LIKE …TRAINEE…” etc
Step 2
Verify the record input in the EBS.AUTO.FUNCTION application, to invoke the actual
committing process. Once verified, you will see the following message
3 RECORDS SELECTED;.F4=PAUSE; CONTINUE (Y/NO)
The above message denotes that the automated process is complete. Now check to see if the
customer records are in INAU status.
Note :
In order to authorize the records, a record in the EBS.AUTO.FUNCTION
application needs to be created in the following way
In order to know the sequence of actions that need to be automated to authorize a record, as
mentioned earlier, we need to manually authorize a record, note down the actions and then
map them to the INPUT BUFFER field.
Summary




TAKOVER.MAPPING is an application is Globus which allows importing of data into Globus
from a flat file
The flat file needs to contain records of fixed length so that TAKEOVER.MAPPING can import
them into Globus
All records that are imported into Globus using the TAKEOVER.MAPPING are imported in the
IHLD status only.
EBS.AUTO.FUNCTION application is used to commit/authorise records automatically
provided all records are of the same type(They are require the same type and number of key
strokes).
Temenos Training Publications
7