Restoring the user profile is just one part of the equation... You also have
to create a directory entry for the user:


I think that when you use CRTUSRPRF this is done for you ....

Check it out and let us know ....


-----Original Message-----
From: Jones, John (US) [mailto:John.Jones@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, March 31, 2004 7:13 AM
To: Midrange Systems Technical Discussion
Subject: LPR/LPD issue: SPLFs not showing up under right ID

We're setting up LPR/LPD between our 2 AS/400s.  The idea is to have an
outq that sends files from Dev to Prod for processing into PDFs.  Both
systems are V5R1 and are current on CUMs and Group PTFs (as of

- IDs were copied from Prod to Dev via SAVSECDTA / RSTUSRPRF.
- A remote outq was created on Dev to send SPLFs to a certain outq on
- Users who previously existed on Dev before the usrprfs were copied
(i.e. the profiles were created on each machine indepent of the other)
work fine; their splfs show up under their ID on Prod.
- Users whose profiles were copied/restored from Prod have there spls
sent but they show under user QTMPLPD.  The IBM TCP reference says that
splfs will show up under QTMPLPD if the usrprf isn't found on the target
system; Prod in this case.  However, the profiles do exist.
- To make it more interesting, if we delete one of the copied users from
Dev & recreate it using CRTUSRPRF (vs. RSTUSRPRF), it works fine.

So it appears theres something in the SAVRST process for the usrprfs, or
a setting in the usrprf itself, that's prohibiting LPD from seeing the
matching usrprf on Prod.

Maybe the GID needs to be different for the usrprf on each system.  I
don't know.

John A. Jones
Americas Security Administrator
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782

This email is for the use of the intended recipient(s) only.  If you have
received this email in error, please notify the sender immediately and then
delete it.  If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission.  We have taken precautions to minimize the risk of transmitting
software viruses, but we advise you to carry out your own virus checks on
any attachment to this message.  We cannot accept liability for any loss or
damage caused by software viruses.  The information contained in this
communication may be confidential and may be subject to the attorney-client
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

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.