Martin -
The DIAG D4 instruction can be used to change the ORIGIN of a
file in the RDR. I pass the real ID of the user in the POWER
DIST= parameter and I send the print to a DVM where DIAGD4 is
running. DIAGD4 changes the ORIGIN to whatever is in the DIST
and then transfers the RDR to RSCS.
You can get the DIAGD4 package on my VM Download page at:
http://zvm.sru.edu/~download.
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 46 years
mailto:f...@zvm.sru.edu http://zvm.sru.edu/~fjh +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"
--------------------------------------------------------------------------
On Tue, 13 Apr 2010 13:35:15 -0400 Benedict, Martin said:
>Les,
> The problem that we have is that some of the prints come from a CMS
>users rdr. The originid is what actually gets passed. If the report came
>from the vse system to the CMS user, then the origin id is the name of
>the VSE guest, and that can't be changed that I can see. We would need
>to somehow alter the origin id in order to be able to have a valid user
>id. We need to have each print job tied to a specific person and not a
>vm guest name.
>
On Tue, 13 Apr 2010 08:08:51 -0400 Benedict, Martin said:
>All,
>
> We are converting to ELP printing. This is Enhanced Locked Printing,
>were you need to swipe a badge on the printer to login and receive your
>prints. This works fine for windows based printing. However, I am trying
>to find a way to send the vmuserid to RSCS, then onto VM/TCPIP and to
>the printer via LPR to lock down our vm prints to corporate printers.
>These reports are generally from a VM users rdr, and sometimes from 1
>or more VSE guest machines. Feel free to respond directly if need be.
>
