An object is anything that has been created and takes up disk space. Every thing on the
system that can be stored or retrieved is represented as an object. The attribute of an object
includes its name, type, size, the date it was created, a short description provided by the person
who created the object and the name of the library in which it is stored. Each object has a name.
The object name and Object type are used to identify an object.
The subsystem is a predefined environment through which the system coordinates the
workflow and use of resource. The system can contain several subsystems, all operating
independently of each other. Subsystem shares resources. The runtime characteristics of a
subsystem are defined in an object called subsystem description.
All system storage is addressed in the same way. The user only needs to know the name of the program to run it. The AS/400 system\u2019s virtual addressing is independent of an object\u2019s physical location and type, capacity and number of disk units on the system. Main storage and disk storage appears contiguous. An object is stored and retrieved via a device-independent addressing mechanism.
A job is the basic unit of work on the AS/400.Each activity is done as a part of a job. Each
piece of work in a subsystem is called a job. Each job is an identifiable sequence of processing
actions that represent use of the system. The job description associated with each job
determines the attributes of the job.
* A user request the job.
* The job is created (job name is assigned, job attributes are allocated)
* The job is placed on a job queue
* The sub system QBATCH takes the job from job queue and starts it.
* Output generated by the batch job is placed on an output queue.
* The spool sub system prints the output on the output queue.
* A user requests a job.
* Job is created and job name, job attributes are assigned.
* Job is placed on a job queue.
* The sub system QINTER takes the job from the job queue and starts processing.
* The output generated by the interactive job is placed on the output queue
* The spool sub system QSPL prints the output.
All objects are stored on AS/400 in a single level storage. In this method all objects are referenced by one virtual address which is translated in to a physical address whether it is an auxiliary storage or main memory.
System library \u2013 15
Product library \u2013 02
Current library \u2013 01
User defined lib \u2013 25
Each piece of work run in a subsystem is called Job. A Job is a basic unit of work on
AS/400. This includes the library list, message logging level, job queue, routing data, assigned
or default printer, output priority, and user profile.
The attributes are:
Job Number Unique system generated sequential number
Job Name Any user defined name (Max 10 char)
User Name Who initiated the job.
A Job description defines an environment in which a batch job or an interactive job to be executed. It provides the initial attributes for a job. Every job has one default IBM supplied job description (Default is QDFTJOBD) (*USRPRF).
A Group Job is attached to one workstation and a user. There should be an initial group job and it can be branched to many other group jobs. The group jobs can have different library lists and different output, message queues. Group Job is useful in enhancing the programmers productivity. It is as though logging into the same user-id many times.
This action might not be possible to undo. Are you sure you want to continue?