Address space
A private area of memory where work runs, kept separate from the memory of other address spaces.
Also written region
Why it matters. Every signed-on user and every started task has one, and batch jobs run in one too. A mistake in one program stays out of the others.
Syntax
D A,L D J,L D A,jobname
- A
- Address spaces that are active: started tasks, TSO users and jobs that have started.
- J
- Batch jobs.
- L
- Give a list, one line for each, not only the counts.
- jobname
- Show only the named job or started task. A name can end in * to match several.
Try it D A,L
- 1
Open SDSF, the screen where you watch jobs and send operator commands.
SDSF - 2
In SDSF, see which jobs are running on the system right now.
COMMAND INPUT ===> /D A,L - 3
Now list only the batch jobs that are running.
COMMAND INPUT ===> /D J,L
Remember
- Each signed-on user and each started task has its own address space. A batch job runs in the one its initiator owns.
- A normal program can't reach into another's private memory. Some areas, such as common storage, are shared by all.
- D A,L lists what is running now.
The usual mistake
An address space is where my files are kept.
Files live on disk, in datasets. An address space is memory for running work, and its private memory is cleared when the work ends.
Datasets hold files. An address space holds a running program.
On real z/OS
Operator commands such as D A,L are typed in SDSF with a leading slash, and on a real system you need the authority for it (an SDSF operator profile and console access); many sites let developers display but not start or stop. MF/OS prints a short table of the jobs it knows. Real z/OS answers D A,L with a longer reply (message CNZ4105I from z/OS 2.3 on; IEE114I before) with counts of jobs, started tasks and TSO users, then each address space with its job, step and ASID. MF/OS doesn't model storage isolation, common storage or cross-memory access.
Where can I practise Address space?
Right here, at ZedBank. You take a junior job at a simulated bank and use Address space in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- z/OSThe main operating system that runs on IBM mainframes, in the same way Windows or Linux runs on a laptop or server.
- Started taskA long-running program that the system starts and leaves running, rather than a job that runs once and finishes.
- JobA unit of batch work submitted to the system, made up of one or more steps that run in order.
- LPARA logical partition: one physical mainframe carved into several independent virtual machines, each running its own operating system.