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


  • Subject: Problem with WRKOUTQ *PRINT and CPYSPLF
  • From: "Art Tostaine, Jr." <art@xxxxxxxxxxx>
  • Date: Mon, 29 Jan 2001 11:28:02 -0500
  • Importance: Normal

I'm working on a Lansa project that shows a user their spool files in
windows.

The PC application starts a batch job on the 400.  The Lansa program does a
WRKOUTQ *PRINT and then a CPYSPLF to get the WRKOUTQ results into a database
file.

The problem is that the WRKOUTQ is executed by a job called
019532/CCA/TP00000010, but the spool file is under a different job.  If I
put an option 8 next to the spool file in WRKSPLF, I get this job info:

Job  . . . . . . . . :   QPRTJOB
  User . . . . . . . :     GMAN
  Number . . . . . . :     019197

So the CPYSPLF fails.  If I run the WRKOUTQ command interactively, it works
as designed.

The server job is submitted under user profile CCA, but it's actu
We are at V4R5.

I can rewrite the App to use API's (which I may do anyway), but why doesn't
it work like this?

Art Tostaine, Jr.
CCA, Inc.
Jackson, NJ 08527

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.