The following projects have been assigned print class ranges.
| ---------- | --------------- | ------------------------------------------------ |
| ALL | 1 | Print screen contents with PA2 key |
| SAS | 9 - 10 | 9 - Print course request forms |
| 10 - Print admissions letters | ||
| FIS | 11 - 29 | 20 - Student checks |
| 24 - Data entry reports | ||
| 27 - Medical Ctr Comptroller - Data entry | ||
| 29 - Student checks All others - Receipts | ||
| FAP | 30 - 31 | 30 - One-time-checks |
| SRG | 35 - 45 | 35 - Photo ID |
| 36 - Gallup Student course schedules | ||
| 40 - Continuing Ed. course schedules | ||
| 44 - Los Alamos course schedules | ||
| 45 - Student course schedule confirmation | ||
| All others - Albuquerque course schedules | ||
| ALL | 60 | Submit batch job to JES internal reader |
| ALL | 64 | Black hole to delete unwanted reports |
Each printer defined to IDMS-DC is assigned one or more print classes. Whenever a program writes to a printer specifying a certain print class, the output will be printed on any printer that has that class assigned to it. More than one printer may be assigned the same class.
Although printers are permanently assigned their classes in the IDMS sysgen (a batch job), the classes can be changed online with a DCMT command. The change lasts only until IDMS-DC is shut down when it is brought back up, the sysgened classes are in effect again. If a dialog writes to a class that doesn't belong to any printer, the output will not be printed until that class is assigned to a printer.
If an office has more than one printer, it is sometimes required that certain terminals send their output to one printer and other terminals to other printers. To facilitate this action, a dialog named DDBA200 was written which lets the user assign terminals to a desired print class, and to change those assignments at will.
Any new or old IDMS application may make use of this dialog. Each application (FAP, SRG, etc. ) is assigned a range of print classes that it alone may use. If it tries to assign a terminal to a class outside this range, it will receive an error message.
The user first types in the application code on the empty screen of the dialog. Each application may have as many codes as it needs, depending upon how many print functions it uses. The dialog uses the code as the CALC key to obtain a PRASOWN record from the database. Next the user enters combinations of terminal ID's and class numbers on the screen. Instead of entering a terminal ID, the user may enter 'THISTERM' to assign the terminal he is logged on to. The dialog then searches for the PRTASSN record within the PRASOWN-PRTASSN set, using the terminal ID as the sort key to search on. If it finds the record, it updates it with the new class assignment. If it doesn't find it, it creates a new record.
Now it is up to the application's dialogs to include the necessary code to do the printing. Usually, the mainline dialog would obtain the PRASOWN record for what ever application it was servicing. It would issue an 'ACCEPT TERMINAL' command to see what terminal it was running on. Next it would search for the PRTASSN record within the PRASOWN-PRTASSN set. If not found, it would display a message to the user, warning that the terminal was not connected to a printer. If found, it would save the class in some variable that it would later use when it issued a 'WRITE PRINTER' command.
If you use the DDBA200 dialog to change a terminal's output class, be sure that the person signed on to that terminal leaves the application and re-enters otherwise the new assignment may not take effect until he does.
