Features¶

Provides the following command line utilities:

• paramconv: Utility for working with MasterCard MPE parameter extract files
• mideu: Utility for working with MasterCard IPM files

paramconv - Convert MPE parameter extract files¶

Use this tool if you are moving between a mainframe and PC based clearing application and need the parameter files available on both platforms. The app currently works exclusively with 1014 blocked file format which is used for communications between MasterCard and the member.

Most simple usage, just provide a MasterCard MPE file to convert:

paramconv <inputfile>

This runs with the following assumptions

• Input file format is EBCDIC
• Output file is the input file plus a ‘.out’ extension

If you have a ASCII file and want to convert it to EBCDIC, you need to provide the source format type:

paramconv -s ascii <inputfile>

You can change the output file location:

paramconv -o <outputfile> <inputfile>

To get all the usage details:

paramconv --help

mideu - MasterCard IPM file tool¶

This utility is for working with MasterCard IPM clearing files. Currently the utility provides the following functions:

• extract - provide IPM transaction data in usable format
• convert - convert IPM files between ASCII and EBCDIC encoding

mideu extract <filename>

mideu extract -s ascii <filename>

mideu extract <inputfile> --csvoutputfile <outputfile>

mideu extract <inputfile> --mongohost localhost --mongodb testdb

mideu extract --help

mideu convert <inputfile>

mideu convert -s ascii <inputfile>

mideu convert --help

output_data_elements:
    - MTI
    - DE1
    - DE10
    - PDS0023
    - DE43_NAME

bit_config:
    1:
        field_name: Bitmap secondary
        field_type: FIXED
        field_length: 8
    2:
        field_name: PAN
        field_type: LLVAR
        field_length: 0
        field_processor: PAN

mongo_config:
    host: 192.168.99.100:27017
    db: test

1014 blocked file format¶

This is the format used to send and receive files from MasterCard.

All file consists of records. Each record is prefixed with a 4 byte binary length. There are no carriage returns or line feeds in the file. Before sending, the contents is blocked into lengths of 1012, and an additional 2 x‘40’ characters are appended at each block. Finally, the total file length is made a multiple of 1014 with the final incomplete record being filled with the x‘40’ character

Say you had a file with the following 2 records:

"This is first record 1234567"  <- length 28
"This is second record AAAABBBBB123"  <- length 34

Add binary length to the start of each record. (x‘1C’ = 28, x‘22’ = 34)

00000000: 00 00 00 1C 54 68 69 73  20 69 73 20 66 69 72 73  ....This is firs
00000010: 74 20 72 65 63 6F 72 64  20 31 32 33 34 35 36 37  t record 1234567
00000020: 00 00 00 22 54 68 69 73  20 69 73 20 73 65 63 6F  ..."This is seco
00000030: 6E 64 20 72 65 63 6F 72  64 20 41 41 41 41 42 42  nd record AAAABB
00000040: 42 42 42 31 32 33                                 BBB123

Block to 1014 by adding 2 * x‘40’ characters every 1012 characters in the data. Finally fill with x‘40’ characters to next 1014 increment. In this case, there is only one increment:

00000000: 00 00 00 1C 54 68 69 73  20 69 73 20 66 69 72 73  ....This is firs
00000010: 74 20 72 65 63 6F 72 64  20 31 32 33 34 35 36 37  t record 1234567
00000020: 00 00 00 22 54 68 69 73  20 69 73 20 73 65 63 6F  ..."This is seco
00000030: 6E 64 20 72 65 63 6F 72  64 20 41 41 41 41 42 42  nd record AAAABB
00000040: 42 42 42 31 32 33 40 40  40 40 40 40 40 40 40 40  BBB123@@@@@@@@@@
00000050: 40 40 40 40 40 40 40 40  40 40 40 40 40 40 40 40  @@@@@@@@@@@@@@@@
... all X'40' characters
000003E0: 40 40 40 40 40 40 40 40  40 40 40 40 40 40 40 40  @@@@@@@@@@@@@@@@
000003F0: 40 40 40 40 40 40                                 @@@@@@

mciutil package¶

To use Mastercard file utilities in a project:

import mciutil

There are some useful functions for working with bitmap, variable length files. Will document in a future version.

Types of Contributions¶

Get Started!¶

Ready to contribute? Here’s how to set up mciutil for local development.

1. Fork the mciutil repo on GitHub.

2. Clone your fork locally:

   $ git clone git@github.com:your_name_here/mciutil.git
   

3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:

   $ mkvirtualenv mciutil
   $ cd mciutil/
   $ python setup.py develop
   

4. Create a branch for local development:

   $ git checkout -b name-of-your-bugfix-or-feature
   

   Now you can make your changes locally.

5. When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:

   $ flake8 mciutil tests
   $ python setup.py test
   $ tox
   

   To get flake8 and tox, just pip install them into your virtualenv.

6. Commit your changes and push your branch to GitHub:

   $ git add .
   $ git commit -m "Your detailed description of your changes."
   $ git push origin name-of-your-bugfix-or-feature
   

7. Submit a pull request through the GitHub website.

Pull Request Guidelines¶

Before you submit a pull request, check that it meets these guidelines:

1. The pull request should include tests.
2. If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
3. The pull request should work for Python 2.7, 3.4, and 3.5, and for PyPy. Check https://travis-ci.org/adelosa/mciutil/pull_requests and make sure that the tests pass for all supported Python versions.

Tips¶

To run a subset of tests:

$ python -m unittest tests.test_mciutil

Development Lead¶

• Anthony Delosa <adelosa@gmail.com>

Contributors¶

None yet. Why not be the first?

0.4.2 (2016-03-13)¶

• Complete data elements added to default config.
• Added versioneer support for easier package versions

0.4.1 (2015-12-16)¶

• Additional data elements added to default config file.

0.4.0 (2015-10-05)¶

• Now supporting python 2.6 (for all those still using RHEL 6)
• Headers rows in mideu csv extracts don’t work in 2.6

0.3.0 (2015-10-03)¶

• added sub commands for mideu
• mideu now supports IPM encoding conversion between ascii and ebcdic
• Now faster using list comps instead of slow loops

0.2.0 (2015-08-28)¶

• Support for config override for mideu - see usage doco
• Progress bar while using mideu.. it takes a while
• Now supports python 3.4, 3.5 and 2.7. Upgrade if you are using 2.6
• New usage documentation

0.1.0 (2015-08-20)¶

• First release.