This article shows a way to configure a new DataGate subsystem for an existing DataGate on an IBM i installation.

This is not an end-user task and doing it incorrectly can at the least disable DataGate and at the worst disable your IBM i.

Before attempting to do this on your IBM i please perform a system backup of your current configuration and familiarize yourself with each command. If you're not familiar with changing your IBM i configuration please coordinate with your System Administrator or IBM. We strongly recommend doing this on a dedicated system with no other current users. It may also be helpful to consult your system's documentation for more information regarding subsystems and job performance. 


Step 1. Stop the DataGate service if it is currently running

Before you perform this step make sure there are no end-user DataGate jobs running on your IBM i.


Step 2. Create a new subsystem description

In the following command, parameters that most closely match the attributes of QINTER have been chosen; you may decide to use other parameters to suit the application. Here, the new subsystem description has been named ASNADG and has been placed in the installation library:

        TEXT('Datagate/400 Subsystem')

In this article, <DataGate_Library> refers to the library into which DataGate is installed and the target subsystem name is ASNADG. You can change that to the subsystem name you want.

See this article to determine what library DataGate is installed in on your system.

Step 3. Remove the default DataGate job queue entries from QINTER


Step 4. Create job queue entries in the new subsystem description

ADDJOBQE SBSD(<DataGate_Library>/ASNADG) JOBQ(<DataGate_Library>/DG8_SVC) +
         MAXACT(*NOMAX) SEQNBR(11)
ADDJOBQE SBSD(<DataGate_Library>/ASNADG) JOBQ(<DataGate_Library>/DATAGATE) +
         MAXACT(*NOMAX) SEQNBR(12) 

Step 5. Create a *CLS object

Once again, parameters like those found in the QINTER subsystem are used here. The class is given the same name as the subsystem description, and it is placed in the same library:

CRTCLS CLS(<DataGate_Library>/ASNADG) RUNPTY(20)

Step 6. Create a new routing entry

Create a routing entry in the new subsystem and attach the class created in the previous step (with the CLS parameter). The command parameters here also resemble QINTER's configuration as much as possible:


Step 7. Start the subsystem

You may also want to add this command to QSTRUP or whatever script that runs at IBM i startup (its IPL). After this has been executed, the ASNADG subsystem should show up in a WRKACTJOB display (with no jobs):

STRSBS SBSD(<DataGate_Library>/ASNADG)

Step 8. Start the DataGate for IBM i service


If the usual server jobs don't show up in a WRKACTJOB display there is a problem with the configuration. There will likely be a job log for the failed SBMJOB command used to start the DataGate server (use 'WRKSPLF DG8SVCPRF') which may indicate the problem.