Started task
A program the system starts and leaves running, like a service that is always on.
Also written STC, started procedure
Why it matters. CICS, Db2 and the job queue are all started tasks. If one stops, the bank notices.
Syntax
S procname[.identifier][,JOBNAME=name][,keyword=value] P jobname C jobname
- procname
- The member of the procedure library to run.
- .identifier
- A name to tell two copies of the same procedure apart.
- JOBNAME=
- The job name to give the task, when it should not be the procedure name.
- SUB=
- Which subsystem starts it. JES2 is the usual one.
- keyword=value
- Fills in a symbolic parameter of the procedure.
- P (STOP)
- Asks the task to end in its own way.
- C (CANCEL)
- Ends it by force, when STOP is not answered.
Try it START
- 1
Open SDSF, the screen where you watch jobs and send operator commands.
SDSF - 2
In SDSF, start the ZedBank monitor, ZBMON, as a started task.
COMMAND INPUT ===> /START ZBMON - 3
Now stop it.
COMMAND INPUT ===> /STOP ZBMON
Remember
- A started task keeps running. A batch job runs once and ends.
- START begins one. STOP asks it to end. CANCEL is for one that won't.
- Services such as CICS and Db2 run this way.
The usual mistake
SUBMIT ZBMON
SUBMIT sends a job that runs once and ends. A started task is begun with START.
START ZBMON
On real z/OS
Operator commands such as START and STOP are typed in SDSF with a leading slash, and need console authority on a real system; many developers cannot use them. MF/OS accepts START ZBMON and says it started. No procedure is read from a procedure library and no real program runs. Real z/OS finds the procedure in the PROCLIB concatenation, and the user ID it runs under comes from the RACF STARTED class (or the started procedures table).
Where can I practise Started task?
Right here, at ZedBank. You take a junior job at a simulated bank and use Started task in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- Address spaceAn isolated pocket of memory in which a program runs, so that one program cannot interfere with another.
- SubsystemA major piece of software running under z/OS that provides a service to applications, such as a database or a transaction manager.
- JobA unit of batch work submitted to the system, made up of one or more steps that run in order.
- OperatorThe person who watches the running systems, responds to messages, and starts, stops and recovers work.
- CICS regionOne running copy of CICS, with its own programs, files and users. A site typically runs several.