Paul Nelson wrote:
Yuk. That won't fly. The subsystem is QSNADS. The client has a custom
version of SNDNETF, and it's higher in the library list than the one in


RQSDTA() can be used to cause a request to be processed, but it generally is superseded by whatever submits the job. It'd take some interesting programming to automate the handling of both the request data from the submitter and the RQSDTA() from the *jobd and have the RQSDTA() processed first.

Unfortunately, it seems that you can't access the programming that does the SBMJOB either? Otherwise, there shouldn't be much of a problem.

Note that SBMJOB has both a SYSLIBL() and a RTGDTA() parameter which can complicate things. You might, for example, set the SYS portion of the submitting job to remove that odd library temporarily for SYSLIBL(*CURRENT). But if you can't alter even that part of the programming, whatever you try might get overridden.

A simple routing program might be the way to go, once you determine what RTGDTA() is used, and possibly what supplies it, when the job is submitted.

What elements are reasonable for you to change?

Tom Liotta

-----Original Message-----

I think RQSDTA would get overlaid by whatever command you are submitting...
Perhaps you want to add a routing entry to your subsystem to process the

-----Original Message-----

In a job description definition, there is a RQSDTA parameter. I was under
the impression that one could use that to call a program or run a command
when a job utilizing the JOBD was submitted.

What I want to do is have a library that is in the system portion of the
library list be removed from the job's library list for the duration of the
batch job. I have no control over the CL program being submitted. It is
vendor software, and I have no access to the source.

Is this possible, or has my memory failed me?

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].