Tweet
When we were connected to the AS/400 using Twin ax we used the B/36 SET procedure to change forms type of everything sent to the printer from a particular display station. After the SET procedure is run by a user, everything printed by this user from this display station would be on the new forms type. This allowed our users the option to either print on standard paper or on 4 ply just by running a menu option and typing in the correct forms type. A request to change the forms type on the printer would then be issued before the spool files from this display station are printed. Now that we are using TCP/IP, we have found that the display station ID's are assigned arbitrarily. This means that when one user changes the form type for their Display Station and then signs off, the next person who signs on and gets the same display station ID will end up issuing request to print on the changed form type. We are trying to allow our users to select a forms type without placing the option into each program.
-
-
S/36 SET procedure - Moving from Twinax to TCP/IP problems
Forms are associated with writers (Use the WRKWTR command for more info). An output queue may or may not be associated with a writer, and a job description for an individual user may be associated with an output queue. By using job descriptions, you should be able to direct the print output of an individual to a writer using particular forms. This is more cumbersome than the older SET command, but it is also more flexible. Dave
Comment