O.K. I have the IP address in the RSCS LINKDEF. Is that the only way to protect the IP address from being overridden?
--- David Boyes <[EMAIL PROTECTED]> wrote: > > > Is there a way to set up a PPS EXEC for specific > printers > > with a hard coded IP address so I do not have to > hope that > > the end users enter the correct IP address when > the print with PPS? > > > > Has anyone ever encountered this situation? > > This is exactly the reason for my recent question on > unified > printing...sigh. > > In addition to the earlier suggestion of moving the > address > configuration into the RSCS link rather than > supplying it on the PPS > command, I'd suggest this: > > 1) Create a file PRINTERS NAMES on a commonly > accessed disk that looks > something like this: > > :nick.PRT300 > :exec.PPS > :tag. > :spoolto. > :parms.PRINTER PRT300 > > 2) Write a PRINT EXEC that takes the DEST parameter, > looks it up in > PRINTERS NAMES and then does the actual printing by > calling the > appropriate exec from the :exec. tag supplying the > :parms. tag as the > actual print options. Eg in your case, the users get > told to use: > > PRINT fn ft fm ( DEST PRT300 > > and the PRINT exec actually runs PPS fn ft fm ( > PRINTER PRT300. If the > printer is CP-driven, or RSCS-driven, supply the > :tag and :spoolto parms > to supply the correct information (and execute > appropriately). > > That way, your users don't know (or care) what the > right print parms > are, and you can change them later w/o having to go > chase down a zillion > execs or retrain a bunch of users. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
