DCPS V2.2 field test available

DCPS V2.2 field test available

Post by Paul Anderso » Sat, 23 Nov 2002 05:42:33



OpenVMS Engineering is pleased to announce that a field test of
DECprint Supervisor (DCPS) V2.2, called DCPS F2.2, is now available.

The major features of this release are new printer support and the
addition of autostart capability to DCPS queues.  DCPS F2.2 adds
support for the following printers:

        HP       Color LaserJet 2500, 5500
                 LaserJet 4200, 4300, 5100, 4100 MFP, 9000 MFP
        Lexmark  C750

It is likely that additional printers will be added in future V2.2
field test releases.  Anyone running the newly-supported printers or
interested in autostart DCPS queues is encouraged to install the field
test.

Please see the F2.2 Release Notes for a full list of enhancements and
bug fixes.  The SPD, Software Installation Guide, System Manager's
Guide and User's Guide have not been changed for this release, but will
be revised for a later field test release.

This kit will expire on July 1, 2003.  DCPS V2.2 is expected to ship in
Q1 2003.

If you are interested in participating in the field test, please send

Paul

--
 Paul Anderson
  OpenVMS Engineering
  Hewlett-Packard Company

 
 
 

DCPS V2.2 field test available

Post by Brian Tillma » Sun, 24 Nov 2002 01:59:35


Quote:>The major features of this release are new printer support and the
>addition of autostart capability to DCPS queues.

We've been using autostart on our DCPS queues for a while now.  It seems to
work.  Why is this a new feature?
--
Brian Tillman                   Internet: tillman_brian at si.com
Smiths Aerospace                          tillman at swdev.si.com
3290 Patterson Ave. SE, MS      Addresses modified to prevent

       This opinion doesn't represent that of my company

 
 
 

DCPS V2.2 field test available

Post by Peter LANGSTOEG » Sun, 24 Nov 2002 02:15:05



>>The major features of this release are new printer support and the
>>addition of autostart capability to DCPS queues.

>We've been using autostart on our DCPS queues for a while now.  It seems to
>work.  Why is this a new feature?

I did use it also for some years now without problems.
I understand it as it was not supported until now...

--
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist

A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

 
 
 

DCPS V2.2 field test available

Post by Paul Anderso » Sun, 24 Nov 2002 02:28:17




> We've been using autostart on our DCPS queues for a while now.  It seems to
> work.  Why is this a new feature?

Autostart was never officially supported, nor was there a way to
implement them with DCPS queues without a bit of muddling with
DCPS$STARTUP.  Now you can specify autostart nodes in the P2 parameter.

We also added a faster way of running DCPS$STARTUP that eliminates all
INITIALIZE /QUEUE commands.  It's useful for those using autostart.

Paul

--
 Paul Anderson
  OpenVMS Engineering
  Hewlett-Packard Company

 
 
 

DCPS V2.2 field test available

Post by Carl Perki » Sun, 24 Nov 2002 05:24:00



}>The major features of this release are new printer support and the
}>addition of autostart capability to DCPS queues.
}
}We've been using autostart on our DCPS queues for a while now.  It seems to
}work.  Why is this a new feature?
}--
}Brian Tillman                   Internet: tillman_brian at si.com

Did the DCPS setup make them autostart, or did you?

If it wasn't it, and it wasn't, and it does it now then it is new.

--- Carl

 
 
 

DCPS V2.2 field test available

Post by Brian Tillma » Thu, 28 Nov 2002 04:04:23


Quote:>Did the DCPS setup make them autostart, or did you?

The latter.  We simply use a command procedure containing a DEFINE_QUEUE
subroutine that looks like this:

$DEFINE_QUEUE: SUBROUTINE
$!
$ DEFINE/SYSTEM/EXECUTIVE/NOLOG DCPS$'P1'_DEVICE_NAME 'P2'
$ IF F$GETQUI("DISPLAY_QUEUE","QUEUE_PRINTER",P1) THEN EXIT
$!
$ WRITE SYS$OUTPUT "Initializing Printer Queue ''P1'"
$!
$ INIT/QUE/BASE_PRIORITY=4 /DEFAULT=(FORM=DCPS$DEFAULT)/NOENABLE_GENERIC -
   /LIBRARY=DCPS$DEVCTL /OWNER=[SYSTEM]/PROCESSOR=DCPS$SMB/START -
   /PROTECTION=(S:M,O:D,G:R,W:RS) /SCHEDULE=(NOSIZE)/SEPARATE=(FLAG) -
   /AUTOSTART_ON=(NODE1::DCPS$,NODE2::DCPS$,NODE3::DCPS$) 'P1'
$ EXIT
$!
$ ENDSUBROUTINE

Some typical calls to this would be:

$ CALL DEFINE_QUEUE 1A_HPLJ4000N_1
"""ip_rawtcp/1a_hplj4000n_1.si.com:9100"""
$ CALL DEFINE_QUEUE 1A1_HPLJ5MP_1
"""ip_rawtcp/1a1_hplj5mp_1.si.com:9100"""
$ CALL DEFINE_QUEUE 1A3_HPLJ4PL_1
"""ip_rawtcp/1a3_hplj4pl_1.si.com:9100"""
--
Brian Tillman                   Internet: tillman_brian at si.com
Smiths Aerospace                          tillman at swdev.si.com
3290 Patterson Ave. SE, MS      Addresses modified to prevent

       This opinion doesn't represent that of my company

 
 
 

