Re: Create an *OUTQ via Ops Nav??

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Jim, I see nothing for doing this. I've no love for OpsNav when it comes to 
configuration stuff - awfully slow - much faster to write a command that 
creates a new user based on some categories.

I recommend a command that has a name and Ip address for input, that uses a 
standard set of values for all the other parameters on the CRTDEVPRT. You 
should be able to use the PJL thing on a *LAN device class - prompt the 
command and see what you get.

I normally use OpsNav only when I have no other choice. There are a few 
things that it can do that I find helpful, but most config stuff is not in 
that camp.

BTW, the WDSC interface has the ability to create custom commands, 
promptable, that could be useful.

HTH

Vern

At 10:59 AM 3/14/2003 -0600, you wrote:
> Is there no way to create an Output Queue (CRTOUTQ)
> via Operations Navigator?
>
> We have apx. 50 HP printers using our Win2K WAN
> so we just point an outq to a specific IP address
> for our AS/400 printing purposes.
>
> We do not have devices created on the iSeries
> for each of these printers.
>
> On a whim I tried to setup a new user NOT using
> 5250 and not only did it take me about 10 minutes
> instead of about 1 on the green screen
>
> I couldn't for the life of me find a way
> to create and outq that prints to a remote printer via IP
> through ops navigator.
>
> If there is a way I would love to be enlightened.
>
> If not...so much for the proposed future death of green screen
> <grin> at least IMHO
>
> I am at V5R1
>
> Jim