QZRCSRVS

Raj:

>  Is it possible to run this QZRCSRVS (our user related) into our new subsystem ? or Can I add a routing entry based on our user profile to route all jobs related to this user profile into new subsystem ?

You can't isolate by "user" but you can isolate by client IP address or by client IP address ranges.

Since the QZRCSRVS servers require a signon from users, how could they possibly run in the correct subsystem for a user before the user even signs on? The server jobs must be running in order to accept a signon, and they will be running in some subsystem. The jobs would have to know what user is going to sign on in order to be running in the right subsystem before the signon happens. (Note that the signons can happen silently without you seeing them being done if you have things configured that way.)

However, IP addresses are known as soon as a connection request arrives. A new server job can be spawned to the appropriate subsystem according to the IP address of the socket. The signon can then be done.

Tom

Hi Gary & Tiotta
Thanks for ur valuable comments.
As the initial job QZDASOINIT is correctly running into our own subsystem (by detecting IP address) Is it possible to make use of QZDASOINIT job itself for processing (instead of QZRCSRVS) ?
If NO then how can I use of my own subsystem for our jobs only ?

Raj

Raj,

You have mapped the Database server (QZDASOINIT) to the new subsystem successfully - did you also do the same for the Remote Command (QZRCSRVS) server?

If you have already configured the Remote Command server to route to your new subsystem, and that still isn't working, and your goal is just to control where the processing load goes, then there are lots of ways to do that.  You could create your very own server job that runs anywhere you like to process requests for your PC program(s), or you could find alternate methods of executing the program than going through the database server.

Suggestion: post the relevant sections of your code and perhaps we can come up with some easy alternatives.

- Gary Patterson

Hi Gary
did you also do the same for the Remote Command (QZRCSRVS) server?  -> NO
This was configured by our administrator and it seems he hasn't configured for QZRCSRVS bcoz then in that case all other QZRCSRVS jobs (different applications) would be moved to our susbystem which we dont want.
Could you please let me know how to create our own server job that can process our request only and shud run in our subsystem ?

Raj:

It's not clear why "all other QZRCSRVS jobs (different applications) would be moved to our susbystem" if you configure for IP address just like for QZDASOINIT. Only QZRCSRVS jobs associated with that IP address should move into the other subsystem.

However --

> Is it possible to make use of QZDASOINIT job itself for processing (instead of QZRCSRVS) ?

It depends on what you're doing with QZRCSRVS.

You can certainly execute commands and call programs through the database server. But there are some things that might be easier to do by running through the command server rather than the database server.

Generally, commands are executed in the database server by calling QCMDEXC as a stored procedure, and programs are also called by calling them as stored procedures.

Now, it gets difficult to determine whether doing the work through the database server is a good idea or not.

Tom

Hi Gary & Tiotta
We have mapped the IP address range for our subsytem (not for a specific job QZDASOINIT).
Can we map the same for jobs like QZRCSRVS?

Raj:

If you are using current i5/OS and iSeries Navigator releases, you should be able to have some control over QZRCSRVS.

I'd have to review a number of combinations of past releases of both to see when various controls became available and/or what authorities are needed. They work for me back to V5R3.

Tom

Hi Tliotta
We are on V5R4. where can I find the options to control over QZRCSRVS ?

Raj

Thanks Tliotta..I'll try and let you know if it works,,