When a job is submitted, it is created and enters the system. At this time, the attributes are given to the job.
The job description holds attributes that the job will use to go through the work management life cycle. These attributes include the user profile the job will start to run under, the request data (which tells the job what it will do), and the initial user portion of the library list, and so on. The job description also holds information that tells the job which job queue to enter and the routing data. The routing data is later used by the subsystem to find the routing entry that contains information needed for the job to start running. The output queue is also defined within the job description. It tells where printer output (also called spooled files) from a job will go.
After the job receives its values (initialization, customization) for its job attributes, it moves to the job queue where it waits to enter the subsystem.