Skip to main content

What is Subsystem?

What is Subsystem?

Subsystem is an operating environment, defined by subsystem description, where the system coordinates processing and resources.

These can be used to control how different jobs run on your system and how much resources are allocated to different jobs.

Here are simple examples on how subsystem can be used.


For instance – in a mostly interactive environment you may want all your batch jobs to run in a batch subsystem which has 25% of your systems memory allocated to it, while your interactive jobs run in a subsystem which has 75% of your systems memory allocated to it. In a mostly batch processing environment you may want more memory allocated to your batch jobs and less for your interactive.


If you have several customers that use your AS/400 with different agreements on how many users can access the system – you can allocate subsystems based on device IDs and you can use different subsystems to limit the number of active jobs per subsystem. So if all customer A’s workstation devices start with an A, all their interactive jobs would go to subsystem A, etc.

Each Subsystem has its own run time attribute that is used by the job to have it executed under that environment.

Subsystems would generally classify based on the Type of Jobs that are being run. Subsystem can also handle different types of Jobs.

Below are the few simple IBM Supplied Subsystems.

1. QBASE - Supports Interactive, Batch and Communication Jobs.

2. QSPL - Spool Subsystem that supports reader/writer Jobs.

3. QCTL - Controlling Subsystem that starts up the system console.

4. QINTER - Supports Interactive Jobs.

5. QBATCH - Supports Batch Jobs.

6. QCMN - Supports all communication Jobs.

How to Create Subsystem?

We can create our own subsystems to run interactive/batch jobs.

We can start or end subsystems whenever we need, without disturbing our other system jobs (Jobs running under QBATCH/QINTER/Our own Subsystem).

Basic elements needed to create subsystem.

a. Subsystem Description

b. Job Queue

c. Class Object

d. Routing Entries

Steps to Create Subsystem:

Create Subsystem Description (CRTSBSD):

        POOLS((1 *BASE))                
        TEXT('My subsystem description')

Subsystem ‘TESTSBSD’ will run in Pool ‘1’ and will use *BASE for main memory storage.

There can be maximum of 50 Jobs inside the subsystem at a time.

Create Job Queue (CRTJOBQ):


Add Job Queue Entry (ADDJOBQE):

Once the JOBQ is created, We need to attach the JOBQ to subsystem.


MAXACT denotes the number jobs that can be processed at a time under this JOBQ.

Create Class (CRTCLS):

Class defines the run time attributes like, Run priority, Time Slice, Default wait time, Maximum temporary storage etc.


Add Routing Entry (ADDRTGE):


Start Subsystem (STRSBS):


Once the Subsystem is started, it can be used to submit the jobs.

End Subsystem (ENDSBS):

Subsystem can be end by using ENDSBS command.



Popular posts from this blog

All about READ in RPGLE & Why we use it with SETLL/SETGT?

READ READ is one of the most used Opcodes in RPGLE. As the name suggests main purpose of this Opcode is to read a record from Database file. What are the different READ Opcodes? To list, Below are the five Opcodes.  READ - Read a Record READC - Read Next Changed Record READE - Read Equal Key Record READP - Read Prior Record READPE - Read Prior Equal Record We will see more about each of these later in this article. Before that, We will see a bit about SETLL/SETGT .  SETLL (Set Lower Limit) SETLL accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Corresponding Record (or Next Record if exact match isn't found).  SETGT (Set Greater Than) SETGT accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Next Record (Greater Than the Key value). Syntax: SETLL SEARCH-ARGUMENTS/KEYFIELDS FILENAME SETGT  SEARCH-ARGUMENTS/KEYFIELDS FILENAME One of the below can be passed as Search Arguments. Key Fiel

What we need to know about CHAIN (RPGLE) & How is it different from READ?

CHAIN READ & CHAIN, These are one of the most used (& useful) Opcodes by any RPG developer. These Opcodes are used to read a record from file. So, What's the difference between CHAIN & READ?   CHAIN operation retrieves a record based on the Key specified. It's more like Retrieving Random record from a Database file based on the Key fields.  READ operation reads the record currently pointed to from a Database file. There are multiple Opcodes that start with READ and all are used to read a record but with slight difference. We will see more about different Opcodes and How they are different from each other (and CHAIN) in another article. Few differences to note.  CHAIN requires Key fields to read a record where as READ would read the record currently pointed to (SETLL or SETGT are used to point a Record).  If there are multiple records with the same Key data, CHAIN would return the same record every time. READE can be used to read all the records with the specified Ke

Extract a portion of a Date/Time/Timestamp in RPGLE - IBM i

%SUBDT Extracting Year, Month, Day, Hour, Minutes, Seconds or Milli seconds of a given Date/Time/Timestamp is required most of the times.  This can be extracted easily by using %SUBDT. BIF name looks more similar to %SUBST which is used to extract a portion of string by passing from and two positions of the original string. Instead, We would need to pass a value (i.e., Date, Time or Timestamp ) and Unit (i.e., *YEARS, *MONTHS, *DAYS, *HOURS, *MINUTES, *SECONDS or *MSECONDS) to %SUBDT.  Valid unit should be passed for the type of the value passed. Below are the valid values for each type. Date - *DAYS, *MONTHS, *YEARS Time - *HOURS, *MINUTES, *SECONDS Timestamp - *DAYS, *MONTHS, *YEARS, *HOURS, *MINUTES, *SECONDS, *MSECONDS Syntax: %SUBDT(value : unit { : digits { : decpos} }) Value and Unit are the mandatory arguments.  Digits and Decimal positions are optional and can only be used with *SECONDS for Timestamp. We can either pass the full form for the unit or use the short form. Below i