On Wednesday, 12/14/2005 at 03:28 EST, David Boyes <[EMAIL PROTECTED]> wrote: > That would get the output delivered to spool with the right tag info, > but it assumes the system printer has already been started via CP START > to actually get it scheduled on a device. The operator would still need > to know the difference between a network printer and a channel-attached > printer and have already started the printer. > > You'd still need code in RSCS to let it actually control the > startup/stop of the CP printer itself, and (IMHO), that would need to be > a new link type, example: > > LINKDEF 01A TYPE CPPRT > LINKPARM 01A CLASS=* OPERFORM=xyzz USERFORM=xyzz CHARS=S0U1 > > and then SMSG RSCS START 01A would issue the appropriate CP commands. > Ditto for PSF printers. Then, no matter what type of printer it is, the > UI is the same.
But I think all of that can be hidden via CIM and/or SMAPI. Simply surface a list of printers, their attributes, and a start/stop button. Oh, and subscribe to the the intervention-required and queue-empty events. :-) The SMAPI will issue the right set of CP/RSCS/TCP/ESM commands to implement it. [A miracle occurs in Step 2.] The same facility can be used to define new printers. And to push on those kinds of functions, feed requirements to the IBM Director. Alan Altmark z/VM Development IBM Endicott
