BMS map
The definition of a CICS screen: where each field sits, how long it is and how it looks.
Also written BMS, map, mapset
Why it matters. Every online screen the bank's staff use is a map. The program fills the fields, and CICS draws them.
See it
DFHMSD starts the map set. The label ZBMAPS is its name.
Syntax
EXEC CICS SEND MAP(name) MAPSET(name) FROM(area) [ERASE] [CURSOR] END-EXEC EXEC CICS RECEIVE MAP(name) MAPSET(name) INTO(area) END-EXEC
- MAP
- The map to use.
- MAPSET
- The group of maps it belongs to.
- FROM / INTO
- The program's symbolic map area.
- ERASE
- Clear the screen first.
- CURSOR
- Where to put the cursor.
- DATAONLY
- Send only the changed data, not the labels.
- MAPONLY
- Send the labels, with no data.
Try it XFER
- 1
You're at the CICS menu, signed on as TELLER1. Open the funds transfer screen.
CICS XFER - 2
Go back to the menu with PF3, and send 50 from ACCT0001 to ACCT0099, an account that does not exist. Use the one-line shortcut.
CICS XFER ACCT0001 ACCT0099 50
Remember
- A map is the layout of one screen: labels, fields and a message line.
- Each field has a position and a length.
- The program sends data to the map. CICS draws the screen.
The usual mistake
Typing a new transaction code while a map is on screen
What you type goes into the fields of the map, not into CICS.
Clear the screen first (PF3 to the menu in MF/OS), then type the code
On real z/OS
Real maps are written in BMS macros, assembled and installed. MF/OS defines its maps in code, with a small field model. The XFER, BALN and other bank screens and their messages (such as XFER3203) belong to ZedBank, not to IBM.
Where can I practise BMS map?
Right here, at ZedBank. You take a junior job at a simulated bank and use BMS map in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- CICSThe transaction manager that runs online mainframe applications, and the software behind a great many screens bank staff use.
- Green screenThe text-only, keyboard-driven interface most mainframe work happens through, named after the green phosphor of early terminals.
- 3270 terminalThe classic mainframe display device, and the protocol still used today to talk to z/OS over a network.
- CopybookA shared block of COBOL declarations kept in a library and included into programs, so a record layout is defined once.
- CICS transactionOne unit of online work in CICS: the whole exchange of receiving a request, doing the work, and sending a response.