LPAR
One real mainframe split into several separate computers, each with its own system.
Also written logical partition
Why it matters. ZedBank keeps its live work on ZBPROD, apart from DEV and TEST on ZBANK. All of it runs on the same machine.
See it
Inside the machine
Tap a flat, the floor under it, or the machine.
Three flats, one building. Pick any part.
Try it D SYMBOLS
- 1
Open SDSF, the screen where you watch jobs and send operator commands.
SDSF - 2
In SDSF, find out which system you are on right now.
COMMAND INPUT ===> /D SYMBOLS - 3
Now look at the processors this partition can use.
COMMAND INPUT ===> /D M=CPU
Remember
- An LPAR is a logical partition: one machine, many separate computers.
- Each LPAR runs its own operating system image, often z/OS, and the users it knows about depend on that system.
- A program in one LPAR can't see or disturb another.
The usual mistake
My ID works in every LPAR.
Here each system keeps its own RACF list, and ZBPROD's list does not include ZB0001. (Some real sites share one RACF database across systems.)
Sign on to that system and check with LISTUSER. Ask for access if you need it.
On real z/OS
On real hardware, PR/SM divides the machine's processors, memory and I/O between LPARs. They are set up at the Hardware Management Console, and processors can be dedicated or shared. Operator commands such as D SYMBOLS are typed in SDSF with a leading slash, and need console authority. A signed-on user cannot switch to another LPAR with a command: you sign on to each system separately, from its own logon. In MF/OS an LPAR is a separate set of datasets, jobs, users and spool; nothing about processors or memory is shared or tuned.
Where can I practise LPAR?
Right here, at ZedBank. You take a junior job at a simulated bank and use LPAR in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- IBM ZIBM's current family of mainframe hardware, and the brand name you will see on most modern mainframe job adverts.
- z/OSThe main operating system that runs on IBM mainframes, in the same way Windows or Linux runs on a laptop or server.
- SysplexA group of mainframe systems joined together so they behave as one, sharing work and data so that no single failure stops the service.
- Address spaceAn isolated pocket of memory in which a program runs, so that one program cannot interfere with another.