CICS transaction
One piece of online work: a request comes in, the work is done, and the answer goes back.
Also written transaction
Why it matters. A funds transfer is one transaction. Its two account changes are made permanent together, or neither is.
See it
RECEIVE MAP reads what the user typed on the screen.
Try it XFER
- 1
At the menu, move 250 from ACCT0001 to ACCT0002. Use the one-line shortcut.
CICS XFER ACCT0001 ACCT0002 250 - 2
Confirm the transfer. On the real screen you press Enter. Here, type CONFIRM.
CICS CONFIRM
Remember
- A transaction is one whole piece of work, from request to answer.
- A transfer changes two accounts together, or not at all.
- The reference on the reply is how you find the transfer later.
The usual mistake
Sending the same transfer again to check that it worked
Each transfer that completes is a new transfer. The money moves twice.
Look at BALN or TRAN to check the result
On real z/OS
The XFER, BALN and other screens are ZedBank's own sample application, and so are their messages. MF/OS doesn't model CICS task dispatching, syncpoint logging or recovery.
Where can I practise CICS transaction?
Right here, at ZedBank. You take a junior job at a simulated bank and use CICS transaction 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.
- Transaction IDA four-character code that tells CICS which program to run, typed on the screen or triggered by a key.
- Pseudo-conversationalThe CICS programming style where a program ends after sending each screen, rather than waiting for the user to reply.
- Commit and rollbackMaking a set of changes permanent together, or undoing them together, so a transaction never half-happens.
- Online transaction processingHandling many small pieces of work in real time while someone waits: a card payment, a balance check, a seat booking.