Enabling Subsystems

To prevent excessive processing overhead during server startup and to prevent unnecessary uses of processor resources for subsystem jobs that might be in use, you must manually start subsystems. Generally, the system administrator or manager-level user is responsible for this task. To manually start subsystems, a version of a JD Edwards EnterpriseOne batch process with a processing option set to enable the use of subsystems is run.

As described, the way that you initially control the creation and start-up of these subsystems and queues depends on the server platform.

Platform (Subsystem or Queue)	Description
IBM i (JDENET)	ERP 8: One IBM i subsystem is used for JD Edwards EnterpriseOne. This subsystem is started automatically when you issue the JD Edwards EnterpriseOne startup command STRNET. The subsystem name is version-specific. For example, for release 9.2, the subsystem name is JDEE920. To process requests that are destined for JD Edwards EnterpriseOne subsystems, you must define a specific job queue running under the JDENET subsystem. For example, a job queue might be named QBATCH. User requests for JD Edwards EnterpriseOne subsystem-defined batch jobs are executed by the job queue that is based on definition in the IBM i user profile. For EnterpriseOne 8.9 and later releases, see the note following this table.
UNIX (jdequeue)	To process requests that are destined for subsystems, you must define one or more queues. For example, a jdequeue might be named QBATCH. User requests for subsystem-defined batch jobs are executed by the job queue, based on the process ID.
NT (`jde.ini` settings)	ERP 8: One or more queues can exist for JD Edwards EnterpriseOne. These queues must have the same name. You define queues using settings in the `jde.ini` file. To process requests that are destined for subsystems, you must define the name and number of queues in the [NETWORK QUEUE SETTINGS] section of the `jde.ini` file. For example, a jdequeue might be named QBATCH. User requests for subsystem-defined batch jobs are executed by the job queue, based on the process ID. For EnterpriseOne 8.9 and later releases, see the note following this table.

Platform (Subsystem or Queue)

Description

IBM i (JDENET)

ERP 8: One IBM i subsystem is used for JD Edwards EnterpriseOne. This subsystem is started automatically when you issue the JD Edwards EnterpriseOne startup command STRNET. The subsystem name is version-specific. For example, for release 9.2, the subsystem name is JDEE920.

To process requests that are destined for JD Edwards EnterpriseOne subsystems, you must define a specific job queue running under the JDENET subsystem. For example, a job queue might be named QBATCH.

User requests for JD Edwards EnterpriseOne subsystem-defined batch jobs are executed by the job queue that is based on definition in the IBM i user profile.

For EnterpriseOne 8.9 and later releases, see the note following this table.

UNIX (jdequeue)

To process requests that are destined for subsystems, you must define one or more queues. For example, a jdequeue might be named QBATCH.

User requests for subsystem-defined batch jobs are executed by the job queue, based on the process ID.

NT (jde.ini settings)

ERP 8: One or more queues can exist for JD Edwards EnterpriseOne. These queues must have the same name. You define queues using settings in the jde.ini file.

To process requests that are destined for subsystems, you must define the name and number of queues in the [NETWORK QUEUE SETTINGS] section of the jde.ini file. For example, a jdequeue might be named QBATCH.

User requests for subsystem-defined batch jobs are executed by the job queue, based on the process ID.

For EnterpriseOne 8.9 and later releases, see the note following this table.

Note: To configure batch queues for subsystem jobs, use application P986130 (Work With Job Queues). P986130 allows you to create, modify, copy, delete, or change the status of job queues, regardless of platform. Use P986130 to change the maximum number of jobs that can run in a queue in addition to defining a default queue in which to submit jobs. Details about P986130 can be found in the System Administration Guides for Tools. The System Administration Guides are available on Oracle Technology Network. For 9.2+, the guide name has been renamed to the JD Edwards EnterpriseOne Tools Runtime Administration Guide.

System administrators can display all of the subsystems that are running on a server by using the Subsystem Jobs application (P986113). Use this application to:

Locate a list of subsystems that are running on a server.
Locate a list of subsystem records that are unprocessed (not available for IBM i servers).
Locate the current record that a subsystem is processing (not available for IBM i servers).
Stop or delete any subsystem.