DCPS V2.2 field test available

Post by Carl Perki » Thu, 28 Nov 2002 06:59:00



}>Did the DCPS setup make them autostart, or did you?
}
}The latter.  We simply use a command procedure containing a DEFINE_QUEUE
}subroutine that looks like this:
}--
}Brian Tillman                   Internet: tillman_brian at si.com

Then it wasn't in DCPS before, was it.

Thus it is a new thing in DCPS.

Therefore they announce it as a new feature.

Duh.

--- Carl

 
 
 

DCPS V2.2 field test available

Post by Brian Tillma » Fri, 29 Nov 2002 03:19:14


Quote:>Then it wasn't in DCPS before, was it.

AUTOSTART is a feature of the VMS queue manager.  It's always there.  Thus,
it WAS in DCPS before.  It just wasn't specifiable via the interface they
supplied.  That doesn't mean that now it's a new feature.
--
Brian Tillman                   Internet: tillman_brian at si.com
Smiths Aerospace                          tillman at swdev.si.com
3290 Patterson Ave. SE, MS      Addresses modified to prevent

       This opinion doesn't represent that of my company
 
 
 

DCPS V2.2 field test available

Post by Carl Perki » Fri, 29 Nov 2002 04:52:00



}>Then it wasn't in DCPS before, was it.
}
}AUTOSTART is a feature of the VMS queue manager.  It's always there.  Thus,
}it WAS in DCPS before.  It just wasn't specifiable via the interface they

No it wasn't. Nowhere in DCPS was there the ability to do this. You
could not specify autostart in DCPS (unless you add the word to the
comments, I suppose - but that isn't exactly a feature). The
only way to prove me wrong is to specify a queue to be autostart
with DCPS. Can you do that? No. That is why you had to make your
own proceedure to do it. Your proceedure is not part of DCPS.
You can tell that it isn't by the fact that you had to write
it yourself. If it was part of DCPS you would not have had to
do it yourself. Duh.

Quote:}supplied.  That doesn't mean that now it's a new feature.
}--
}Brian Tillman                   Internet: tillman_brian at si.com

In DCPS could you specify the queue to be autostart before this version?

No.

Now you can.

If something didn't use to be there and it is there now then it is
a new feature.

Nobody ever claimed it was a new feature of the VMS queue manager.
It is a new feature of DCPS. You can tell because it wasn't there
before but it is there now.

Say person X stubs his toe and is in pain. Moments later you stub
your toe and are in pain. Is your pain new? According to you, it
isn't because person X alread had stubed toe pain. This is incorrect.
Just becuase some other piece of software has some feature doesn't
mean that when DCPS gets the ability to use that feature it isn't
new - it certainly is new to DCPS. You can tell because it could't
do it before but it can now.

Since you have a proceedure of your own that does the autostart
thing, you must have wanted it to do autostart queues. So tell
me, if you had called DEC/Compaq/HP up and asked them if DCPS did
autostart queues and they had said yes it does have the feature
would you have agreed with them? When you asked them how to do this
and they said "you just write your own proceedure to do it and use
that instead of the ones we wrote" would you have agreed that this
did actually mean that DCPS did, in fact, have the autostart capability
as one of its features? I suspect not. If, however, you do think
that this means that it had that feature then I can tell you that
OpenVMS has the feature that it can run on IBM's Power4 architecture
systems - all you have to do to use this feature is to do the
programming for it yourself.

Again, if something didn't use to be there and it is there now then
it is a new feature. Any argument otherwise is just plain stupidity.
(Me spending my time explaining to you that you are being stupid
is itself stupid. Oh well.) Don't you thihnk the world has enough
stupidity in it already without your adding to it?

So are we done being stupid yet?

--- Carl

 
 
 

1. DCPS V2.1 field test available

Dear fans of DCPS,

OpenVMS Engineering is pleased to announce that a field test of DECprint
Supervisor (DCPS) V2.1, called DCPS F2.1, is now available.

The major feature of this release is new printer support, although there
are some bug fixes of interest.  The most important of these fixes
solves the problem in which some queues could not be started and a
%DCPS-F-STREAMUSE error was received.

DCPS F2.1 adds support for the following printers:

        GENICOM Intelliprint mL450
                LN45
        HP      LaserJet 2200, 4100, 9000
        IBM     InfoPrint 21, 32, 40
        Lexmark C720
                T520, T522, T620, T622
                W820
        Xerox   DocuPrint N32

It is likely that additional printers will be added in future V2.1 field
test releases.  Anyone running the newly-supported printers is
encouraged to install the field test.

This kit will expire on January 1, 2003.  DCPS V2.1 is expected to ship
in Q2 2002.

If you are interested in participating in the field test, please send

Paul

--
 Paul Anderson
  OpenVMS Engineering
  Compaq Computer Corporation

2. Client Access Performance Problem

3. field test of DECprint Supervisor (DCPS) V2.2,

4. monitors

5. field test of DECprint Supervisor (DCPS) V2.2

6. Problem with ctTabs and response dialog

7. DCPS F2.3 field test kit now available

8. deskscan II v2.5 for NT4 now available (about flipping time!)

9. DCPS V1.8 field test available

10. DCPS F2.3 field test available

11. DECdtm V2.0 for OpenVMS Field Test Announcement !!

12. Field test V5.00-1 of CXML for OpenVMS Alpha available