× 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.



You can use them in C, the headers are in QSYSINC/H.   


 |  -----Original Message-----
 |  From: Walt Fles [mailto:wfles@xxxxxxxxxxx]
 |  Sent: Friday, June 04, 2004 09:38
 |  To: Midrange Systems Technical Discussion
 |  Subject: Re: C access to a job's spooled files
 |  
 |  
 |  It looked like to me those are CL API calls, not C level, 
 |  am I right?
 |  
 |  
 |  Tom Daly wrote:
 |  
 |  >You can use QUSRJOBI to retrieve info abou tthe job and 
 |  QUSLSPL can be used
 |  >to return a list of spoolfiles for a job.  The Work 
 |  Management API book and
 |  >the Print API book will help with these.
 |  >
 |  >
 |  >Tom D.
 |  >
 |  > |  -----Original Message-----
 |  > |  From: Walt Fles [mailto:wfles@xxxxxxxxxxx]
 |  > |  Sent: Thursday, June 03, 2004 17:14
 |  > |  To: Midrange Systems Technical Discussion
 |  > |  Subject: C access to a job's spooled files
 |  > |  
 |  > |  
 |  > |  All,
 |  > |  I know if I spawn a job I can do a "Qp0wGetJobID" from 
 |  within C,
 |  > |  but can I use that information to find a job's information 
 |  > |  and also the 
 |  > |  spooled files of the job,
 |  > |  once I detect that the job has completed ( ie, via a 
 |  waitpid() ).
 |  > |  
 |  > |  I would like to have access to a spawned job's spooled 
 |  > |  files from within 
 |  > |  C, not CL, COBOL or RPG.
 |  > |  
 |  > |  
 |  > |  
 |  > |  TIA!
 |  > |  
 |  > |  
 |  > |  
 |  > |  --
 |  > |  This is the Midrange Systems Technical Discussion 
 |  > |  (MIDRANGE-L) mailing list
 |  > |  To post a message email: MIDRANGE-L@xxxxxxxxxxxx
 |  > |  To subscribe, unsubscribe, or change list options,
 |  > |  visit: http://lists.midrange.com/mailman/listinfo/midrange-l
 |  > |  or email: MIDRANGE-L-request@xxxxxxxxxxxx
 |  > |  Before posting, please take a moment to review the archives
 |  > |  at http://archive.midrange.com/midrange-l.
 |  > |  
 |  > |  
 |  >
 |  >--
 |  >This is the Midrange Systems Technical Discussion 
 |  (MIDRANGE-L) mailing list
 |  >To post a message email: MIDRANGE-L@xxxxxxxxxxxx
 |  >To subscribe, unsubscribe, or change list options,
 |  >visit: http://lists.midrange.com/mailman/listinfo/midrange-l
 |  >or email: MIDRANGE-L-request@xxxxxxxxxxxx
 |  >Before posting, please take a moment to review the archives
 |  >at http://archive.midrange.com/midrange-l.
 |  >
 |  >  
 |  >
 |  
 |  --
 |  This is the Midrange Systems Technical Discussion 
 |  (MIDRANGE-L) mailing list
 |  To post a message email: MIDRANGE-L@xxxxxxxxxxxx
 |  To subscribe, unsubscribe, or change list options,
 |  visit: http://lists.midrange.com/mailman/listinfo/midrange-l
 |  or email: MIDRANGE-L-request@xxxxxxxxxxxx
 |  Before posting, please take a moment to review the archives
 |  at http://archive.midrange.com/midrange-l.
 |  
 |  


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.