Little information is available about the print job. After a job leaves a print server queue, it is removed from the queue, regardless of whether it actually prints. This could cause a print job to be lost if the printer is turned off in the middle of the print job. This is inherent in the NetWare design.

Notes about printing performance:

Many people prefer to configure their print servers in PSERVER. In early versions of NetWare, PSERVER performance was significantly better than NPRINTER/RPRINTER performance.

This performance difference is less for IntraNetWare. Actual print job throughput is affected by many other factors such as topology, job size and content, and print server settings. Under many circumstances, NPRINTER provides an excellent IntraNetWare NDS solution.

PSERVER in IntraNetWare NDS

Advantages of using PSERVER in NDS:

Does not require that PSERVER.NLM be installed on the NetWare server

Increases performance. Although overall print job throughput is affected by many factors, file transfer time on the network may be faster using PSERVER because:

In NPRINTER/RPRINTER, NetWare uses SPX to transfer packets. Packet size for data transmitted in SPX is 512 bytes.

In PSERVER, NetWare uses IPX to transfer packets. Packet size for data transmitted in IPX is up to 1 Kilobyte for Ethernet and up to 4 Kilobytes for Token-Ring networks.

Because of this difference in packet size, PSERVER may be faster than NPRINTER/ RPRINTER. Actual IPX packet size is negotiated by the client application. This actual IPX packet size is often less than the maximum because of packet size limitations of gateways and routers.

If printing is a significant part of your network traffic, and if network traffic is a proven concern for your network, you may find it better to use the print servers in PSERVER.

Disadvantage of using PSERVER in NDS:

Requires a NetWare server user license for each PSERVER device

Also, in IntraNetWare you can “pool” printers by assigning a single print queue to multiple printers, or “share” printers by assigning multiple print queues to a single printer. Be careful when configuring “pooled” printer environments because the printers need to have the same capabilities in terms of printer data stream and resources such as fonts, forms, internal memory, resolution, and so on. Though Novell recommends assigning one print queue per printer for ease of management, it may be useful to “share” a printer between multiple queues when a printer supports multiple emulations such as PostScript and PCL.

100

Argecy Computer Corporation 248-324-1800

Page 104
Image 104
IBM 1116 manual Pserver in IntraNetWare NDS, Advantages of using Pserver in NDS, Disadvantage of using Pserver in NDS

1116 specifications

The IBM 1116 is a renowned mini-computer that was introduced in the mid-1970s, symbolizing a significant leap forward in computing technology during that era. It was primarily designed for scientific and engineering applications, showcasing IBM's commitment to developing versatile and powerful computing solutions.

One of the standout features of the IBM 1116 is its ability to execute a wide range of instructions, accommodating various programming needs. The architecture of the 1116 was based on the System/360, which allowed it to leverage existing software and programming languages, such as Fortran, COBOL, and assembler. This compatibility made it easier for businesses to transition to the new system without having to develop new software from scratch.

The 1116 came equipped with a robust memory architecture, supporting up to 64 KB of core memory that could be expanded with additional memory modules. This expandability was crucial for businesses, as it allowed them to scale their computing resources in accordance with their growing computational needs. The system also featured floating-point hardware, which enabled efficient calculations required in scientific tasks, improving performance significantly for users engaged in data analysis and simulation.

In terms of I/O capabilities, the IBM 1116 supported various devices, including magnetic tapes, disk drives, and printers, which enhanced its versatility in different operational settings. Its design emphasized modularity, enabling easy upgrades and maintenance, which was a significant advantage for organizations looking to optimize their IT infrastructure.

The IBM 1116 also boasted a user-friendly operating environment. It supported multiprogramming, which allowed multiple users to run different jobs simultaneously. This capability significantly improved resource utilization and reduced downtime, making the system more efficient.

Overall, the IBM 1116 represented a perfect blend of versatility, expandability, and processing power. Its compatibility with existing software and a wide array of peripherals made it a vital asset for organizations in diverse industries. While it may seem obsolete today, the IBM 1116's influence is still felt in modern computing, showcasing the enduring legacy of IBM’s innovative designs during the mini-computer revolution. The characteristics and technologies embedded in the IBM 1116 paved the way for future advancements in computing, illustrating its historical significance in the evolution of information technology.