× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Reddy

Good point - I mistakenly used the RETURN variables for job name, user, and number as incoming parameters. Oops!

Good luck on this - there is an API that can list jobs, and only those on a JOBQ. Perhaps there is a format there to help - or in the job info API you are using.

Vern

On 5/11/2011 12:30 PM, Reddy wrote:
Vern Hamberg<vhamberg@...> writes:

Hi Dennis

I must admit to being confused by the OP - who at one point said that
the job MIGHT be still on a jobq. If that is the case, RTVJOBA does seem
to return the library lists. So that command could be used for jobs on a
JOBQ

But it sounds like the job COULD be active OR on the jobq - different
approach for each, perhaps, in which case the status of the job would
have to be determined first - easy enough. If active, the OP could use
the API for getting messages from the job log and look for the first
(only?) CPI1125 - this contains the attributes used on the SBMJOB. One
of these attributes is INLLIBL, and it is filled in with whatever was
specified. If *CURRENT or *JOBD were specified, they are expanded to the
actual libraries used.

Seems this gives the OP a good, fairly simple approach to this puzzle -
yes, a verrrrrrrrrrry eenteresting one! But NOT stupid!

Vern

On 5/11/2011 8:35 AM, Dennis wrote:
Unfortunately, until the job becomes active, the job log contains only:
..

At least at V5R3 that's so. It's an interesting puzzle!

"Vern Hamberg"<vhamberg@...> wrote:

The parameters used when the job is submitted are in one of the first
messages in the job log - if you have that log, you can work through
it.
This does include the various library list portions.

HTH
Vern
Thanks Vern, But RTVJOBA could only be used in a job that this command runs in
and only when the job becomes active. And I am trying to get INLLIBL of the
job that is still in the JOBQ. The purpose of my post was to replicate jobs in
JOBQ onto to the HA server and in case of DR. According to one of the vendors
who has this product (JOBQ*****) to replicate jobs in jobqs onto HA and DR,
was able to get the INLLIBL and *LDA info of a submitted job with the later
release of their product with one of the latest IBMi API. I am trying to find
what that IBMi API is. or if there is another means of getting to that
information.

And I verymuch appreciate your suggestions!!!
Reddy




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 by midrange.com 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.