HOWTO: Configuring the AS/400 to run DataGate/400 in an alternate SubSystem

The information in this article applies to

DataGate/400, All versions using TCP/IP
AS/400

SUMMARY:

The documented procedures for configuring the DataGate/400 TCP/IP server assume that the the server and its subsequent DataGate task jobs will be run in the QINTER subsystem. ASNA supports and recommends running the DataGate/400 server in QINTER, since this will offer the best performance for the majority of AS/400 configurations. However, some AS/400 configurations may achieve better performance when the DataGate server and its tasks are run in a different subsystem.

MORE INFORMATION:

Using a series of commands as outlined below, an AS/400 system administrator may create a new subsystem and configure it for running the DataGate TCP/IP server.

NOTE: Please coordinate with your System Administrator or IBM while working on the AS/400. Executing these commands is one way to configure a new DataGate subsystem on a certain AS/400 system, and is most likely NOT the optimal configuration for any given AS/400 system. Before attempting to configure your system in a similar way, please perform a system backup of your current configuration, and familiarize yourself with each command. The commands assume that DataGate has been installed into the default installation library, DG8_40.

1) Stop the service if it is currently running:

DG8_40/ENDDG8SVR

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 ADBTASK and has been placed in the installation library:

CRTSBSD SBSD(DG8_40/ADBTASK) POOLS((1 *BASE) (2 *INTERACT)) +

  TEXT('Datagate/400 Subsystem')

3) Remove the default DataGate job queue entries from QINTER:

RMVJOBQE SBSD(QINTER) JOBQ(DG8_40/DG8_SVC) RMVJOBQE SBSD(QINTER) JOBQ(DG8_40/DATAGATE)

4) Create job queue entries in the new subsystem description:

ADDJOBQE SBSD(DG8_40/ADBTASK) JOBQ(DG8_40/DG8_SVC) MAXACT(*NOMAX) + SEQNBR(11) ADDJOBQE SBSD(DG8_40/ADBTASK) JOBQ(DG8_40/DATAGATE) MAXACT(*NOMAX) + SEQNBR(12)

5) Create a "class object". Again, parameters like those found in the QINTER subsystem are used. The class is given the same name as the subsystem description, and it is placed in the same library:

CRTCLS CLS(DG8_40/ADBTASK) RUNPTY(20)

6) 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:

ADDRTGE SBSD(DG8_40/ADBTASK) SEQNBR(9999) CMPVAL(*ANY) PGM(QSYS/QCMD) + CLS(*SBSD) MAXACT(*NOMAX) POOLID(2)

7) Start the subsystem. You may also want to add this command to the QSTRUP or whatever script that runs at the end of "IPL". After this has been executed, the ADBTASK subsystem should show up in a WRKACTJOB display (with no jobs):

STRSBS SBSD(DG8_40/ADBTASK)

8) Start the DataGate/400 service:

DG8_40/STRDG8SVR

If the usual server jobs don't show up in a WRKACTJOB display, then 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.

NOTE: Please consult your system's documentation for more information regarding subsystems and job performance.

See also our DataGate /400 Installation Procedures, "Configuring DataGate/400 for TCP/IP Access" and/or "Configuring DataGate/400 for APPC Access".