NetBase for MPE Reference Guide

Chapter 7
7-8
Using Pseudo Devices with Remote Spooling
In the previous example in the “Remote Spooling” section, we assumed that the local device
referenced was an actual device class on the local system. With NetBase remote spooling, the local
device or device class does not have to exist. Remote spooling supports the use of pseudo devices.
For example, we want all the spool files created on a device with the user’s name to be created on
the remote system:
:RUN NBDIR.PUB.NETBASE
D> DEVICE username=LP,NORWAY
There is no device class configured on the local system with the user’s name, so we can use the
following MPE syntax to implement a pseudo device:
:FILE MYREPORT;DEV=#username
:FCOPY FROM=MYFILE;TO=*MYREPORT
The pound sign (#)in front of the device is used to "fake out" MPE. When MPE sees this sign, it
assumes you are referencing a remote device and does not check to see if the device actually exists
on the local system. This allows you to set the MPE file equation for your remote spool file. Next,
since NetBase intercepts the open of the spool file, it checks to see if there is an entry in the
directory for username. When it finds one, the spool file is automatically created on the remote
system.
A NetBase Spooling Implementation Example
Let us assume that we have four systems: EENEY, MENEY, MINEY and MOE. Our print engine is MOE.
On our EENEY, MENEY and MINEY systems we would have the following directory entry to redirect
spool files to MOE.
:NBDIR.PUB.NETBASE
D> DEVICE LJ=LJ,MOE;COPY;TEMP
For each spool file destined for LJ, NetBase will create it (except $STDLISTs) on MOE. A local copy
will be created until its counterpart on MOE is complete. If the network fails during a spool file’s
creation, the process continues and builds a copy on the local system.