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 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. 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.
The following documentation refers to <Install_lib> , where DataGate is currently installed on your server.
The following documentation refers to ADBTask , the example target subsystem that you want DataGate to run under.
Please modify the commands for your specific DataGate installation library and subsysyem
1) Stop the DataGate service if it is currently running:
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:
where ADBTask is an example of the new susbsystem to run DataGate withinin.
3) Remove the default DataGate job queue entries from
4) Create job queue entries in the new subsystem description:
Again, where ADBTask is an example of the new susbsystem to run DataGate withinin.
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:
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:
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):
8) Start the DataGate/400 service:
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
SBMJOBcommand 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.