RE: Isolating specific QZDASOINIT jobs into a memory pool (in supportofPortal)

This method uses the source IP to determine where to go, so if you are sourcing 
from inside your own system, it may prove difficult.

This is for V5R3.  I imagine it'll work at V5R4 but haven't verified.

--------------
Information required to assign remote DB jobs to subsystems:
*       source IP address (application server's IP)
*       subnet mask  (32-bit in most cases)
*       new subsystem name  (RDB_xxxxxx for example)
*       action to take if subsystem down (allow in default sbs / reject 
connection)
*       desired memory assigned at startup if not in *BASE
*       desired threads assigned at startup if not in *BASE

For this example, we will use the following parameters:
*       source IP = 192.168.1.100
*       subnet mask = 255.255.255.255
*       new subsystem name = RDB_TEST
*       action to take if subsystem down = reject

1.      Create a subsystem description using the new subsystem name.  If not 
using the *BASE pool, you can specify a defined amount of memory and maximum 
threads assigned to the subsystem.  Max threads should equal or exceed the 
anticipated number of DB jobs (pooled objects) from the remote system.  This 
example creates a subsystem using the *BASE memory pool.
        a.      CRTSBSD SBSD(QGPL/RDB_TEST) POOLS((1 *BASE)) TEXT('Remote DB 
Connector:  Client Test')             
2.      Create a prestart job entry for the new subsystem.  You will use the 
earlier-defined subsystem name.  The PGM and CLS definitions are default system 
settings and should not be changed.  USER is the user for the client or 
connection in question.  JOB is the parameter which specifies the job name 
(QZDASOINIT when the system is at default).  MAXUSE being 1 does not allow for 
any reuse of a job.  Your mileage may vary on that parm.
        a.      ADDPJE SBSD(QGPL/RDB_TEST) PGM(QSYS/QZDASOINIT) USER(TESTUSER) 
JOB(QZ_TEST) MAXUSE(1) CLS(QSYS/QPWFSERVER)          
3.      Create an entry in iSeries Navigator which defines the source IP, 
source subnet mask, new subsystem name and action to take if the subsystem is 
down.
        a.      Click on the System Name à Network à Servers à iSeries Access
        b.      Right-click on Database and select Properties
        c.      Click the Subsystems tab and then select the radio button for 
Specific Clients
        d.      Click the Add... button and enter parms required. 
                1a.  Name it, enter remote system IP, enter mask 
(255.255.255.255 usually), enter subsystem name, select alternate action.       
             
        e.      Click OK to accept your entries.  Note, if you specify Reject 
as an alternate action, you will be prompted with a warning.  Click Yes. 
        f.      Click OK on the database properties box.
4.      To test the connection from remote system, assuming it has iSeries 
Access installed, after starting the subsystem, do the following:
        a.      Click on the System Name à Databases à System Name à Schemas
        b.      Click on "Run a SQL Script"
        c.      When the window appears, the correct DB and job name should 
appear in the bottom informational area.  You should see jobs in your subsystem.

--
Justin C. Haase - iSeries System Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation


CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.