This is a great response from Wolfgang - may I add a couple of
comments? ...
Item 11: Set the 'Initially Spooled' flag to 'N' - you don't want to
spool non-existent devices. An :OPENQ <ldev> at system
startup time (either manually entered, or in a command file
or in a SYSSTART file) will allow print jobs to be created
for any of the pseudo-classes defined for the profile.
Item 20.4: I'd do a hardware reset (RS) instead of a TC, here -
especially if you've performed a normal =SHUTDOWN of the
system.
Otherwise, this is exactly the way we accomplished the configuration,
and it works like a charm!
Lee Gunter 503-375-4498 [log in to unmask]
HMO Oregon 503-375-4401 fax
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.
______________________________ Reply Separator _________________________________
Subject: Configuring a dummy device
Author: [log in to unmask] at ~INTERNET
Date: 8/13/96 8:10 AM
> Okay,
>
> Now I feel embarrassed I need to know how to configure a dummy device as a
> printer. It seems that since we started taking manuals on CD-ROM, my boss
> decided to chuck the manuals and save bookshelf space. Well, the
> 'Configuring Terminals, Printers & Other Serial Devices' manual was left
> OFF of the CD-ROM My support specialist said that I would have to pay in
> order to get the printed manual, even though it should have been on the
> CD-ROM and even though all of the other documents on the CD-ROM refer to
> this manual. ....But that is another story. I just want to know how to
> configure a dummy device as a printer, spooled, with many device class
> names. This is for NBSpool and IP printing.
>
> TIA,
>
> Kevin "lost without my manuals" Newman
>
HOW TO CONFIGURE PSEUDO PRINTER:
********************************
CONFIGURATION OVERVIEW:
A) Create a pseudo DTC
B) Creating a profile
C) Assigning a profile to an ldev on the pseudo DTC
D) Validating the configuration in NMMGR
E) Validating the configuration in SYSGEN
F) Reboot the system
CREATE A PSEUDO DTC
*******************
Creation, modification and assignment of profiles is done using the NMMGR
utility.
1) Enter the following command in response to an MPE XL prompt:
:RUN NMMGR.PUB.SYS
or
:NMMGR
This will bring up the OPEN CONFIGURATION FILE screen.
2) OPEN CONFIGURATION FILE screen: Press OPEN FILE (f1).
NMCONFIG.PUB.SYS is the default file. Other files may
be configured but only NMCONFIG is downloaded to
DTC's.
3) MAIN menu: Press GO TO DTS (f1).
4) HOST Configuration menu: Press GO TO DTC (f1)
5) Go to DTC48 Configuration screen (f5).
As an example we are using the following criteria:
* DTC name: PSEUDO
* DTC LAN station address: 08-00-09-00-00-00
* DTC Node Name: PSEUDO.domain.organization
* Enter card types (Modem or Direct connect)
Screen Sample:
_____________________________________________________________________
NMMGR/3000 (B.04.07) #175 DTC48 Configuration Data: Y
Fill in the required information; then press the Save Data key.
Command:
To see another DTC, enter the name then press Read DTC:
DTC name: [PSEUDO ] DTC LAN station address: [08-00-09-00-00-00] (in hex)
DTC node name: [PSEUDO.DOMAIN.ORGANIZATION ]
(node.domain.organization)
DTC IP Address: [ ] (optional) Enable logging class: (Y/N)
1 Y 2 [Y] 3 [Y]
Enter card types as installed in DTC: 4 [N] 5 [N] 6 [N]
Card # Type
0 [D] (D = Direct connect
1 [D] M = Modem)
2 [D]
3 [D]
4 [D]
5 [D]
To configure a card, enter a card number then press Config Card. [0]
File: NMCONFIG.PUB.SYS
____________________________________________________________________
6) Press Save Data (f6).
7) Press Configure Card (f4).
8) Press Go To Profiles (f1).
CREATE A PROFILE
****************
9) Enter Profile name & Type (e.g. NBCLS00 and PRINTER)
10) Press Add Profile (f5).
11) Leave default information. Tab to device class fields and enter
device class(es) needed to manage the networked printer(s).
NOTE: As of 5.0 there is a limit of 450 device classes per
printer profile; with a total number of 1000 device classes
supported. However there are problems configuring this
number of device classes on the initial release of 5.0 -
approximately 1024 total combined characters of all device
classes.
Screen Sample:
________________________________________________________________
NMMGR/3000 (B.04.07) #21 Printer Profile ...
Command:
PATH: DTS.PROFILE.NBCLS00
Printer type [18] (18, 21, 22, or 26)
or printer type file name [ ]
Line speed [9600 ] (300, 1200, 2400, 4800, 9600, 19200, or 38400 bps)
Record width [132 ] (1... 2048 bytes)
Modem type [0] (0 - none, 1 - US, 2 - European)
Modem behavior [0] (0 - none, 1 - DCE, 2 - DTE, 3 - DCE high)
Parity [NONE] (None, Even, Odd, 0's, or 1's)
Initially spooled? [Y] (Y/N)
NLIO device? [N] (Y/N)
Hardware handshaking? [N] (Y/N)
If configuring device classes, enter names below. If additional names are
required, press Go To CLASSES, otherwise press Prior Screen.
Device class [PSEUDO1 ] [PSEUDO2 ] [PSEUDO3 ] [ ]
names [ ] [ ] [ ] [ ]
File: NMCONFIG.PUB.SYS
______________________________________________________________
12) Press Save Data (f6).
ASSIGNING A PROFILE TO AN LDEV ON THE PSEUDO DTC
************************************************
13) Press Prior Screen (f8) twice to get back to the DTC Direct
Card Configuration screen.
14) Enter LDEV and Profile name - (example shows ldev 600 - set up
this DTC as appropriate to your environment using unique LDEV
numbers.)
15) Press Save Data (f6).
Sample Screen
______________________________________________________________________
NMMGR/3000 (B.04.07) #27 DTC Direct Connect Card Configuration ..
Command:
DTC name PSEUDO Card number 0
Port # Ldev Profile Name
0 [600 ] [NBCLS00 ]
1 [0 ] [ ]
2 [0 ] [ ]
3 [0 ] [ ]
4 [0 ] [ ]
5 [0 ] [ ]
6 [0 ] [ ]
7 [0 ] [ ]
To configure a different card, enter its number; then press Config Card. [ ]
If you are done configuring, press Validate DTS/LINK
File: NMCONFIG.PUB.SYS
______________________________________________________________________
VALIDATING THE CONFIGURATION IN NMMGR
*************************************
16) Press Validate DTS/LINK (f5).
If you are performing the validation at a different time than when
you configured the Pseudo DTC and LDEV follow the instructions
below:
VALIDATING THE CONFIGURATION IN NMMGR ALTERNATE METHOD:
The purpose of the validation process is to ensure that the configuration is
syntactically correct and no conflicts exist within NMMGR. The prior steps
lead to the validation step 15.3 below.
16.1) MAIN menu: Press GO TO UTILITY (f2).
16.2) UTILITY menu: Press GO TO VALIDATE (f3).
16.3) VALIDATE CONFIGURATION FILE menu: Press VALIDATE DTS/LINK (f2).
The following message should appear if there are no errors detected by
NMMGR:
SEARCHING FOR SUBSYSTEM VALIDATION ROUTINE VALIDATEDTS --->
VALIDATION OF DTS/LINK STARTED. <---
---> VALIDATION OF DTS/LINK FINISHED. <---
NMMGR will now cross-validate the NMCONFIG file with SYSGEN.
SYSGEN version E.01.00 : catalog version E.01.00 TUE, MAR 28, 1995,2:12 PM
Copyright 1987 Hewlett-Packard Co. All Rights Reserved.
**note** Retrieving NMMGR configuration data...
** First level command **
io log (lo) misc (mi) spu (sp)
sysfile (sy)
basegroup (ba) keep(ke) permyes (pe) show (sh)
tape (ta)
clear (cl)(c) exit (ex)(e) help (he)(h) oclose (oc)
redo
sysgen> PERMYES ON
sysgen> SY
** SYSFILE configurator commands **
aauto (aa) aboot (ab) acmsl (ac) asprog (as)
cmsl (cm) dauto (da) dboot (db) dcmsl (dc)
dsprog (ds) lcmsl (lc) rauto (ra) rboot (rb)
rcat (rc) rcmsl (rcm) rdcc (rd) ripl (ri)
rnmlib (rn) rsprog (rs) show (sh)
clear (cl)(c) exit (ex)(e) help (he)(h) hold (ho)
sysfile> RDCC
**note** Retrieving NMMGR configuration data...
sysfile> HO
sysfile> EX
sysgen> KE
keeping to group CONFIG.SYS
Purge old configuration (yes/no)?Automatic yes
** configuration files successfully saved **
sysgen> EX
Cross-validation with SYSGEN was successful.
Copying validated configuration file to backup file, please wait ***
(PRESS RETURN WHEN DONE VIEWING SCREEN CONTENTS)
NOTE: message stating Cross-validation with SYSGEN was successful, or
ERROR messages.
17) Press RETURN.
18) Press PRIOR SCREEN (f8) until you exit the program.
VALIDATING THE CONFIGURATION IN SYSGEN
**************************************
Current versions of NMMGR cross validate in SYSGEN automatically. Here
are the steps to manually cross validate if necessary:
19) Validating the configuration in sysgen
Validating within SYSGEN provides LDEV and CLASS data to the system and also
makes sure that no conflicts exist with system configuration. For more
information on SYSGEN refer to the System Configuration Manual
(Hewlett-Packard Number 32650-90042).
Enter the following command in response to an MPE XL prompt:
MPE/XL:SYSGEN
SYSGEN> SYSFILE
SYSFILE> RDCC NMCONFIG.PUB.SYS
(if any conflicts exist, an **ERROR** will be displayed; in
this case EXIT out of SYSFILE> and SYSGEN> and correct the
configuration in SYSGEN and/or NMMGR.)
SYSFILE> HOLD
SYSFILE> EXIT
SYSGEN> KEEP
KEEPING TO GROUP CONFIG.SYS
PURGE OLD CONFIGURATION (YES/NO)?Y
** CONFIGURATION FILES SUCCESSFULLY
SAVED **
SYSGEN> EXIT
MPE/XL:
When all configuration information is both validated and cross-validated, the
system must be shutdown and restarted for the configuration changes to take
effect. For more detailed information, refer to System Startup And Shutdown
Manual (HP Part Number 32650-60004).
SYSTEM SHUTDOWN AND RESTART
***************************
20) At the console, shutdown the system as follows: (Some systems may vary
slightly in the following dialog. Consult your system startup and shutdown
manual).
20.1) Press the CTRL key and type A.
20.2) At the = prompt, enter SHUTDOWN.
20.3) A series of console messages will end with a blank line. At the
blank line, press the CTRL key and type B.
20.4) At the CM> prompt, enter TC.
20.5) Enter Y to the following prompts:
restart the system (Y/N):
Boot from the primary boot path (Y or N)?>
Interact with IPL (Y or N)?>
20.6) At the ISL> prompt, enter START NOREOVERY and respond to the date
prompt.
During bootup, the DTC is initialized. If it completes successfully,
a DCC STARTUP - OK message appears. If not, one or more DCC ERROR
messages appear. For more on DCC messages refer to Appendix A of the
MPE/iX ASYNCHRONOUS SERIAL COMMUNICATIONS manual. You may have to
reconfigure the DTC port and go through the entire process again.
The device classes are now operational as pseudo devices.
|
