× 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: RE: Client/Server spool file
  • From: "Sims, Ken" <KSIMS@xxxxxxxxxxxxxxxx>
  • Date: Mon, 5 Jun 2000 13:01:28 -0400

Hi Rob -

>When Notes does it's thing, it runs under the following 
>job:  167121/QUSER/QSQSRVR.
>
>However the spool file shows up as:
>
>            File                                
>File        Nbr   Job         User        Number
>QPJOBLOG      97  QPRTJOB     RON32       167669
>BOM240        96  QPRTJOB     RON32       167669
>
>This reminds me of SNDNETSPLF.  I swear that SNDNETSPLF
>is NOT being used!

Any time a spooled report is generated for a user profile other than the
user profile of the job, it goes into a QPRTJOB with that user profile.
SNDNETSPLF is just one instance of this behaviour.

>While I think that IBM is really clever to figure out 
>the actual user id, and I should be grateful, it does 
>cause me a problem.  How do I figure out the job name 
>for this parameter in the CPYSPLF command?  I cannot 
>use * for current job because then I'll get message 

There is a PTF for this.  You create a data queue (probably in QTEMP but it
doesn't have to be).  You set a particular environment variable with the
name of the data queue.  As a result, *every* spooled file created in the
job will have an entry put in the data queue with all of the information
necessarily to be able to access that spooled file.  The PTF cover letter
has the details.

V4R4  SF61082
V4R3  SF60837
V4R2  SF61083

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.


This e-mail and any attachment contains information which is private and
confidential and is intended for the addressee only.  If you are not an
addressee you are not authorized to read, copy or use the e-mail or any
attachment.  If you have received this e-mail in error please notify the
sender by return e-mail and then destroy it.
+---
| 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 ...


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.