INFO: Explanation of DataGate/400 Service Jobs

The information in this article applies to:

• DataGate/400, Release 5.0 and Higher
• AS/400

SUMMARY:

Here is information on the DataGate/400 Service jobs, such as how many there are and what they are doing.

MORE INFORMATION:

Note: DataGate/400 Jobs run as a Batch Job, but need Interactive Priority.

• Default DataGate/400 Jobs for TCP/IP:

Once DataGate/400 is installed and running, there will be Jobs running in an AS/400 Subsystem.  The default Subsystem, if none is specified during installation, is QINTER.  The jobs listed in Figure 1 are the default jobs that are required to run when DataGate/400 starts. These jobs handle all the necessary requests from clients using Acceler8DB. These jobs are defined by the JOBQE (Job Queue Entries) created during DataGate/400 installation:

Subsystem/Job	User	Type	CPU %	Function	Status
DG8SVC DG8SVC DG8SVC DG8SVC	DG8SVCPRF DG8SVCPRF DG8SVCPRF DG8SVCPRF	BCH BCH BCH BCH	.0 .0 .0 .0	CMD-DG8SVC CMD-DG8_START CMD-DG8_START CMD-DG8_START	SELW DEQW DEQW DEQW

Figure 1

The CMD-DG8_START jobs in the Function column handle new incoming DataGate/400 requests. Once the request has been fulfilled and the user job has been created (See "various jobs..." section below), the CMD-DG8_START job will end and a new one will be created in its place.  These events will be logged in the job log for the DG8SVC jobs and or Spool file for the DataGate/400 service profile.

• Various Jobs as they are needed for TCP/IP:

Once there is a successful user connection to the AS/400 through DataGate/400, there will be two more jobs that will appear (Figure 2A) in the addition to the jobs listed in Figure 1:

Subsystem/Job	User	Type	CPU %	Function	Status
DG8LICMGR DG8_43	DG8SVCPRF Your_DB_User_Profile	BCH BCH	.0 .0	CMD-DGLICMGR CMD-DG8_START	DEQW TIMW

Figure 2A

NOTE: Figure 2B below is for DataGate/400 for .NET 7.x and higher:

Subsystem/Job	User	Type	CPU %	Function	Status
DG8LICNET DG8_NET	DG8SVCPRF Your_DB_User_Profile	BCH BCH	.0 .0	CMD-DGLICMGR CMD-DG8_START	DEQW TIMW

Figure 2B

The first job that would be executed will be the DataGate/400 License Manager (DG8LICMGR or DG8LICNET).  This will verify if there are any valid available licenses.  If there are useable licenses, then the User Job (DG8_43 or DG8_NET) will be created and appear in the Subsystem.  The User Jobs will come and go when users are connecting / disconnecting to DataGate/400.  The status and CPU% will vary for the User Jobs.  The user profile for the User Job will be what the Account to User on Server appears for the Database Name on the Client PC.

After the DataGate/400 License Manager Job is established, it remains active until the DataGate/400 Server is shut down.

TIP: Once there is an User Job on the AS/400, you can use AS/400 Native Tools to work with these Jobs.  For example,  You can view the Object Locks, Open Files, JobLog.

• How Do I determine which DataGate/400 Job (configured for TCP/IP) corresponds to my Application?

Once there is a User Job (DG8_43 or DG8_NET), you can work with the User Job and view the JobLog.  Here is an example of the display of the Microsoft Transaction Server Job (mtx.exe) on the AS/400:

Note: This is a sample screen capture and is intended for instructional purposes.

Other ASNA KB Articles:

• INFO: OS/400 Installation requirements of DataGate/400
• PROBLEM: DataGate Service won’t start
• PROBLEM: An additional version of DataGate has been configured, but cannot be started.
• HOWTO: Finding out the Release Level of the product
• PROBLEM: DataGate Service starts but only one DataGate job is running
• HOWTO: Collect internal trace records of a DataGate/400 Job
• PROBLEM: DataGate Produces Large Number of Job Logs

Keywords: running, OS/400, job, "user job", client, debug, TCP/IP, router