Cool .... that's what I was looking for ....


-----Original Message-----
From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, March 25, 2004 2:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Profile Swapping and Spoolfile...

Hi, Ken

Use OVRPRTF and change SPLFOWN to *JOB


At 02:14 PM 3/25/2004 -0800, you wrote:
>I noticed something interesting today.
>I wrote a simple program that uses API's QSYGETPH and QWTSEP to swap to
>another users profile.
>However, whenever a spool file is created from this job after "the swap"
>ends up being associated with a QPRTJOB job instead of the interactive job
>in which it was created.
>This makes it difficult, within a program, to create a Spoolfile and then
>access it for further processing.
>For example. I have a program that creates a profile listing (DSPUSRPRF XXX
>*PRINT) and then sends the listing it to someone. The program creates the
>Spoolfile QPUSRPRF, which is then processed like this: SNDNETSPLF
>Specifying  ' * '  for  JOB .....
>Well since that the Spoolfile isn't associated with JOB(*) ... It is
>associated with that other job named QPRTJOB which was created under the
>"swapped to" user ID, the SNDNETSPLF command fails because it can't find
>I can't think of an easy way to handle this.  Has anyone written any code
>handle this situation? It would probably be code written for a server
>process that accepts incoming requests from another user and then swaps to
>that user to run....
>Any help would be greatly appreciated. thanx!
>Kenneth E. Graap
>IBM Certified Specialist
>AS/400e Professional System Administrator
>NW Natural (Gas Services)
>Phone: 503-226-4211 x5537
>FAX:    603-849-0591

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-2022 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].

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