Welcome Guest | My Membership | Login

Tech Tip: Spooler Management (D3, Pick, R80 specific)


One of the most powerful commands is SP-ASSIGN for assigning the output to be printed (or managed) either currently or at a later time.

While SETPTR exists for many other MultiValue platforms, I will focus on SP-ASSIGN and its derivatives for this article. Those familiar with SETPTR can easily convert my suggestions to use on those platforms.

Most of the time the printers are created in a proc stored in the DM (or SYSPROG) account accessible by the USER-COLDSTART process. Thus, when the system is booted, the printers are created once and remain available.

I have created a regular data file called PRINTERS and a program called CREATE.PRINTERS that will replace the details within that PROC. Basically the PRINTERS file's primary key would be F0, F1, F2 and field 1 would be the network printer name, field 2 would be the serial port number, and field 3 would be the SKIP parameter.

Thus, the CREATE.PRINTERS program would SELECT the PRINTERS file and create the appropriate TCL commands for each printer with SP-KILL then DEV-MAKE


Social Media Login

Use your existing social media logins to access your Membership/Subscription information.

Existing Magazine/Newsletter Subscriber (Quick Access)

If you are an existing International Spectrum subscriber, but have not registered with the website, please enter the Reference Code found on the magazine or in the e-mails you receive from us.

Magazine Reference Code location

Spectrum Login

New Subscriber

If you currently do not receive the Magazine or other emails from International Spectrum, select the "Subscribe" button below to create an new membership account.


Find out more about the different between the FREE and a Professional Membership at:
Compare Account Options


# # #          # # #          # # #


Related Articles

  • From the Inside: July/August 2012

    Technology is making the office obsolete, but are IT and the enterprise keeping up?

  • JSON: Born for MultiValue

    Company: Precision Solutions

    Very few MultiValue systems live in isolation anymore, especially not the large ones. We are frequently being asked to exchange information with other systems. Many of us have had the "pleasure" of working with XML. While it certainly gets the job done, a new, lightweight data representation scheme is quickly gaining popularity.

  • Linux Shared Memory and Your MultiValue Database

    There are a number of different ways for programs to pass data to each other. One of the most common in the MultiValue world is using disk. (Remember the old "port" files?) Sometimes, however, this can still be a bottleneck. You might want to consider putting that data into shared memory.

  • Interview with Kelly Bleck of Precision Solutions

    Company: Precision Solutions

    New blood! Yes, folks. There is new talent coming into the MultiValue market. Whenever we are introduced to someone who has just recently joined our community, we like to have a talk with them — find out their first impressions, their thoughts on what could be improved, and what they like and don't like about our tools. Additionally, we like to hear what they think we need to do to thrive in our changing marketplace.

  • The Rock and the Hard Place: Parallel and Agile Development Part 3: Must We Choose?


    This last installment in this series on parallel and agile development methodologies explores some of the well-known Agile schools of thought and offers some suggestions for how to choose — or combine — the ones that are right for you.

Return to top