In this case, this was the one I just did in the Mocha Windows client a few minutes ago at xx:35 (GMT timezone in the log)īelow, is a preview/display of the spool I made of those screenshots above. Check your spooled jobs to confirm/delete them and ask your instructor if he sees your stuff on the server. In the end, meaning, your print command is actually going thru to the server, it's just not showing you the "Print operation complete to the default printer device". I just realized it's not showing the "Print operation complete to the default printer device." But if you access your spooled jobs in your AS400 server, you should see what you've been trying to print and you probably have a TON of jobs/stuff you need to delete or remove. Hmm, I think it's actually working fine in Mocha, just with a minor aesthetic bug. Some googling around looks like X print (not X-Print) is a software dependency from Mozilla for some unix/debian operating systems, unless it was supposed to come bundled along with the mocha installation. }So reading from this, is it actually supposed to be printing something or updating/refreshing the terminal from what you are describing?Ĭan you check your default printer on your Win7 Desktop? These are described in the following table:Īdding +local print key to our. On unix-like systems there are a number of arguments associated with +local print key to control how the resulting postscript is generated. +local print key will cause a print screen to be sent to the default printer when the print screen key is pressed (usually Control-P). This behaviour can be changed to have the host on which tn5250 is running do the print screen by using the +local print key argument. Usually pressing the print key results in the screen being printed by the iSeries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |